Built with AI. Should still show up in search.
You don't need to have read a single SEO blog post. The rubric reads your site and reports what is wrong in language you can act on.
Vibe coders and solo builders
You shipped something real in a weekend. The parts a crawler needs got skipped.
Cursor, Claude Code, v0, Bolt, Lovable: whatever built it, speed came from not stopping to write metadata. The site works perfectly in your browser and arrives at a crawler as an empty div with a placeholder title.
What this usually looks like
- Organic traffic that never started, rather than traffic that fell
- Pages that render client-side and ship no content in their HTML
- An empty
on every route - No sitemap, no canonical tags, no llms.txt
Why this fits: You are technical enough to merge a pull request and uninterested in becoming an SEO. The fix queue is a to-do list where every item shows exactly what it changes.
Content teams publishing at scale
The risk is not quality. It is your own posts competing with each other.
When you publish a lot, with or without AI drafting, the failure mode is cannibalization: four posts targeting one intent, splitting the signal between them, none of them winning. It is invisible from inside the CMS because each post looks fine on its own.
What this usually looks like
- Several posts ranking weakly for the same query instead of one ranking well
- Rankings that move sideways when you publish more
- No shared view of which intents you have already covered
- Titles converging on the same shape without anyone deciding they should
Why this fits: Site memory tracks what your corpus already covers, and overlap is flagged before you publish rather than diagnosed six months later.
Agencies and consultants
Audit-to-merge as a repeatable deliverable, not a bespoke project each time.
The work is the same shape for every client and gets rebuilt from scratch every time. What makes it hard to package is the gap between the audit, which is easy to produce, and the remediation, which is where the hours actually go.
What this usually looks like
- A retainer where the audit is the deliverable and the client does the work
- Reports that cannot honestly distinguish "we checked this" from "we could not"
- Competitor monitoring done by hand, or not at all
- No defensible way to show a client that last quarter moved anything
Why this fits: The unmeasured state alone changes what you can put in a client report, because you stop having to present a gap as a pass.
Who it is not for
Teams who want a fully autonomous agent with no review step. The loop stops twice and asks, and that is a design decision rather than a missing feature. If the value you are buying is "nobody has to look at it", this is the wrong tool and the gates will feel like an obstacle for as long as you use it.
It is also a poor fit for a site with a handful of pages and no publishing cadence. Most of what the rubric catches (crawl waste, cannibalization, coverage gaps) needs enough surface area to be worth automating. A five-page site is an afternoon of manual work, and the free scan will tell you that for nothing.