Technical SEO · Cluster Guide
Technical SEO Checklist: 21 Things to Fix Before You Chase Rankings
A client once told us their content was "the best in the category" and still wasn't ranking. They were right about the content. The problem was that Google had never actually seen most of it. This is the checklist we wish someone had handed them a year earlier.
Technical SEO is the work of making sure search engines can crawl, render and index your site correctly before content or keywords even enter the picture. Most “why aren't we ranking” problems trace back to one of three things: pages Google can't reach, pages it can reach but won't store, or a site that's too slow to reward. This checklist walks through all three, in the order we actually check them.
The Site That Had Nothing Wrong With It
A few years into doing this work, you learn to recognize a very specific kind of frustration. It shows up in an email that starts with some version of: "I don't understand it. We've published forty articles. They're well-researched. We paid a proofreader. And we get almost no organic traffic."
Nine times out of ten, the content genuinely is fine. The site just never gave Google the chance to notice it existed. A misconfigured robots.txt file was quietly blocking an entire folder. A migration eighteen months earlier had left half the internal links pointing at 404 pages. The sitemap hadn't been updated since the site's original launch. None of this shows up when you read the articles. All of it shows up the moment you check the technical layer underneath them.
That's what this checklist is for. Not a list of things that might help — a list of things that, left broken, put a hard ceiling on everything else you do.
Gate One: Can Google Even Crawl the Page?
Before a page can rank for anything, a crawler has to physically reach it. This sounds too basic to matter, and that's exactly why it's the most common failure point.
- Check robots.txt first, not last. A single misplaced
Disallow: /line — often left over from a staging environment — can quietly block your entire site, or one important folder, from every crawler at once. - Confirm important pages aren't set to
noindexby accident. CMS defaults and plugin settings change more often than anyone remembers to check. - Fix broken internal links. Every dead link is a dead end for both users and crawlers, and they compound after any redesign or URL migration.
- Submit — and actually maintain — an XML sitemap. It doesn't guarantee indexing, but it gives Google a direct map instead of making it discover pages purely through links.
- Watch your crawl budget on larger sites. According to Ahrefs' analysis of the web, a striking share of pages online are technical duplicates of one another — parameter variations, session IDs, thin filtered pages — and every one of them is a crawl request Google spends instead of spending it on a page you actually want ranked.
“Most sites don't have a content problem. They have a crawl problem wearing a content problem's clothes.”Chenthil Kumar, Digimarketlabs
Gate Two: Will Google Actually Index It?
Crawled is not the same as indexed. Google's own Search Console documentation is direct about this: a page can be visited by Googlebot, read in full, and still be deliberately excluded from the index if Google judges it thin, duplicate, or not worth storing.
- Check your Page Indexing report in Search Console regularly, not just when traffic drops — "Crawled — currently not indexed" is a quality judgment, not a technical error, and it needs a content fix, not a resubmission.
- Resolve duplicate and near-duplicate content with proper canonical tags, especially on ecommerce and filtered-listing pages where the same product can generate dozens of near-identical URLs.
- Consolidate thin pages instead of leaving dozens of low-value pages competing for the same crawl budget and diluting your site's overall quality signal.
- Watch for accidental canonical loops or self-referencing errors introduced during a CMS migration — these are one of the most common causes of pages that "should" be indexed and quietly aren't.
Not sure which of these is actually hurting you?
A full technical audit tells you exactly which of these 21 items apply to your site, ranked by impact — not just a scanner report.
Gate Three: Is It Fast Enough to Be Rewarded?
Once a page clears crawling and indexing, speed and stability start to matter — both for how Google evaluates it and for whether a visitor sticks around to read it. We go deep on this in our dedicated guide to Core Web Vitals, but the checklist basics are:
- Get your Largest Contentful Paint under 2.5 seconds. Google's own published threshold, and the one most Core Web Vitals tooling checks against first.
- Compress and lazy-load images. Still the single most common cause of a slow LCP on content-heavy sites.
- Audit third-party scripts. Chat widgets, ad tags and analytics snippets pile up and quietly tax every page load.
- Check mobile specifically, not just desktop. Google indexes mobile-first, and mobile performance is consistently the weaker of the two on most sites.
Structured Data: Making Your Content Legible to Machines
Structured data (schema markup) doesn't replace good content, but it does remove the ambiguity a search engine — or an AI system building an answer — would otherwise have to guess at. Article, FAQPage, Product and BreadcrumbList schema are the highest-leverage starting points for most sites, and they matter even more now that they double as a signal for AI Overview citation, not just classic rich results.
- Validate your schema, don't just add it — invalid or mismatched structured data can be ignored entirely or, worse, flagged as a quality issue.
- Match schema to visible content exactly. FAQ schema describing questions that aren't actually visible on the page violates Google's own guidelines.
- Add BreadcrumbList schema site-wide. It's one of the simplest structured data types to implement correctly and it reinforces your site's internal hierarchy for both search engines and readers.
The Checklist, All 21 Items
- robots.txt isn't accidentally blocking important sections
- No unintended
noindextags on pages you want ranked - XML sitemap exists, is current, and is submitted in Search Console
- Internal links resolve — no orphaned or broken links
- Canonical tags point to the correct, intended version of each page
- Duplicate and near-duplicate content is consolidated or canonicalized
- Thin, low-value pages are merged, improved or removed
- Crawl budget isn't wasted on parameter or session-ID URLs
- Search Console Page Indexing report is reviewed on a regular cadence
- Largest Contentful Paint is under 2.5 seconds on mobile
- Images are compressed and lazy-loaded below the fold
- Third-party scripts are audited and trimmed regularly
- Mobile performance is tested separately from desktop
- HTTPS is enforced site-wide with no mixed-content warnings
- URL structure is clean, consistent and human-readable
- Redirect chains are flattened to a single hop
- 404 pages are monitored and fixed, not left to accumulate
- Structured data validates without errors
- Schema matches the page's actual visible content
- BreadcrumbList schema is implemented site-wide
- A recurring audit cadence exists — this list gets rechecked, not just run once
Why This Isn't a One-Time Project
The uncomfortable truth about a technical audit is that it has an expiration date the moment you finish it. A new developer joins and changes a redirect rule. A plugin update silently resets a noindex default. A migration six months from now reintroduces three items on this exact list. That's the entire premise behind our recurring monthly audit approach — catching the regression in month one instead of discovering it in month eight, after the traffic is already gone.
Where to Go From Here
If crawling and indexing are sorted, the next place most sites leave real ranking potential on the table is the content layer itself — see our guide to on-page SEO best practices for what to fix once the technical foundation is solid, or our keyword research guide if you're not yet sure which pages deserve the investment in the first place.
FAQ
Technical SEO questions, answered directly
How often should a technical SEO audit be run?
At minimum annually, or before and after any major site change — redesign, migration, CMS switch. For sites that change frequently, a recurring monthly check catches regressions long before they show up as a traffic drop.
Can I fix all of this myself with a free tool?
Many of these items can be checked with Google Search Console alone, which is free. Where most self-audits fall short is prioritization — a tool will flag two hundred issues with no sense of which three are actually costing you traffic.
Does technical SEO matter if our content is already excellent?
It matters more, not less — excellent content that Google can't crawl or won't index is invisible regardless of quality. Technical SEO is the precondition, not a competing priority.
Is technical SEO different for a small site versus a large one?
The checklist items are the same, but crawl budget and duplicate-content issues scale up significantly on sites with thousands of pages, which is why larger ecommerce and marketplace sites need this reviewed far more frequently.
Want this checklist run against your actual site?
Book a strategy call and we'll tell you honestly which of these 21 items need attention first — before recommending anything.
Sources & further reading
Where this guide draws from
Keep reading