A tool I reviewed audited my own site and found a bug I'd missed
Started Solo Stack Lab a couple weeks ago — reviews of AI/SEO/automation tools for solo people running content or affiliate sites. Built mostly with Claude Code (an AI coding agent). Rule: sign up and actually use the tool before writing about it.
Ran Frase (one of the tools I reviewed) against my own site. It flagged zero og:image tags, site-wide — every link I'd ever shared had no preview image. I'd written "social previews done" in my notes days earlier. Wrong. Fixed same day, put it in the review instead of quietly patching it.
Other stuff from the first couple weeks, no particular order: Surfer SEO's "start for free" button charges $59/mo immediately, no free tier. Make logged "success" on an automation while an email silently never sent because of an OAuth scope thing. n8n rejected my affiliate application with zero explanation, while three other programs approved same day.
Current traffic per GSC: 19 impressions, 0 clicks, average position 36, three months. Early.
Anyone done the early-content-site thing — did backlinks or more content move the needle first for you?
The part about writing “social previews done” in your notes and then discovering they were completely broken is painfully relatable. 😅
I think that's also why actually using a tool before reviewing it is such a good rule. A feature can look perfect on paper while something completely different breaks once it touches a real workflow.
And honestly, 19 impressions / 0 clicks after only a couple of weeks doesn't sound particularly worrying to me. I'd probably prioritize publishing consistently first, then use GSC to see which pages/queries start getting impressions before going hard on backlinks.
Curious to see how the traffic changes once you've got a bigger sample size.
The "og:image done" → "actually zero tags" gap is pure measurement clarity in action. Your notes were a mental model. The tool was reality.
Most founders never run this kind of audit because it's easier to trust our own annotations. But what you're doing here is outsourcing verification to something that doesn't know how to lie - it just counts what exists.
That 19 impressions / 0 clicks is interesting because it actually tells you something specific: you're getting search visibility but the click-through is catastrophic. Most people would blame "position 36" and build more content. But your stack audit already found a concrete friction point (og:image, and presumably those "success" logging failures).
The measurement system determines what you can see. You built one that surfaces friction instead of just celebrating views.
The “I already marked this as done” part is the most interesting to me. It shows how easily our own notes become assumptions instead of evidence. Automated audits are valuable not just because they find bugs, but because they challenge what we think we've already verified. Curious whether you'll start treating these audits as a recurring pre-publish check.
The strongest part is the willingness to let the product audit the founder’s own assumptions. That makes the “review” model more credible because the process is producing findings, not just content about tools.