Overview
The AI Deep-Dive Audit reads a sample of your pages together, the way a consultant would, and looks for problems that only show up across pages: two pages competing for one topic, a service with no page of its own, business details that disagree from page to page. A checklist audit can miss these because each page passes on its own.
You get a score out of 100 with a letter grade, a mark for each of six sections, and up to 12 findings, each with its fix.
When to use this
Run it once the Technical SEO audit is clean and rankings have not moved, or before a strategy call.
How it works
- It picks the pages. It reads your sitemap (up to 2,000 addresses) or, when there is none, your homepage's links. It starts with the homepage, then takes one page per template and spreads the rest across your site's sections, so no one section fills more than a third of the sample. That is 10 pages by default, or 25 if you choose.
- It reads each page. It takes the title, H1, meta description, the first 8 headings, the canonical tag, robots directives, contact details, and about 700 characters of body text. Pages that need JavaScript are rendered during the first 45 seconds of reading.
- It reads what you already know. Findings from this website's other audits and its previous AI Deep-Dive are passed in, so earlier findings are re-checked.
- One AI model with extended thinking writes the findings. Then the code checks them. A finding labelled Confirmed must name a page that was read and quote what it saw there; anything else becomes Needs verification. Invented measurements and promised outcomes are removed.
If the site refuses the crawler, the audit runs on public data instead (Google PageSpeed Insights, the Chrome UX Report, and what Google shows for the site), lists the checks it could not do, and gives no score. The run's summary says whether any credits were used.
Steps
To run an AI Deep-Dive audit:
- Open your website, then Deep Audits under Site Audit, and pick the AI Deep-Dive tab. It needs a finished SEO audit first.
- Under Pages to read, choose 10 pages or 25 pages. The run button shows the price of your choice.
- Select Run AI Deep-Dive Audit. A run usually takes 2 to 4 minutes and stops at 5.
- The report saves to the tab when it finishes. Re-run audit starts a fresh one.
Understand the results
The score. Each of the six sections starts at 100. Every Confirmed finding in a section takes off points by priority: P0 Critical 40, P1 High 25, P2 Medium 15, P3 Low 5, down to 0. The overall score is the average of the six, and the grade runs A+ (97 and up), A (90), B (80), C (70), D (60), F. Opportunities, Needs verification and Informational findings never cost points, so 100 means nothing was confirmed wrong on the pages read, not that the site is perfect.
The six sections are Semantic coverage, Extractability, Answerability, Crawlability, Authority signals and Schema. Score by section shows each mark, what cost the points, and the findings behind it.
The findings sit in tabs: Confirmed, Opportunities, Needs verification, Informational and Fixed. Open one for the recommended fix (copy or code to paste), steps, affected pages, why it matters, and how to verify it.
Export downloads a PDF report, Excel data or a CSV. Open full report opens a Google Sheet.
Sample output
This is an example on a made-up website, not a real report:
AI Deep-Dive score: 82/100 (B), from 10 pages read
Semantic coverage 75 1 confirmed finding (P1) took off 25.
Extractability 85 1 confirmed finding (P2) took off 15.
Answerability 100 Nothing confirmed wrong on the 10 pages read.
Crawlability 60 1 confirmed finding (P0) took off 40.
Authority signals 95 1 confirmed finding (P3) took off 5.
Schema 75 1 confirmed finding (P1) took off 25.
Remove the noindex tag from the Services page
P0 Critical · Confirmed · Technical Readiness · 1 page
/services/ carries <meta name="robots" content="noindex, follow">.
Recommended fix: delete the tag, or set it to "index, follow".
Affected pages (1): /services/
Why it matters: the tag tells Google not to show the page in results.
How to verify the fix: URL Inspection in Search Console reports
indexing allowed for /services/.
What to do with the results
To work through an AI Deep-Dive:
- Open the Confirmed tab and start at the top, P0 Critical first. Top priorities shows the first five confirmed findings and opportunities.
- Open the finding and apply its recommended fix, or select Copy fix prompt (free) and paste it into your AI coding tool or send it to your developer. Each section in Score by section has a prompt for all of its findings at once.
- Or select Write the fix with AI (1 credit). It reads the page as it is now and writes the code or copy to paste: the HTML, the JSON-LD block or the rewritten text, with where it goes and how to check it. Anything the page does not show, such as a price or a phone number, is left as [FILL: …] for you to complete, never made up. You are charged only when the fix is written.
- For a Needs verification finding, do its Check this first step before building anything.
- When the changes are live, select Re-run audit.
- Read the line under the score: Compared to previous audit counts what is new, fixed and still there, and the Fixed tab lists what the new run no longer reports. View history opens every saved run.
Two runs can word or rank findings differently, so confirm a fix with its How to verify the fix check.
Limits and usage
- 10 pages cost 5 credits and 25 pages cost 12 credits. A run that fails is not charged. See plans and credits.
- 25 pages is the most one run reads: the AI model has to finish inside the 5-minute limit. On a slow site, pages the run had no time to read are named as not read.
- It reads part of each page, so it can say something was not seen, never that the whole site lacks it.
- It has no rankings, traffic or backlink data. Findings that need them say which tool to check.
- Write the fix with AI costs 1 credit per finding and reads only that finding's page on your site.
Troubleshooting
The run stopped because reading the site took too long
A slow or JavaScript-heavy site used up the analysis time. Nothing was charged. Run it again with 10 pages.
The audit shows no score
The site refused the crawler, so the audit ran on public data, or the run was saved before scores were added (12 October 2026). Allow SearchBlueprint's crawler if it was refused, then re-run the audit to get a score, a grade and a mark for each section.
A finding shows as fixed but the problem is still there
The new run did not report it, which is not proof. Run the finding's How to verify the fix check on the live page.