What is real, and what is not.
A product built on refusing to round unmeasured up to a pass cannot be vague about its own state. So here is the ledger.
Shipped Available now
- The free public scorecard, end to end: real crawl, real rubric, honest failure when the engine is down
- The 129-check catalogue with its eight weighted categories
- Per-check method declaration: rule, graph, third-party API, or model judgement
- Per-check fix capability: Auto, Assist, Human
- Coverage reporting on every score
- Competitor monitoring, weekly, with published politeness limits
- Core Web Vitals: LCP, INP and CLS
Not shipped Not built yet
Described on this site, in some cases in detail, because the design is real and worth explaining. Not available to you today, and every page that describes one says so on the page.
- The access ladder: modes A to E. Designed, and present in the codebase only as static demo reference data
- Every platform connector: WordPress, Webflow, Shopify, Ghost, HubSpot, Notion and the rest
- Pull-request delivery, CMS draft writing, and anything labelled build-verified in practice
- Outbound webhooks
- A documented authenticated API
- Actionable Insights in competitor monitoring
- Data export and downloadable reports
- FCP, TBT, Speed Index and an accessibility score
- A per-check browsable reference. One indexable page for each of the 129
- Any public status or uptime reporting
Things we will not claim
- Per-article citation lift. Citation share is recorded per prompt and per engine, with no link back to the specific article that earned it. Claims of the form "posts with X are cited 41% more" are not something this data supports, so you will not find one here.
- Build-verified on a hosted CMS. There is no build to run. That badge appears only where a repository is held or mirrored.
- A ranking outcome. Nobody can promise one.
- Certification. No SOC 2, no ISO 27001, no penetration-test report, no uptime guarantee.
Where content goes
Some checks are model-judged, and running them sends content from the pages you scan to a large-language-model provider. We do not train models on it and do not resell it, but it does leave our infrastructure, and that is worth stating on its own rather than in a sub-processor footnote. The privacy page covers it in full.
A correction we had to make
The public scan endpoint once wrote a finished result the moment it was called (a grade, a score, canned category rows) and returned "queued". Nothing was ever fetched, for any URL, and the fabricated result was publicly shareable. It now either runs on the real engine or reports honestly that scanning is unavailable.
It is on this page because a company that claims honest measurement should publish the time it failed at exactly that, not just the policy that followed.