Deep audits: Technical, Mobile CRO and Ultra-Think

Three optional audits sit alongside your main report. What each one actually checks, and which to run when.

Open in the appUpdated 2026-07-28

What it does

Your main audit produces the graded report. The Deep Audits tab on a website adds three optional, slower audits that go past the checklist. They are separate because each one costs real time and money to run, and most sites do not need all three.

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

When to use it

AuditAnswersRun 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 does not convert, and most of that traffic is mobile. This is a conversion audit, not a ranking one.
Ultra-Think Audit"What is wrong across the site that no single page reveals?"You have fixed the obvious things and rankings still have not moved. Also good before a strategy call, because the output is a prioritised argument rather than a list.

The distinction that matters most: Technical is a checklist, Ultra-Think is a reading. The Technical audit checks defined things and tells you pass or fail. 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: cannibalised topics, a site structure that buries the money pages, thin clusters, an internal linking pattern that concentrates authority in the wrong place. A checklist cannot 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.

How to run it

  1. Open your website and go to the Deep Audits tab.
  2. Pick an audit and press its Run button.
  3. Leave the tab open or come back later. Each takes a few minutes; the report saves to the website when it finishes and appears in place of the Run button.

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

Reading the results

Technical SEO Audit returns a checklist workbook. Every row is a permanent check with a status: Pass, Fail, or No action needed. Failing checks get a per-URL tab naming the exact page and the fix. Rows never disappear between runs, so you can compare two audits row by row.

Mobile CRO Audit returns conversion findings for the mobile rendering: tap targets, above-the-fold content, form friction, and the path to the primary action. It deliberately contains no screenshots.

Ultra-Think Audit returns one prioritised fix list across four dimensions (technical, on-page, content, and authority signals), each with an estimated ranking impact. Work it top down. It is ordered by expected impact, not by how easy each fix is.

Limits and cost

  • Each audit runs up to 5 minutes and stops there. Very large sites are sampled rather than crawled exhaustively.
  • Ultra-Think is the most expensive of the three because it uses an extended thinking model over a slice of your real page content.
  • Each run consumes a usage credit.
  • Reports are stored against the website, so re-opening one is free.

When it goes wrong

"Not run for this website yet" after it looked like it ran. The run stopped at the 5 minute ceiling before it could save. Very large sites are the usual cause. Run it again; runs are not resumable.

Empty or very short output. Almost always the crawler could not 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 are measuring different things and this is expected. Technical can pass cleanly while Ultra-Think reports a serious structural problem, because nothing structural is a checklist failure.

Related

Still stuck?

Open the Support chat in the bottom-right corner. Anything it cannot answer becomes a card the team triages, and you get the reference in the reply.