Technical SEO Audit Checklist: Run a Full Audit

Run the audit top to bottom. Each section is a pass over one layer of the site; the sections build on each other, so fix everything in a section before moving to the next. Scope the depth to your site size — a five-page brochure site does not need the same crawl-budget attention as a fifty-thousand-URL marketplace — but the order of checks is the same for both.

For each item, mark it pass, fail, or not applicable. Every fail becomes a finding; the Priority Matrix at the end tells you the order to fix them in.

The crawler's job is to discover your pages and decide which to index. If this layer is broken, nothing downstream matters.

Robots.txt

• robots.txt exists and is served correctly (no 404, no redirect)
• It blocks only what should be blocked — admin, search results, parameter soup — and does not accidentally block CSS, JS, images, or real content
• No blanket Disallow: / that kills the whole site
• The sitemap URL is referenced in robots.txt

Sitemap

• An XML sitemap exists and is submitted in Google Search Console
• It contains only canonical URLs (no duplicate/parameter versions), with no 404s or redirects inside
• lastmod is accurate — misleading dates erode trust in the sitemap

Canonicals

• Every page has a self-referencing canonical tag
• No page canonicalizes to a URL that redirects or 404s
• No conflicting signals (canonical pointing one way, internal links another)

Indexing status

• Check "Crawled but not indexed" and "Discovered but not indexed" in Search Console — pages stuck here are pages the crawler found but decided not to index, usually for quality, duplicate, or crawl-depth reasons (Crawled but Not Indexed, Google Crawl Budget)
• No important pages are accidentally noindex
• No important pages are behind login walls, paywalls, or infinite-scroll traps the crawler cannot pass
• 404s are handled — soft-404s (pages returning 200 with "not found" content) are cleaned up

Architecture determines what the crawler can reach and what it thinks matters.

• Every important page is within roughly four clicks of the homepage (Internal Linking Structure)
• URL structure is clean and permanent — short, readable, no changing URLs after launch
• No parameter-based duplicates flooding the crawl (sort, filter, tracking parameters produce separate URLs unless handled)
• No orphan pages — pages with no internal links pointing to them
• Breadcrumbs exist and match the URL hierarchy (Breadcrumb Navigation SEO)
• HTTPS is enforced site-wide; no mixed content or insecure page warnings

How your pages become visible to the crawler decides whether your content actually exists to be indexed.

• The content that matters is in the initial HTML — not loaded only by JavaScript
• If the site is a JavaScript-rendered app, key content is server-side rendered or prerendered, and the rendered output is tested with the crawler's rendering (Search Console URL Inspection renders like Google does) (Frontend vs Backend Rendering (SEO Impact))
• Text, headings, and internal links are all present in the crawlable output
• Images have descriptive alt text and are not the only content on the page
• Lazy-loaded content (images, infinite scroll) has a fallback the crawler can read

Structured data is how you tell search engines explicitly what a page is — and it is where audits find both missed opportunities and dead markup.

• Appropriate schema exists for the page types that matter: Article, Product, LocalBusiness, Organization, BreadcrumbList, FAQ (semantic only — see below)
• Schema matches the visible content (no markup for content that is not on the page)
• Schema validates with no errors or warnings (Rich Results Test)
• LocalBusiness schema uses the precise subtype for the business, with areaServed, geo, and openingHours populated where relevant (Structured Data (Schema.org), Local Schema Markup)
• FAQPage markup is not relied on for rich results — Google discontinued FAQ rich results entirely in May 2026; FAQ content is still valuable for users and for semantic clarity, but it no longer produces the expanded rich result, and building markup around a retired feature wastes effort

Speed is a ranking factor hiding in plain sight — it is invisible until it hurts, then it leaks rankings quietly every day.

• Core Web Vitals pass: LCP (loading), INP (interaction), CLS (layout stability) within Google's thresholds
• Largest Contentful Paint is not dominated by a slow hero image or render-blocking script
• No layout shift from images or embeds without reserved space
• Mobile performance is genuinely good — most searches happen on phones, and the mobile experience is what Google's indexing evaluates
• No per-request database queries during HTML rendering (the classic slow-site pattern) — cache aggressively
• Assets (CSS, JS, images) are compressed and reasonably sized; nothing critical blocks first paint

Internal links are the map you hand to both users and crawlers — and a silent audit item that shapes everything.

• Every important page receives internal links with descriptive anchor text (not "click here")
• Cluster pages link up to their pillar; pillars link down to their clusters
• No important page is a dead end (links out but nothing links to it)
• Footer and navigation expose the site's full structure
• No broken internal links (check with a crawler or Search Console's link report) (On-Page SEO)

Content problems that look editorial but are diagnosed technically.

• No thin pages — pages with almost no content that add nothing beyond a template
• No near-duplicate pages (same content on multiple URLs, city-name-swap templates, paginated fragments that should be one page) — Google's spam policies target scaled, templated mass-production, and thin location pages are a classic version of the pattern
• No keyword cannibalization — two pages targeting the same intent, splitting the ranking signal
• Title tags and meta descriptions are unique, correct length, and not duplicated across pages

Indexing is not automatic — new and changed pages need a push, and there are two legitimate levers.

• New important pages are submitted via URL Inspection in Search Console (and requested for indexing)
• The site uses IndexNow where supported — a lightweight protocol that pings search engines the moment a page changes, so fresh content does not wait for the next crawl cycle (IndexNow)
• XML sitemaps are updated when content ships, not monthly

Not all findings are equal. Rank every finding on two axes — impact (how much it costs in rankings) and effort (how hard it is to fix) — and work this order:

1. Indexability failures (pages blocked, noindexed, or never reached) — nothing ranks if the crawler cannot index it. Fix first regardless of effort.
2. Canonical and duplicate-content conflicts — split authority is silently wasted authority.
3. Rendering failures — content invisible to the crawler is content that does not exist.
4. Performance failures — slow pages leak rankings continuously; fix the worst offenders, then the rest.
5. Architecture and internal-link gaps — improve the map so equity flows where it should.
6. Structured data and content-level items — polish that compounds once the foundation is sound.

The one thing to resist is chasing perfection: the goal of an audit is a healthy site that ranks, not a site with zero theoretical issues. Many technical items have diminishing returns, and the highest-ROI work is usually fixing the indexability and duplication failures first (Technical Perfectionism — the anti-perfectionism concept the XKnow vault uses to keep audits pragmatic).

This checklist catches what is broken. The harder question is what to build — and that is where a checklist becomes a system. A real content operation needs more than a fix list: it needs the keyword map that says which pages matter, the content strategy that says which pages to build, and the industry-specific audit knowledge that says what "healthy" means in your vertical.

The XKnow SEO Vault is a Markdown / Obsidian knowledge system that contains this checklist as one asset among many: 571 interconnected notes covering keyword research, search intent, local SEO, technical SEO, content strategy, E-E-A-T, schema, link building, long-tail SEO, and audits — plus industry-specific audit checklists (medical schema checklists, local audit checklists for home services, legal local-SEO checklists) and the research evidence behind each requirement.

If you want technical SEO to be a maintained system rather than a once-a-year fire drill, the vault is where the checklists, SOPs, and industry versions live — with the research references that say why each item matters.

Get the complete SEO Knowledge Vault →

• Google structured data changes; seo-kreativ, inetventures (2026) — Google retired FAQ rich results in 2026; FAQPage markup now only supports semantic understanding. (accessed 2026-09-09)
• Google Spam Policies for Web Search (official, updated 2026-08-28) — Google spam policies target scaled content abuse and doorway pages; genuine local pages are unaffected. (accessed 2026-09-09)

• Mobile SEO Checklist
• SEO for Developers
• SEO Checklist