Report tab

The Report tab audits your own website as an AI system sees it. Unlike the answer metrics, it needs no collection cycle: results are available as soon as an audit runs.

The three sub-tabs

Schema — structured data and page markup. Whether a machine reading your page can tell what it is about, what you sell, and who publishes it.

Technical — whether the page is readable at all: how much of the content exists without running JavaScript, page weight, language declaration, transport security.

Robots.txt — whether AI crawlers are permitted to fetch your pages in the first place.

The three are ordered by dependency, and that is the order to fix them in. Perfect structured data on a page that AI crawlers are blocked from is worth nothing; a page they can fetch but that renders empty without JavaScript is worth nearly nothing.

Running an audit

An audit is per brand and uses the brand's website. A run crawls a set of pages from the site and scores each one, then rolls the pages up into a site-level score. Larger sites take longer; progress is shown while it runs.

Results persist, so you can compare a re-run against the previous state after making changes.

Reading the results

Each audit gives you:

• A site score — the roll-up across audited pages
• A page list — every audited page with its own score
• Per-page findings — what is wrong and what to change

Work from the page list, not the site score. The site score tells you whether things are improving; individual pages are where the work is.

Findings are written to describe the page in front of them rather than a generic template — a fix that says a block is missing means it is missing on that page.

How this connects to the metrics

The audits explain the supply side of your Visibility:

Related

• Sources tab — whether your pages are actually cited
• Bots tab — whether crawlers arrive