internal linking

Technical SEO Audit Checklist — A Hands-On Guide for 2026

When was the last time you actually crawled your own site and looked at what Google sees? If you’re like most site owners I’ve worked with, the answer is either “never” or “too long ago.” I’ve run technical SEO audits on over 50 sites in the past five years, and the pattern is always the same: small technical issues quietly stack up until rankings start slipping.

A technical SEO audit isn’t glamorous. There’s no viral hack or secret trick. It’s methodical work that makes sure search engines can find, crawl, index, and rank your pages properly. Think of it as the foundation inspection before you decorate the house.

This guide walks you through every step of a technical SEO audit in 2026. I’ve organized it as a checklist you can follow from top to bottom, whether you’re auditing a 50-page blog or a 50,000-page e-commerce site.

What You Need for a Technical SEO Audit

Before you start digging into issues, gather your tools. You don’t need expensive enterprise software for a solid audit. Here’s my standard toolkit:

  • Google Search Console — Your single most important free tool. It shows exactly what Google sees, including crawl errors, index coverage, and Core Web Vitals data.
  • Screaming Frog SEO Spider — The free version crawls up to 500 URLs. For most small-to-medium sites, that’s enough. The paid version ($259/year) handles unlimited URLs.
  • PageSpeed Insights — Google’s own speed testing tool, powered by Lighthouse. Tests both mobile and desktop performance.
  • Chrome DevTools — Built into every Chrome browser. The Network and Performance tabs are essential for debugging speed issues.
  • Ahrefs Webmaster Tools or Semrush — Either works for checking backlink health and finding technical issues at scale.

Set aside 2-4 hours for a thorough audit of a site with fewer than 1,000 pages. Larger sites may take a full day. I recommend scheduling audits quarterly — monthly if you publish frequently or make regular site changes.

Crawlability and Indexing

Diagram showing the crawlability and indexing flow from Googlebot through robots.txt, XML sitemap, to indexed pages with status checks

If search engines can’t crawl your pages, nothing else matters. This is always my first stop in any audit.

Check Your robots.txt

Visit yoursite.com/robots.txt and look for anything suspicious. I once found a client’s staging Disallow: / directive that accidentally stayed after a migration. Their organic traffic dropped 73% before anyone noticed. The fix took 30 seconds; the recovery took three months.

Make sure you’re not accidentally blocking important directories, CSS files, or JavaScript that Googlebot needs to render your pages. Use Google’s robots.txt tester in Search Console to validate.

Review Your XML Sitemap

Your sitemap should include every page you want indexed and exclude everything you don’t. Check for these common issues:

  • Pages returning 404 or 301 status codes listed in the sitemap
  • Non-canonical URLs included
  • Sitemap not submitted in Google Search Console
  • Sitemap file exceeding the 50,000 URL or 50MB limit

For a deeper dive into sitemap best practices, I wrote a comprehensive guide on XML sitemaps for large websites that covers everything from sitemap indexes to dynamic generation.

Check Index Coverage

In Google Search Console, go to Pages (formerly Index Coverage). Look for pages marked as “Discovered – currently not indexed” or “Crawled – currently not indexed.” These are pages Google found but chose not to index — often a sign of thin content, duplicate issues, or crawl budget problems.

Run a site:yoursite.com search in Google to get a rough count of indexed pages. Compare that to your total page count. If there’s a big gap, you’ve got indexing issues to investigate.

Site Speed and Core Web Vitals

Core Web Vitals targets showing LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1 with optimization tips

Google has confirmed that Core Web Vitals are a ranking factor. In 2026, the three metrics that matter are:

Largest Contentful Paint (LCP) measures how quickly the main content loads. Target: under 2.5 seconds. The biggest culprits for poor LCP are unoptimized images, slow server response times, and render-blocking CSS or JavaScript. On one audit, I found a client loading a 4.2MB hero image. Compressing it to 180KB dropped their LCP from 6.1s to 1.8s.

Interaction to Next Paint (INP) replaced First Input Delay in 2024. It measures responsiveness across all interactions, not just the first one. Target: under 200ms. Heavy JavaScript frameworks are the usual culprit. Break long tasks into smaller chunks and defer non-critical scripts.

Cumulative Layout Shift (CLS) measures visual stability. Target: under 0.1. Always set explicit width and height attributes on images and video elements. Reserve space for ad slots and dynamically loaded content. I’ve seen CLS scores drop from 0.35 to 0.02 just by adding image dimensions.

Quick Speed Wins

These fixes consistently deliver the biggest improvements in my audits:

  1. Enable compression — Gzip or Brotli compression typically reduces file sizes by 70-80%.
  2. Implement browser caching — Set cache headers for static assets (images, CSS, JS) with expiry times of at least one year.
  3. Optimize images — Use WebP or AVIF format, lazy load below-the-fold images, and serve responsive sizes.
  4. Minimize render-blocking resources — Inline critical CSS, defer non-essential JavaScript, and use font-display: swap for web fonts.
  5. Use a CDN — Content delivery networks reduce latency by serving assets from geographically closer servers.

Mobile-Friendliness and Responsive Design

Google uses mobile-first indexing, meaning it primarily uses the mobile version of your content for indexing and ranking. If your site doesn’t work well on mobile, you’re invisible to a huge portion of search traffic.

Here’s what to check:

  • Viewport meta tag — Make sure <meta name="viewport" content="width=device-width, initial-scale=1"> is present on every page.
  • Tap targets — Buttons and links should be at least 48×48 pixels with adequate spacing. Google flags small tap targets as mobile usability issues.
  • Text readability — Font size should be at least 16px for body text without requiring pinch-to-zoom.
  • No horizontal scrolling — Content should fit within the viewport width. Test on actual devices, not just Chrome DevTools.
  • Content parity — Your mobile and desktop versions should have the same content. Hidden content on mobile may not get indexed.

I audit mobile usability by actually using the site on my phone for 10 minutes. Automated tools catch many issues, but nothing beats the frustration of trying to tap a tiny link with your thumb to motivate fixing it.

HTTPS and Security

HTTPS and security checklist showing a shield icon with SSL security checks including certificate validation, redirects, and security headers

HTTPS has been a ranking signal since 2014, and in 2026 it’s essentially mandatory. Browsers actively warn users about non-secure sites, which kills trust and increases bounce rates.

SSL Certificate Checks

Verify your SSL certificate is valid and not expiring soon. I schedule quarterly certificate checks because an expired cert can take your entire site offline. Most hosting providers now include free SSL through Let’s Encrypt, so there’s no excuse for running HTTP in 2026.

Mixed Content Issues

Mixed content happens when your HTTPS pages load resources (images, scripts, stylesheets) over HTTP. This triggers browser warnings and can break page functionality. Use Chrome DevTools Console to identify mixed content warnings, then update the URLs to HTTPS.

Security Headers

While not direct ranking factors, security headers signal a well-maintained site:

  • HSTS (Strict-Transport-Security) — Forces HTTPS connections
  • X-Content-Type-Options: nosniff — Prevents MIME type sniffing
  • X-Frame-Options — Protects against clickjacking
  • Content-Security-Policy — Controls which resources can load

Check your headers at securityheaders.com — an A+ grade takes 15 minutes to configure and gives you peace of mind.

Structured Data and Schema Markup

Structured data helps search engines understand your content and can earn rich results (star ratings, FAQ dropdowns, how-to steps) in search results. These rich results consistently improve click-through rates by 20-30% in my experience.

Common Schema Types to Audit

  • Article/BlogPosting — For blog posts and news articles
  • Organization — Your brand information, logo, social profiles
  • FAQ — Frequently asked questions that can appear directly in search results
  • BreadcrumbList — Navigation breadcrumbs that show site hierarchy in SERPs
  • Product — For e-commerce pages with price, availability, and reviews
  • HowTo — Step-by-step instructions with optional images

Use Google’s Rich Results Test to validate your structured data. Look for errors and warnings — even valid schema can have issues that prevent rich results from showing. For a complete implementation guide, check out my article on schema markup for SEO.

JSON-LD Best Practices

Always use JSON-LD format (recommended by Google) rather than Microdata or RDFa. Place it in the <head> section. Make sure the structured data accurately represents the page content — Google penalizes misleading markup. One site I audited had Product schema on their blog posts, which resulted in a manual action that took weeks to resolve.

Internal Linking and Site Architecture

Internal linking structure diagram showing homepage connected to categories and posts with parent links and cross-links

Internal links distribute authority across your site and help search engines understand your content hierarchy. Poor internal linking is the most underrated technical SEO issue I encounter.

The Three-Click Rule

Every important page should be reachable within three clicks from the homepage. Use Screaming Frog’s crawl depth report to identify pages buried too deep. Pages at crawl depth 4+ often struggle to rank because they receive less internal link equity.

Orphan Pages

Orphan pages have no internal links pointing to them. They’re essentially invisible to search engine crawlers that follow links. I find orphan pages on nearly every audit — usually old landing pages or product pages that were removed from navigation but never redirected or deleted.

Anchor Text Distribution

Review your internal link anchor text. It should be descriptive and varied, naturally incorporating relevant keywords. Avoid generic text like “click here” or “read more.” Descriptive anchors help both users and search engines understand what they’ll find on the linked page.

Broken Internal Links

Run a full crawl and export all links returning 404 status codes. Every broken link is a dead end for both users and crawlers. Fix them by updating the URL, setting up a 301 redirect, or removing the link entirely. On a recent audit, I found 127 broken internal links on a 400-page site — all caused by a URL restructuring that nobody updated the old links for.

Canonical Tags and Duplicate Content

Duplicate content confuses search engines because they don’t know which version to rank. Canonical tags tell Google which URL is the “official” version of a page.

Common Duplicate Content Issues

  • WWW vs non-WWW — Pick one and redirect the other with a 301.
  • Trailing slashes/page/ and /page are technically different URLs. Be consistent.
  • HTTP vs HTTPS — All HTTP URLs should redirect to HTTPS.
  • URL parameters — Sorting, filtering, and tracking parameters create duplicate URLs. Use canonical tags or parameter handling in Search Console.
  • Pagination — Category and archive pages with pagination need proper canonical treatment.

Auditing Canonical Tags

Crawl your site and check that every page has a self-referencing canonical tag, every canonical URL returns a 200 status code, no page canonicalizes to a redirected or 404 URL, and canonical tags match between mobile and desktop versions.

I once found a site where a plugin was setting canonical tags to a staging domain. Every page was telling Google that the “real” version lived at staging.example.com. Traffic dropped 60% before the team noticed. Always verify your canonicals point to production URLs.

Hreflang for International Sites

If you serve content in multiple languages or target different regions, implement hreflang tags. Each language version should reference all other versions, including itself. Errors here are extremely common — Google’s John Mueller has called hreflang “one of the most complex aspects of SEO.” Validate your implementation with hreflang-checker tools before assuming everything works.

The Complete Checklist

Complete technical SEO audit summary with foundation checks and performance checks organized in two columns

Here’s every check from this guide in one place. I print this out and work through it section by section during audits:

Crawlability & Indexing

  • robots.txt allows important pages and resources
  • XML sitemap is valid and submitted to Search Console
  • No critical pages blocked by noindex tags
  • Index coverage report shows no unexpected exclusions
  • Site:search count roughly matches expected page count

Site Speed & Core Web Vitals

  • LCP under 2.5 seconds on mobile and desktop
  • INP under 200ms
  • CLS under 0.1
  • Images compressed and served in modern formats
  • Browser caching and compression enabled

Mobile & Responsiveness

  • Viewport meta tag present on all pages
  • Tap targets at least 48x48px
  • No horizontal scrolling on mobile
  • Content parity between mobile and desktop

HTTPS & Security

  • Valid SSL certificate with adequate expiry date
  • HTTP to HTTPS redirects working
  • No mixed content warnings
  • Security headers configured

Structured Data

  • Schema markup valid in Rich Results Test
  • JSON-LD format used (not Microdata)
  • Markup accurately reflects page content
  • No manual actions for structured data in Search Console

Internal Linking

  • All important pages within 3 clicks of homepage
  • No orphan pages
  • No broken internal links (404s)
  • Descriptive anchor text used

Canonicals & Duplicates

  • Self-referencing canonical on every page
  • WWW/non-WWW redirect in place
  • URL parameters handled properly
  • Hreflang tags correct (if applicable)

FAQ

How often should I run a technical SEO audit?

I recommend a full technical audit every quarter, with monthly spot checks on critical metrics like Core Web Vitals and crawl errors. If you’re making frequent site changes — redesigns, migrations, new features — increase the frequency to monthly. Automated monitoring tools can alert you to issues between scheduled audits.

Can I do a technical SEO audit without paid tools?

Absolutely. Google Search Console, PageSpeed Insights, Chrome DevTools, and the free version of Screaming Frog cover about 80% of what you need. Paid tools like Ahrefs or Semrush add convenience with scheduled crawls and historical data, but they’re not required for an effective audit. I did my first two years of professional audits with only free tools.

What’s the most common technical SEO issue you find?

Broken internal links and missing or incorrect canonical tags, by far. On average, I find 15-20 broken internal links per 100 pages audited. These accumulate over time as content gets updated, moved, or deleted without proper redirects. The fix is straightforward but tedious — which is why automated crawling tools are so valuable.

How long does it take to see results from fixing technical SEO issues?

It depends on the severity. Critical issues like a robots.txt blocking your entire site can show improvement within days of fixing. Core Web Vitals improvements typically reflect in rankings within 2-4 weeks. Broader changes like fixing internal linking structure or resolving duplicate content usually take 4-8 weeks as Google recrawls and re-evaluates your pages.