Complete SEO Audit Checklist: How to Run a Full SEO Audit (2026)

Updated: 27.09.2026

Most SEO audits end as a PDF attachment nobody opens. The findings are real, the effort was genuine, and nothing gets fixed – because the report never answered the question that matters most: where do we start?

This SEO audit checklist is built around that question. It covers more than 50 items across six sequential phases – technical, on-page, content, off-page, and monitoring – and pairs every phase with a prioritization layer so findings translate directly into an ordered fix list. Whether you’re learning how to do an SEO audit for the first time or standardizing the process across a client roster, this SEO audit guide is designed to be repeatable, not just readable.

Key Takeaways

• Run the six phases in sequence – technical before on-page, on-page before content – because each phase’s findings inform the next. Skipping ahead typically means treating symptoms rather than root causes.
• Use the impact-versus-effort matrix to sort every finding into four quadrants before assigning any work. The 20% of fixes in the high-impact, low-effort quadrant typically drive 80% of the ranking and traffic gains.
• Crawlability and indexability problems suppress every other improvement. Resolve robots.txt blocks, redirect chains, and canonical conflicts before touching title tags or content.
• AI tools such as ChatGPT can accelerate content gap analysis and draft recommendations from data you supply, but they cannot crawl your site, read log files, or measure live Core Web Vitals – those tasks require dedicated audit tools.
• Ecommerce and local sites need additional checks beyond the core six phases: faceted navigation controls and product schema validation for ecommerce; Google Business Profile completeness and NAP consistency for local.
• A one-time audit captures a snapshot. Monthly crawl-error checks, quarterly content and backlink reviews, and an annual full audit convert that snapshot into a durable performance program.
• Translate every technical finding into business language before presenting it to stakeholders – lost traffic, missed conversions, and competitive exposure – not error counts. Findings that stay in a spreadsheet have zero ROI.

What Is an SEO Audit? (Definition, Purpose, and Core Components)

An SEO audit is a structured evaluation of every factor that affects how well a website ranks in organic search – and more importantly, why it ranks where it does. It maps the gap between where your site stands today and where it needs to be to compete for the queries that drive real traffic and revenue. Done well, an SEO audit checklist is not a one-time diagnostic; it is the foundation of a repeatable growth system that keeps a site competitive as search algorithms, competitor behavior, and user expectations shift.

Why a Site Audit Matters Before You Change Anything

Without an audit, optimization work is guesswork. A developer might improve page speed on pages that already pass Core Web Vitals while ignoring a crawlability issue that blocks an entire product category from being indexed. A content team might publish new articles while dozens of existing pages cannibalize the same keywords. An audit surfaces these conflicts before effort is wasted, giving every subsequent change a clear rationale and a measurable baseline to compare against.

Audits are also the earliest warning system for algorithmic changes. When rankings drop, an audit distinguishes between a penalty, a technical regression, a content quality issue, and a competitor improvement – four problems that require four different responses.

The Four Pillars Every Audit Covers: Technical, On-Page, Content, and Off-Page

What is included in an SEO audit? A complete site audit organizes findings across four interconnected areas:

• Technical SEO – crawlability and indexability, site architecture, Core Web Vitals, mobile usability, HTTPS, and structured data implementation. This is the infrastructure layer; problems here suppress every other improvement.
• On-page SEO – title tags, meta descriptions, heading structure, schema markup, internal linking, and E-E-A-T signals. This layer controls how search engines interpret individual pages.
• Content – topical authority, thin or duplicate pages, keyword cannibalization, and content freshness. This determines whether a site earns trust on a subject or spreads itself too thin.
• Off-page / backlink profile – link quality, toxic links, anchor text distribution, and gaps relative to competing domains. This reflects how the broader web perceives the site’s authority.

Each pillar informs the others. A technically sound site with weak content authority will plateau. A site with strong content but poor crawlability leaves rankings on the table. Working through all four – in sequence, with the right tools – is what separates a genuine audit from a surface-level checkup.

Why Run an SEO Audit: The Business Case and ROI of Fixing What You Find

An SEO audit is not a maintenance ritual – it is a diagnostic that reveals exactly where a site is losing revenue it has already earned the right to capture. Pages that rank on page two instead of page one, crawl errors that hide product pages from Google, and slow load times that push visitors to competitors are all measurable losses. The audit names them, and fixing them has a direct path to revenue.

Translating Technical Findings into Revenue Language for Stakeholders

Most technical findings land poorly with decision-makers – especially in a B2B SEO audit, where several stakeholders sign off – because they are framed as engineering problems rather than business problems. A crawl budget issue becomes compelling when it is described as “Google is not indexing our newest product pages, which means they cannot appear in search results and generate no organic revenue.” A Core Web Vitals failure becomes urgent when it is tied to page abandonment before a purchase decision.

The translation exercise works in three steps. First, identify the finding – for example, a large cluster of thin pages diluting topical authority. Second, connect it to a measurable traffic or ranking outcome: those pages are competing with stronger content for the same queries and losing. Third, estimate the revenue at stake by applying the site’s known conversion rate and average order value to the organic traffic the pages should be receiving but are not. This framing gives stakeholders a reason to fund remediation rather than defer it.

Note that case study outcomes circulated by agencies and vendors – such as claims of traffic doubling after a technical fix – should be treated as company claims until verified against a primary source. The underlying logic is sound: fixing indexation, page speed, or duplicate content problems removes friction that suppresses rankings. The magnitude of the gain depends on the site’s baseline, the severity of the issue, and the competitiveness of the target queries.

Building the Case: Traffic, Conversion, and Competitive Risk Framing

Beyond the upside, audits surface competitive risk – the cost of inaction. If a competitor has recently improved its site architecture, earned stronger backlinks, or published more authoritative content on your core topics, your current rankings are not stable; they are eroding. An audit makes that erosion visible before it shows up in a revenue report.

A practical business case for an audit rests on three pillars:

• Traffic opportunity: Queries where the site ranks on page two or three represent recoverable traffic. Fixing the on-page or technical issues holding those pages back is lower-cost than acquiring new rankings from scratch.
• Conversion leakage: Pages with high impressions but low click-through rates, or high traffic but low conversion, often have fixable problems – weak title tags, missing schema, or poor page experience – that the audit identifies.
• Competitive exposure: Gaps in topical coverage or backlink profile relative to ranking competitors represent positions the site will lose if left unaddressed.

Framed this way, the audit is not a cost; it is the prerequisite for any informed SEO investment decision.

The 6-Phase SEO Audit Framework: From Setup to Ongoing Monitoring

To perform an SEO audit, work through six sequential phases: configure your tools and access credentials, run a technical crawl to surface crawlability and indexability issues, review on-page elements such as titles and schema, assess content quality and topical coverage, evaluate your backlink profile for toxic links and gaps, then set up monitoring so findings don’t go stale. Each phase produces a discrete set of findings that feed a prioritized fix list – skipping phases or running them out of order typically means missing the root cause of a problem.

These six SEO audit steps form the organizing spine of this guide. Sections 4 through 9 cover each phase in full detail. This section maps the overall flow and clarifies who on your team owns each part.

The Master SEO Audit Checklist at a Glance

The complete checklist across all six phases covers more than 50 items, organized by phase and priority tier, with ecommerce and local SEO add-ons appended at the end. A downloadable SEO audit checklist PDF and a free SEO audit template in Google Sheets, with one tab per phase, are available alongside this article so teams can track progress without rebuilding the structure from scratch.

Here is a compressed view of what each phase covers:

Phase 1 – Setup: Connect Google Search Console and Google Analytics; configure your crawler (Screaming Frog or equivalent); document baseline rankings and traffic.

Phase 2 – Technical SEO audit: Check crawlability and indexability (robots.txt, XML sitemap, canonical tags, redirect chains); audit Core Web Vitals and mobile usability; verify HTTPS and structured data validity.

Phase 3 – On-page SEO audit: Review title tags, meta descriptions, heading hierarchy, and internal linking; check schema markup; evaluate E-E-A-T signals on key pages.

Phase 4 – Content audit: Identify thin pages, duplicate content, and keyword cannibalization; map topical authority gaps; flag pages to consolidate, update, or remove.

Phase 5 – Backlink and off-page audit: Pull your backlink profile; identify toxic or spammy links; compare link gaps against competitors; prepare a disavow file if needed.

Phase 6 – Monitoring and reporting: Set up rank tracking and Search Console alerts; schedule recurring audit cadences; assign owners to each open finding.

Ecommerce sites add checks for faceted navigation, product schema, and duplicate pages generated by filters. Local sites add Google Business Profile completeness, NAP consistency, and citation audits.

Who Owns Each Phase: SEO, Content, and Dev Team Handoffs

A common reason audits stall is unclear ownership. The table below assigns each phase to its primary owner and flags where handoffs are required.

Phase	Primary owner	Requires dev access?	Content team involved?
1 – Setup	SEO specialist	Yes – analytics/GSC permissions	No
2 – Technical	SEO specialist	Yes – server, CMS, redirect config	No
3 – On-page	SEO specialist	Minimal – CMS edits	Yes – copy revisions
4 – Content	Content team lead	No	Yes – primary owner
5 – Off-page	SEO specialist	No	No
6 – Monitoring	SEO specialist	Yes – dashboard/alert setup	Partial – report review

Phases 2 and 6 consistently require developer involvement: implementing redirect fixes, resolving Core Web Vitals issues, and configuring monitoring infrastructure all touch code or server configuration. Flagging those items for your dev queue at the start of the audit – rather than after findings are complete – prevents the most common bottleneck.

Phase 1: Setup and Tools – Building Your Audit Toolkit

Before crawling a single URL or pulling a keyword report, the audit falls apart without the right data access. Skipping setup means you’ll diagnose symptoms without the baseline data needed to confirm whether a fix actually worked.

Access and Data You Need Before Starting (GSC, Analytics, Crawler)

Three data sources form the foundation of any credible audit:

Google Search Console is non-negotiable. It shows which pages Google has indexed, which queries drive impressions and clicks, manual actions, Core Web Vitals field data, and crawl errors. If GSC isn’t already verified for the property, set that up first – the data is only collected from the moment of verification, so there’s no retroactive history.

Google Analytics (or an equivalent analytics platform) connects search performance to user behavior. You need it to identify high-traffic pages with poor engagement, conversion drop-off points, and the pages worth prioritizing when you triage fixes.

A site crawler – Screaming Frog SEO Spider is the standard choice for on-premise audits – maps the site’s internal link structure, surfaces broken links, flags redirect chains, identifies missing or duplicate title tags and meta descriptions, and exports a full URL inventory. For large sites, configure the crawler to respect crawl limits and authenticate behind login walls where needed.

Before starting, confirm you have: admin access to GSC and Analytics, crawler software installed and configured, and permission to export data from any CMS or e-commerce platform the site runs on.

Matching Tools to Audit Tasks

Different audit phases call for different tools. Trying to do everything in one platform leads to gaps.

Audit task	Primary tool	What to check
Crawl errors, index coverage	Google Search Console	Coverage report; inspect individual URLs
Full site crawl, redirect chains, broken links	Screaming Frog	Response codes, canonical tags, internal links
Backlink profile, toxic links	Ahrefs or Semrush	Referring domains, anchor text distribution, lost links
Keyword rankings, competitor gap	Semrush or Ahrefs	Position tracking, keyword gap report
Page speed, Core Web Vitals lab data	PageSpeed Insights	LCP, CLS, INP scores per URL
Core Web Vitals field data	Google Search Console	CWV report under Experience

For most audits, Screaming Frog handles the crawl layer, GSC supplies index and performance data, PageSpeed Insights covers speed diagnostics, and Ahrefs or Semrush covers the backlink and keyword layers. You don’t need all five tools running simultaneously – sequence them by phase so each tool’s output informs the next step.

Phase 2: Technical SEO Audit Checklist (Crawlability, Indexability, and Core Web Vitals)

Technical SEO is the foundation everything else rests on. If Googlebot cannot reliably crawl and index your pages, on-page optimizations and content improvements will not move rankings. This phase is your technical site audit guide: SEO fixes start at the structural layer of your site, before you touch a single title tag.

Crawlability and Indexability: Robots.txt, XML Sitemaps, and Canonicals

Crawlability and indexability are distinct problems. A page can be crawlable but excluded from the index, or indexed but never crawled efficiently. Auditing both together prevents you from chasing symptoms instead of causes.

Work through these items using Screaming Frog SEO Spider for crawl data and the Google Search Console Coverage report for indexation status:

• Item 1 – Robots.txt review: Fetch yourdomain.com/robots.txt and confirm no critical directories or page types are accidentally disallowed. Tool: Screaming Frog > Robots.txt tester.
• Item 2 – XML sitemap audit: Verify the sitemap is submitted in GSC, returns a 200 status, and contains only canonical, indexable URLs – no noindex pages, redirects, or 4xx URLs. Tool: GSC > Sitemaps report.
• Item 3 – Noindex tag audit: Pull all pages tagged noindex and confirm each exclusion is intentional. Staging pages, thank-you pages, and filtered URLs are expected; category pages and product pages are not. Tool: Screaming Frog > Response Codes + Directives.
• Item 4 – Canonical tag audit: Check that every page declares a self-referencing canonical or points to the correct preferred URL. Flag pages with missing, self-conflicting, or chained canonicals. Tool: Screaming Frog > Canonicals tab.
• Item 5 – Redirect chain audit: Identify chains longer than one hop (A → B → C) and loops. Resolve them to direct 301s to reduce crawl waste and preserve link equity. Tool: Screaming Frog > Redirects.
• Item 6 – HTTPS and mixed-content check: Confirm the entire site serves over HTTPS and that no page loads HTTP resources (images, scripts, stylesheets) that trigger browser warnings. Tool: Screaming Frog > Security tab; Chrome DevTools.
• Item 7 – 4xx and 5xx error sweep: Export all broken internal links and server errors. Prioritize pages with inbound links or significant traffic. Tool: GSC > Coverage > Excluded + Crawl stats; Screaming Frog.
• Item 8 – Duplicate URL variants: Check for parameter-driven duplicates (?sort=, ?ref=), trailing-slash variants, and www vs. non-www inconsistencies. Each should resolve to a single canonical. Tool: Screaming Frog > URL parameters; GSC.

Core Web Vitals Thresholds and Diagnostic Workflow (LCP, INP, CLS)

Core Web Vitals are Google’s user-experience signals with published pass/fail thresholds. Failing them does not guarantee a ranking penalty, but passing them removes a confirmed ranking disadvantage. Run diagnostics in Google PageSpeed Insights (which uses real-world Chrome User Experience Report data) and cross-reference with the GSC Core Web Vitals report.

Google’s published thresholds from web.dev are:

Metric	Good	Needs Improvement	Poor
LCP (Largest Contentful Paint)	< 2.5s	2.5s – 4.0s	> 4.0s
INP (Interaction to Next Paint)	< 200ms	200ms – 500ms	> 500ms
CLS (Cumulative Layout Shift)	< 0.1	0.1 – 0.25	> 0.25

Diagnostic workflow: Start with the GSC Core Web Vitals report to identify which URL groups fail at scale. Then open those URLs in Google PageSpeed Insights for per-page diagnostics and specific fix recommendations. Common LCP culprits are unoptimized hero images and render-blocking resources; CLS failures often trace to images without explicit dimensions or late-loading ads; INP issues typically point to heavy JavaScript execution on interaction.

Crawl Budget and JavaScript Rendering for Large Sites

In a detailed SEO audit of a site with thousands of pages, crawl budget – the number of pages Googlebot will crawl within a given timeframe – becomes a real constraint. Wasted crawl budget on low-value URLs means important pages get crawled less frequently.

Audit crawl budget by reviewing the GSC Crawl Stats report (Settings > Crawl Stats). Look for a high ratio of crawled-but-not-indexed pages, which signals Googlebot is spending time on URLs that add no value.

JavaScript-rendered content adds a separate layer of risk. Googlebot processes JavaScript in a second wave, which can delay indexation. Use GSC’s URL Inspection tool to compare the rendered HTML against the raw HTML. If key content or links appear only in the rendered version, consider server-side rendering (SSR) or static generation for those templates.

Internal Linking Audit: Orphan Pages and Anchor Text Diversity

Internal links distribute PageRank and signal topical relationships to crawlers. An orphan page – one with no internal links pointing to it – is effectively invisible to Googlebot unless it appears in the sitemap.

Export your full crawl from Screaming Frog and filter for pages with zero inlinks. Cross-reference against GSC to find orphaned pages that still receive organic traffic, which indicates they have value worth preserving. For pages with inlinks, review anchor text distribution: over-optimized exact-match anchors on every internal link look unnatural, while generic anchors (“click here”) waste the relevance signal.

Mobile-First Indexing and Basic Accessibility Checks

Google indexes the mobile version of your site first. If your mobile and desktop versions serve different content, structured data, or internal links, the mobile version is what determines your rankings.

Check mobile rendering using GSC’s URL Inspection tool (toggle to mobile) and Google’s Mobile-Friendly Test. Flag pages where:

• Content visible on desktop is hidden or absent on mobile
• Structured data present on desktop is missing from mobile templates
• Tap targets are too small or elements overlap on small screens
• Font sizes fall below readable thresholds without zooming

Accessibility overlaps with technical SEO in meaningful ways. Missing alt attributes on images deprive crawlers of context; poor heading hierarchy disrupts both screen readers and crawler understanding of page structure. A Screaming Frog crawl flags missing alt text at scale; manual spot-checks with a screen reader or the Chrome Accessibility panel catch structural issues.

The on-page and content phases build directly on what this technical layer reveals. Before moving forward, every item in the checklist below should have a status – pass, fix required, or not applicable – logged in your audit tracker.

Here is the complete technical SEO checklist for this phase:

• Item 1 – Robots.txt: Confirm no critical pages are disallowed. Tool: Screaming Frog.
• Item 2 – XML sitemap: Submitted in GSC, 200 status, indexable URLs only. Tool: GSC Sitemaps.
• Item 3 – Noindex audit: All noindex exclusions are intentional. Tool: Screaming Frog Directives.
• Item 4 – Canonical tags: Every page has a valid, non-conflicting canonical. Tool: Screaming Frog Canonicals.
• Item 5 – Redirect chains: No chains longer than one hop; no loops. Tool: Screaming Frog Redirects.
• Item 6 – HTTPS and mixed content: Full HTTPS, no mixed-content warnings. Tool: Screaming Frog Security; Chrome DevTools.
• Item 7 – 4xx/5xx errors: All broken links and server errors identified and prioritized. Tool: GSC Coverage; Screaming Frog.
• Item 8 – Duplicate URL variants: Parameter, trailing-slash, and www variants resolve to one canonical. Tool: Screaming Frog; GSC.
• Item 9 – Core Web Vitals: LCP < 2.5s, INP < 200ms, CLS < 0.1 across key templates. Tool: Google PageSpeed Insights; GSC Core Web Vitals report.
• Item 10 – Crawl budget (large sites): Low-value URLs de-prioritized; JS rendering verified via URL Inspection. Tool: GSC Crawl Stats; URL Inspection.
• Item 11 – Orphan pages: No valuable pages exist with zero internal inlinks. Tool: Screaming Frog inlinks filter.
• Item 12 – Mobile-first rendering: Mobile and desktop versions serve equivalent content and structured data. Tool: GSC URL Inspection (mobile); Mobile-Friendly Test.

The content signal table below applies to the content audit phase, but it is useful to reference here when deciding whether a technically sound page is worth preserving or consolidating:

Content Signal	Recommended Action
Ranking, traffic, and engagement are all healthy	Keep As-Is – no intervention needed
Ranking but thin; low dwell time	Update – expand depth and add supporting evidence
Two or more pages targeting the same keyword	Merge – consolidate into one authoritative page and redirect
No rankings, no traffic, no inbound links for 12+ months	Delete – remove and redirect to the closest relevant URL

Phase 3: On-Page SEO Audit Checklist (Titles, Meta Tags, Schema, and E-E-A-T Signals)

On-page SEO is where search intent and page content either align or diverge. Technical fixes get pages crawled and indexed; on-page work determines whether those pages rank for the right queries and earn clicks. This phase audits every element a search engine reads before deciding how to rank and display a page.

Title Tag and Meta Description Character Guidelines

Title tags and meta descriptions are the first signals Google reads for topical relevance and the first copy a searcher sees in results. Both need to be accurate, within display limits, and written for the target query.

Title tags

• Keep titles under 60 characters (roughly 600px display width) to avoid truncation in search results.
• Place the primary keyword near the front of the title.
• Each page must have a unique title; duplicate titles across pages dilute relevance signals.
• How to check: Run a Screaming Frog crawl and filter the Title column for missing, duplicate, or over-length entries. Cross-reference Google Search Console’s Coverage report for pages Google has rewritten the title on – a sign of a mismatch between title and page content.

Meta descriptions

• Target 120-158 characters. Longer descriptions are truncated on mobile.
• Meta descriptions are not a direct ranking factor, but a well-written description improves click-through rate.
• Flag pages with missing or duplicate meta descriptions for rewriting.
• How to check: Screaming Frog’s Meta Description tab; filter for missing, duplicate, and over-length.

Heading Structure and Keyword Placement

Headings (H1-H6) give both users and crawlers a document outline. Errors here are common and easy to fix.

• One H1 per page: Multiple H1s create ambiguity about the page’s primary topic. Screaming Frog flags pages with missing or multiple H1s.
• H1 must match search intent: The H1 should reflect the target keyword and the page’s actual content – not a brand tagline or generic label.
• Logical heading hierarchy: H2s should represent major sections; H3s should nest under the relevant H2. Skipping levels (H1 → H3) is not a ranking penalty, but it degrades accessibility and structured readability.
• Keyword placement: The target keyword or a close semantic variant should appear in the H1, at least one H2, and naturally within the first 100 words of body copy. Forced repetition is counterproductive – match the language your audience uses.
• How to check: Screaming Frog’s H1 and H2 tabs; manually review pages flagged for missing or duplicate headings.

Schema Markup Validation with Google’s Rich Results Test

Schema markup helps Google understand page content and can unlock rich results – star ratings, FAQs, how-to steps, and product information – that increase click-through rates without changing organic position.

What to audit:

• Confirm that schema types match page content: Article schema on blog posts, Product schema on product pages, LocalBusiness schema on location pages, FAQ schema where a genuine Q&A section exists.
• Check for required properties. Google’s Rich Results Test (search.google.com/test/rich-results) shows which required and recommended fields are missing for each schema type.
• Validate that schema data matches visible page content. Mismatches – such as a schema price that differs from the displayed price – can trigger a manual action.
• Look for deprecated schema types or properties that no longer qualify for rich results.
• How to check: Run key page templates through Google’s Rich Results Test. For site-wide coverage, use Screaming Frog’s custom extraction or a dedicated schema validator.

E-E-A-T Signals to Check On-Page

Google’s quality rater guidelines use Experience, Expertise, Authoritativeness, and Trustworthiness (E-E-A-T) to evaluate page quality – particularly for YMYL (Your Money or Your Life) topics such as health, finance, and legal content. While E-E-A-T is not a direct algorithmic score, the on-page signals that support it correlate with ranking stability.

Checklist:

• Author attribution: Does the page identify who wrote it? For expertise-sensitive content, include a named author with a bio that documents relevant credentials or experience.
• Author bio page: The author’s bio page should link to or describe verifiable credentials, publications, or professional profiles.
• Last-reviewed or updated date: Visible dates signal freshness and editorial oversight, especially for evergreen guides and medical or financial content.
• Primary sources and citations: Pages that cite original research, government data, or peer-reviewed sources demonstrate subject-matter depth. Audit whether claims are supported by linked evidence.
• About and contact pages: A clear About page and accessible contact information are baseline trust signals. Their absence is a flag in a quality review.
• HTTPS: Confirm the page is served over HTTPS – a prerequisite for trust, already covered in Phase 2, but worth verifying at the page level if mixed-content warnings appear.
• How to check: Manual review of priority pages; Google Search Console’s manual actions report for any trust-related penalties; third-party tools such as Semrush’s On-Page SEO Checker for E-E-A-T recommendations.

Prioritization tip: Start with your highest-traffic and highest-converting pages. Title tag and H1 fixes are low-effort and often produce measurable ranking shifts within weeks. Schema validation is worth running across all page templates, since a single fix applies site-wide.

Phase 4: Content Audit Checklist (Topical Authority, Thin Pages, and Cannibalization)

A content audit does more than count words – it maps every page against the questions your audience is actually asking, then surfaces the gaps, duplicates, and dead weight that dilute your site’s authority. The goal is a leaner, more coherent content set that signals genuine expertise on your core topics.

Identifying Thin Pages (Under 300 Words) and Low-Value Content

Thin pages are those that exist in the index but deliver little to a reader: stub articles, auto-generated category pages with no descriptive copy, boilerplate product descriptions, or paginated archive pages that duplicate content from elsewhere on the site.

How to check: Run a full crawl in Screaming Frog and export the word-count column. Filter for pages under 300 words, then cross-reference with Google Search Console to see whether those URLs receive any impressions or clicks. Pages with low word count and zero organic traffic are the clearest candidates for action.

What to look for:

• Pages under 300 words that are indexed and receiving no impressions
• Auto-generated tag or category pages with duplicate or near-duplicate copy
• Paginated pages (page 2, page 3) indexed without a canonical pointing to the root
• Product or service pages that contain only a headline and a contact form
• Blog posts that restate a topic already covered in depth elsewhere without adding new information

Tool: Screaming Frog (word count export) + Google Search Console (Performance report filtered by URL)

Finding Keyword Cannibalization Across Pages

Cannibalization happens when two or more pages on the same site compete for the same primary keyword. Google must choose which page to rank, and it often rotates between them – meaning neither ranks as well as a single consolidated page would.

How to check: In Google Search Console, open the Performance report and filter by a target keyword. If multiple URLs appear in the top positions for the same query, cannibalization is likely. You can also use a site: search in Google (site:yourdomain.com “target keyword”) to surface competing pages quickly.

What to look for:

• Two or more pages targeting the same primary keyword with similar title tags
• A newer page outranking an older, more authoritative page on the same topic
• Fluctuating rankings for a keyword where no off-site changes occurred
• Multiple blog posts covering the same subtopic at the same depth

Tool: Google Search Console (Performance report, URL filter) + Screaming Frog (title tag export sorted by keyword)

Mapping Content to Topical Clusters

Topical authority – the degree to which your site comprehensively covers a subject area – is built through clusters: a pillar page that addresses a broad topic, supported by cluster pages that cover specific subtopics in depth, all interlinked. An audit reveals where clusters are incomplete, where pillar pages lack supporting content, and where orphaned posts cover subtopics with no internal links connecting them to the broader topic.

How to check: List your core topic areas. For each, identify the pillar page and map every related post or page to it. Flag subtopics your site has not covered that competitors address, and flag cluster pages that have no internal link from the pillar.

What to look for:

• Subtopics with no dedicated page (content gaps)
• Cluster pages that receive no internal links from the pillar or related pages
• Pillar pages that link out to cluster content but the cluster pages do not link back
• Topics covered only in passing within longer posts rather than in dedicated, indexable pages

Tool: Screaming Frog (internal link report, orphan page detection) + a spreadsheet to map pillar-to-cluster relationships manually

Update, Merge, or Delete: A Decision Framework for Old Content

Every page flagged in the steps above needs a clear decision. The three options are update, merge, or delete – and the right choice depends on whether the page has existing authority, whether the topic still has search demand, and whether the content can be meaningfully improved.

Scenario	Decision	Action
Page ranks, traffic is declining, content is outdated	Update	Refresh facts, add depth, improve internal links
Two pages target the same keyword, one has backlinks	Merge	Consolidate into the stronger URL; 301 the other
Page has no traffic, no backlinks, no search demand	Delete	Remove and 301 to the most relevant live page
Page has thin content but covers a unique subtopic	Update	Expand to meet the depth the topic requires
Auto-generated page with no unique value	Delete or noindex	Remove from index; redirect if it has inbound links

How to check: Pull organic traffic data from Google Analytics (or GSC) for the past 12 months. Cross-reference with a backlink check in your preferred link analysis tool. Pages with traffic or backlinks warrant update or merge; pages with neither are deletion candidates.

Tool: Google Search Console + Google Analytics (traffic trend by URL) + Screaming Frog (to confirm redirect chains after merges)

Phase 5: Backlink and Off-Page Audit Checklist (Toxic Links, Disavow, and Competitor Gaps)

Your backlink profile is a vote of confidence from the web – but not every vote helps. A backlink audit separates the links that reinforce your authority from those that could trigger a manual action or algorithmic penalty. The goal is a clean, relevant profile with identifiable gaps you can close.

Toxic Link Identification Criteria

Not every low-quality link warrants action, but certain patterns consistently signal risk. Pull your full link profile using Ahrefs, Semrush, or Google Search Console’s Links report, then flag links that match one or more of these criteria:

• Irrelevant anchor text at scale – exact-match commercial anchors pointing from unrelated domains suggest manipulation. How to check: Export anchor text distribution in Ahrefs or Semrush and filter for over-optimized commercial terms.
• Links from penalised or deindexed domains – if the linking domain has no Google-indexed pages, its link passes no value and may carry risk. Tool: Site: search in Google or a domain-health check in Ahrefs.
• Sitewide or footer links from low-authority domains – a single low-DR domain contributing hundreds of links via a footer widget is a common footprint. Tool: Ahrefs’ “Links per domain” column.
• Link farms and private blog networks (PBNs) – thin content, identical WHOIS data, or cross-linking clusters are indicators. Tool: Majestic’s Trust Flow vs. Citation Flow ratio; a very low TF relative to CF is a PBN signal.
• Paid link patterns – sudden spikes of links from unrelated niches, especially around a product launch, can look manipulative. Tool: Ahrefs’ referring domains graph filtered by acquisition date.

Do not disavow every low-DR link. Links from small but legitimate local sites, niche directories, or older editorial mentions are usually harmless. Focus disavow action on links that are both low-quality and appear manipulative in pattern.

Building and Submitting a Disavow File

Google’s disavow tool is a last resort – use it only after attempting to remove links manually. The process:

1. Request removal first. Contact the linking site’s webmaster. Document every outreach attempt (date, contact method, response). Tool: A simple spreadsheet tracking domain, contact email, date sent, and outcome.
2. Compile the disavow list. Disavow at the domain level where possible (domain:example.com) rather than individual URLs, unless only specific pages are problematic. Tool: Export flagged domains from Ahrefs or Semrush into a plain-text .txt file.
3. Format the file correctly. Each domain entry on its own line, prefixed with domain:. Add comment lines (starting with #) to document why each domain is included – this helps if you ever need to audit the file later.
4. Submit via Google Search Console. Navigate to the Disavow Links tool under the Manual Actions section of GSC, select your property, and upload the file. Google processes submissions over several weeks.
5. Keep a versioned archive. Save each disavow file with a date stamp. If you later acquire a site or merge properties, you’ll need the history.

Review your disavow file at least annually. Links you disavowed years ago may now be from legitimate sites that changed ownership.

Competitor Backlink Gap Analysis Method

A gap analysis identifies domains linking to competitors but not to you – these are your highest-probability link acquisition targets because the site has already demonstrated willingness to link to content in your niche.

6. Select two to four direct competitors. Choose sites ranking for the same primary keywords, not just the same industry. Tool: Ahrefs’ “Link Intersect” or Semrush’s “Backlink Gap” report.
7. Filter for relevant, high-authority domains. Sort by DR (Ahrefs) or Authority Score (Semrush) and remove domains that link to every competitor – those are likely directories or aggregators with low editorial value.
8. Categorise gap opportunities by link type:

• Resource pages – pitch your best data or guide as a resource addition.
• Broken link targets – find pages on competitor sites that have gone dead and offer your content as a replacement.
• Guest post sources – sites that have published competitor bylines are often open to similar pitches.

9. Prioritise by relevance over raw authority. A DR 45 site in your exact niche will likely outperform a DR 80 general news site for topical authority signals.
10. Log targets in a CRM or outreach tracker. Record domain, contact, link type, and status. Tool: Ahrefs’ built-in prospecting export, Pitchbox, or a Google Sheet.

Run a competitor gap analysis at the start of any link-building campaign and revisit it quarterly – competitor profiles shift, and new gap opportunities appear as the market evolves.

Phase 6: Monitoring, Reporting, and Audit Cadence

A one-time audit captures a snapshot; a repeatable cadence turns that snapshot into a program. The goal of this phase is to assign every audit area a review frequency, a responsible tool, and a realistic time estimate – so nothing falls through the cracks between major audits.

What to Check Monthly vs. Quarterly vs. Annually

How often should you do an SEO audit? It depends on the area, because different audit areas decay at different rates. Crawl errors and Core Web Vitals can shift after a single deployment; backlink profiles and content gaps move more slowly. Matching review frequency to decay rate prevents both over-auditing low-volatility areas and under-auditing high-volatility ones.

The schedule below reflects general practitioner guidance, not a fixed standard. Adjust frequency based on site size, publishing volume, and development pace.

Audit Area	Recommended Frequency	Primary Tool	Time Required
Crawl errors and index coverage	Monthly	Google Search Console	30-60 min
Core Web Vitals (LCP, INP, CLS)	Monthly	PageSpeed Insights / GSC	30-60 min
Organic traffic and ranking shifts	Monthly	Google Search Console + Analytics	45-60 min
Internal links and orphan pages	Quarterly	Screaming Frog SEO Spider	1-2 hrs
On-page elements (titles, meta, schema)	Quarterly	Screaming Frog / Search Console	2-3 hrs
Backlink profile and toxic link review	Quarterly	Ahrefs or Semrush	1-2 hrs
Content audit (thin pages, cannibalization)	Quarterly	Screaming Frog + GSC	2-4 hrs
Full technical SEO audit	Annually	Screaming Frog + GSC + PageSpeed	4-8 hrs
Competitor backlink gap analysis	Annually	Ahrefs or Semrush	2-3 hrs
Site architecture and URL structure review	Annually	Screaming Frog	2-4 hrs

Monthly checks should be lightweight – flag anomalies, not rebuild the audit from scratch. Quarterly reviews are where you act on patterns. The annual full audit is the moment to reassess site architecture, revisit the disavow file, and realign content to topical clusters.

Reporting Findings So Stakeholders Actually Act

Audit findings that stay in a spreadsheet rarely get fixed. Effective reporting translates technical observations into business language: lost traffic, missed conversions, and competitive exposure – not just error counts.

A practical reporting structure has three layers:

1. Executive summary (one page): What changed, what it means for traffic or revenue, and the top three actions required. No jargon.
2. Priority fix list: Each issue ranked by impact and effort, with the responsible team (SEO, dev, content) and a suggested deadline. The next section covers the prioritization method in detail.
3. Evidence appendix: Screenshots from Google Search Console, crawl exports, and Core Web Vitals data for anyone who wants to verify the findings.

For monthly check-ins, a shared dashboard in Google Looker Studio or a simple Google Sheets tracker is usually sufficient. Quarterly reviews warrant a short written report. The annual audit typically needs a presentation with before/after comparisons and a roadmap.

One governance habit that prevents audit fatigue: assign a single owner for each audit area in the cadence table above. When ownership is diffuse, monthly checks get skipped. When one person is accountable for crawl errors and a different person owns content quality, both areas get consistent attention.

What to Fix First: The 80/20 Rule and the Impact vs. Effort Priority Matrix

In SEO, the 80/20 rule – formally the Pareto principle – holds that a small fraction of your audit findings will account for the majority of your potential ranking and traffic gains. Applied to the SEO audit factors in this checklist, this means that fixing crawlability blockers, title tag gaps, and a handful of high-authority link opportunities will typically move the needle far more than resolving every minor warning in a crawl report. The principle is not a precise formula; it is a decision filter that stops teams from treating a 400-item issue list as a flat to-do queue.

The 80/20 Rule in SEO: Which 20% of Fixes Drive 80% of Gains

A structured SEO audit is the starting point for every meaningful ranking improvement – but only if you know which findings to act on first. The way to identify that high-value minority is to score every finding on two axes: how much organic traffic or ranking improvement it is likely to produce, and how much development or editorial effort it requires.

Plotting findings on a simple two-by-two grid produces four quadrants:

• High impact, low effort – fix immediately. These are your quick wins: missing or duplicate title tags, pages blocked in robots.txt that should be indexed, broken internal links to high-traffic pages, missing canonical tags causing duplicate-content dilution, and absent alt text on image-heavy pages. None of these require engineering sprints, and each removes a direct ranking obstacle.
• High impact, high effort – plan and resource. Core Web Vitals remediation (especially LCP on large e-commerce category pages), JavaScript rendering overhauls, and site architecture restructuring belong here. The payoff is significant, but the work requires developer time and a proper project brief. Schedule these in the next sprint cycle rather than letting them languish.
• Low impact, low effort – batch and automate. Meta description rewrites on pages with low impressions, minor schema additions, and small image compression tasks can be handled in bulk or templated. Do them, but do not let them crowd out the high-impact work.
• Low impact, high effort – deprioritize or drop. A full URL restructure on a site with stable rankings, or disavowing a handful of borderline links on a domain with a strong profile, rarely justifies the risk and resource cost. Park these unless a specific business trigger changes the calculus.

Quick Wins vs. Major Projects: Sequencing Your Fix List

Once you have placed every finding in a quadrant, sequence the work in three waves.

Wave 1 – Unblock and fix (weeks 1-4). Address everything in the high-impact, low-effort quadrant first. In practice, this usually means: correcting indexability errors surfaced in Google Search Console, fixing broken redirects, resolving duplicate title tags at scale, and adding missing structured data to pages already ranking on page two. These changes require no new content and minimal dev involvement, so they can ship quickly and begin influencing crawl behavior within the next index cycle.

Wave 2 – Build and improve (weeks 5-12). Move to the high-impact, high-effort items. Prioritize within this quadrant by business value: a slow-loading product page on a high-revenue category outranks a slow-loading blog post. Assign each item an owner, a definition of done, and a target ship date. Without that structure, high-effort fixes stall indefinitely.

Wave 3 – Maintain and optimize (ongoing). Batch the low-impact, low-effort items into regular maintenance cycles – monthly for meta updates, quarterly for schema audits. Revisit the deprioritized quadrant at each quarterly audit to check whether site growth or algorithm changes have shifted the impact assessment.

The matrix works because it forces an explicit trade-off conversation before any work begins. A crawl report that surfaces 600 issues looks overwhelming; the same list sorted into four quadrants becomes a manageable project plan with a clear starting point.

Common SEO Audit Mistakes to Avoid

When teams get how to do SEO audit work wrong, it is rarely during the crawl – it is in how findings are scoped, prioritized, and communicated. The technical work is the easier part. These are the process errors that turn a thorough audit into a shelf document.

The most common mistakes auditors make include:

• Treating the audit as a one-time project rather than a recurring process
• Auditing every page and issue with equal weight instead of filtering by impact
• Ignoring how Googlebot renders JavaScript-heavy pages versus how a browser renders them
• Skipping mobile-specific checks and assuming desktop findings apply universally
• Failing to communicate findings in business terms stakeholders can act on
• Fixing low-effort, low-impact issues first because they are easy to close
• Omitting a disavow review when the backlink profile has grown significantly since the last audit
• Conflating crawl errors with indexation problems – not every crawl error hurts rankings

Treating the Audit as a One-Time Event

A site audit captures a snapshot. Algorithms update, content is published, and technical configurations drift – so findings from six months ago may no longer reflect the site’s actual state. Scheduling recurring audits (monthly crawls, quarterly deep reviews) is what converts a one-time report into a durable performance system. Without that cadence, fixes made in one quarter can be quietly undone by a CMS update or a developer pushing a new redirect rule.

Auditing Everything Equally Instead of by Impact

Crawlers surface hundreds of issues. Treating a missing alt attribute and a broken canonical tag as equivalent problems wastes the fix budget. The matrix below maps twelve common audit findings by impact and effort so you can sequence work rationally rather than by issue count.

	Low Effort	High Effort
High Impact	Quick Wins: Fix broken internal links · Add missing title tags · Submit XML sitemap	Major Projects: Site speed overhaul · Content consolidation · Backlink disavow campaign
Low Impact	Fill-ins: Update alt text · Fix redirect chains · Correct meta descriptions	Deprioritize: Redesign URL structure · Full site migration · Rebuild navigation

Start with Quick Wins – they return the most ranking value per hour spent. Schedule Major Projects with dev and content teams. Batch Fill-ins into sprint work. Deprioritize the bottom-right quadrant unless a business reason forces it.

Ignoring Mobile and Rendering Differences

Google indexes the mobile version of a page first. An audit that only checks desktop rendering can miss viewport issues, tap-target failures, and content that loads differently on mobile – all of which affect both rankings and Core Web Vitals scores. Separately, JavaScript-rendered content that appears in a browser may not be visible to Googlebot if the crawler times out before the script executes. Always test rendered HTML in Google Search Console’s URL Inspection tool alongside your crawler output.

Skipping Stakeholder Communication After Findings

An audit that produces a spreadsheet no one reads has zero ROI. The findings need to be translated into prioritized actions with clear owners – developers for technical fixes, content teams for thin pages, marketing for backlink gaps. Without that handoff, even a technically excellent audit stalls. Frame each finding as a business risk or opportunity (lost traffic, missed conversions, competitor advantage) rather than a technical observation, and assign a named owner to every item in the Quick Wins and Major Projects quadrants before the audit review meeting ends.

Can ChatGPT Do an SEO Audit? AI-Assisted Auditing Explained

ChatGPT and similar large language models can assist with specific parts of an SEO audit – particularly content analysis, gap identification, and drafting recommendations – but they cannot replace the crawl-based, live-data work that a full audit requires. Think of AI as a capable research and writing assistant that works on text you supply, not a tool that can independently access your site, read server logs, or measure real-time Core Web Vitals.

What AI Tools Can Do: Content Gap Analysis and Draft Recommendations

When you paste in a page’s copy, a list of target keywords, or a competitor’s content outline, AI models can quickly identify missing subtopics, flag thin coverage, and suggest heading structures that better match search intent. This makes them genuinely useful for the content audit phase: you can prompt a model to compare your existing article against a topic outline and surface gaps a manual SEO audit might spend hours finding.

AI is also effective at drafting meta titles and descriptions at scale, rewriting thin introductions, generating schema markup templates, and producing first-draft recommendations from a list of crawl findings you paste in. If your Screaming Frog export flags three hundred pages with duplicate title tags, an AI model can help you draft a prioritized fix list and write replacement titles faster than doing it by hand.

For keyword clustering and topical authority mapping, AI can group a keyword list by intent and suggest which URLs should target which cluster – useful groundwork before you restructure internal linking.

What AI Tools Cannot Do: Crawl Data, Log Files, and Live Site Rendering

AI models have no ability to crawl your site, fetch live URLs, or read your server’s log files. They cannot measure Largest Contentful Paint, detect a misconfigured robots.txt blocking Googlebot, identify orphan pages, or verify whether your XML sitemap matches what Google has indexed. Any output an AI produces about your site’s technical health is based entirely on text you provide – it cannot observe the site itself.

This matters because the highest-impact audit findings – crawlability blocks, indexability errors, Core Web Vitals failures, and toxic backlink patterns – all require dedicated tools: Google Search Console, a crawler like Screaming Frog, a log file analyzer, and a backlink platform. AI cannot substitute for any of these.

The practical workflow is to use dedicated audit tools to generate the data, then use AI to help interpret findings, draft recommendations, and communicate results to stakeholders. That combination is faster than either approach alone, but the data must come from the tools – not from the model’s training memory, which may be months or years out of date.

Top 5 SEO Audit Tools for a Full Site Audit

The five tools that cover a full site audit are Screaming Frog, Google Search Console, Ahrefs or Semrush, PageSpeed Insights, and Google Rich Results Test. Together they address every major audit phase: Screaming Frog handles crawl-level technical discovery, Google Search Console surfaces indexing and performance data directly from Google, Ahrefs or Semrush power backlink and keyword analysis, PageSpeed Insights diagnoses Core Web Vitals, and Google Rich Results Test validates structured data.

The table below maps each tool to its primary audit task and the phase where it delivers the most value.

Tool	Best For	Audit Phase
Screaming Frog	Crawl-level technical issues: broken links, redirect chains, missing tags, duplicate content	Technical SEO
Google Search Console	Indexing status, search performance, manual actions, Core Web Vitals field data	Technical & On-Page
Ahrefs or Semrush	Backlink profile, toxic link identification, keyword gap, competitor analysis	Off-Page & Content
PageSpeed Insights	Core Web Vitals lab and field data, render-blocking resource diagnosis	Technical SEO
Google Rich Results Test	Schema markup validation, eligibility for rich results	On-Page SEO

Screaming Frog for Crawl-Level Technical Issues

Screaming Frog SEO Spider crawls a site the way Googlebot does, returning a structured export of every URL, status code, title tag, meta description, canonical, and heading. For a technical SEO audit checklist, it is the fastest way to surface broken internal links, redirect chains longer than one hop, pages blocked by robots.txt, and duplicate title tags at scale. The free tier crawls up to 500 URLs; the paid licence removes that cap and adds JavaScript rendering, log file analysis, and scheduled crawls.

Google Search Console for Indexing and Performance Data

Google Search Console is the only tool that shows how Google itself sees the site. The Coverage report identifies pages excluded from the index and the reason why. The Performance report shows impressions, clicks, and average position by query and URL. Core Web Vitals field data – based on real Chrome users – appears here before it surfaces anywhere else. No third-party crawler can replicate this data, which makes GSC a non-negotiable starting point for any audit.

Ahrefs or Semrush for Backlink and Keyword Analysis

Both platforms maintain large link indexes and keyword databases that GSC does not provide. For a backlink profile audit, either tool lets you export referring domains, identify low-quality or irrelevant links, and compare your link profile against competitors to find acquisition gaps. For content audits, their keyword data shows which pages rank for unintended queries – a reliable signal of cannibalization. The choice between them is largely a matter of workflow preference and existing licence access; both are industry-standard for this phase.

PageSpeed Insights for Core Web Vitals Diagnostics

PageSpeed Insights combines Google’s Lighthouse lab scores with Chrome User Experience Report (CrUX) field data for a given URL. Lab data identifies specific render-blocking resources, image sizing issues, and unused JavaScript. Field data shows whether real users are experiencing LCP, INP, and CLS within Google’s thresholds. Running PageSpeed Insights on key templates – homepage, category page, product page – gives a representative picture without crawling every URL.

Choosing Between Free and Paid Tools

Three of the five tools above are free: Google Search Console, PageSpeed Insights, and Google Rich Results Test. Screaming Frog’s free tier is sufficient for smaller sites. The cost of the audit toolkit, for most teams, comes down to whether a paid Ahrefs or Semrush subscription is already in place. For sites under 500 URLs with no active link-building programme, a free-only stack covers the majority of audit tasks. Larger sites or those with competitive backlink gaps will need one of the paid link-intelligence platforms to complete the off-page phase.

Ecommerce SEO Audit Checklist: Faceted Navigation, Product Schema, and Duplicate Pages

Ecommerce sites generate SEO problems that general audits miss entirely – filtered URLs that multiply crawlable pages into the thousands, product schema that breaks when inventory changes, and category structures that produce near-identical pages competing for the same queries. An ecommerce SEO audit checklist addresses these patterns directly.

Faceted Navigation and Filtered URL Parameters

Faceted navigation – the filter menus that let shoppers sort by size, color, price, or brand – is the single largest source of duplicate and low-value URLs on most ecommerce sites. Each filter combination can generate a unique URL, and without controls, Googlebot wastes crawl budget on thousands of pages that carry no distinct ranking value.

Audit your filtered URLs with these checks:

• Identify parameter-generated URLs – Crawl the site with Screaming Frog and filter for URLs containing query strings (e.g., ?color=red&size=M). Flag any that are indexable.
• Verify robots.txt or noindex directives – Confirm that low-value filter combinations are either blocked from crawling or tagged noindex. Check Google Search Console’s Coverage report for unexpected indexed parameter URLs.
• Audit canonical tags on filtered pages – Each filtered URL should canonicalize to the base category page unless the filtered view has genuine standalone search demand.
• Review internal links to filtered URLs – Screaming Frog’s inlinks report shows whether navigation widgets are passing link equity to parameter pages that should be excluded.
• Check crawl budget consumption – In GSC’s Crawl Stats report, a high ratio of crawled-but-not-indexed URLs often signals uncontrolled faceted navigation.

Product Schema Markup Validation

Product schema enables rich results – price, availability, and review stars – that improve click-through rates in organic listings. Ecommerce sites frequently deploy schema at launch and then let it drift as inventory, pricing, and reviews change.

Validate product schema with these steps:

• Run Google’s Rich Results Test on representative product pages – Check at least one page from each product template, not just a single flagship product.
• Confirm required properties are present – name, image, description, offers (with price, priceCurrency, and availability) are required for eligibility.
• Check for out-of-stock or discontinued products still marked `InStock` – Stale availability data can trigger manual actions. Cross-reference your inventory feed against live schema.
• Validate aggregate review schema – If aggregateRating is present, confirm the ratingCount and ratingValue reflect current data, not a hardcoded launch value.

Duplicate Category and Product Pages

Ecommerce catalog structures routinely produce duplicate content through pagination, sorting variants, breadcrumb permutations, and products listed under multiple categories.

Audit duplicate and near-duplicate pages with these checks:

• Crawl for duplicate title tags and meta descriptions – Screaming Frog’s duplicate content reports surface category pages that share titles because they pull from the same template field.
• Audit paginated series – Confirm that /category/page/2 and beyond either use rel=”next”/”prev” (if your CMS supports it) or carry a noindex tag, depending on your chosen approach.
• Check canonical consistency across product variants – Color and size variants that live on separate URLs should canonicalize to the primary product page unless each variant has meaningful distinct search demand.
• Review thin category pages – Categories with fewer than a handful of products often lack enough content to rank. Flag them for content expansion or consolidation.
• Audit session IDs and tracking parameters – URL parameters appended by analytics or affiliate systems create duplicate pages. Declare them in GSC’s URL Parameters tool or strip them server-side.

Local SEO Audit Checklist: Google Business Profile, NAP, and Citations

For businesses that depend on foot traffic or serve a defined geographic area, local SEO failures are often invisible until rankings drop – a mismatched phone number or an unclaimed Business Profile can quietly suppress visibility in local pack results. A local SEO audit checklist targets the signals Google uses to verify business identity and proximity relevance.

Google Business Profile Completeness and Accuracy

Start by claiming and verifying ownership of every location in Google Business Profile (GBP). Then audit each profile against this checklist:

• Business name: Matches the legal or commonly used trading name exactly – no keyword stuffing. How to check: Compare GBP name to signage, website header, and legal registration. Tool: Google Business Profile dashboard.
• Primary and secondary categories: Primary category reflects the core service; secondary categories cover adjacent offerings. How to check: Review category options in GBP and compare to top-ranking local competitors. Tool: GBP dashboard or BrightLocal.
• Address and service area: Physical address is accurate; service-area businesses hide the address if they don’t serve customers at the location. How to check: Cross-reference GBP address with the website contact page. Tool: GBP dashboard.
• Phone number: Uses a local number, not a tracking number that differs from the website. How to check: Compare GBP phone to the website’s footer and schema markup. Tool: Manual check plus Google Rich Results Test for LocalBusiness schema.
• Website URL: Points to the correct landing page – a location-specific page, not the generic homepage, for multi-location businesses. How to check: Click through from GBP and confirm the destination. Tool: GBP dashboard.
• Hours of operation: Current and updated for holidays. How to check: Compare to posted hours on the website and any third-party listings. Tool: GBP dashboard.
• Photos and posts: Profile includes interior, exterior, and product/service images; GBP posts are active. How to check: Audit photo count and post recency in the GBP dashboard. Tool: GBP dashboard.
• Q&A and reviews: Unanswered questions and unacknowledged reviews are audit failures. How to check: Open the public GBP listing and scan the Q&A and Reviews tabs. Tool: GBP dashboard.

NAP Consistency Across Directories and Citations

NAP – Name, Address, Phone – must be identical across every directory, citation, and social profile. Even minor formatting differences (“St” vs. “Street”, a suite number present in one listing but absent in another) create conflicting signals.

• Audit existing citations: Pull a full citation report to identify every directory where the business appears. How to check: Run a citation audit. Tool: BrightLocal Citation Tracker or Semrush Listing Management.
• Identify NAP mismatches: Flag any listing where name, address, or phone differs from the canonical version on the website. How to check: Export citation data and compare each field to the website’s contact page. Tool: BrightLocal or Moz Local.
• Suppress or correct duplicate listings: Duplicate GBP listings or duplicate directory entries split authority and confuse users. How to check: Search the business name in Google Maps and major directories. Tool: GBP dashboard for Google; manual search or BrightLocal for directories.
• LocalBusiness schema on the website: Confirm the website’s structured data encodes the canonical NAP and matches GBP exactly. How to check: Run the homepage and contact page through Google’s Rich Results Test. Tool: Google Rich Results Test.
• Location pages for multi-location businesses: Each location needs a dedicated, indexable page with unique content, embedded map, and location-specific LocalBusiness schema. How to check: Crawl the site and confirm each location URL is indexable and not duplicated. Tool: Screaming Frog.

After correcting mismatches, re-run the citation audit within four to six weeks to confirm propagation across directories.

Conclusion

The six phases above give you a complete, ordered path from initial setup through ongoing monitoring. Work through them in sequence, log every finding with a clear owner and priority tier, and schedule the recurring cadence before the first audit is even complete – that habit is what separates a one-time report from a system that compounds over time.

If you’re ready to start, the downloadable SEO audit checklist template alongside this article has one Google Sheets tab per phase so your team can track progress without rebuilding the structure from scratch.