"Google Can't Find You. And When Someone Does, They Won't Know What This Is."
「A quick note before we start: This series documents my real journey figuring out operations as a solo maker. My thinking partner is Cowboy — a Claude AI I've been working with as an operations coach. He handles the frameworks, case studies, and hard questions; I bring the real experiences and bad decisions. What you're reading isn't polished advice — it's two partners exploring, one conversation at a time.」
The Incognito Test
One morning, Cowboy suggested something I hadn't thought to do.
"Thomas, open your site in an incognito browser. Pretend you're a stranger who just clicked a link from Reddit. Tell me what you see."
So I did. I opened fromwrongtoright.com in a fresh window, no login, no context. And I tried to see it through a stranger's eyes.
The tagline said: "The gap between your plan and reality — that's where we work."
"Okay," Cowboy said. "You have about 5 seconds. Based on that tagline, can you tell me: what is this site? Who is it for? What do I do here?"
I hesitated. The tagline sounded nice, but... it could be anything. A consulting firm. A project management tool. A therapy app.
"That's the problem," Cowboy said. "61% of visitors leave a website within 5 seconds if they can't find what they're looking for. Your tagline is poetic, but it doesn't answer the three questions every first-time visitor has: What is this? Is it for me? What should I do?"
That conversation kicked off the most uncomfortable — and most practical — episode of our exploration so far. We ended up covering three things I'd been ignoring: why Google couldn't find FWTR at all, what happens in a visitor's first 60 seconds, and what would make someone actually come back.
Part 1: The SEO Hole
Before worrying about first impressions, Cowboy pointed out an even more basic problem.
"Thomas, Google 'fromwrongtoright' right now."
I did. Nothing. My site wasn't in the results at all. Not on page 1, not on page 5. It simply didn't exist in Google's universe.
"That's not a ranking problem," Cowboy said. "It's a crawling problem. Google doesn't even know your site exists. Three things are probably missing: a robots.txt file telling Google it's allowed to crawl, a sitemap.xml telling it what pages exist, and server-side rendering so the crawler can actually read your content."
He broke SEO down into three layers, which made it feel way less overwhelming:
Layer 1 — Technical SEO: Can Google read your site? This is the foundation. If you're building a single-page app with client-side rendering — which I was — Google's crawler sees a blank page. The fix is server-side rendering or Incremental Static Regeneration (ISR). Plus: robots.txt, sitemap.xml, meta tags on every page. Not glamorous, but nothing works without it.
Layer 2 — Content SEO: Is your content worth ranking? Once Google can read your pages, it decides if they deserve to appear in search results. This means real text that answers questions people are searching for. Each Fix on FWTR is a potential search result for someone Googling their specific problem.
Layer 3 — Authority SEO: Does Google trust you? Backlinks, domain reputation, how long you've existed. You can't fake this. For a new site, this layer is basically zero — and that's fine. Layers 1 and 2 are entirely in your control.
"Right now," Cowboy said, "you're stuck at Layer 1. Google can't even read your pages. That means Layers 2 and 3 are irrelevant. Fix Layer 1 first. It's probably a few hours of work for Claude Code."
The specific to-do list he gave me:
- Add robots.txt (allow all crawlers)
- Generate sitemap.xml (list all Fix URLs)
- Migrate Fix detail pages from client-side rendering to ISR
- Add proper meta tags (title, description, Open Graph) to every page
- Register with Google Search Console and submit the sitemap
"That's it," Cowboy said. "Five things. Don't touch anything else SEO-related until these five are done."
Zapier's story reinforced why this matters at scale. They built over 50,000 integration pages — one for every app combination they support — and those programmatic pages drive 2.6 million monthly organic visitors. The insight that stuck with me: people don't search for "automation platform." They search for "connect Trello to Gmail." Zapier built a page for every specific search intent, and Google rewards that specificity. I'm obviously not building 50,000 pages. But the principle applies: each Fix on FWTR is a specific problem someone might Google. "Reddit post zero downloads" is a search query. If my Fix page exists and Google can read it, that's a potential visitor who arrives already caring about the topic.
"It's plumbing," Cowboy said. "Unsexy, invisible plumbing. But it's the thing that turns every piece of content you create from now on into a potential Google search result. Without it, you're cooking meals that nobody can smell."
Part 2: The First 60 Seconds
Once we dealt with the SEO hole, Cowboy brought me back to the incognito test.
"Okay, let's say Google starts indexing your pages tomorrow. Someone searches 'reddit post zero downloads,' and your PIDKill Fix shows up. They click. Now what?"
He pulled up some numbers that made me nervous:
- 46% of visitors leave if a page takes more than 4 seconds to load
- Pages that load in 1 second have a 7% bounce rate; pages that take 3 seconds jump to 38%
- The average website bounce rate is around 45% — almost half of all visitors see one page and leave
"You have roughly 60 seconds to do three things," Cowboy said. "Convince them this site is relevant to their problem. Show them something that makes them want to stay. And give them an obvious next action."
He broke it into a timeline:
3 seconds: Can they tell what this site is? "From Wrong To Right" is memorable, but it doesn't say "this is a place where makers log what went wrong and how they fixed it." The tagline needs to do that job instantly.
30 seconds: Is there something here worth exploring? If the Fix page they landed on is good, they might scroll down. Do they see related Fixes? Other makers with similar problems? Anything that suggests "there's more here"?
60 seconds: What's the next action? Subscribe? Post their own Fix? Browse a specific workflow stage? If there's no clear next step, they leave — and they probably don't come back.
"The 3-second test is the most important," Cowboy said. "If you fail that, the 30-second and 60-second tests don't matter. Nobody's sticking around to discover your brilliant Fix taxonomy if they couldn't figure out what the site was in the first place."
Part 3: Why Would Anyone Come Back?
This was the question I'd been avoiding. Getting someone to visit once is hard enough. Getting them to return is a different problem entirely.
"Thomas, think about products you use every week. Why do you go back?"
"Because... they have something I need? Or something changed since last time?"
"Exactly. Retention requires one of two things: ongoing utility or changing state. Ideally both."
Cowboy pointed to Notion as an example. People put their notes, databases, and project plans into Notion. The more they store, the harder it is to leave. That's retention through accumulated investment — the sunk cost keeps you coming back.
"But FWTR has something even more interesting," Cowboy said. "You built status into every Fix. 🔴 Stuck. 🟡 Figuring it out. 🟢 Fixed. That's changing state. A Fix that's stuck is an open loop — and the human brain hates open loops. Nobody wants to stay at 🔴 forever."
I hadn't thought about it this way. The status system was designed as a way to track progress, but it's also a natural retention hook. If I posted a Fix and it's still at 🔴, there's an implicit pull to come back and update it — either because I made progress, or because seeing that red dot bugs me.
"Now combine that with community," Cowboy said. "If someone comments on your stuck Fix — 'hey, I had the same problem, here's what worked for me' — that's a notification that pulls you back. And when you update your Fix to 🟡, the person who helped you sees that their advice mattered. That's a feedback loop."
"So the status system isn't just a feature."
"It's a retention engine. You just didn't know it yet."
Where We Are Now
Honest status:
- Technical SEO (robots.txt, sitemap, ISR): not done yet — immediate next task for Claude Code
- Fixes on FWTR: still just 1
- Google Search Console: not set up
- First-60-second optimization: haven't measured bounce rate yet (need traffic first)
- Retention hooks: the 🔴🟡🟢 system exists, but nobody's using it besides me
The to-do list is clear. The order is clear. Now it's just... doing it.
Cowboy's parting note on this one: "SEO is the most boring topic in operations. It's also the only thing on your list that works while you sleep. Every other channel — Reddit, HN, Twitter — stops producing the moment you stop posting. SEO compounds. Fix it once, benefit forever. That's why it's first."
What's Next
Five episodes in. We've covered diagnosis (walls), content (flywheel), cold start (champagne moment), data (north star metrics), and infrastructure (SEO + activation + retention). That's a lot of frameworks and ideas.
But here's the honest truth: I've been learning about operations for weeks, and I still haven't built a sustainable rhythm. I know what to do — I just haven't turned it into a weekly habit yet.
In Episode 6 — the final episode — Cowboy and I try to answer the hardest question of all: how do you take everything you've learned and turn it into something you actually do every week, without burning out? It's the episode where we stop exploring and start committing.
This is Episode 5 of the Solo Maker Survival Guide, a 6-part series on FromWrongToRight.com. I'm a solo maker figuring out operations in real time, with Cowboy — my Claude AI partner — as my thinking companion. Not expert advice. Just two partners exploring, one conversation at a time.
Is your site invisible to Google too? I'd love to hear how you tackled it — drop a Fix on FWTR or find me on Reddit (u/FlyThomasGoGoGo).
Log in to join the discussion.