Crawld for small technical teams
Technical enough to merge a pull request, uninterested in becoming an SEO.
One of the three audiences this was designed for. The others are on the solutions index.
The situation
You shipped something real and fast. The parts a crawler needs got skipped, because they are invisible in a browser and nothing told you they were missing.
Which findings dominate here
The product is the same product for every segment: one rubric, 129 checks, the same three outcomes. What changes is which findings do the damage.
Client-side rendering
The most common finding on sites built with AI tooling. Your page works perfectly in a browser and arrives at an answer-engine crawler as an empty div.
Missing metadata
Empty descriptions, placeholder titles, no canonical tags: the scaffolding defaults nobody went back to fill in.
Machine-readable structure
Sitemaps, llms.txt, structured data that matches what the page actually contains.
What the loop looks like
Scan, read the ranked list, fix the top few yourself in an afternoon. Most of what dominates here is Auto-capability work. One correct answer, no judgement required.
Where this is a poor fit
If you want the fixes to arrive as a pull request rather than as a list you action yourself, that is the delivery model the product is designed around and it is not built yet.