Skip to main content
SEO audit overview with site health cards and audit history table
Use this page as your full technical SEO workflow. It covers the summary view, run-level diagnosis, crawl-log validation, and URL-level issue execution.

Important: Fix highest-severity template-level issues first. They usually unlock the fastest site-wide improvement.

Questions this page should answer

  1. Is technical health improving from audit to audit?
  2. Which issue groups are causing the biggest risk right now?
  3. Which exact URLs should be fixed first this sprint?

Before you analyze

  • Keep the same date range used in your weekly reporting cadence.
  • Start with the summary cards, then open the newest completed run.
  • Compare at least two runs before assigning root cause.

What this page gives you

  • Top-level technical health snapshot (Site health, Errors, Warnings, Notices).
  • Run-level diagnosis with issue grouping and crawl behavior.
  • URL-level issue detail to create precise execution tasks.
  • A complete triage path in one document.

How to read the top cards

  • Site health: overall technical quality score for the crawl.
  • Errors: highest-priority issues that can block crawling/indexing quality.
  • Warnings: medium-priority issues that can create risk if ignored.
  • Notices: lower-priority issues to batch and resolve over time.
Use this interpretation:
  • Rising Errors means immediate action.
  • Flat but high Warnings means hidden debt that can become future blockers.
  • Stable Site health with concentrated issues still requires focused fixes.

Key signal: If errors rise and pages crawled stay stable, the issue is usually real quality degradation, not sampling noise.

How these metrics are calculated (simple)

Site health

Higher score means fewer severe issues across crawled pages.

Errors / Warnings / Notices

Severity counts are direct totals of findings grouped by severity (Error, Warning, Notice).

How to use audit history

Use Audit history to choose the run to investigate first:
  • Open the newest completed run first.
  • Compare with the previous run for issue-trend confirmation.
  • Watch Pages crawled and Duration to detect crawl volatility.
If a run looks abnormal, continue with run-level diagnosis below.

Run detail: All issues view

This is where you prioritize issue categories by impact before touching individual URLs.
SEO audit run detail All issues view with category-level issue analysis
What to do:
  • Identify issue groups affecting the most pages.
  • Prioritize error classes on key templates first.
  • Choose one high-impact issue class and close it end-to-end.
What this tells you:
  • Whether risk is concentrated in one technical area.
  • Whether the issue is likely template-wide or page-specific.

Run detail: Crawl log view

Use crawl log when you need evidence about how URLs were crawled and where failures happened.
SEO audit run Crawl log view with per-URL crawl results and statuses
What to check:
  • Repeated HTTP errors, timeouts, or blocked responses.
  • Failure clusters by folder/template.
  • Crawl behavior changes after deployments.
When to use:
  • Issue counts changed sharply.
  • Developers need URL-level crawl proof.

If the crawl log shows 403 responses

A 403 means the website, firewall, or CDN blocked the crawler from reading the page. Review the blocked request in your security event log. The current crawler identifies itself with this user agent:
Use this value to find requests in logs. A user agent is a label that any client can copy; it does not prove that a request came from Atomic AI. Do not create a domain-wide firewall, WAF, rate-limit, or bot-protection bypass based only on this value. Atomic AI does not provide fixed IP addresses for site audit allowlisting. Contact the Atomic AI team and your security administrator to establish an independently verified source restriction before creating an exception. Limit any agreed exception to the affected bot rule and public read-only audit paths. Keep authentication, WAF rules and rate limits in place for other traffic, including private pages and administrative or write endpoints. If a verified source restriction is unavailable, keep those protections enabled. Existing projects with an agreed transition keep AtomicAGIBot/1.0 until October 19, 2026 at 16:00 UTC. Both identities are request labels, not authentication. See Atomic AGI web access for request identification and access controls. The audit reads the homepage, robots.txt, sitemap files, and public pages in its scope. It does not need access to private pages. Review which controls an exception would disable: Cloudflare skip options can include WAF and rate-limiting rules. After an agreed rule change, run the audit again and check for successful 2xx or expected redirect responses. Confirm that requests without the verified source still receive the normal security controls.

Issue detail: affected URLs view

After selecting an issue class, use issue detail to assign exact fixes.
SEO issue detail view with affected URLs for one technical issue
How to work this table:
  1. Group URLs by template/folder.
  2. Prioritize commercial and high-visibility pages.
  3. Assign owner and deadline per URL group.
  4. Validate fixes in the next audit run.
Use this interpretation:
  • Many URLs in one path usually means a shared template defect.
  • Mixed status behavior can indicate rendering/routing inconsistency.

Fix a page with AI and verify the finding

The affected-URLs table includes a Finding state. The screenshot below uses illustrative local findings. Fix with AI is available when you have write access to Technical, AI agents, and Integrations, and the project has an active WordPress or Webflow website connection.
SEO audit affected URLs showing Finding states and Fix with AI actions
  1. Check the URL and issue evidence, then select Fix with AI on that row.
  2. The agent sidebar opens a new chat with the audit evidence and the connected website context. This asks the agent to implement a change on the connected website and publish it where supported. Follow its progress and inspect the resulting page links.
  3. Atomic rechecks the individual finding when the agent finishes. A saved CMS change alone does not mark it fixed.
  4. If verification is incomplete, use the row’s Recheck action when available. This checks that page and finding without rerunning the full site audit.
Read the states as follows: The agent can report limitations for Webflow static pages, server configuration, redirects, robots rules, or other unsupported changes. Assign those changes to the website owner instead of treating the conversation as proof of completion. A targeted check updates this finding; run a full audit to review site-wide health after broader changes.

Quick weekly checklist

  1. Check summary cards for direction change.
  2. Open latest run and triage top issue groups.
  3. Use crawl log to confirm root cause.
  4. Move to issue-detail URL lists and assign work.
  5. Validate reduction in the next completed run.

What to fix first

Team routine

  1. Weekly: run full triage from summary to issue-detail assignments.
  2. Bi-weekly: verify fix closure and rerun checks.
  3. Monthly: report resolved issue classes and repeated root causes.

Keep in mind

  • One clean run does not prove long-term stability.
  • Crawl-size shifts can change totals without real quality movement.
  • Never mark fixes complete before the next successful audit confirmation.

Where to go next