Pages and issues

Pages and issues

Filter the audited URL inventory, inspect check evidence, and export the current view.

The Pages view is the URL-level inventory behind the SEO summary. It shows which addresses were included, which checks ran, and how many issues were associated with each page. The Issues view groups repeated failures so a shared cause can be investigated across affected URLs.

Open detail before generalizing an issue. The useful decision record includes the check definition, outcome, captured value, affected URL, severity, and practical repair path. Exports reflect the current filters, so preserve those filters and the scan date when handing the data to another team.

Repeated failures often point to a template, component, CMS rule, or deployment configuration rather than isolated editorial mistakes. Group affected URLs by pattern before assigning work. Fixing the shared cause is usually more reliable than editing pages individually, and a follow-up scan can confirm whether the repair changed the check result across the intended coverage.

Verified against the current productUpdated July 26, 2026
PageUse it forKey controls
PagesCompare audited URLs and their issue counts.Search, outcome, category, export, page detail
IssuesGroup failures by severity, outcome, and category.Search, severity, category, affected URLs, issue detail
Audit coverageSee which technical areas and checks ran.Crawlability, indexability, metadata, links, structured data, performance

Issue detail

A useful issue includes the check name, outcome, practical explanation, affected URLs, captured evidence, and a repair path.

A repair decision should distinguish the observed value from the recommended fix. Review whether the failure comes from one page, a reusable template, generated metadata, or infrastructure. Record the intended owner and verify the result in a later completed scan.

Coverage matters

Plan limits can mean only part of a site is rendered or performance-tested. Check coverage before generalizing a result to the entire domain.

Look for caps, exclusions, failures, and template representation. If a critical section was not tested, request a focused follow-up rather than assuming it behaves like the sampled pages.