From the Blog Technical SEO Audit

SEO

A complete technical SEO audit checklist: crawlability, indexation, Core Web Vitals, schema markup, mobile optimization, and site architecture — with free tools for every step.

What Is a Technical SEO Audit?

A technical SEO audit is a systematic review of your website's technical foundation to identify issues that prevent search engines from crawling, indexing, and ranking your pages. It covers crawlability, indexation, site speed, mobile friendliness, schema markup, site architecture, and security.

Most businesses focus on creating content and building backlinks, but ignore the technical foundation that makes all of that work. You can write the best article in your industry, but if Google cannot crawl it, index it, or understand its structure, it will never rank.

This checklist covers every technical SEO issue we fix for clients, in the order they matter. Each step includes what to check, why it matters, and the free tool to check it with.

Phase 1: Crawlability and Indexation

Crawlability and indexation are the foundation of technical SEO. If Google cannot access your pages or chooses not to index them, nothing else matters.

Step 1: Check robots.txt for Blocking Errors

Your robots.txt file tells search engines which pages to crawl and which to skip. A misconfigured robots.txt can block entire sections of your site from Google.

• What to check: visit yoursite.com/robots.txt and look for Disallow rules that might block important pages.
• Common mistakes: blocking CSS or JavaScript files (prevents Google from rendering your pages), blocking entire directories that should be indexed, using Disallow: / instead of specific paths.
• Tool: Google Robots.txt Tester in Search Console.

Step 2: Verify Your XML Sitemap

Your sitemap tells Google which pages exist on your site and which ones to prioritize. A broken or outdated sitemap wastes crawl budget and delays indexation.

• What to check: verify your sitemap exists at /sitemap.xml, contains only 200-status URLs, excludes noindex pages, and is submitted in Search Console.
• Common mistakes: including 404 or redirect URLs, missing important pages, sitemap not updated after site changes.
• Tool: Google Search Console Sitemaps report.

Step 3: Check Google Search Console Coverage Report

The Coverage report shows which pages Google has indexed, which it has excluded, and why. This is the single most important report for identifying indexation issues.

• What to check: look for pages in "Error" and "Excluded" states. Focus on "Crawled - currently not indexed" and "Discovered - currently not indexed" warnings.
• Common issues: pages blocked by robots.txt, soft 404 errors, redirect chains, canonical tag issues, thin content excluded by Google.
• Tool: Google Search Console Coverage report.

Step 4: Fix Crawl Errors

Crawl errors mean Google tried to access a page and failed. Every crawl error is a page that will not rank.

• What to check: 404 errors (page not found), 500 errors (server errors), redirect loops, and timeout errors.
• Fix: restore missing pages, fix broken internal links, resolve redirect chains, and ensure server stability.
• Tool: Google Search Console Pages report + Screaming Frog crawl.

Step 5: Audit Internal Linking

Internal links help Google discover pages and understand their importance. Orphan pages (pages with no internal links pointing to them) are invisible to search engines.

• What to check: find orphan pages, broken internal links, and pages with too few internal links.
• Fix: add contextual internal links from relevant pages, fix broken links, and ensure every important page has at least 3 internal links.
• Tool: Screaming Frog Internal Links report.

Phase 2: Site Speed and Core Web Vitals

Site speed is a confirmed Google ranking factor. Core Web Vitals (LCP, INP, CLS) measure the real user experience of your site's loading speed, interactivity, and visual stability.

Step 6: Run Google PageSpeed Insights

PageSpeed Insights gives you both lab data (simulated test) and field data (real user measurements). Focus on the field data — it reflects what actual visitors experience.

• What to check: LCP (Largest Contentful Paint) should be under 2.5 seconds, INP (Interaction to Next Paint) under 200ms, CLS (Cumulative Layout Shift) under 0.1.
• Tool: Google PageSpeed Insights (pagespeed.web.dev).

Step 7: Optimize Largest Contentful Paint (LCP)

LCP measures how long it takes for the largest visible element on your page to load. This is usually the hero image or the main heading.

• What to check: identify the LCP element, check if the image is optimized, compressed, and served in modern formats.
• Fix: compress images to WebP, preload the LCP image, use responsive image attributes, and reduce server response time.
• Tool: PageSpeed Insights LCP diagnostic.

Step 8: Fix Cumulative Layout Shift (CLS)

CLS measures visual stability — how much the page layout shifts unexpectedly during loading. High CLS means elements jump around as the page loads, frustrating users.

• What to check: images without width/height attributes, dynamically injected content, web fonts causing FOIT/FOUT, ads or embeds without reserved space.
• Fix: set explicit width and height on all images, reserve space for ads and embeds, use font-display: swap for web fonts.
• Tool: PageSpeed Insights CLS diagnostic.

"Technical SEO is the foundation. Without it, your content and backlinks have nothing to stand on. Fix the foundation first, then build on top of it."

Step 9: Reduce Render-Blocking Resources

Render-blocking CSS and JavaScript prevent the page from displaying until they finish loading. This directly impacts LCP and First Contentful Paint.

• What to check: identify render-blocking stylesheets and scripts in PageSpeed Insights.
• Fix: inline critical CSS, defer non-critical JavaScript, load third-party scripts asynchronously, and minify CSS and JS files.
• Tool: PageSpeed Insights "Eliminate render-blocking resources" audit.

Phase 3: Mobile Optimization

Google uses mobile-first indexing, meaning it primarily uses the mobile version of your site for ranking and indexing. If your mobile experience is poor, your desktop rankings suffer too.

Step 10: Test Mobile Usability

Google's Mobile Usability report identifies pages that do not work well on mobile devices — text too small, clickable elements too close, content wider than screen.

• What to check: pages with mobile usability errors in Search Console, responsive design issues, viewport configuration.
• Tool: Google Search Console Mobile Usability report + Chrome DevTools device toolbar.

Step 11: Verify Responsive Design

Your site should work perfectly on every screen size — from 320px phones to 2560px monitors. Responsive design means the layout adapts fluidly, not that it just "shrinks."

• What to check: test on real devices (iPhone, Android, tablet), check for horizontal scrolling, verify touch targets are large enough, ensure text is readable without zooming.
• Tool: Chrome DevTools responsive mode + real device testing.

Step 12: Check Mobile Page Speed

Mobile connections are slower than desktop. A page that loads in 2 seconds on desktop might take 5 seconds on 4G. Test speed specifically on mobile.

• What to check: run PageSpeed Insights with mobile selected, check LCP and INP on mobile specifically.
• Fix: optimize images for mobile (smaller sizes), reduce JavaScript execution time, implement lazy loading for below-the-fold content.
• Tool: PageSpeed Insights mobile test.

Phase 4: On-Page Technical Elements

On-page technical elements help search engines understand what each page is about and how pages relate to each other.

Step 13: Audit Title Tags and Meta Descriptions

Title tags and meta descriptions are the first things users see in search results. They directly affect click-through rates and help search engines understand page content.

• What to check: every page has a unique title tag (50-60 characters), every page has a unique meta description (150-160 characters), target keywords appear naturally in titles and descriptions.
• Common issues: duplicate titles across pages, missing meta descriptions, titles too long (truncated in SERPs), keyword stuffing.
• Tool: Screaming Frog Page Titles and Meta Descriptions report.

Step 14: Validate Heading Structure

Headings create a logical hierarchy that helps both users and search engines understand your content. Every page should have one H1, followed by H2s and H3s in order.

• What to check: one H1 per page, no skipped heading levels (H1 > H3), headings contain relevant keywords, logical content hierarchy.
• Tool: Screaming Frog H1 Report + manual review.

Step 15: Check Canonical Tags

Canonical tags tell Google which version of a page is the "master" version. Without them, Google might index duplicate versions of the same content, diluting your rankings.

• What to check: every page has a self-referencing canonical tag, canonical URLs are absolute (not relative), no canonical chains, no conflicting canonical and noindex tags.
• Tool: Screaming Frog Canonicals report.

Step 16: Verify Structured Data (Schema Markup)

Schema markup helps search engines and AI engines understand your content's structure, entities, and relationships. Valid schema can trigger rich results in Google and citations in AI engines.

• What to check: Article schema on blog posts, FAQPage schema on FAQ sections, BreadcrumbList schema on all pages, LocalBusiness schema on homepage, Organization schema on homepage.
• Common issues: schema validation errors, missing required fields, schema on pages where it does not apply.
• Tool: Google Rich Results Test + Schema.org validator.

Phase 5: Site Architecture and Security

Site architecture affects how search engines discover and prioritize your content. Security affects user trust and rankings.

Step 17: Audit URL Structure

Clean, descriptive URLs help search engines and users understand what a page is about. Parameter-heavy, dynamic URLs are harder to crawl and less click-worthy in search results.

• What to check: URLs are descriptive and keyword-rich, no excessive parameters, no session IDs in URLs, consistent URL casing (lowercase), no deep nesting (more than 3 levels deep).
• Tool: Screaming Frog URL report.

Step 18: Check HTTPS and Security

HTTPS is a confirmed Google ranking factor. Mixed content (HTTP resources on an HTTPS page) causes security warnings and breaks page functionality.

• What to check: entire site served over HTTPS, no mixed content warnings, valid SSL certificate, HTTP to HTTPS redirects in place.
• Tool: Why No Padlock + Chrome DevTools Security tab.

Step 19: Verify hreflang Tags (If Applicable)

If your site serves content in multiple languages or targets multiple countries, hreflang tags tell Google which version to show to which audience.

• What to check: hreflang tags are correct, bidirectional (every page references all language versions including itself), no conflicting canonical tags.
• Tool: Ahrefs hreflang tag checker + manual review.

Step 20: Audit Redirect Chains and Loops

Redirect chains (A redirects to B which redirects to C) waste crawl budget and slow down page loading. Redirect loops (A redirects to B which redirects back to A) make pages completely inaccessible.

• What to check: find chains longer than 2 redirects, identify redirect loops, verify all redirects point to the final destination URL.
• Fix: update internal links to point directly to the final URL, replace intermediate redirects with direct redirects.
• Tool: Screaming Frog Redirect Chains report.

How to Prioritize Your Fixes

Not all technical SEO issues are equal. Fix them in this order:

1. Critical (fix immediately): pages blocked from indexation, crawl errors on important pages, server errors (5xx), security issues (mixed content, expired SSL).
2. High priority (fix this week): Core Web Vitals failures, mobile usability errors, broken internal links, missing canonical tags.
3. Medium priority (fix this month): missing schema markup, suboptimal title tags, redirect chains, unoptimized images.
4. Low priority (fix when possible): URL structure improvements, hreflang optimization, internal link reorganization.

Frequently Asked Questions

Key Takeaways

• Start with crawlability and indexation — if Google cannot access your pages, nothing else matters.
• Fix Core Web Vitals: LCP under 2.5s, INP under 200ms, CLS under 0.1.
• Mobile-first indexing means your mobile experience determines your rankings.
• Validate schema markup with Google Rich Results Test on every page.
• Audit internal linking to ensure every important page has at least 3 internal links.
• Prioritize fixes: critical issues first, then high, medium, and low priority.
• Run a full audit every 3-6 months and a quick health check monthly.

← Back to all articles