Technical SEO
Technical SEO Audit Checklist: 12 Things Killing Your Rankings Before You Even Publish
Most ranking problems in 2026 trace back to crawlability or indexation, not content quality. Before you write another word of copy, check whether Google can actually find, crawl, and index the pages you already have — a gap between crawled and indexed pages of more than 20-30% is a clear signal something structural is broken.
Business owners almost always call me about content — “we need more blog posts,” “our copy needs work.” Sometimes that’s true. But just as often, the real problem is invisible from the front end: a robots.txt rule quietly blocking a whole section, a sitemap that hasn’t been regenerated in months, thin archive pages diluting the site’s authority. No amount of great writing fixes a page Google was never allowed to see in the first place.
This is the checklist I actually run, in the order it actually matters — crawlability first, because nothing else means anything if Google can’t reach the page at all.
Why the order matters
It’s tempting to jump straight to whichever item looks easiest, but fixing schema markup on a page Google can’t crawl accomplishes nothing — you’re polishing a door nobody can open. The sequence below runs crawlability first, then indexation, then everything downstream of it, because that’s the order Google’s own pipeline actually works in. Skip ahead and you’ll spend hours “fixing” things that were never the real bottleneck, then wonder why nothing changed in Search Console three weeks later.
The 12-point checklist
Robots.txt blocking pages it shouldn’t
The single most common self-inflicted wound. A rule meant for a staging environment gets left in production, and entire sections silently disappear from crawling. Check it directly, don’t assume.
Noindex tags left on live pages
Almost as common — a page built during development with noindex on, then published without anyone removing it. Spot-check every important template, not just the homepage.
Missing or stale XML sitemap
Your sitemap is a direct signal about which URLs deserve attention. If it hasn’t regenerated since your last content push, Google is working from an outdated map of your site.
A crawled-vs-indexed gap over 20-30%
Compare your sitemap’s URL count against what’s actually indexed in Search Console. A large gap almost always means Google is crawling pages and deciding, deliberately, not to index them.
Thin or auto-generated archive pages
Author pages, empty category archives, and tag pages with one post on them dilute your site’s overall quality signal. Either build them into something genuinely useful or noindex them.
Conflicting canonical signals
Your rel=canonical tag, sitemap entry, and internal links all need to point to the same preferred URL. When they disagree, you’re asking Google to guess which version matters — and it won’t always guess right.
Redirect chains and loops
Every extra hop between the old URL and the final destination wastes crawl budget and slows the page down. One redirect is fine; three in a row is a problem worth fixing directly at the source.
Missing or broken schema markup
With only a small share of sites implementing structured data properly, accurate Organization, Article, and Service schema is a genuine differentiator — and it’s how AI engines increasingly decide what to cite.
Core Web Vitals failures
LCP, INP, and CLS aren’t separate from technical SEO — they’re part of it. See our Core Web Vitals breakdown for what’s usually behind a failing score.
Mobile usability errors
Google indexes the mobile version of your site by default. Text too small to read, buttons too close together, or content that only appears on desktop all count against you directly.
Orphan pages and broken internal links
A page with no internal links pointing to it is invisible to both visitors and crawlers, no matter how good the content is. Every important page should be reachable within a couple of clicks from the homepage.
No AI-crawler readiness
GPTBot, ClaudeBot, PerplexityBot, and Google-Extended are now hitting most sites alongside Googlebot. Check your robots.txt handles them intentionally, not by accident — this is table stakes for showing up in AI search visibility too.
One mistake worth naming directly: trusting a single automated tool and calling the audit done. Automated crawlers are excellent at finding broken links and missing tags, but they can’t tell you why Google is choosing not to index a page it can clearly see, or which of three redirect chains is actually costing you the most crawl budget. That diagnostic layer — reading server logs, cross-referencing Search Console data against what a crawler reports — is where a checklist stops being enough on its own.
How to run this yourself
- Pull your Coverage report in Google Search Console before touching anything else.
- Crawl your own site with a free tool like Screaming Frog’s free tier.
- Compare sitemap URL count against indexed count — flag any gap over 20%.
- Fix in order: crawlability first, then indexation, then speed and schema.
- Re-check quarterly — a clean audit today doesn’t stay clean after the next core update.
Working through all twelve manually takes real time, and misdiagnosing the cause of a crawl or indexation issue can waste months chasing the wrong fix. Our technical SEO audit covers exactly this list with the tooling and log-file analysis to actually confirm the cause, not just guess at it — usually paired with the Growth package for sites that need the fixes implemented too, not just diagnosed.
Not sure how many of these 12 apply to your site?
Send me your URL and I’ll tell you honestly which of these are actually costing you traffic.
Start a projectFrequently asked questions
What is a technical SEO audit?
A technical SEO audit checks the infrastructure behind your website — crawlability, indexation, site speed, schema markup and mobile usability — rather than the content itself. It finds the issues stopping Google from finding, understanding or trusting pages that would otherwise rank.
How often should I run a technical SEO audit?
Quarterly is a reasonable baseline for most small business sites, since Google rolls out multiple core updates a year and new AI crawlers keep appearing. A full audit is also worth running any time you notice an unexplained traffic drop, right after a site migration, or before a major content push.
What’s the difference between crawled and indexed?
Crawled means Google’s bot has visited and read the page. Indexed means Google decided the page was worth storing and eligible to appear in search results. A page can be crawled repeatedly and still never get indexed if Google judges it thin, duplicate, or not valuable enough — this gap is one of the most common things a technical audit uncovers.
Do I need schema markup on every page?
Not every page needs every schema type, but every page should have something accurate describing what it is — Organization and WebSite schema site-wide, plus Article, Service, or FAQPage schema where relevant. Only a small share of websites implement any structured data at all, which makes it a real competitive advantage rather than a formality.
Can I run a technical SEO audit myself?
A small site owner can work through a structured checklist like this one using free tools — Google Search Console, PageSpeed Insights, and a crawler like Screaming Frog’s free tier. Log file analysis and fix validation across a larger or more complex site usually benefit from a professional audit, since misdiagnosing the cause of a crawl or indexation issue can waste months.