Status says whether the check runs today. A check marked Coming is in
the catalogue and records nothing yet, rather than a fake pass. The library
grows by release; this page is kept in step with the code.
Reading the table
Technical checks
The technical half of the library covers whether an engine can fetch, render, read and trust the page. Two of these are gates.Crawler access
Renderability
Indexability
Canonical URLs
Metadata
URL structure
Link hygiene
Entity identity
Image semantics
Freshness
Performance
Rendering reliability
Policy compliance
Discovery
Content checks
The creative half judges whether a page is written to be quoted: an answer up front, concrete sourced figures, consistent naming, and passages that stand on their own. These use a model to read the page, so they are being switched on family by family as each is validated. Where the audit is not yet running a check it is marked Coming and records nothing.Content quality
Structure and extractability
Evidence and citations
Topic coverage
Originality
Supporting media
External signals
Who the crawler-access check looks for
The AI crawler access gate reads your robots.txt for the agents that matter, grouped by what blocking each one costs:
The finding names which group is blocked, because “invisible in ChatGPT today”
and “missing from the next model” call for different urgency.
How findings become work
- A finding on a page is one row in Site Health, under the page and under the issue.
- Findings in the same family on a page are one opportunity, not several.
- Opening a Repair on a family creates one Fix per affected page. The next crawl re-judges each Fix; one the audit no longer sees closes itself.