Nobody Can Find What You Build If You Don't Make It Discoverable
Why Good Work Still Doesn't Get Found
Cristian Lascu
April 02, 2026
Last week I shared the Building Loop, the three-phase system I use for everything I ship. This week I used it on something most builders never think about: making their work findable.
Because here's the uncomfortable truth that nobody in the "build in public" space talks about honestly: you can build the best product in the world, and if your prospected clients can't find it, it might as well not exist.
The Discovery Problem
Over the past six weeks, I've shipped three free tools for this community: the Visibility Audit, the Business Model Canvas, and the Building Loop One-Pager. I've written six newsletter issues. I've built over 100 topic pages on the website.
And until last week, most of it was invisible to search engines.
This happened mostly because the technical foundation underneath it was broken. Pages that should have been indexed weren't. Metadata that search engines need to understand and rank your content was missing or malformed. The sitemap, literally the map that tells Google what exists on your site, was missing over 100 pages.
I knew this intellectually. I'd been meaning to "fix SEO" for weeks. But I kept prioritizing content over infrastructure, which is the equivalent of writing books and storing them in a warehouse with no address.
What I Found When I Actually Looked
I ran a full technical audit on thesovereigntechnologist.com. The results were humbling:
246 pages had canonical redirect issues, meaning Google was potentially seeing two versions of every page.
112 pages were completely absent from the sitemap. Google didn't know they existed.
114 pages were missing Open Graph tags, broken preview cards on LinkedIn and X.
93 pages had no meta description, Google was guessing at what to show in search results.
4 pages were stuck in "crawled but not indexed" limbo.
Every one of these is a fixable technical issue. None of them require better writing or different content. They require the kind of systematic infrastructure work that technologists are actually good at, if they know to do it.
How I Fixed It (Using the Building Loop)
I applied the same Shape → Validate → Ship cycle to this problem:
Shape. I scoped the work to a single sprint. I created a technical specification that listed every issue, its priority, and the exact code fix needed. Fourteen issues, ordered by impact.
Validate. Before touching any code, I validated which fixes would have the most impact. HTTPS canonical redirects and sitemap completeness were the clear winners as they affected hundreds of pages each. Missing alt text on four images? Important but not urgent. The validation step prevented me from spending a Saturday on low-impact tweaks while the foundations were crumbling.
Ship. I executed the fixes over five days and shipped them all in a single deployment. Then I submitted the updated sitemap to both Google and Bing, triggered IndexNow submissions for all pages, and used Google Search Console to request re-indexing of the stuck pages.
The Results So Far
It's been one week since the fixes went live. Here's what's changed:
Google indexed pages increased by nearly 100%. Pages that were invisible are now showing up in search results.
I got my first impression in Bing, which might sound trivial, but Bing's IndexNow protocol is notoriously difficult to get right. Cracking it means every future page I publish gets submitted to Bing automatically within hours. And that's a bigger win than it sounds as Bing feeds directly into AI-powered search and assistants. Being indexed there means your content has a chance of being surfaced by generative AI, not just traditional search.
The sitemap now includes every page on the site. No more orphan content sitting in the dark.
These are early signals that SEO compounds over weeks and months. But the trajectory is clear: the infrastructure now supports the content, instead of undermining it.
Why This Matters for Your Side Project
I'm sharing this level of detail for a specific reason: most technologists who build side projects never do this work.
They build the product. They might write a blog post or two. They share it on Twitter and Reddit. And then they wonder why organic traffic never arrives.
The reason is almost always the same: the technical SEO foundation is broken or non-existent. No sitemap. No meta descriptions. No canonical tags. No structured data. The content is there, but search engines can't properly read, categorize, or rank it.
And the ironic part? This is infrastructure work. It's the kind of systematic, detail-oriented engineering that technologists do professionally every day. You'd never ship an API without monitoring and observability. But most of us ship websites without the equivalent: the metadata, structure, and signals that make our content observable to search engines.
If you've built something and you're wondering why nobody's finding it, before you write another blog post or buy ads, run a technical SEO audit. You might be surprised by what you find, and how fixable it is.
The One-Pager (From Last Week)
If you missed it, the Building Loop One-Pager is the system I used to scope and execute this entire SEO sprint. Three phases, fifteen questions, one A4 page.
The One Thing
Discoverability is infrastructure, not marketing. Treat it like you'd treat monitoring for an API and built into the foundation from the start.
You wouldn't deploy a service without health checks. Don't deploy a website without SEO fundamentals.
What I'm Building This Week
This week I'm monitoring the SEO results and letting the indexing compound. On the product side, I'm exploring what a lightweight validation framework could look like something that helps you test your side project idea in a weekend before committing your sovereign hours to building it. Still shaping. If you have thoughts on what that should include, hit reply.
What resonated? What did I get wrong? Hit reply: I read everything and I'm building this with you and with your input.
P.S. The toolkit: Visibility Audit (where you stand) → Business Model Canvas (is your idea viable) → Building Loop (how to execute). All free, all designed for builders with limited time.
P.P.S. Know a technologist who built something great but nobody can find it? Forward this email. They can subscribe at thesovereigntechnologist.com.
That’s all for this week.
See you next Thursday.
