Skip to content

Checklist · 10 min read

SEO Audit ChecklistFinding what actually holds you back

Diagrams
02
Tools
03
Sections
06

The short answer

An SEO audit is a structured review of a website to find the issues that most limit its search visibility and the opportunities most likely to grow it. A useful audit is prioritised, not exhaustive: it checks measurement, indexing, technical health, content and intent, internal links and authority, then ranks fixes by business impact and effort.

What a good audit is for

Most SEO audits are too long to act on. An automated crawl produces hundreds of warnings, a report lists them all with equal weight, and the team either freezes or fixes the easy, unimportant items first. The audit becomes a document rather than a decision.

A good audit answers three questions: what is stopping important pages from being found, what is stopping them from being chosen, and what would most grow qualified visibility from here? Everything in the checklist below serves one of those questions. If a finding does not, it goes in an appendix, not the summary.

An audit that lists everything has prioritised nothing.

Audit in the order problems compound

Problems lower in the stack cap everything above them. Checking content quality before confirming pages are indexed wastes effort; checking links before fixing cannibalisation misreads the situation. Work from the base upward.

Fig. 01 · Stack

The audit stack, top to bottom

  1. Authority

    Links, mentions, brand demand

  2. Architecture and internal links

    Depth, orphans, anchor text, hubs

  3. Content and intent

    Quality, coverage, cannibalisation, freshness

  4. Technical health

    Crawl, render, canonicals, speed, mobile

  5. Indexing

    What is in, what is out, and why

  6. Measurement

    Can we trust the data at all?

Audit bottom-up, report top-down. Leaders want opportunities first; fixes must happen foundations first.

The audit, section by section

1. Measurement: can you trust the numbers?

Before diagnosing anything, confirm that the data is sound. Broken analytics, missing Search Console properties or untracked conversions make every later conclusion unreliable. This step is often skipped and is the reason many audits reach wrong conclusions.

Checklist

0/6

Measurement checks

2. Indexing: what is in, what is out

Compare three lists: the pages you want indexed, the pages search engines report as indexed, and the pages a crawl finds. Differences between them are the most valuable findings in any audit. Important pages excluded from the index are urgent; large numbers of unimportant pages included are a quality and crawl problem.

  • Review the page indexing report in Search Console for excluded important URLs and their stated reasons.
  • Check for accidental noindex tags, robots.txt blocks and canonical tags pointing elsewhere.
  • Look for soft 404s: thin or empty pages returning a 200 status.
  • Identify index bloat: tag archives, parameter URLs, internal search results and staging pages that should not be in search.

3. Technical health

Assess technical issues by template and by the number of important pages affected. Our technical SEO guide explains each area in depth; the audit simply records status and scale.

Checklist

0/10

Technical checks

4. Content and intent

This is where audits usually find the largest opportunities and spend the least time. For each priority topic, check whether a page exists, whether it matches the search intent revealed by the results, and whether it is genuinely better than what ranks.

  • Coverage gaps: valuable topics with no page at all.
  • Cannibalisation: several pages competing for the same intent, splitting signals.
  • Thin or outdated pages: little substance, old facts, broken examples.
  • Intent mismatch: the wrong format for what the results reward.
  • Near misses: pages ranking in positions roughly 5 to 20 that could move up with substantive improvement.
  • Experience and trust: visible authorship, first-hand evidence and accurate information, especially on advice pages.

Decide the fate of weak pages using a consistent method; our content pruning guide gives one. The audit should state how many pages fall into each action, not just list them.

5. Architecture and internal links

Check how deep important pages sit, which pages receive the most internal links, and whether that matches business priority. Commonly, the pages that matter most are buried, while the about page and old blog posts receive the bulk of links through navigation and footers.

  • Click depth of priority pages from the home page.
  • Orphan pages with no internal links.
  • Anchor text quality: descriptive versus generic.
  • Hub pages: does each major topic have one, linking to its supporting pages?

6. Authority and reputation

Review the link profile at a summary level: which pages earn links, whether competitors have materially stronger references, and whether old URLs with links now return errors. Look for unlinked mentions and broken backlinks to reclaim. Note any obviously manipulative links, but most sites do not need a disavow exercise.

7. Search features and AI visibility

Finally, look at how your priority queries are actually presented. Which results features appear: AI summaries, local packs, shopping listings, videos, question boxes? Do you appear in them, and are competitors cited where you are not? This tells you whether the opportunity is ranking higher, or appearing in a different part of the page entirely.

Check how AI assistants describe your business when asked directly about your category. Inaccurate or missing descriptions usually trace back to unclear positioning on your own site or inconsistent information across profiles. Note these as findings; the remedies are covered in generative engine optimisation.

Tools are inputs, not verdicts

Crawlers, rank trackers and site-health scores are indispensable for collecting data and useless as judges. A health score of ninety can hide a deindexed product range; a score of sixty can describe a site whose only problems are cosmetic. Never report a tool's score as the audit's conclusion.

Use tools for scale and humans for judgement. The person reviewing findings should understand the business: which templates earn revenue, which sections are strategic, which pages exist for legal or customer-service reasons. That context is what turns a list of warnings into a sensible plan.

Prioritising what you found

Fig. 02 · Scorecard

How to rank audit findings

Bars show relative emphasis, not measured data

Weights express relative emphasis in prioritisation, not measured effects. Multiply impact by confidence, then divide by effort.

Present the result as a short list: perhaps five to ten actions, each with an owner, an estimate and the reason it matters. Put the full findings in an appendix for the people implementing them. Leaders should be able to read the first page and know what will happen next.

Self-diagnostic

0/5

Is your audit report usable?

Test the audit document itself before you share it.

  1. 01Does the first page list fewer than ten prioritised actions?

    If yes: Good; people can act on it. If no: Cut and rank. Move the rest to an appendix.
  2. 02Does each action have an owner and a reason?

    If yes: It is ready for a delivery plan. If no: Assign owners before circulating.
  3. 03Are findings grouped by template rather than listed by URL?

    If yes: Fixes will scale across the site. If no: Regroup; URL lists hide patterns.
  4. 04Did you verify measurement before drawing conclusions?

    If yes: Your conclusions rest on sound data. If no: Check tracking first; conclusions may be wrong.
  5. 05Is there a date to re-audit and confirm fixes worked?

    If yes: The audit becomes a cycle, not a document. If no: Set one; unvalidated fixes often fail quietly.

How often to audit

A full audit once or twice a year suits most sites, plus a focused audit before and after any redesign or site migration. Between audits, a monthly review of indexing, experience and performance reports catches regressions early. The real goal is to need fewer big audits because small checks have become routine.

Key takeaways

  1. 01A useful audit is prioritised, not exhaustive, and leads with a short list of actions.
  2. 02Audit from the foundations up: measurement, indexing, technical, content, architecture, authority.
  3. 03The largest opportunities usually sit in content and intent, not in technical warnings.
  4. 04Group findings by template so fixes scale across the site.
  5. 05Assign owners, set a re-audit date and confirm that fixes actually registered.

Frequently asked

What should an SEO audit include?
A complete audit covers measurement accuracy, indexing status, technical health, content quality and intent match, site architecture and internal links, and authority from external links and mentions. Crucially, it ends with a prioritised action list ranked by business impact, confidence and effort, rather than an unranked list of every warning.
How long does an SEO audit take?
It depends on the size and complexity of the site. A small business site can be reviewed in days; a large ecommerce or multi-market site may take several weeks, mainly because content, logs and templates take time to analyse properly. Automated crawls are fast; the judgement is what takes time.
Can I do an SEO audit myself?
Yes, for the fundamentals. Search Console, a crawling tool and a careful review of your key pages against live results will reveal most important issues on a small site. Larger sites, migrations and international setups benefit from specialist experience, particularly in prioritising findings correctly.
What is the most common issue found in SEO audits?
There is no universal answer, but patterns recur: important pages excluded from the index, multiple pages competing for the same query, thin or outdated content, and priority pages buried deep in the site structure. Purely cosmetic technical warnings are common too, but they rarely matter.

Published by Fabulous.Media, a network of specialist marketing agencies. Updated 9 October 2026. Platform features change often; check current official documentation before acting on platform-specific detail.

Read next

Prefer a specialist to do this with you? The network has a house for every discipline in this library.

Request an Introduction