> ## Documentation Index
> Fetch the complete documentation index at: https://docs.devtune.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Audit

> Use domain readiness, page evidence, diagnoses, and findings to decide what needs attention.

**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 work in Actions.

## Open Audit

1. Open a project
2. Select **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
* **Readiness over time** across completed audits
* 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** to review a prefilled title and send the finding to Actions
* Select **Dismiss finding** when it should no longer appear as open
* Restore a dismissed finding later

Creating an action does not change the site. It creates reviewable work with the finding evidence attached.

## Pages

The **Pages** tab combines classic search, AI-answer, crawl, and traffic evidence for individual pages. Use the **7 days**, **28 days**, and **90 days** controls to change the reporting window.

The summary band shows:

* **Classic search clicks** from Google Search Console
* **AI citations (probes)** from tracked AI answers
* **Pages ready**, the share of assessed pages with a citability score of at least 80
* **Locked pages**, which are excluded from automated suggestions and change actions

Below the summary, the daily trend keeps classic clicks, AI citations, and answer fetches on separate scales. Coverage notices state when Search Console or crawl measurement is incomplete.

### Needs attention

**Needs attention** groups pages by the strongest available diagnosis, then orders the highest-opportunity pages first within each group. Diagnoses include:

* **Lost citations & presence**
* **Cited, at risk**
* **Ranks on Google, not cited**
* **Fetched, not cited**
* **Locked**
* **No traction**
* **Healthy**

Healthy and lower-priority pages remain available in **All pages** even when they are not promoted into **Needs attention**.

### Inspect a page

Select a row in **All pages** to open the page inspector. It shows:

* Clicks, impressions, average position, AI citations, citability, and answer fetches
* **Direct traffic** status and supporting comparison when enough sources are measured
* **Google eligibility** signals for indexing, canonical selection, crawlability, and structured data
* Daily citation history
* The latest crawled content preview and content-change dates
* A link to queued work in Actions, when present

DevTune does not monitor Google manual actions or security issues. Check those reports directly in Search Console.

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.

## Next steps

* [Interpret Direct traffic](/ai-traffic/direct-traffic)
* [Review measured outcomes](/insights-actions/outcomes)
* [Work from Actions](/insights-actions/actions-hub)