Complete SEO Audit Checklist

Scope and Access

Set the evidence boundary before diagnosing the site. Access or scope gaps should be logged as findings because they can prevent later checks from being verified reliably.

• Confirm Search Console and GA4 access. Evidence: working access to the relevant properties. Pass: the auditor can inspect the intended site's search and analytics data; fail: access is missing, restricted, or tied to the wrong property. Severity: High when required evidence is unavailable. Owner: site or analytics administrator. Corrective action: grant or correct access. Validation: reopen both properties and verify the intended data is visible.
• Confirm the primary domain and canonical host. Evidence: live responses, redirects, canonical declarations, and property context. Pass: the preferred host is clear and signals consistently point to it; fail: host variants resolve inconsistently or canonical intent conflicts. Severity: High for broad duplication or conflicting signals. Owner: SEO and engineering. Corrective action: align host handling and canonical declarations. Validation: retest representative host variants.
• Collect the XML sitemap and robots.txt. Evidence: the files served by the audited host and their current directives or URL entries. Pass: the files are available when expected and align with intended crawl and indexation behavior; fail: important pages are omitted or blocked unintentionally. Severity: High when priority pages are affected, otherwise Medium. Owner: SEO or engineering. Corrective action: correct the relevant sitemap entries or crawl directives. Validation: fetch the files again and recrawl affected URLs.
• List priority pages tied to meaningful business actions. Evidence: an agreed URL set supported by site architecture, analytics context, or stakeholder input. Pass: the audit explicitly identifies the pages that matter most; fail: findings cannot be prioritized against business importance. Severity: Medium. Owner: SEO and business stakeholder. Corrective action: finalize the priority URL set before triage. Validation: confirm major findings are mapped to affected page groups.
• Define audit depth, including whether review is sitewide or limited to the top 100 URLs. Evidence: written scope and the inclusion rule used for the sample. Pass: crawl and manual review coverage match the agreed scope; fail: important page classes are silently excluded or the sample cannot support the conclusions. Severity: Medium. Owner: audit lead. Corrective action: adjust the crawl or sample deliberately. Validation: compare the final evidence set with the documented scope.

Crawl and Indexation

Verify whether intended pages can be discovered, crawled, canonicalized, and indexed. Separate intentional exclusions from defects, preserve the affected URL set as evidence, and validate each fix through a new crawl or inspection.

• Run a reproducible site crawl. Evidence: crawl export, configuration, response data, canonical data, directives, and discovered links. Pass: the crawl completes with settings suitable for the site and includes expected page classes; fail: configuration gaps or blocked discovery make the dataset incomplete. Severity: High when priority areas are missing. Owner: SEO. Corrective action: correct crawl settings or access constraints. Validation: rerun the crawl and compare coverage.
• Review Search Console indexation evidence. Evidence: indexed and excluded URL examples plus inspection data where needed. Pass: important canonical pages are eligible for indexing and exclusions have an understood reason; fail: priority pages are unexpectedly excluded or large unintended duplicate sets appear. Severity: High for priority-page loss, otherwise Medium. Owner: SEO with engineering or content. Corrective action: repair the specific exclusion cause. Validation: reinspect representative URLs after recrawl.
• Validate canonical declarations against the preferred URL for each tested page class. Evidence: page canonicals, redirects, sitemap entries, and internal links. Pass: signals point consistently to the intended version; fail: canonicals target unsuitable pages or conflict with other strong signals. Severity: High for broad conflicts, otherwise Medium. Owner: SEO and engineering. Corrective action: align canonical signals. Validation: recrawl and inspect representative pages.
• Identify orphan or weakly discovered pages by comparing crawl discovery with available first-party URL inventories. Evidence: crawler data plus sitemap, analytics, or Search Console exports. Pass: important indexable pages have a useful internal discovery path; fail: priority pages exist without meaningful internal links. Severity: Medium, or High for commercially important pages. Owner: SEO and content or engineering. Corrective action: add contextually useful links or reconsider the page's role. Validation: rerun discovery from normal site entry points.
• Review crawl-efficiency problems only where evidence shows unnecessary URL generation, loops, or low-value crawl paths. Evidence: crawl patterns, server behavior, faceted URLs, redirects, and available crawl reports. Pass: intended discovery is not materially impeded by avoidable crawl paths; fail: large low-value spaces or loops interfere with important discovery. Severity: Medium, rising when priority areas are affected. Owner: SEO and engineering. Corrective action: fix the specific source of waste. Validation: compare subsequent crawl behavior.

On-Page Quality

Test whether important pages communicate a distinct purpose and satisfy the search task they target. Use crawl evidence for pattern detection, then manually review representative pages before assigning corrective work.

• Review title elements for distinctiveness and intent alignment. Evidence: crawl export plus manual review of priority templates. Pass: titles accurately describe page purpose without unnecessary duplication across competing URLs; fail: titles are misleading, systematically duplicated, or disconnected from visible content. Severity: Medium, or High for core landing-page patterns. Owner: SEO or content. Corrective action: rewrite affected titles to reflect each page's actual purpose. Validation: recrawl and manually confirm examples.
• Check H1 alignment with the page's primary task. Evidence: rendered page, primary heading, title element, and main content. Pass: the primary heading clearly identifies the main subject and supports the same intent as the visible content; fail: it is missing where the template requires it, misleading, or centered on another task. Severity: Medium. Owner: content or template owner. Corrective action: revise the heading without forced repetition. Validation: render the page and compare heading, title, and body purpose.
• Find pages whose main content is materially duplicative, insufficient for the intended task, or unsupported by useful differentiation. Evidence: similarity signals followed by manual comparison. Pass: each indexable page has a clear reason to exist and useful unique information; fail: near-identical pages compete without meaningful distinction. Severity: High for large competing sets, otherwise Medium. Owner: content and SEO. Corrective action: improve, consolidate, redirect, or exclude according to actual page purpose. Validation: compare the resulting page set again.
• Measure internal-link depth for priority pages in the context of site architecture. Evidence: crawl paths and source pages containing links. Pass: important pages are reachable through clear, crawlable, contextually relevant paths; fail: they depend on unnecessarily deep navigation or isolated discovery. Severity: Medium, rising when priority pages are hard to discover. Owner: SEO, content, or engineering. Corrective action: improve relevant navigation or contextual linking. Validation: recrawl from normal entry points.
• Review content maintenance where freshness is relevant. Evidence: visible claims, dates, product or policy information, and current page purpose. Pass: time-sensitive information is current or clearly qualified; fail: stale statements can mislead readers about the present offering. Severity: High for consequential inaccuracies, otherwise Medium. Owner: subject owner or content team. Corrective action: update or remove obsolete material. Validation: editorial review against the current source of truth.

Technical Foundations

Test rendering, usability, security, URL resolution, and link integrity with evidence from representative templates. Treat tool warnings as leads to investigate, not automatic failures, and retest affected page groups after deployment.

• Review Core Web Vitals evidence for LCP, CLS, and INP using appropriate field data when available and lab diagnostics for investigation. Pass: representative templates meet the performance condition chosen for the audit and no priority template shows an unresolved user-experience problem; fail: evidence shows material performance issues. Severity: High when widespread on priority templates, otherwise Medium. Owner: engineering or performance owner. Corrective action: address the diagnosed loading, rendering, or interaction bottleneck. Validation: repeat measurement using the same evidence standard.
• Test mobile usability on representative templates and priority pages. Evidence: rendered pages across relevant viewport conditions, interaction checks, and available first-party diagnostics. Pass: users can read, navigate, and complete intended actions without mobile-specific obstruction; fail: layout, controls, content, or overlays prevent normal use. Severity: High for blocked actions, otherwise Medium. Owner: design and engineering. Corrective action: repair the responsible component or template. Validation: retest the affected interaction.
• Check HTTPS behavior and mixed-content exposure. Evidence: browser security state, crawl protocol data, redirects, canonical targets, and resource requests. Pass: intended pages load securely and important resources are requested securely; fail: insecure resources, conflicting protocol signals, or unintended insecure accessibility remain. Severity: High for security or broad canonicalization problems. Owner: engineering. Corrective action: update resource references and protocol handling. Validation: recrawl and reload affected templates.
• Trace redirects on changed, consolidated, and canonical URL patterns. Evidence: redirect hops, final status, destination relevance, and internal links pointing into chains. Pass: required redirects resolve efficiently to the intended final page and internal links use the preferred destination; fail: chains, loops, irrelevant targets, or avoidable intermediate hops remain. Severity: High for loops or broken journeys, otherwise Medium. Owner: engineering with SEO. Corrective action: simplify redirect logic and update internal destinations. Validation: retest each affected pattern.
• Audit broken links and server responses, including 4xx and 5xx evidence. Evidence: crawl export with source URL, target URL, response status, and page role. Pass: priority internal links resolve to intended live destinations and server errors do not affect normal crawl or user journeys; fail: broken internal targets or recurring server failures remain. Severity: High for widespread or priority failures, otherwise Medium. Owner: engineering or content according to cause. Corrective action: restore the destination, update the link, or remove it when no replacement is appropriate. Validation: recrawl original source pages and confirm the failures are resolved.

Finding Log and Validation

Use the table to turn evidence into an actionable queue. Severity should reflect the observed impact, the owner should control the system that needs changing, and the ETA is an operating target rather than a guarantee. Close an issue only after its validation condition passes.