Audits
How the weekly audit compares two 28-day periods, finds drops and quick wins, and creates improvement tickets for existing pages.
The audit runs once a week and looks at pages you already have. It compares the last 28 days with the 28 days before, using Search Console data. It flags drops, page-2 rankings, low click-through rates and new queries, then creates improvement tickets for the pages that matter most, with converting pages first.
Note: The audit needs Search Console. Without it, the audit stops with "The audit needs Search Console. Connect it in Settings > Integrations." See Search Console.
What the audit does
- Syncs your sitemap and conversions so the page inventory is fresh.
- Reads Search Console query and page data for both 28-day periods.
- Flags each page with code rules (see below).
- Sends pages with real movement to the AI audit agent, converting pages first.
- The agent diagnoses the likely cause and picks one action per finding.
- Creates tickets for the top findings, up to Max tickets per audit.
- Writes a report in Insights > Agent reports.
Flags
| Flag | Rule |
|---|---|
| page-2 | Average position 11 to 30, with 100 or more impressions |
| low-ctr | More than 200 impressions and CTR under 1% |
| severe-low-ctr | Same, with more than 1,000 impressions |
| clicks-drop | Had 10 or more clicks before, now under 75% of that |
| position-drop | Position got 5 or more places worse, with 50 or more impressions |
| rising | Position got 5 or more places better, with 50 or more impressions |
| scaling | CTR above 3% with under 400 impressions |
| new-queries | New queries with 30 or more impressions that were not there before |
| converts | The page appears in converting sessions |
Pages with no flags, or only the "converts" flag, are skipped. Small numbers are treated as normal noise.
Likely causes
The agent picks a cause for each finding: content decay, SERP shift, snippet issue (high impressions, low CTR), intent mismatch, cannibalization, internal-link gap, indexing or technical issue, or seasonality.
Actions and tickets
| Action | Ticket type | Who does it |
|---|---|---|
| refresh | Refresh | Writer, then QA |
| snippet | Title/meta | Writer, then QA |
| internal_links | Internal links | Writer, then QA |
| technical | Technical | A person. Starts in Needs human |
| watch | No ticket | Listed in the report only |
Content tickets get a brief from the brief agent and start in To do with source audit. Technical tickets get a short brief with the issue, evidence and why it matters.
The audit skips pages and keywords that already have an open or recent ticket.
Warning: The agent avoids risky title changes on pages that already rank well. On a refresh of a page with 50 or more clicks, QA keeps the existing title. Changing a ranked title can lose traffic.
Close a technical ticket
- Open the ticket and read the brief: the issue, the evidence and why it matters.
- Fix it on your site (for example a redirect, an indexing setting or a slow page).
- In Done the fix?, enter the Page URL and click Mark done.
Settings
| Setting | Where | Default |
|---|---|---|
| Audit day (step 6) | Settings > Weekly schedule | Thursday |
| Hour (UTC) | Settings > Weekly schedule | 6 |
| Max tickets per audit | Settings > Weekly schedule | 5 (0 to 20) |
Click Run audit on the Overview page to run it now.
Audits and daily search performance
The audit looks at two 28-day blocks to find patterns. For day-to-day movement, use the Search performance page. It pulls Search Console numbers every day and shows pages going up and down, Day over day or Week over week. The first pull reads the last 90 days.
Tip: Search Console data is about 2 to 3 days behind. The audit uses data that ends 3 days ago so each period is complete.
Related
Did this page help? Tell us at support@agenticseo.com.