Technical SEO Audit Checklist: What a Detailed Audit Should Actually Cover


In short. A detailed SEO audit covers six areas: crawlability, indexation, site architecture, on-page signals, Core Web Vitals and structured data. Each item should come with a reason and a priority — not just a red flag. Use this checklist to judge whether an audit is thorough or shallow before you act on it.
A detailed SEO audit should tell you three things: where search engines are struggling with your site, why it matters, and what to fix first. Too many audits stop at a long list of red flags with no priority attached — which leaves you with a 60-page PDF and no idea where to start. According to Google Search Central, crawling and indexing are the two foundations everything else sits on; if those break, nothing downstream works. This checklist walks through what a thorough technical audit actually inspects, grouped into six areas, so you can judge whether the audit you’re reading (or paying for) is complete or just thorough-looking.
Use it as a scorecard. For each group below, a good audit checks every item, explains the impact, and ranks the fix. If an audit skips a whole group, it isn’t detailed — it’s partial.
1. Crawlability — can search engines reach your pages?
Crawlability is whether search engines can find and access your pages at all. Everything else is irrelevant if a page can’t be crawled. A detailed audit starts here because it’s the most common place real damage hides — a stray rule in a config file can wipe sections out of search.
- robots.txt — check it isn’t blocking important directories, CSS or JavaScript. One misplaced
Disallowcan hide a whole section. - XML sitemap — present, submitted in Search Console, listing only canonical, indexable URLs (no redirects, no 404s, no
noindexpages). - Crawl budget — on large sites, confirm search engines aren’t wasting crawls on faceted filters, session IDs or endless parameter combinations.
- Internal linking depth — important pages should be reachable within three clicks of the homepage; orphan pages (linked from nowhere) should be flagged.
- Server response codes — a crawl should surface 4xx and 5xx errors, redirect chains and soft 404s.
In our audits we regularly see a single robots.txt line quietly blocking an entire blog or product category — the pages exist, they’re just invisible to search. It’s the cheapest fix with the biggest upside.
If the audit doesn’t open a crawl export and reconcile it against the sitemap, it hasn’t checked crawlability properly.
2. Indexation — are the right pages actually indexed?
Indexation is whether crawled pages make it into the search index, and whether the right ones do. A page can be crawlable but still excluded — or the wrong version can get indexed. A detailed audit compares what should be indexed against what is.
Here’s what a thorough indexation check covers:
- Index coverage report in Search Console — review every “excluded” and “error” category, not just the green count.
- Canonical tags — each page points to a single preferred URL; self-referencing where appropriate, no conflicting signals.
- noindex directives — confirm no important pages are accidentally set to
noindex, and that thin or duplicate pages correctly are. - Duplicate content — identify near-identical pages (parameter URLs, HTTP/HTTPS, www/non-www, trailing slashes) competing for the same query.
- Pagination and faceted navigation — check these don’t flood the index with low-value variations.
The goal is a clean index: your valuable pages in, your clutter out. According to Ahrefs, index bloat — thousands of thin pages diluting a site’s focus — is a frequent and under-diagnosed problem. A good audit quantifies it, not just mentions it.
3. Site architecture — is the structure logical and shallow?
Site architecture is how your pages are organised and linked. Good architecture helps search engines understand topic relationships and distributes authority sensibly. A detailed audit maps the structure, not just individual pages.
- URL structure — clean, readable, consistent; no deep nesting or unnecessary parameters.
- Hierarchy and silos — related content grouped logically so topic clusters are clear to crawlers.
- Internal link equity — authority flows to your money pages, not just the homepage and contact page.
- Breadcrumbs — present and marked up, reinforcing hierarchy for users and search engines.
- Mobile parity — the mobile version contains the same content and links as desktop, since Google indexes mobile-first.
Architecture problems rarely throw a single red flag — they show up as slow, diffuse underperformance. That’s why a checklist that only scans page-by-page misses them. A detailed audit steps back and looks at the shape of the whole site.
4. Page speed and Core Web Vitals — is the experience fast enough?
Core Web Vitals are Google’s measurable signals for loading, interactivity and visual stability. They affect both ranking and conversion. A detailed audit measures real-world performance, not just a lab score on the homepage.
The three metrics to check, per web.dev:
- Largest Contentful Paint (LCP) — how fast the main content loads. Aim for under 2.5 seconds.
- Interaction to Next Paint (INP) — how quickly the page responds to input. Under 200 milliseconds is good.
- Cumulative Layout Shift (CLS) — how much the layout jumps while loading. Under 0.1 is good.
A thorough audit pulls field data (real users, from the Chrome UX Report in Search Console) alongside lab data, because they often disagree. It also checks common culprits: unoptimised images, render-blocking scripts, no caching, bloated third-party tags and oversized fonts. Flagging “your site is slow” isn’t an audit — identifying which three resources cause the delay is.
Speed fixes are where effort and impact diverge most. A detailed audit should tell you which changes shave a second and which shave a millisecond — so you spend engineering time where it pays back.
5. On-page technical signals — is each page sending clear instructions?
On-page technical signals are the metadata and markup that tell search engines what a page is about and how to display it. These are page-level but systematic — a good audit checks them at scale, not one by one.
What belongs on the checklist:
- Title tags — unique, present, within length, keyword-relevant; no duplicates across the site.
- Meta descriptions — present and distinct (they don’t rank but affect click-through).
- Heading structure — one logical H1 per page, hierarchical H2s and H3s.
- Image optimisation — descriptive alt text, compressed files, modern formats.
- hreflang — for multilingual or multi-region sites, correct language and region tags with return references (a common and quietly costly error).
- HTTPS — the whole site served securely, with no mixed-content warnings.
An audit that checks these across the full crawl — counting how many pages have missing or duplicate titles, for example — gives you something actionable. A spot-check of five pages doesn’t.
6. Structured data — are you eligible for rich results?
Structured data is code that describes your content to search engines in a format they can parse directly — enabling rich results like review stars, FAQs and product details. It won’t fix a broken site, but on a healthy one it’s a visibility edge. A detailed audit checks both presence and validity.
Here’s what to verify:
- Schema presence — relevant types implemented (Organization, Product, Article, LocalBusiness, FAQ, Breadcrumb) where they apply.
- Validity — markup passes Google’s Rich Results Test with no errors or warnings.
- Accuracy — the markup matches the visible content (mismatches can trigger manual actions).
- Coverage — schema is applied consistently across page templates, not just a handful of pages.
- Enhancement reports in Search Console — review for errors on items already deployed.
Structured data is the area most often skipped in cheap audits because it’s fiddly to check properly. Its absence from a report is a quick tell that the audit wasn’t detailed.
How to tell a detailed audit from a shallow one
A shallow audit runs one tool, exports the issues and reformats them. A detailed audit interprets. Here’s how to spot the difference when you receive one:
- Priority, not just findings. Every issue should be ranked by impact and effort. A flat list of 200 problems is a data dump, not an audit.
- Reasons attached. “Fix your canonicals” isn’t enough — a good audit explains which pages, why it matters and what happens if you don’t.
- Cross-referenced data. Crawler output checked against Search Console, log files and live rendering — not a single automated score.
- A clear next step. The output should be a plan you can hand to a developer, in order.
A detailed SEO audit is only as useful as the decisions it drives. If you finish reading one and still don’t know what to do Monday morning, it covered the surface — not the substance. Run this checklist against any audit you get: six areas, every item, reason plus priority. That’s the bar.


