SEO Audit Checklist

TL;DR — An SEO audit is a health check for your website: you look at whether search engines can find and understand your pages, whether the on-page basics are in place, whether your content is actually good, and whether other sites link to you. The trick is not to check everything. You find the biggest, most fixable problems and hand back a short list — not a giant report nobody reads.

Evidence for this claim Google Search Console provides performance and indexing reports that can inform an SEO audit. Scope: Google-owned search data; supplement with crawl and business data. Confidence: high · Verified: 2026-07-14 Google Search Console: Get started Evidence for this claim Google's SEO Starter Guide organizes the core work around crawlability, useful content, links, and search appearance. Scope: Baseline Google guidance, not a complete audit methodology. Confidence: high · Verified: 2026-07-14 Google Search Central: SEO Starter Guide

What an SEO audit is

An SEO audit is a review of your website to find what’s stopping it from showing up well in search — and to produce a short list of fixes worth doing. That’s it. It covers four areas:

1. Technical — can search engines crawl and index your pages at all?
2. On-page — do your titles, meta descriptions, headings, and images check out?
3. Content — is your content genuinely helpful, and are there gaps or stale pages?
4. Off-page — do other sites link to you, and are any of your linked pages broken?

There’s also a newer, fifth area a lot of people are starting to add: whether AI answer engines (like AI Overviews or ChatGPT) can find and cite you. It’s worth a look, but nobody has it fully figured out yet, so treat it as a “keep an eye on it” item, not a scoreboard.

The one thing to get right

The biggest mistake beginners make is thinking a longer audit is a better audit. It isn’t. The free SEO audit template I helped build at Ahrefs makes this point up front: “That’s why our template only has 13 steps, not an overwhelming 100-200 like many others.” The reasoning is simple — “It’s better to spend 80% of your time fixing the 20% of things that matter.”

So don’t try to catalog every imperfection. Find the handful of things holding you back and fix those.

A first-pass checklist anyone can run

You can do a real first audit with free tools:

• Is your site being indexed? Google’s own starter guide suggests you “try searching on Google for your site with the site: search operator” (type site:yourdomain.com). If nothing shows up, that’s your number-one problem.
• Set up Google Search Console (and Bing Webmaster Tools) — the free control panels the search engines give you. Check the Page Indexing report for pages that aren’t getting indexed.
• Run a free crawl. A free Ahrefs Webmaster Tools account (or Screaming Frog for up to 500 URLs) will crawl your site and flag broken links, missing titles, missing image alt text, and slow pages.
• Read your titles and descriptions. Do your important pages have a clear, unique title tag and a meta description? Missing and duplicate ones are the most common thing audits find.
• Look at your content honestly. Is it “helpful, reliable, and people-first,” as Google puts it? Are there obvious topics you should cover but don’t?
• Check who links to you. Do you have any broken pages that other sites still link to? Those are easy wins to recover.

Then — and this is the part beginners skip — write down only the 5 to 10 biggest issues and start fixing them in order of “how much will this help vs. how hard is it.” Want the full framework, the tools, and the data behind what actually shows up in real audits? Switch to the Advanced tab.

TL;DR — A full SEO audit spans technical, on-page, content, and off-page — plus an emerging AI-visibility layer — but its output is a prioritized plan, not an inventory. Start from the pain point, scope so it’s manageable, gather data with a crawler + Search Console + analytics, then triage by impact vs. effort. Fix crawling/indexing gatekeepers first, but spend most of your time on content unless something technical is genuinely broken. Ship 5–10 findings in a format people will actually implement. For the technical-only deep dive, use the sibling Technical SEO Checklist; for very large sites, the Enterprise SEO Audit.

Evidence for this claim Google Search Console provides performance and indexing reports that can inform an SEO audit. Scope: Google-owned search data; supplement with crawl and business data. Confidence: high · Verified: 2026-07-14 Google Search Console: Get started Evidence for this claim Google's SEO Starter Guide organizes the core work around crawlability, useful content, links, and search appearance. Scope: Baseline Google guidance, not a complete audit methodology. Confidence: high · Verified: 2026-07-14 Google Search Central: SEO Starter Guide

What this audit is — and what it isn’t

This is the broad, full-site audit. It’s deliberately wider than the Technical SEO Checklist, which is the technical-only floor — crawlability, indexing, HTTPS, Core Web Vitals, structured data, sitemaps, robots.txt, canonicalization, mobile. When you need the deep technical diagnosis, go there. This article covers all of that plus on-page, content, and authority, and — more than anything — how to prioritize across all of it.

It’s also distinct from the size- and vertical-specific audits. Auditing a huge multi-team, multi-CMS site is a genuinely different job (you scope by template, not by page) — that’s the Enterprise SEO Audit. Storefronts have their own faceted-nav and variant problems (the Ecommerce SEO Audit), and multi-region sites add hreflang and geotargeting (the International SEO Audit). This general audit is the baseline the enterprise version explicitly departs from.

The philosophy: prioritize, don’t enumerate

The differentiating thesis of a good audit is that exhaustiveness is not rigor. The 1-million-domain site audit study I ran at Ahrefs makes the point in the “What should you fix?” section: “Sometimes, the best course of action is to do nothing because the costs outweigh the benefits.” Not every flag is a problem worth your time.

On the Voices of Search podcast I put the ordering heuristic plainly: “Most of your time is better spent fixing your content unless you have some huge issues with crawling or indexing or something.” That’s the whole prioritization logic in one sentence — technical gatekeepers first if they’re broken, otherwise content is usually where the return is.

And when you deliver, keep it short. In the enterprise-audit context I’ve written that “SEO checklists are impractical at scale” and — the line that generalizes to any site — “I’ve seen several hundred-page documents detailing everything you checked, but no one is going to read those.” The output that gets implemented is “reporting on 5-10 main issues or opportunities.”

The audit process (not just the checklist)

A checklist is what you look at. A process is how you turn it into results. Scaled down from the enterprise version, the shape is:

1. Start from the pain point. Even for a solo site owner, ask “what’s actually wrong?” before you crawl anything. As I’ve said about client work: “If clients are coming to you asking for an audit, they already have a pain point. Talk to them. Solve that one thing and they’ll be happy with the audit.”
2. Set scope, in writing. Decide what you’re auditing (whole site? one section? which templates, markets, or subdomains?) and write it down in a line or two — the properties/sections in scope and who owns each one. That short scope note is what keeps a large or multi-template site from turning into an unscoped crawl of everything.
3. Gather data — and label it. Crawl the site, and pull Search Console + analytics. Keep straight what kind of data each source gives you: Search Console’s Performance and Page Indexing report totals are observed, first-party numbers, but the example URLs GSC lists under an indexing reason are a sample, not a complete inventory of every affected page — don’t treat a handful of examples as the whole picture. On a large or template-driven site, don’t crawl a few convenient URLs and call the result representative; group findings by template, section, or market and sample enough pages from each cohort to say whether an issue is isolated or sitewide.
4. Prioritize. Score findings by impact vs. effort (below). Discard the low-impact noise.
5. Deliver a short report. 5–10 findings, in whatever format your implementers actually use — ideally developer-ticket style, tied to business outcomes.
6. Track implementation, then verify it — don’t assume it. Once something ships, log the release date. A ranking or traffic change after that date isn’t proof the fix worked: Google’s own traffic-drop framework lists concurrent causes — algorithm updates, demand/seasonality shifts, other site changes — that move the same numbers. Watch the specific cohort the fix targeted against a dated baseline for a few weeks before crediting (or blaming) it.

The evidence package every audit finding needs

A finding should be reproducible by someone who did not run the audit. A screenshot without a URL, a crawl warning without settings, or a Search Console count without a collection date is context—not a complete finding.

Store these fields with every material recommendation:

Use evidence hashes to identify the exact saved response, export, configuration, or rendered capture that supported a finding; a hash does not make the source accurate or prove that a dynamic page stayed unchanged. Screenshots are useful for visible state, but pair them with the URL, timestamp, machine-readable capture, and test conditions. Preserve the original capture separately from later annotations.

Label the conclusion honestly:

• Observed: the supplied evidence directly demonstrates the stated behavior.
• Inferred: observations support a likely cause, but do not directly prove it. Evidence for this claim Google's SEO Starter Guide organizes the core work around crawlability, useful content, links, and search appearance. Scope: Baseline Google guidance, not a complete audit methodology. Confidence: high · Verified: 2026-07-14 Google Search Central: SEO Starter Guide
• Not reproduced: the reported behavior was tested under stated conditions and did not occur; this is not proof that it never occurs. Evidence for this claim Google Search Console provides performance and indexing reports that can inform an SEO audit. Scope: Google-owned search data; supplement with crawl and business data. Confidence: high · Verified: 2026-07-14 Google Search Console: Get started
• Not evaluated: the method, access, or scope did not test this claim. Do not turn it into zero, false, healthy, or passed.

Specialized audits should extend this record rather than replace it. Ecommerce adds SKU, variant, market, feed, and fulfillment state; international work adds requested locale, response location, canonical, and hreflang cluster; JavaScript audits add raw versus rendered output and navigation state; migrations add before/after captures, mapping version, and release cohort. AI-search observations have their own measurement methodology for prompts, models, answers, citations, and eligible-run denominators.

When to run an audit (the triggers)

An audit isn’t a one-time project. Run one when:

• Traffic or rankings drop. Google’s official guide to debugging search traffic drops is your checklist here. Its first move: “Check the Crawl stats report and Page indexing report to find if there’s a corresponding spike in issues detected.” Then “Check the Manual Actions report on Search Console to see if any have been issued to your website”, “Check the Security Issues report to find if Google detected a security threat on your website”, and remember that “core updates and other smaller updates may change how some pages perform in Google Search results.” Crucially, Google also flags demand: “Sometimes changes in user behavior will change the demand for certain queries, either due to a new trend, or seasonality throughout the year.” Check Search Console Performance and Google Trends before assuming something broke.
• Before/after a migration or redesign — the highest-risk moments for SEO.
• After an algorithm update — to see what moved and why.
• Before a big content push — to fix the foundation first.
• On a recurring cadence — quarterly for most sites, monthly for large or fast-changing ones. (That’s common practice, not an official Google/Bing cadence — no such official guidance exists.)

The checklist, by category

Technical & crawlability/indexing

Keep this section short here and go deep in the Technical SEO Checklist. The gatekeeping questions: Is the site crawlable (robots.txt not blocking anything important)? Are your important pages actually indexed (Page Indexing report)? Are sitemaps submitted and clean? Is canonicalization consolidating duplicates correctly? Is HTTPS in place and is the site mobile-friendly? If any of these are broken, they jump to the top of the priority list — nothing downstream matters if pages can’t be crawled or indexed.

One official nuance worth checking during the technical pass: rendering. Google warns that “if your site is hiding important components that make up your website (like CSS and JavaScript), Google might not be able to understand your pages.”

On-page

This is where audits find the most, and where the volume can trick you into over-reporting. My 1-million-domain study quantified exactly how common these are — the top of the list:

The catch: common is not the same as important. On meta descriptions specifically, my take from that study is candid: “I don’t focus much on meta descriptions. If it’s a page that’s important to you and you can write a better meta description that fits, go for it.” Fix the on-page issues on pages that matter; don’t burn a week normalizing alt text sitewide because a tool turned 80% of your pages red.

Content

For most sites this is where the real return lives. Audit for:

• Quality. Google’s guidance is that good content is “easy-to-read and well organized,” “unique,” kept up to date, and “helpful, reliable, and people-first.” Assess depth relative to search intent — not word count. (Word count isn’t a ranking factor; don’t flag “thin” pages by a number alone.)
• Gaps. What topics should you cover for your audience that you don’t yet?
• Outdated pages. Updating strong old content usually beats publishing new content. I keep pushing this in talks and podcasts because it’s underrated.
• Pruning candidates. Pages that get no traffic, no links, and serve no purpose.

One myth to kill here: E-E-A-T is not a ranking factor you should score. Google’s own SEO starter guide has a section literally titled “Thinking E-E-A-T is a ranking factor” and answers it “No, it’s not.” It’s content-creation guidance, not an audit metric.

Off-page / authority

• Backlink profile — do you have links from relevant, credible sites, and how do you compare to competitors?
• Dead pages with backlinks — one of the highest-ROI checks. If a page that other sites link to now 404s, you’re leaking authority; redirect it to a relevant live page.
• Brand mentions — unlinked mentions and general brand presence.

A caution on the flip side: don’t over-disavow. Aggressively disavowing “toxic” links is a known industry over-correction. Most sites should not disavow without clear evidence of a manual action or genuine spam impact.

AI / answer-engine visibility (forward-looking)

Newer, and honestly not fully proven yet — keep it principle-level. Can AI crawlers access your content? Is your structured data in place so engines can parse entities? Is your brand showing up (and cited correctly) in AI answers? Worth a look on modern audits; not worth fabricating a scoring rubric around.

Prioritization: the impact/effort framework

This is the section most competitor checklists skip, and it’s the one that makes an audit useful. Score every finding on two axes — impact (how much will fixing it help) and effort (how hard/expensive is the fix) — and plot a 2×2:

Two framings I lean on hard:

• “Sometimes, the best course of action is to do nothing because the costs outweigh the benefits.” The bottom-right quadrant is real. Not fixing something is a valid, often correct, audit recommendation.
• Equate fixes to money. “You should try to equate fixes to cash. This is what businesses care about.” Reframing a fix from “301 these old URLs” to “recover the link equity on pages worth six figures in traffic value” is what gets it prioritized and shipped.

The 2×2 is the mental model, but a finding needs more than an impact/effort guess to survive scrutiny. For each one, record: what you observed, the affected cohort (a template, section, or market — not just “the site”), the evidence behind it, your confidence in it, the effort to fix, the risk of the fix (or of leaving it), any dependencies (a dev sprint, a CMS change, another team), and who owns it. That’s what turns “raise the priority” from a gut call into something a stakeholder can act on — and it’s worth saying plainly: a finding earning a spot on this list is an observation and a recommendation, not implementation approval. That’s a separate call for whoever owns the page or the budget.

Common myths this audit debunks

• More items = more thorough. No — 13 focused items beat 200 unread ones.
• E-E-A-T is a ranking factor to score. Google says it isn’t.
• Bounce rate / word count are ranking factors to flag. Neither is a direct ranking factor; assess content against intent, not metrics.
• An audit is a one-time project. It’s triggered and recurring.
• SEO studies tell you what to fix. They tell you what’s common — including my own 1M-domain study. Common isn’t causal, and it isn’t always worth fixing on your site.

Where to go next

For the technical-only depth this article intentionally skips, use the Technical SEO Checklist. For scaling the process to massive sites, the Enterprise SEO Audit; for stores and international sites, the Ecommerce and International audit guides.

AI summary

A condensed take on the Advanced version:

• An SEO audit spans four areas — technical, on-page, content, off-page — plus an emerging AI-visibility layer. Its output is a prioritized 5–10 item plan, not a 100–200 item report.
• Broader than a technical checklist. The Technical SEO Checklist is the technical floor; this adds on-page, content, and authority, and — the key differentiator — how to prioritize across them. Distinct from the enterprise, ecommerce, and international audits.
• Philosophy: “It’s better to spend 80% of your time fixing the 20% of things that matter.” 13 focused steps beat 100–200. “Sometimes, the best course of action is to do nothing.”
• Ordering heuristic (Patrick Stox): “Most of your time is better spent fixing your content unless you have some huge issues with crawling or indexing or something.” Gatekeepers first if broken, otherwise content.
• Process: pain point → write down scope (properties/templates/markets + owner) → gather data, labeling it (observed totals vs. GSC’s example-URL samples; sample by cohort on large/template-driven sites) → prioritize by impact, confidence, effort, risk, dependencies, and owner → deliver a short report → log the release date and verify against a dated baseline before crediting a fix.
• Triggers: traffic drop (use Google’s debug guide — Crawl Stats, Page Indexing, Manual Actions, Security Issues, plus seasonality/demand), migration, redesign, algorithm update, content push; recurring quarterly/monthly.
• Data: the 1M-domain study — 3XX redirects (95.2%), HTTP→HTTPS (88%), missing alt (80.4%), missing meta descriptions (72.9%) are the most common findings, but common ≠ important.
• Myths debunked: E-E-A-T isn’t a ranking factor; bounce rate and word count aren’t either; an audit isn’t one-time; and correlation studies don’t tell you what to fix.
• Prioritize by impact vs. effort, and “equate fixes to cash.”

Official documentation

Primary-source documentation from the search engines.

Google

• SEO Starter Guide — the practical baseline: indexing checks with site:, content quality criteria, and the E-E-A-T “not a ranking factor” clarification.
• Debug Google Search Traffic Drops — the official framework for the “why did traffic drop” audit trigger (Crawl Stats, Page Indexing, Manual Actions, Security Issues, seasonality).
• How to use Search Console — URL Inspection, Page Indexing, Rich Results, and the reports an audit leans on.
• Crawling and Indexing — the hub for the technical-audit basics (robots, sitemaps, canonicalization, faceted nav).
• Analyzing a search traffic drop (2021 blog) — companion walkthrough to the debugging guide.

Bing / Microsoft

• Bing Webmaster Guidelines — how Bing discovers, crawls, indexes, evaluates, and surfaces content across Bing, Copilot, and grounding results.
• Getting Started Checklist — Bing’s onboarding checklist (verify site, submit sitemap, review crawl info).
• Recommendations — Bing’s prioritized, impact-based guidance feature.

Quotes from the source

On-the-record statements. Each link jumps to the quoted passage on the source page.

Google — audit fundamentals

• “Try searching on Google for your site with the site: search operator.” — Google SEO Starter Guide, on checking indexing status. Jump to quote
• “No, it’s not.” — Google’s answer, under the heading “Thinking E-E-A-T is a ranking factor,” in the SEO Starter Guide. Read the section

Google — debugging a traffic drop

• “Check the Crawl stats report and Page indexing report to find if there’s a corresponding spike in issues detected.” Jump to quote
• “Check the Manual Actions report on Search Console to see if any have been issued to your website.” — Google Search Central docs.
• “Check the Security Issues report to find if Google detected a security threat on your website.” — Google Search Central docs.
• “Core updates and other smaller updates may change how some pages perform in Google Search results.” — Google Search Central docs.
• “Sometimes changes in user behavior will change the demand for certain queries, either due to a new trend, or seasonality throughout the year. This means your traffic may drop as a result of external influences.” — Google Search Central docs.

Patrick Stox / Ahrefs

• “That’s why our template only has 13 steps, not an overwhelming 100-200 like many others.” — Free SEO Audit Template. Jump to quote
• “It’s better to spend 80% of your time fixing the 20% of things that matter.” — Free SEO Audit Template. Jump to quote
• “If clients are coming to you asking for an audit, they already have a pain point. Talk to them. Solve that one thing and they’ll be happy with the audit.” — Patrick Stox, Free SEO Audit Template.
• “Sometimes, the best course of action is to do nothing because the costs outweigh the benefits.” — We Studied Over 1 Million Domains, “What should you fix?” section.
• “I don’t focus much on meta descriptions. If it’s a page that’s important to you and you can write a better meta description that fits, go for it.” — We Studied Over 1 Million Domains.
• “SEO checklists are impractical at scale.” and “I’ve seen several hundred-page documents detailing everything you checked, but no one is going to read those.” and “You should try to equate fixes to cash. This is what businesses care about.” — What is an Enterprise SEO Audit & How To Do One.
• “Most of your time is better spent fixing your content unless you have some huge issues with crawling or indexing or something.” — Patrick Stox, Prioritizing SEO Efforts (Voices of Search). Sourced from the episode’s show-notes/summary page; there’s no timestamped transcript to deep-link, but the quote is attributed to Patrick Stox there.

Google — content quality criteria

• Good content is “easy-to-read and well organized,” “unique,” and “helpful, reliable, and people-first.” — Google SEO Starter Guide. Read the section

SOP: run a quarterly SEO audit

A repeatable procedure you can run every quarter (monthly for large/fast-changing sites). Aim for a half-day, not a week.

1. Define scope and the pain point (15 min). Write one sentence: what prompted this audit, and what does “success” look like? If nothing prompted it, pick the section with the most business value and scope to that. Write down which properties, sections, or templates are in scope and who owns each — on a large or multi-template site, that short scope note is what keeps the audit from sprawling into everything.

2. Pull the data (30–45 min).

• Crawl the site (Ahrefs Site Audit / Screaming Frog). Tick “Backlinks” in crawl settings if your tool supports it, so you can catch dead pages with links.
• Export Search Console: Performance (last 3 months vs. prior), Page Indexing, and any Manual Actions / Security Issues.
• Pull analytics (GA4) for traffic and conversions by landing page.

3. Triage into the four buckets (60 min).

• Technical: any indexing/crawl blockers? These jump to the top if present.
• On-page: titles, meta, headings, images — but only on pages that matter.
• Content: quality, gaps, stale/pruning candidates.
• Off-page: dead pages with backlinks, competitor link gap.

4. Score and document each finding (20 min). For each one, note the affected cohort, your confidence, effort, risk, and any dependencies, then drop it into the 2×2. Kill the low-impact/high-effort items outright.

5. Write the deliverable (30 min). 5–10 findings only. Each one: what’s wrong, why it matters (in traffic/revenue terms where you can), the exact fix, and an owner — ideally as a ticket a developer or writer can pick up.

6. Log it, verify shipped fixes, and schedule the next one. Note what you found and when approved fixes shipped, so next quarter is a diff, not a from-scratch re-run — and so you can check the targeted cohort against a dated baseline before crediting a fix for a change in rankings or traffic.

Playbook: sudden traffic drop

A linear runbook for when organic traffic drops and you need to audit fast. Follow Google’s official debugging guide order — don’t skip steps.

1. Confirm it’s real and where. In Search Console Performance, compare the drop window to the prior period. Is it site-wide or a section/page? Clicks and impressions, or just clicks (a CTR/SERP-feature issue)?
2. Rule out demand/seasonality first. “Sometimes changes in user behavior will change the demand for certain queries.” Check Google Trends for the affected queries before assuming a technical break.
3. Check for manual actions. Open the Manual Actions report. If there’s a penalty, nothing else matters until it’s resolved.
4. Check Security Issues. A hack or malware flag can tank visibility fast.
5. Check indexing. In the Page Indexing report, look for a “spike in issues detected” — pages falling out of the index around the drop date.
6. Check crawl. In the Crawl Stats report, look for response-code spikes or a drop in successful crawls (server problems, accidental robots.txt block).
7. Check for an algorithm update. “Core updates and other smaller updates may change how some pages perform.” Cross-reference the drop date with known update dates. If it lines up with a core update, the fix is content quality, not a switch.
8. Check for recent changes on your side. Migrations, redesigns, redirect changes, a noindex shipped by accident.
9. Prioritize and fix. Whatever you find, run it through impact/effort and fix the top items first.

Audit anti-patterns

Concrete mistakes that make audits worse, not better.

The 200-page report. “I’ve seen several hundred-page documents detailing everything you checked, but no one is going to read those.” If nobody implements it, it wasn’t an audit — it was a document. Ship 5–10 findings.

Checking everything on every page. “SEO checklists are impractical at scale.” Normalizing alt text across 80% of a site because a tool turned it red is a classic time sink with little return. Fix on-page issues on pages that matter.

Treating E-E-A-T as a scored ranking factor. Google is explicit it’s not a ranking factor — “No, it’s not.” Auditing it as a checkbox metric wastes effort on something that isn’t a direct signal.

Flagging bounce rate or word count as “issues.” Neither is a direct ranking factor. Assess content against search intent, not a metric threshold. A 400-word page that fully answers the query beats a padded 2,000-word one.

Aggressive disavowing. Bulk-disavowing “toxic” links without a manual action or clear spam impact is an over-correction that can do more harm than good. Most sites should leave it alone.

Treating “most common” as “most important.” My 1M-domain study shows 3XX redirects on 95.2% of sites — that doesn’t make them the top priority anywhere. Common ≠ causal ≠ worth fixing.

Doing nothing with the pain point. If someone asked for the audit, they already have a problem. Auditing everything except the thing they care about is the fastest way to deliver a “thorough” audit nobody’s happy with.

What audits actually find

Grounded in the 1-million-domain site audit study (1,002,165 domains crawled). These are the most common findings — the point of each example is the judgment call, not the raw flag.

Before: “80% of your images are missing alt text.” The study found missing alt attributes on 80.4% of sites. The naive move is a sitewide alt-text sprint. After: add alt text to images on pages that matter (and where it aids accessibility/image search), and let boilerplate/decorative images be. The flag is real; the sitewide priority isn’t.

Before: “73% of pages have missing or empty meta descriptions.” Missing/empty meta descriptions hit 72.9% of sites. My own stance: “I don’t focus much on meta descriptions.” After: write good descriptions on your handful of most important, highest-traffic pages; skip the long tail. Google rewrites most of them anyway.

Before: “95% of your site has 3XX redirects.” 3XX redirects appear on 95.2% of sites — the single most common flag in the entire study. After: this is almost never a top priority on its own. Clean up internal links that point to redirects (a separate 62.7%-of-sites issue) where it’s cheap, and otherwise leave working redirects alone.

Before: “You have pages returning 404 that other sites link to.” Not in the top-15 by frequency, but high ROI when present. After: 301-redirect those dead-but-linked pages to the most relevant live page to recover the authority — this is one of the highest-value, lowest-effort fixes an audit turns up.

The mental models

1. The four (plus one) buckets. Technical → on-page → content → off-page, with AI-visibility as an emerging fifth. Every finding belongs to one. If you can’t place a finding in a bucket, question whether it’s a real finding.

2. The ordering heuristic. “Most of your time is better spent fixing your content unless you have some huge issues with crawling or indexing.” Gatekeepers (crawl/index) come first only if broken; otherwise content usually wins on ROI.

3. Impact × Effort (the 2×2). High-impact/low-effort first; high-impact/high-effort you schedule; low-impact/low-effort you batch; low-impact/high-effort you skip. Doing nothing is a valid recommendation. Each finding on the grid should also carry an affected cohort, confidence, risk, dependencies, and an owner — the grid gives you the order, those fields tell you whether it’s actually ready to hand off.

4. The 80/20 rule. “It’s better to spend 80% of your time fixing the 20% of things that matter.” The whole job is finding that 20%.

5. Equate fixes to cash. “You should try to equate fixes to cash. This is what businesses care about.” Translate every recommendation into traffic/revenue terms — that’s what gets it shipped.

6. Common ≠ important. Frequency (from studies, including mine) tells you what’s widespread, not what’s causal or worth fixing on your site. Prioritize by impact, not prevalence.

The full SEO audit checklist

Technical (deep dive → Technical SEO Checklist)

• Site is indexed (site:yourdomain.com returns pages).
• robots.txt isn’t blocking anything important.
• Page Indexing report reviewed — no unexpected drop in indexed pages.
• XML sitemap submitted (GSC + Bing) and lists only canonical, indexable URLs.
• Canonicalization consolidating duplicates as intended.
• HTTPS in place; mobile-friendly; CSS/JS not blocked from rendering.
• Core Web Vitals reviewed (PageSpeed Insights / CrUX).

On-page

• Important pages have unique, well-formed title tags (not too long).
• Meta descriptions present on pages that matter (skip the long tail).
• One clear H1 per page; sensible heading structure.
• Images that matter have descriptive alt text.
• Internal links point to live pages, not redirects/404s.

Content

• Content is helpful, unique, well-organized, and current.
• Content gaps identified vs. audience needs and competitors.
• Outdated high-value pages flagged for updates.
• Zero-traffic, zero-link pages flagged for pruning/consolidation.
• Depth assessed against intent — not word count.

Off-page / authority

• Backlink profile reviewed vs. competitors.
• Dead pages with backlinks found and redirected.
• No knee-jerk disavowing without a manual action / clear spam impact.

AI / answer-engine (forward-looking)

• AI crawlers can access content; structured data in place.
• Brand presence in AI answers spot-checked.

Deliverable

• Findings triaged by impact, confidence, effort, risk, dependencies, and owner.
• Report trimmed to 5–10 findings, each tied to a business outcome.
• Approved fixes logged with a release date; results checked against a dated baseline for the targeted cohort before crediting the fix.

SEO audit cheat sheet

Which audit do I need?

Priority order when something’s broken

1. Crawl/index blockers (page can’t be seen at all)
2. Manual action / security issue
3. High-impact content gaps and stale money pages
4. On-page fixes on pages that matter
5. Off-page / dead-links-with-backlinks recovery
6. Everything else → impact/effort filter

Most common findings (1M-domain study)

• 3XX redirects — 95.2% · HTTP→HTTPS — 88% · Missing alt — 80.4%
• Missing meta descriptions — 72.9% · Slow pages — 72.3%
• Title/SERP mismatch — 68.5% · Missing H1 — 59.5%
• Common ≠ important — filter by impact.

Audit frequency — quarterly (most sites), monthly (large/fast-changing). Common practice, not official guidance.

Deliverable size — 5–10 findings. Not 200 pages.

Ready-to-copy AI prompts

Prompts to speed up parts of an audit. Always verify AI output against your actual data — treat these as drafting aids, not sources of truth.

Triage a crawl export into a prioritized plan

I’m auditing a website. Here’s a CSV export of issues from my site crawler [paste]. Group these into four buckets — technical/indexing, on-page, content, off-page — then rank them by impact vs. effort. Flag which ones are “common but low priority” and which are genuine quick wins. Give me a final list of no more than 10 findings, each with a one-line fix.

Draft the executive summary

Turn these 8 SEO audit findings [paste] into a one-page summary for a non-technical stakeholder. For each finding, state the business impact in plain language (traffic or revenue terms where possible), then the recommended fix. No jargon, no more than one paragraph per finding.

Content-gap starting point

Here are my site’s main topics [paste] and three competitors’ [paste URLs]. Suggest content gaps — topics my audience likely searches for that I don’t cover well. Prioritize by likely search demand and relevance to my business, and mark which are “update an existing page” vs. “new page.”

Interrogate a traffic drop

Organic traffic to [section] dropped ~X% starting [date]. Walk me through Google’s official debugging order — demand/seasonality, manual actions, security issues, indexing, crawl, algorithm updates, recent site changes — and for each, tell me the exact Search Console report or tool to check and what a “yes, this is the cause” signal looks like.

Tools you’ll actually use

• Google Search Console (free) — the single most important audit tool. URL Inspection, Page Indexing, Crawl Stats, Manual Actions, Security Issues, and the Performance report all map directly to Google’s official traffic-drop debugging framework. One caveat when you use the Page Indexing report: the example URLs it lists under each reason are a sample, not a complete inventory — use the reported totals to gauge prevalence, not the handful of example rows.
• Bing Webmaster Tools (free) — Bing’s equivalent, plus a Recommendations feature that surfaces prioritized guidance.
• Ahrefs Site Audit / Webmaster Tools — crawl-based site audit; a free Ahrefs Webmaster Tools account crawls sites you verify (tick “Backlinks” in crawl settings to catch dead pages with links). Site Explorer covers the off-page/backlink side.
• Screaming Frog SEO Spider — desktop crawler (free up to 500 URLs) for on-page and technical checks; the Log File Analyser handles crawl-log analysis.
• GA4 / analytics — traffic and conversions by landing page, to weigh which pages actually matter before you prioritize fixes.
• PageSpeed Insights / CrUX — Core Web Vitals, blending lab and real-user field data for the performance pass.

Describe each tool by what it does for the audit, not by a feature list — and remember no single tool “scores” your SEO. The score is a starting point, not the finding.

Test yourself: SEO Audit Checklist

Five quick questions on running a full SEO audit and prioritizing what you find. Pick an answer for each, then check.

Resources worth your time

My related writing

• Free SEO Audit Template (With Video Walkthrough) — the 13-step template and the “80% of your time on the 20% that matters” philosophy (with Joshua Hardwick).
• We Studied Over 1 Million Domains to Find the Most Common Technical SEO Issues — the data behind what audits actually find, and “what should you fix?”
• What is an Enterprise SEO Audit & How To Do One — the process (pain point → scope → audit types → deliverable) and “equate fixes to cash.”
• The Beginner’s Guide to Technical SEO — where the technical slice of the audit fits in the bigger picture.

My speaking

• Prioritizing SEO Efforts (Voices of Search podcast) — the “most of your time is better spent fixing your content” ordering heuristic.
• What I Learned from Auditing Over 1,000,000 Websites — why most common ≠ most important, and the prioritization thresholds that matter.

From around the industry

• Google — SEO Starter Guide — the practical baseline for a first audit, including the E-E-A-T “not a ranking factor” clarification.
• Google — Debug Search Traffic Drops — the official framework for auditing a traffic decline.
• Backlinko — The Complete SEO Checklist — a long, exhaustive, category-by-category checklist; useful for coverage, the opposite of the prioritized approach here.
• Semrush — How to Perform a Complete SEO Audit in 20 Steps — a step-by-step audit walkthrough with per-step tool call-outs.
• Screaming Frog — SEO Spider — the desktop crawler most audits are run with.
• r/TechSEO — the community for crawl/index and audit debugging.

Stats worth citing

All from my study of over 1 million domains (1,002,165 domains crawled) — the most common technical issues found, which is not the same as the most important:

• 3XX redirects — 95.2% of sites.
• HTTP→HTTPS redirects — 88% of sites.
• Missing alt attributes — 80.4% of sites.
• Missing/empty meta descriptions — 72.9% of sites.
• Slow pages — 72.3% of sites.
• Page/SERP title mismatch — 68.5% of sites.
• Only a single dofollow internal link — 66.2% of sites.
• Missing/empty H1 tags — 59.5% of sites.

The LinkedIn announcement framed it: “What do technical SEO issues look like across 1,002,165 websites? We ran the largest site audit study ever to find out!” — and the comments quickly turned to how to prioritize the findings with an impact/effort framework, which is exactly the point: prevalence isn’t priority.

SEO Audit Checklist

An SEO audit checklist is the structured set of things you review across a site's technical health, on-page elements, content quality, and off-page authority — used to produce a short, prioritized action plan, not an exhaustive 100–200 item inventory.

Related: Technical SEO Checklist, Enterprise SEO Audit, Crawling

SEO Audit Checklist

An SEO audit is a systematic review of a website’s technical health, on-page optimization, content quality, and off-page authority to find what’s stopping it (or could stop it) from ranking and getting found in search. An SEO audit checklist is the structured set of things you check during that review — and, just as importantly, the way you triage what you find into a prioritized list of fixes.

The items usually group into four or five buckets: technical/crawlability and indexing, on-page (titles, meta descriptions, headings, images), content (quality, gaps, outdated pages), off-page/authority (backlinks, dead pages with links), and increasingly a forward-looking AI/answer-engine visibility dimension.

Two things people get wrong about it:

• More items isn’t more rigor. A good audit’s output is a short, prioritized action plan — 5–10 findings that move the needle — not a 100–200 item report nobody reads. Sweating every minor imperfection on every page rarely does much for rankings.
• It’s broader than a technical SEO checklist. The technical checklist is the technical-only floor (crawlability, indexing, HTTPS, Core Web Vitals, structured data). A full SEO audit spans that plus on-page, content, and authority — and orders everything by impact vs. effort.

Related: Technical SEO Checklist, Enterprise SEO Audit, Crawling

Changelog