Skip to main content
Technical Audit checks your Website the way search engines and AI crawlers reach it. Each execution is an Audit Run: it starts at the Website’s entry address, follows links from the homepage, then adds pages that only a sitemap lists, up to the run’s page limit. Every page is checked the moment it is retrieved, so results fill in while the run continues. Its results are Findings. An Issue identifies a failed check or a condition that needs correcting; a Recommendation suggests an improvement. Technical Audit does not measure whether an AI Platform mentioned or cited your Brand.

​
Run an audit

Open Technical Audit in the Project navigation and select Run audit, or Run again after an earlier run. While it runs, the status line shows how many pages have been audited out of the page limit. If a run is already in progress, you see that run rather than starting a second one. Starting a run needs edit access to Technical Audit. A run you start counts toward your Plan’s monthly Technical Audit allowance; scheduled audits keep running on their own cadence. See Plans. The audit’s own crawler obeys your robots.txt. A page robots.txt disallows is listed as skipped, not audited. When the page limit, rather than a failed request, leaves found pages uncrawled, the run says Page limit reached.

​
Read the result

1

AI Readiness

The headline score, out of 100, for how prepared the Website is for AI discovery and access. It appears once the crawl finishes; until then it is pending. Its state is Ready (90–100), Strong (80–89), Needs attention (60–79) or Critical (0–59). A Readiness Cap limits the score when a blocking condition applies, such as AI search crawlers blocked in robots.txt or the homepage not loading, and names the reason.
2

Fix first

The Overview lists the Findings to fix first, then every Finding grouped by Theme: Discovery, Access, Rendering, Indexing, Retrieval, Citation and Experience. Themes follow the path a page takes to an AI answer, and a Finding sits in the earliest Theme it breaks. Switch the grouping to By owner to see who can fix what and copy one message for each of them.
3

AI platform access

For Google, ChatGPT, Claude, Perplexity and Copilot, the access grid shows where each platform gets stuck first and which Findings cause it.
Each Finding states its Finding Severity (Error, Warning or Notice), its Finding Priority (High, Medium or Low, from its severity, how many pages it affects and its effect on AI Readiness), who can fix it, how many pages it affects and example addresses. A Finding shown while the crawl is still running is marked provisional and can change.

​
Explore the run

  • Questions answers common SEO and AI search questions from this run’s data.
  • Pages lists every page the crawl found, as folders, with status, speed and failed checks. Open a page to see its checks, links and the Findings that name it.
  • Structure shows how pages link together: reach from the homepage on the Map, and click depth and link weight in Links.
  • Speed shows Lighthouse lab scores for one page per template on a simulated phone. These Speed Samples are lab data from a single load: they are not what visitors experience and do not count toward AI Readiness.
  • Tools fetches a page as a chosen AI crawler, or tests what your robots.txt allows a crawler to fetch.
Use History to open an earlier Audit Run. Since last run compares the shown run with the previous complete one: AI Readiness before and after, resolved and new Findings, and what changed on the site. When the start address or page limit changed between the runs, the scores are not directly comparable and the comparison says so. The export menu downloads pages or Findings as CSV, the full run as JSON, or copies a summary to paste into Sira or another assistant.

​
Act on a Finding

Open a Finding to read why it matters, how to fix it, who can fix it and the evidence behind it. Where someone else has to make the change, copy the ready-made message for them. Where it is offered, Preview this fix projects what AI Readiness would be if the Issue were resolved; it changes nothing on your Website. After the change is live, select Check if it’s fixed in the Finding. It requests the affected pages from your live site in a few seconds and does not start a new audit. Some Findings depend on the whole site or on a Lighthouse lab run; those can only be confirmed by running the audit again. See Check whether a Technical Audit fix worked.
A new AI Analysis is a separate measurement and does not verify a Technical Audit Finding.

Check an audit fix

Check the live page, then confirm with a new Audit Run.

Review your first Analysis

Interpret visibility evidence separately from the Technical Audit.

Project Overview

Return to the Project summary after reviewing the audit.
Last modified on October 27, 2026