How it works, and where it stops.
API access is on the Scale plan. Onboarding is by hand today, so the fastest way to get keys is to ask.
What an audit gives you
One crawl answers two questions. Whether a search engine can rank the page, and whether an answer engine can read and cite it. They are separate verdicts because a page can pass one and fail the other.
- 73 SEO checks, each one telling you what it read and where
- 39 citability checks, read from the bytes your site served
- Every finding names the check it came from, and every check has a page in the catalogue
- Dismiss a finding once and the next audit does not reopen it
Why your report may be short
Some failures make every other finding meaningless, so we report the cause and hold the symptoms. If your page renders empty without JavaScript, its structured data is not missing, it is unreachable. Listing thirty schema problems underneath that would bury the one fact you need.
The same goes for a blocked crawler. If your robots file shuts out the crawler an engine uses, nothing about your content matters to that engine, because it never reached the content. A short accurate report beats a long report about a page nothing could read, so we would rather hand you three findings that are true than forty that are noise.
Claim states
Claims move through three states and the transitions are enforced in code, not by convention. A claim cannot skip from unproven to verified, and cannot reach verified without a source.
- unproven
Derived from the site, with no external evidence. Reading a website is not proof the website is honest.
- asserted
Evidence attached. Shippable.
- verified
A source that stands up. Shippable, and the only state a claim cannot reach without one.
Public endpoints
Two endpoints need no authentication. Both are rate limited at the edge. The free audit writes nothing, so a stranger typing a domain into it creates no record against that domain.
| Method | Path | What it does |
|---|---|---|
| GET | /api/v1/seo/catalogue | Returns the check catalogue behind this site |
| POST | /api/v1/aeo/free-audit | Runs a single URL answer engine audit and stores nothing |
What we leave to other tools
If you need any of these, ask before planning around them.
- other tools
A public SDK. The REST endpoints above are the supported way in
- other tools
Vector or semantic search across your findings
Need API access.
Tell us what you want to build against it. We will say plainly whether the endpoints you need exist today, and if they do not, that they do not.