Deep audits

Your main audit produces the graded report. The Deep audits row under Site Audit adds three optional, slower audits that go past the checklist. They're separate because each one costs real time and money to run, and most sites don't need all three.

Each writes its own report and saves it against that website, so you can run one now and the others later.

Choose an audit

Audit	Answers	Run it when
Technical SEO Audit	"Is anything broken at the infrastructure level?"	After a migration, a redesign, or the first time you take a site on. Also whenever the main report's Technical discipline scores below a B.
Mobile CRO Audit	"Does the mobile experience lose people who did arrive?"	The site gets traffic but doesn't convert, and most of that traffic is mobile. This is a conversion audit, not a ranking one.
AI Deep-Dive Audit	"What is wrong across the site that no single page reveals?"	You've fixed the obvious things and rankings still haven't moved. Also good before a strategy call, because the output is a prioritized argument rather than a list.

The distinction that matters most: Technical is a checklist, AI Deep-Dive is a reading. The Technical audit checks defined things and tells you pass or fail. AI Deep-Dive (the rail and the button call it the AI Deep-Dive Audit; older screens and sheets said Ultra-Think) sends a representative slice of your pages to an AI model with extended thinking on, and asks it to find problems that only appear when pages are seen together: cannibalized topics, a site structure that buries the money pages, thin clusters, an internal linking pattern that concentrates authority in the wrong place. A checklist can't see any of those, because each individual page passes.

If you only run one, run Technical first. It finds the problems that make everything else pointless.

Run a deep audit

To run a deep audit:

Open your website, then Deep audits under Site Audit. The website needs a finished SEO audit first, because deep audits save onto its latest one.
Pick the Technical SEO, Mobile CRO or AI Deep-Dive tab and select its run button, for example Run Technical SEO Audit. The button shows the price. On Mobile CRO and AI Deep-Dive, choose Pages to read above the button first. 10 pages is the default. A bigger choice reads more of the site and costs more, and the button shows the new price before you run.
Leave the page open or come back later. Each takes a few minutes, and the report saves to the website when it finishes. Re-run audit starts a fresh one.

Note that runs are per website, not per account, so auditing three client sites means three runs.

The fourth tab, Agent readiness, has no run button of its own: every SEO audit takes that score, and Check again re-reads it for free. See check your agent readiness.

Read the reports

Technical SEO Audit returns a health score and every check filed as To fix, Needs review or Passed, each failure with its fix. See run the Technical SEO audit.
Mobile CRO Audit returns a score out of 100 and a PDF built from real phone screenshots, with the problem marked on each one. See run the Mobile CRO audit.
AI Deep-Dive Audit returns a score out of 100, a mark for each of six sections, and up to 12 findings, each with a fix and a Copy fix prompt button. See run the AI Deep-Dive audit.

Each of those pages has a sample of the output.

What to do with the results

To act on any deep audit:

Open the highest-priority findings first: Critical and High, or P0 and P1 on the AI Deep-Dive.
Apply each finding's recommended fix, or send it to your developer. On the AI Deep-Dive, Copy fix prompt gives you the finding as a prompt for an AI coding tool.
When the changes are live, select Re-run audit.
Compare the new run with the last one: each report shows Compared to previous audit, and View history opens every saved run.

Limits and usage

The Technical and AI Deep-Dive audits run up to 5 minutes, and Mobile CRO up to 8 minutes. Very large sites are sampled rather than crawled exhaustively.
AI Deep-Dive reads 10 of your pages by default, or 25 if you choose, with an extended thinking model, so it takes the longest to reason. Mobile CRO checks your homepage plus 10, 25 or 50 more pages.
A run of 10 pages costs 5 credits, the same for all three audits. 25 pages costs 12 credits and 50 pages (Mobile CRO only) 23 credits. See plans and credits.
Reports are stored against the website, so re-opening one is free.

If something isn't working

The tab still says Not run after it looked like it ran. The run stopped at its time ceiling before it could save. Very large sites are the usual cause. Run it again; runs aren't resumable.

Empty or very short output. Almost always the crawler couldn't read the site: a bot block, a login wall, or a site that renders entirely in JavaScript with nothing in the HTML. Check the site loads for an anonymous visitor in a private window first.

The three audits disagree. They're measuring different things and this is expected. Technical can pass cleanly while AI Deep-Dive reports a serious structural problem, because nothing structural is a checklist failure.

For what shipped recently, see the changelog.