Skip to main content
Audit brings technical readiness and page-level search evidence into one project view. Use it to find access problems, inspect why a page needs attention, and turn supported findings into actions in the Actions queue.

​
Open Audit

  1. Open a project
  2. Select Insights › Audit in the project sidebar
  3. Choose Domains or Pages
Audit does not turn missing sources into zeroes. When a crawl, Search Console, AI-answer, or traffic source does not cover a page, the affected value appears as unavailable or unmeasured.

​
Domains

The Domains tab focuses on technical readiness for owned domains. Select a domain to review:
  • Overall readiness out of 100
  • AEO readiness, Agent readiness, and SEO health pillars
  • Host checks for crawler access, sitemap coverage, indexability, and orphan pages
  • Open findings grouped by severity
External properties can appear for visibility context, but host-level checks do not apply to them. A subdomain may inherit host checks from its owned parent domain; Audit labels that relationship instead of presenting a separate measurement.

​
Work with findings

Expand a finding to read What to change, verification guidance, affected pages, and attached evidence. If your account role can manage the project, you can:
  • Select Create action, review the prefilled title, then select Create in Actions
  • Select Dismiss finding when it should no longer appear as open
  • Select Show and restore → to review dismissed findings, then Restore one to reopen it
Creating an action does not change the site. The action joins the Actions queue as Accepted, with the finding evidence attached. Findings that already have an action link to it instead.

​
Pages

The Pages tab combines classic search, AI-answer, crawl, and traffic evidence for individual pages. Use the Last 7 days, Last 30 days, and Last 90 days presets to change the reporting window. Page metrics update once a day and cover complete UTC days, ending yesterday. New probe results, traffic, and Search Console or analytics data appear after the next daily update. Locking or unlocking a page, changing domains, changing tracked pages, and finishing a crawl update the Pages tab the same day. The heading states how many pages lost AI citations or presence in the window, or have them at risk. The summary band shows:
  • Classic search clicks from Google Search Console
  • AI citations from your tracked prompts
  • Lost or at risk, the number of pages diagnosed Lost citations & presence or Cited, at risk, with how many pages had no AI citations or presence in your tracked prompts
  • AI referral bounce rate for each domain, when PostHog is your connected analytics provider
Below the summary, the daily trend keeps classic clicks and AI citations on separate scales. Coverage notices state when Search Console or crawl measurement is incomplete.

​
Diagnoses

The Pages table labels each page with its strongest available diagnosis and orders pages by diagnosis and supporting evidence, highest opportunity first. Diagnoses are:
  • Lost citations & presence
  • Cited, at risk
  • Ranks on Google, not cited
  • Fetched, not cited
  • Locked
  • No traction
  • Healthy
Citation and presence counts cover your tracked prompt set. A page with no tracked citations may serve a subject those prompts do not cover; this is not proof that AI never cites it or that the page needs rewriting. Answer fetches measure requests, not buyer queries. Use Sort pages to reorder the table by search clicks, AI citations, citability or answer fetches. Where a diagnosis supports one, the row offers Create action, which opens a prefilled action form. Pages that already have an action show a link to it, and queued in Actions → opens the Actions queue.

​
Inspect a page

Select a row in the Pages table to open the page inspector. It shows:
  • The page’s diagnosis and lock status
  • Section clarity findings for the page
  • Why this ranks here, the evidence behind the page’s position in the table
  • Clicks, impressions, position, AI citations, citability, and answer fetches
  • Next action: Create action, or a link to the page’s action in the Actions queue
  • Daily AI citation history
If you can manage the project, the inspector also lets you lock or unlock a page. A lock protects the page from automated suggestions and change actions; it does not remove the page’s evidence from Audit.

​
Crawler access

Crawler access reports the sampled URLs and each provider’s search indexing, answer fetching or grounding capability. Probe passed means a synthetic request returned expected page content with applicable policy permitting retrieval. Verified crawler · HTTP 2xx is supporting HTTP evidence, not proof that the expected content was delivered. Access unconfirmed means some checks lack conclusive evidence. The score is provisional and uses only assessed combinations. Some access restricted applies to part of the sample, not the whole site. Restricted by policy remains visible even if a request succeeds. Training-only restrictions do not lower the score. Connected traffic can support a new audit only within its preceding 24 hours. The evidence panel shows the actual complete-hour window and source precision; omitted hours and untested URLs are not assessed. Each run retains its own evidence. Public audits use public observations without connected-project traffic.

​
Intentional restrictions

In a retrieval finding, select the exact URLs you intend to restrict, confirm your intent, then choose Acknowledge restriction. The finding, evidence and score remain visible. Recommendations and generated prompts omit those URLs. Other URLs remain actionable, including URLs first discovered in a later audit. Select the URLs and choose Reconsider restriction to restore their recommendations. This differs from dismissing a finding. Management permission is required, and locked pages remain protected. The API exposes this operation at POST /api/v2/projects/{projectId}/audit/retrieval-intent with auditRunId, findingId, urls, operation of acknowledge or reconsider, and confirmedIntent: true. The public MCP tools are devtune_acknowledge_retrieval_restriction and devtune_reconsider_retrieval_restriction. Both require actions.write; audit.read cannot mutate intent. Agents must obtain your explicit intent rather than infer it from detected restrictions.

​
Next steps