The Technical SEO Checklist: 25+ Checks to Find and Fix Site Issues (Ranked by Priority)
I've audited a lot of sites over the years, and the pattern is almost always the same: someone's been pouring effort into content or link building while half their pages aren't even indexing properly. The technical foundation was broken the whole time, and nobody noticed because it doesn't show up in your GA4 dashboard screaming at you.
This technical SEO checklist exists to fix that. It's built for people who already understand what technical SEO is and just want to know what to fix first — because that question matters more than most resources admit.
Most checklists hand you 30 items and call it a day. That's not useful when you're staring at a redirect chain three hops deep and your homepage isn't showing up in a site: search. So we've grouped everything into three tiers: critical blockers, high-impact fixes, and advanced enhancements. Work them top to bottom. Fix the things that actually move rankings before you burn time on the nice-to-haves.
Every check follows the same four-part structure: what it is, why it matters, how to check it, and how to fix it. Let's get into it.
Priority 1 — Critical Blockers (Fix These First)
These are the issues that stop pages from being crawled, indexed, or served at all. Nothing else on this list matters until they're handled. If you only work through one section today, make it this one. The fastest, highest-stakes wins are right here.
Confirm Your Pages Are Indexable (Tier 1)
What it is: Indexability is whether a page is allowed to appear in search results. A single noindex directive — often slipped in during a site build or staging migration and never removed — quietly keeps a page out of Google entirely.
Why it matters: An unindexed page can't rank or earn a single click, regardless of how good the content is. In my experience, this is the most common "invisible" problem on otherwise well-run sites. The page looks completely normal to a human visitor, so it goes undetected for months.
How to check: Open the URL Inspection tool and the Pages report inside Google Search Console. Google groups excluded pages by reason, so you'll see exactly which ones carry noindex tags and which are "crawled – currently not indexed." Cross-check in Bing Webmaster Tools too — the two indexes rarely align.
How to fix: Remove accidental noindex tags from any page you want to rank. For "crawled – currently not indexed" URLs, treat the exclusion as a quality signal. Improve the content rather than trying to force indexation.
Audit Your robots.txt File (Tier 1)
What it is: The robots.txt file tells crawlers which parts of your site they're allowed to access. You'll find it at yourdomain.com/robots.txt.
Why it matters: One overzealous Disallow rule can block critical pages — or worse, the CSS and JavaScript that search engines need to render your site. This kind of block is completely silent. There's no error in the browser; the site looks fine. But from the crawler's perspective, entire sections may as well not exist.
How to check: Read through the Disallow directives manually or run a crawler to flag blocked resources. Confirm that no important folders, scripts, or stylesheets are accidentally off-limits.
How to fix: Narrow or remove any overly broad rules. While you're in there, also check whether you've blocked AI crawlers — if you care about AI search visibility, an unintentional block on AI retrieval bots could be quietly costing you presence in AI-generated results.
Check Crawlability and Crawl Budget (Tier 1)
What it is: Crawlability is how easily search engines can move through your site. Crawl budget is the number of pages they'll crawl in a given window. For most small sites, budget isn't something to stress about — but for large, content-heavy, or ecommerce sites, it's very real.
Why it matters: When crawl budget gets eaten up by thin, duplicate, or low-value URLs, your important pages get discovered and refreshed more slowly. I've seen ecommerce sites where filter combinations were generating thousands of junk URLs and consuming crawl budget that should have been going to product pages.
How to check: Look at the Crawl Stats report in Google Search Console to see how bots are spending their time. Pair that with a crawler to identify which low-value URLs are eating into the budget.
How to fix: Trim thin or duplicate content URLs, tighten up your internal linking paths, and keep priority pages within a few clicks of the homepage. A cleaner structure is honestly the most underrated crawl budget fix there is.
Fix Server Errors and Broken Links (Tier 1)
What it is: Server errors (5xx status codes) signal something's wrong on the server side. Broken links (404s) send users and crawlers to pages that no longer exist.
Why it matters: 5xx errors can block crawling outright. Broken links waste link authority and strand real users at dead ends — which erodes trust and increases bounce. Not a great combination.
How to check: Run Screaming Frog or Sitebulb and filter for 5xx errors and broken links. Both tools surface the exact URLs and the status codes they return, which makes triage a lot faster than hunting page by page.
How to fix: Hand 5xx errors to a developer — they're almost always server or hosting issues. For broken links, restore the removed page if it still has value, or point it to a relevant alternative using a 301 redirect.
Resolve Duplicate Versions of Your Site (Tier 1)
What it is: Your site can technically load at several different addresses — HTTP and HTTPS, www and non-www. Each of those is a separate URL as far as search engines are concerned.
Why it matters: When more than one version loads without redirecting, search engines may treat them as distinct sites. That splits ranking signals and creates duplicate content problems across what is actually the same set of pages. It's a surprisingly common oversight, especially on older sites or after platform migrations.
How to check: Type each variation into your browser — http\://, https\://, www, and non-www — and watch which ones load without redirecting to a single version.
How to fix: Pick one preferred version (HTTPS without the www, or with — your call) and 301 redirect everything else to it. One canonical home for your site, no exceptions.
Verify HTTPS Is Properly Implemented (Tier 1)
What it is: HTTPS encrypts the connection between your site and its visitors using an SSL certificate. It's been a lightweight Google ranking signal since 2014.
Why it matters: Modern browsers mark non-HTTPS pages as "Not Secure," which erodes visitor trust and bumps bounce rates. For sites handling logins, account data, or payments, it's simply non-negotiable.
How to check: Look for the lock icon in the browser bar. Then try loading the HTTP version of a page and confirm it redirects cleanly to HTTPS rather than loading independently.
How to fix: Install an SSL certificate — most hosts include one, and Let's Encrypt provides them free. Once it's live, hunt down any mixed-content warnings caused by resources still loading over HTTP, and fix those too.
Priority 2 — High-Impact Fixes
These issues won't hide your site from Google, but they have a direct bearing on how well your pages rank and how people experience them. Clear every Tier 1 blocker first, then work through these. This is the tier where most measurable ranking gains tend to appear.
Set Canonical Tags Correctly (Tier 2)
What it is: A canonical tag tells search engines which version of a page is the authoritative copy when duplicates or near-duplicates exist. A self-referencing canonical simply points a page at itself, confirming there's no preferred version elsewhere.
Why it matters: Get this wrong and you can inadvertently deindex the pages you most want to rank, or scatter signals across duplicate URLs. Canonical mistakes tend to be subtle — they don't throw errors, they just quietly underperform. In my experience, they're one of the more common causes of "why isn't this page ranking?" on sites that look otherwise healthy.
How to check: Verify self-referencing canonicals using a crawler or the URL Inspection tool. Add a random parameter to a URL and confirm the canonical doesn't change — if it shifts, you have a consolidation problem worth investigating.
How to fix: Point duplicate URLs to one preferred version. And avoid mixed signals — canonicalizing a page to another URL while also tagging it noindex is exactly the kind of contradiction that confuses Google.
Clean Up Redirect Chains and Loops (Tier 2)
What it is: A redirect chain is when URL A sends users to B, which sends them to C. A redirect loop is when pages point back to each other endlessly. Both tend to accumulate during site restructures when nobody's tracking them carefully.
Why it matters: Chains slow load times, waste crawl budget, and dilute the authority passed between pages. Loops trap crawlers and users alike. A three-hop chain isn't a crisis, but a site with hundreds of them is quietly bleeding performance.
How to check: Filter for "redirect" issues in Screaming Frog or Sitebulb to surface every chain and loop across the site.
How to fix: Point each internal link and redirect straight to the final destination URL. Cut out every middleman hop you can.
Improve Your Core Web Vitals (Tier 2)
What it is: Core Web Vitals are Google's three page-experience metrics: LCP (Largest Contentful Paint, target under 2.5 seconds), INP (Interaction to Next Paint, target under 200 milliseconds), and CLS (Cumulative Layout Shift, target under 0.1).
Why it matters: Poor scores hurt both rankings and the actual experience of your visitors, and the impact bites hardest on mobile. I've worked on sites where fixing LCP alone — mainly oversized hero images and render-blocking fonts — produced noticeable ranking improvements within a few weeks. It's not always that clean, but it's worth taking seriously.
How to check: Start with the Core Web Vitals report in Google Search Console to identify which pages are failing. Then run the flagged URLs through PageSpeed Insights and Lighthouse for specific, actionable diagnostics.
How to fix: The usual culprits are heavy images and bloated code. Image optimization — compressing files and specifying correct dimensions — is almost always where the biggest gains are. Beyond that, eliminate render-blocking resources and have a developer minify your CSS and JavaScript.
Confirm Mobile-First Readiness (Tier 2)
What it is: Mobile-first indexing means Google predominantly uses the mobile version of your site for both indexing and ranking. Responsive design serves consistent content across all screen sizes from a single URL.
Why it matters: Content, links, or structured data that exist on desktop but are hidden or absent on mobile can effectively vanish from the index. It's one of the quietest, most damaging mismatches in technical SEO — especially on older sites built before mobile-first was the norm.
How to check: Load your site on an actual phone, not just a browser dev tool. Confirm that content, internal links, and structured data genuinely match what desktop visitors see.
How to fix: Migrate to responsive design if you're not already there, and audit for full content parity between devices. Whatever desktop users get, mobile users should get too.
Strengthen Site Architecture and Internal Linking (Tier 2)
What it is: Site architecture is how your pages are organized and connected. Internal linking, breadcrumbs, and click depth all shape how easy it is for users and crawlers to move through your site.
Why it matters: A clean, logical hierarchy helps users, search engines, and AI systems understand how your pages relate to each other — and how much weight each one carries. Pages buried five clicks deep from the homepage tend to rank worse than shallower ones, even when the content quality is similar.
How to check: Map your click depth and flag any important pages sitting more than three or four clicks from the homepage.
How to fix: Add contextual internal links with descriptive anchor text — not "click here," but something that tells the reader and the crawler what they're navigating to. Build hub pages that draw related content together, and use breadcrumbs to reinforce your hierarchy.
Fix Orphan Pages (Tier 2)
What it is: Orphan pages are pages with no incoming internal links. Nothing on your site points to them.
Why it matters: If no internal link references a page, users and crawlers both struggle to reach it. The page might as well not exist from a discovery standpoint — even if the content itself is strong. On content-heavy sites, orphan pages tend to pile up over time as articles are published and older posts never get updated with links to newer ones.
How to check: Run a crawler connected to your XML sitemap and analytics data. That combination is what reliably surfaces orphaned URLs — a page with no links is otherwise invisible to a crawl.
How to fix: Add relevant internal links from related pages to pull each orphan back into your site's structure.
Buried pages and architecture gaps add up fast on larger sites. A professional Technical SEO Audit surfaces every orphan page and structural weakness automatically — no manual crawling required.
Priority 3 — Advanced Enhancements
With the foundations solid, these refinements sharpen your visibility further. They're worth pursuing only after Tier 1 and Tier 2 are handled — and several are use-case specific, so skip the ones that don't apply to your setup.
Add and Validate Structured Data (Tier 3)
What it is: Schema markup is structured code that describes your content to search engines. It's usually implemented as JSON-LD, with common types including Article, Product, and Organization.
Why it matters: Structured data helps both search engines and AI systems understand your content and the entities it references. Done well, it can unlock rich results — star ratings, prices, FAQs — directly in the SERP, which lifts click-through without requiring a ranking improvement.
How to check: Validate your markup with Google's Rich Results Test to confirm it's correctly formed and eligible for enhanced listings.
How to fix: Add JSON-LD to the page head using a schema generator or CMS plugin, then re-test. Focus on the types that genuinely reflect your content — don't add markup just because it exists.
Use Semantic HTML for Cleaner Parsing (Tier 3)
What it is: Semantic HTML uses meaningful tags — header, nav, main, footer, and a clean H1 through H6 hierarchy — rather than piling everything into generic div and span containers.
Why it matters: Clear structure helps both search engines and AI agents interpret your page accurately. Generic tags render fine in a browser but communicate nothing to machines about what each section actually contains or represents.
How to check: Review the page source directly, or ask a developer to confirm semantic tags are being used consistently across your templates.
How to fix: Replace generic containers with meaningful tags and maintain a strict, logical heading hierarchy — one H1 per page, with subheadings nested sensibly beneath it.
Handle JavaScript SEO Issues (Tier 3)
What it is: JavaScript SEO is about ensuring that content loaded via JavaScript is visible to search engine crawlers. Rendering is the step where Google processes that JS to "see" what a page actually contains.
Why it matters: If Google can't render your content, it may never index it. JS-heavy sites — particularly those built on React, Angular, or Vue without server-side rendering — can accidentally hide their most important content behind scripts that fail to load in the crawler environment.
How to check: Use the URL Inspection tool's rendered view and Google's Mobile-Friendly Test to compare what Google renders against what you see in the browser.
How to fix: Keep critical content and links out of scripts that might fail to render. For heavier JS frameworks, work with a developer on server-side or hybrid rendering to ensure the important content is available immediately in the HTML.
Implement hreflang for International Sites (Tier 3)
What it is: hreflang tags tell search engines which language or regional version of a page to serve to which audience.
Why it matters: Without them, a German visitor might land on your English page, or your US content might compete with your UK version for the same query. On multi-region sites, hreflang is the thing that brings order to an otherwise messy situation.
How to check: Validate your annotations with an hreflang testing tool — the implementation rules are surprisingly fiddly and easy to misconfigure even for experienced teams.
How to fix: Add correct hreflang tags in the page head or XML sitemap, always include an x-default fallback, and audit carefully for the bidirectional mismatches that most commonly cause problems.
Tame Faceted Navigation (Ecommerce) (Tier 3)
What it is: Faceted navigation is the filtering system on ecommerce sites — size, color, price, brand, and so on. Each filter combination can generate its own URL.
Why it matters: Left unchecked, those combinations multiply into near-infinite URLs, flooding your site with duplicate content and draining crawl budget on pages that serve no meaningful SEO purpose. I've seen ecommerce crawls return hundreds of thousands of URLs when the actual product catalog had fewer than five thousand items.
How to check: Crawl the site and count how many URL variations your filters are actually generating. The number is usually much higher than people expect.
How to fix: Apply noindex, canonical tags, and robots.txt rules strategically to filter URLs you don't want indexed, while keeping valuable category and product pages fully crawlable.
Review Meta Tags and Page-Level Signals (Tier 3)
What it is: Meta tags — primarily title tags and meta descriptions — are the snippets that represent your page in the search results.
Why it matters: They don't directly control rankings, but strong, unique titles and descriptions do influence click-through rate from the SERP. A better title on the same ranking position means more traffic without any ranking movement.
How to check: Run a crawler to find missing, duplicate, or truncated titles and descriptions across the site.
How to fix: Write unique, keyword-relevant titles under roughly 60 characters and compelling descriptions under about 155. Match the intent of the search query honestly — overselling what the page delivers just lifts bounce rates.
Audit Your Backlink Hygiene (Tier 3)
What it is: The disavow file tells Google to ignore specific backlinks. It's a tool most sites will genuinely never need.
Why it matters: Google largely ignores bad links on its own these days. The bigger risk, in practice, is an old or carelessly assembled disavow file — sometimes left behind by a previous agency — that quietly blocks valuable links you actually want counted.
How to check: Pull up the existing disavow file in Google Search Console and check for any manual actions against the site.
How to fix: If the file incorrectly lists important links, remove them and re-upload. Only add to the disavow file after a confirmed manual action or when there's clear evidence of manipulative link building that Google hasn't ignored on its own.
Optimize for AI Search Visibility
Here's the reassuring part: if you've worked through the tiers above, you've already done most of what's needed for AI search visibility too.
AI systems and traditional search engines pull from the same crawled content. The technical foundations that determine whether Google can access, render, and understand your site are the same ones that determine whether AI retrieval bots can use your content in AI-generated answers. Clean semantic HTML, accurate schema markup, accessible crawlability, and fresh, well-structured content — all of it carries over.
The one thing specifically worth checking is your robots.txt file. Some sites have accidentally blocked AI crawlers like GPTBot or ClaudeBot with broad disallow rules. If you want AI search visibility, double-check that those blocks are intentional rather than inherited.
This isn't a separate technical discipline. It's the same work, serving two purposes now.
8 Common Technical SEO Mistakes to Avoid
Even experienced teams slip on these. Not because they're careless, but because these problems tend to hide — they don't throw errors or generate alerts. They just quietly drag performance down.
-
1
noindex left on important pages — scan your XML sitemap for noindexed URLs and strip the tag from anything that should rank.
-
2
Canonical tags pointing to the wrong URL — verify self-referencing canonicals and confirm URL parameters don't inadvertently shift them.
-
3
Internal links pointing to redirected or broken pages — update them to the final destination to stop leaking authority through unnecessary hops.
-
4
Blocking CSS or JavaScript in robots.txt — Google needs these to render the page; accidental blocks here can make a site look broken to crawlers.
-
5
Judging Core Web Vitals from the homepage only — scores vary significantly across page templates, and the homepage is often the fastest page on the site.
-
6
Orphan pages nobody links to — connect them into your site architecture with contextual internal links.
-
7
Duplicate site versions (HTTP/HTTPS, www/non-www) — enforce one version with 301 redirects and let everything else redirect cleanly to it.
-
8
Assuming a sitemap guarantees indexing — an XML sitemap helps Google discover URLs; it doesn't override quality signals or force indexation.
Which Technical SEO Audit Tools You Actually Need
You don't need a large or expensive toolstack to run a thorough technical SEO audit. The free tools get you surprisingly far, and the paid crawlers are mainly about scale.
Free tier:
Google Search Console — still the single most valuable tool in the stack. Indexing status, coverage reports, Core Web Vitals, crawl stats, and the URL Inspection tool all live here.
Bing Webmaster Tools — a useful second perspective. Bing and Google index things differently, and it's worth knowing where the gaps are.
PageSpeed Insights and Lighthouse — the go-to pair for speed diagnostics and getting specific, prioritized fix recommendations.
Crawler tier (paid or freemium):
Screaming Frog — the flexible workhorse for site-wide crawls. Particularly strong for filtering status codes, broken links, redirect chains, and canonical tags at scale.
Sitebulb — similar crawling power, but with more structured reporting and built-in prioritization, which makes it more approachable if you're less experienced with crawl data.
The right tool depends on your site's size and what you're trying to diagnose, not on which one has the best logo. And it's worth saying: tools surface the problems. Interpreting them, ranking them by impact, and knowing what to fix first — that's where the real expertise is.
Turn This Checklist Into a Real Audit
The core principle behind this entire list comes down to one thing: fix the blockers before chasing the refinements. Work the tiers in order, and your effort lands where it actually matters.
A thorough technical SEO audit needs three things to go well — time, the right tools, and the judgment to know which of 40 flagged issues to touch first. Most teams have one or two of those at any given moment. That's usually where progress stalls: not from a lack of effort, but from prioritization uncertainty.
That's what we handle at SEO Jerry. Our Technical SEO Audit runs this same prioritized process end to end — from crawlability and indexability through to Core Web Vitals — and we fix the issues rather than hand you a raw list of them.
Ready to turn this checklist into real results? Get a professional Technical SEO Audit and let's work through it together.
Ready to Fix Your Technical SEO Issues?
Get a professional Technical SEO Audit and turn this checklist into real results.
Get Your Technical SEO Audit