Reading a site audit
Each completed run has a site audit: your site as machines receive it, on one page with no scripts, safe to email and to archive. Open it from the run’s page (Runs, then the run) with Open the site audit, or PDF for print. It describes your own pages as machines receive them. Your standing in AI answers is on the Overview and in Results, from the poll; the report is the audit behind your page plays.
Masthead
Section titled “Masthead”Which site, when it was analysed, how many pages were read out of how many were listed, how many templates and crawler identities probed. If the pages examined are a small fraction of those listed, read the findings as statements about templates, not about every page. See Sampling and templates.
What machines see
Section titled “What machines see”A plain account of how each class of machine experiences the site now: whether the AI crawlers were served, how much of the site’s text needs JavaScript, how well the site’s passages answer its questions, and how many findings survived review.
Machine access
Section titled “Machine access”The matrix. Rows are templates; columns are identities; a cell is pages served over pages requested. Anything short of the full count means that identity was refused, challenged or served an error.
A red AI-crawler column means that engine’s crawler cannot read the template. A red Plain HTTP column means most retrieval tools see a challenge page. A JS n% chip on a template means that share of its text exists only after JavaScript runs, which crawlers that do not execute it never see. See Machine identities.
Performance by template
Section titled “Performance by template”Lab and real-user timings per template. See Performance by template.
Live answer engines
Section titled “Live answer engines”The run’s own snapshot: its most important questions asked once of the configured engines, with whether the site was cited. It is a dated check for this report, not your Answer Share, which comes from the continuous poll over your topics.
Answer coverage
Section titled “Answer coverage”The run’s questions, put to a retrieval engine over the site’s own passages. Answered means a passage fully answers it; partial means a passage exists but is incomplete; unanswered means nothing on the site answers it. The highest-value gaps are where a page is missing. See The retrieval simulation.
Findings
Section titled “Findings”Grouped by severity. Each one names its scope (site, template or page), the pages affected, what to do, its evidence, and the knowledge-base entries it rests on with their grades. The count of candidates discarded in review is stated, so you know how much was filtered.
In the app, findings are not a separate queue. A finding about pages that matter to one of your topics becomes evidence on a page fix play; the rest are grouped by category as Foundations plays. The play’s acceptance check passes when a later run no longer finds the issue. See Plays.
What to do, in order
Section titled “What to do, in order”Ranked by impact against effort, with access blockers first, because nothing else matters while machines cannot read the page. The Plays page ranks the same work against everything else you could do, on and off the site.
Entity graph and citable claims
Section titled “Entity graph and citable claims”The things the site defines and the factual statements it makes, scored for how verifiable they are. See Entities and claims.
Method and limits
Section titled “Method and limits”What the sample covers, what a user-agent probe can and cannot prove, what the simulation is a model of, and why lab timings are indicative only. Read it before quoting a number.
The report can be downloaded as PDF from the run’s page or from the API with ?format=pdf: the same page rendered for
print, on A4. The board brief and the quarterly review are separate documents, built from Results; see
Results.