Chudi.dev is my own technical property, built from a near-zero organic footprint. I own every decision in it, which makes it the one site where I can show the architecture and the search data side by side.
Goal
Build an authoritative technical web property that earns visibility in conventional search while staying machine-readable for AI retrieval, and instrument it well enough to tell which changes moved anything.
Process
Built on SvelteKit with a content pipeline, prerendered JSON-LD structured data, generated sitemaps, IndexNow submission on publish, internal-link architecture built around search intent, and machine-readable surfaces for agent retrieval. Search Console wired in as the feedback loop rather than a vanity dashboard.
Result
Google Search Console, Performance report, property https://chudi.dev/. Custom range 19 February to 16 August 2026, read 19 August 2026. The tiles round: 3.09K clicks and 1.1 percent CTR where the API returns 3,087 and 1.07 percent.
289,416 impressions and 3,087 clicks at an average position of 8.2 over the six months from 19 February to 16 August 2026, with impressions rising from a near-flat baseline in February. Click-through sits at 1.07%, consistent with a footprint weighted toward long-tail informational queries. Figures pulled from the Search Console API, not read off the dashboard.
What I take from it
Position 8.2 across that volume is the interesting figure, not the impression count. It means the site is being surfaced broadly at page-one-adjacent depth, which is exactly the position where technical and structural work still moves the number.
Six months of Search Console data for chudi.dev: 289,416 impressions and 3,087 clicks at position 8.2, on architecture I built and instrumented myself.