How to Run a Technical SEO Audit (2026 Guide)

Content gets the credit, but technical SEO decides whether that content ever gets a chance. If Googlebot can't crawl a page, can't render it, or decides it's a duplicate, it doesn't matter how good the writing is — the page won't rank. A technical SEO audit is the systematic check that nothing in your site's plumbing is quietly throwing away rankings you've already earned.

This guide walks through the audit as a repeatable process. Run it top to bottom; the early steps surface the issues that block everything downstream, so order matters.

1. Check crawlability first

Start where Google starts: can it reach your pages at all? Crawlability problems are the most expensive because they invalidate everything below them. Pull your crawler and your server logs and confirm Googlebot is getting clean responses, not redirects, blocks, or errors.

• robots.txt — confirm you aren't accidentally blocking important directories. A single stray Disallow: can de-index a whole section. Reference your sitemap here too.
• Crawl budget — on large sites, watch for Googlebot burning crawls on faceted URLs, session IDs, infinite calendars, and parameter duplicates instead of your money pages.
• Server responses — important URLs should return 200, not 4xx, 5xx, or unexpected redirects.

A minimal, healthy robots.txt usually looks like this:

User-agent: *
Allow: /
Sitemap: https://example.com/sitemap.xml

If Googlebot can't crawl it, every other optimization on the page is invisible.

2. Audit indexation and duplicate content

Crawling gets a page read; indexing gets it eligible to rank. The single most revealing report in any audit is index coverage — the count of pages you intend to be indexed versus the count Google actually indexed. A large gap in either direction is a flag.

• Index coverage — too few indexed pages means something is blocking them; too many usually means thin, parameter, or duplicate URLs are leaking in.
• Canonicalization — every page should declare a self-referencing canonical, and duplicate variants (HTTP/HTTPS, www/non-www, trailing slash, tracking parameters) should all point to one canonical version.
• Duplicate content — boilerplate pages, paginated archives, and printer-friendly copies can compete with your real page. Consolidate with canonicals or noindex as appropriate.
• Noindex / nofollow audit — make sure no template is shipping a stray noindex on pages you want ranked. This is one of the most common silent killers.

3. Review site architecture and internal linking

Architecture is how authority and crawl priority move through your site. A flat, logical structure where important pages are a few clicks from the homepage outranks a deep, tangled one. Map your click depth and your internal link graph.

• Click depth — key pages should be reachable within three clicks of the homepage. Pages buried deeper get crawled less and rank weaker.
• Internal links — orphan pages (zero internal links) are nearly invisible to Google. Every page that matters needs descriptive, contextual internal links pointing to it.
• Anchor text — descriptive anchors tell Google what the target page is about. Pair this with a strong on-page SEO checklist so each page reinforces the right terms.

4. Measure Core Web Vitals and page speed

Speed is a ranking signal, but more importantly it's a measured user experience. Google grades the field data of real visitors, not a one-off lab score, so optimize for the percentiles your actual users hit.

• Largest Contentful Paint (LCP) — aim under 2.5s. Usually fixed by faster servers, image compression, and removing render-blocking resources.
• Interaction to Next Paint (INP) — aim under 200ms. Driven by heavy JavaScript and long main-thread tasks.
• Cumulative Layout Shift (CLS) — aim under 0.1. Reserve space for images, ads, and embeds so the page doesn't jump.

Treat field data (real users) as the source of truth and lab tools as your debugger for chasing down the cause.

5. Confirm mobile-friendliness

Google indexes the mobile version of your site, so the mobile experience is your site as far as ranking is concerned. Check that the mobile and desktop versions serve the same primary content, structured data, and metadata.

• Parity — don't hide important content, links, or schema behind desktop-only rendering.
• Viewport and tap targets — readable text without zooming, and buttons that aren't crammed together.
• No intrusive interstitials — pop-ups that block content on mobile can suppress rankings.

6. Verify HTTPS and security

HTTPS is a baseline ranking signal and a trust requirement. Audit it end to end so there are no weak links.

• Valid certificate — not expired, correctly covering all subdomains in use.
• No mixed content — every asset (images, scripts, fonts) should load over HTTPS, or browsers will flag the page.
• Forced redirects — all HTTP requests should 301 to their HTTPS equivalent, and only one canonical host should resolve.

7. Validate structured data

Structured data doesn't directly raise rankings, but it earns rich results that lift click-through, and broken markup can disqualify you from those features entirely. Crawl for schema, then validate it.

• Coverage — Article, FAQ, Product, Breadcrumb, and Organization markup where each applies.
• Validity — no missing required fields or syntax errors that trigger warnings.
• Accuracy — markup must reflect what's visible on the page; mismatches can lead to manual actions.

If schema is new to you, our schema markup guide covers which types to add and how to implement them without breaking the spec.

8. Audit your XML sitemaps

Your sitemap is the list of URLs you're asking Google to crawl, so it should be clean and current. A sitemap full of redirects and errors trains Google to trust it less.

• Only canonical, indexable 200 URLs — no redirects, no noindex pages, no error URLs.
• Submitted and reachable — referenced in robots.txt and submitted in Search Console.
• Split large sitemaps — keep each under 50,000 URLs and use a sitemap index for big sites.

9. Find broken links and redirect chains

Broken links and messy redirects waste crawl budget and leak the authority your links should be passing. Crawl the whole site and flag every non-200 destination.

• Broken internal links — fix or remove links pointing to 404s.
• Redirect chains and loops — collapse A → B → C into a single A → C hop so equity isn't diluted.
• Soft 404s — pages that return 200 but show "not found" content confuse indexing and should return a real 404 or 410.

10. Run log-file and render checks

The deepest layer of the audit confirms what Google actually sees, not what you assume it sees. Two checks separate a thorough audit from a surface one.

• Log-file analysis — server logs show exactly which URLs Googlebot crawls and how often, exposing wasted budget and ignored pages that no crawler simulation can.
• Render check — for JavaScript-heavy sites, inspect the rendered HTML to confirm content and links exist after rendering, not just in the raw source. If critical content only appears after client-side JavaScript runs, Google may miss it.

Fixing what these checks surface is often the difference between a site that crawls efficiently and one that quietly strands half its pages.

Frequently asked questions