Roadmap
What has shipped, and what is next
Nothing appears under Shipped that you cannot go and use right now. Nothing under Next or Considering carries a date, because a date on unbuilt work is a guess wearing the clothes of a commitment — and the only ways to keep one are to miss it or to build the wrong thing on time.
Shipped
Live on the site today. Every entry here is usable without an account unless it says otherwise.
Readable report URLs and any-format addresses
Scan URLs now name the site they audited. The scan box accepts a bare domain — example.com, with or without www or a scheme — instead of demanding a full absolute URL.
Page captures on every scan, including quick scans
A screenshot returns with the report as evidence of exactly what was measured, on both scan depths. Captures are held under the same expiry as the report and are never written to disk.
Per-account scan allowances
Individual accounts can be granted higher limits or unlimited scanning, rather than everyone sharing one tier.
Live badges, certificates and verified profiles
Prove a domain you own and publish a live score badge, a downloadable quality certificate, and a public report page at /site/your-domain. The badge refuses to render below its threshold, which is the only reason a badge is worth anything.
Score history and trend lines
Scores are kept per URL so a report can show movement over time. The reports themselves are never stored, so a trend costs a few hundred bytes per scan rather than a megabyte.
AI visibility as a first-class module
Crawler access resolved per user-agent token, answer-engine extractability, and agent operability — three separate capabilities rather than one score, because a site routinely passes one and fails the others.
The 986-rule engine across 11 modules
Every rule carries a confidence tier, a citable reference and a last-reviewed date. Roughly two thirds are informational and excluded from the score, so breadth never dilutes what the number means.
Next
Being built, in roughly this order. These turn a scan you run into something that keeps watching.
Scheduled monitoring and alerts
Re-run a scan on a schedule and be told when a score moves or a specific finding appears. The most common request, and the one that turns an audit you remember to run into a thing that watches for you.
A public API
The same engine behind an authenticated endpoint, returning the report structure the site already renders, so results can go wherever you keep the rest of your data.
CI integration
Fail a build when a score drops below a threshold or a chosen rule regresses. Catching an accessibility regression in review is worth considerably more than catching it in an audit three months later.
Considering
Wanted by enough people to be worth naming, not yet committed to. If one of these is the thing standing between you and using this properly, say so — it moves the order.
Team accounts
Shared site lists and history for agencies and in-house teams managing more than one property.
Compliance-shaped reporting
Accessibility findings mapped to WCAG success criteria in the form an audit trail expects, rather than in ours.
Competitive comparison
Your score beside three named competitors on the same rules, on the same day.
This page is maintained by hand and updated when something actually ships. If an entry here no longer matches what the product does, that is a bug worth reporting.
Audit your site in 40 seconds
986 deterministic rules across eleven modules. Every finding comes with evidence, a citation and a fix preview.
Run a free scanNo signup. No credit card. Nothing stored but the result.