Technical SEO Audit: Complete Step-by-Step Checklist

March 31, 2026 · 12 min read

A technical SEO audit is the foundation of any successful search strategy. Without a solid technical base, even the best content and link building efforts will underperform. This comprehensive guide walks you through every critical checkpoint — from crawlability to security — so you can identify and fix the issues that silently kill your rankings.

Whether you're managing an enterprise site with millions of pages or a small business website, this checklist will help you systematically uncover technical issues that prevent search engines from properly discovering, crawling, and ranking your content.

What Is a Technical SEO Audit?

A technical SEO audit is a systematic review of your website's infrastructure to ensure search engines can efficiently crawl, index, and render your pages. Unlike content audits that focus on keywords and copy, a technical audit examines the underlying architecture: server configuration, URL structure, page speed, mobile compatibility, and security.

Think of it as a health checkup for your website. You might look great on the surface, but hidden issues — slow server responses, broken redirects, missing canonical tags — can silently erode your search performance over months.

When should you run a technical audit?

• Quarterly as a routine maintenance task
• After a site migration or redesign
• When you notice a sudden drop in organic traffic
• Before launching a major content campaign
• After significant changes to your CMS or hosting
• When preparing for a major product launch or seasonal traffic spike
• After Google algorithm updates that impact your rankings

The average technical audit uncovers 50-200 issues depending on site size and complexity. Most sites have at least a dozen critical problems that directly impact rankings, even if they appear to function normally for human visitors.

Step 1: Crawlability & Indexing

If search engines can't crawl your pages, nothing else matters. Start your audit by verifying that Googlebot can access and index your most important content.

Robots.txt Audit

Your robots.txt file controls which pages search engines can crawl. A single misplaced directive can block your entire site from appearing in search results.

Check these critical elements:

• Verify robots.txt is accessible at yourdomain.com/robots.txt
• Ensure important pages aren't accidentally blocked
• Check that CSS and JavaScript files aren't disallowed (Google needs these for rendering)
• Verify sitemap location is declared correctly
• Remove outdated or conflicting directives

Common robots.txt mistakes include blocking entire sections with Disallow: /blog/ when only specific pages should be blocked, or using wildcards incorrectly. Test your robots.txt file using Google Search Console's robots.txt Tester tool.

XML Sitemap Validation

Your XML sitemap acts as a roadmap for search engines. It should list all important pages you want indexed, with accurate metadata about update frequency and priority.

Sitemap checklist:

• Verify sitemap is accessible and properly formatted
• Check that it contains only indexable URLs (no 404s, redirects, or noindex pages)
• Ensure sitemap size doesn't exceed 50MB or 50,000 URLs
• Validate lastmod dates are accurate
• Submit sitemap to Google Search Console and Bing Webmaster Tools
• Create separate sitemaps for different content types (pages, posts, images, videos)

Use our Sitemap Generator to automatically create and validate XML sitemaps that follow best practices.

Index Coverage Analysis

Review Google Search Console's Index Coverage report to identify pages that should be indexed but aren't, and vice versa.

Key metrics to monitor:

Crawl Budget Optimization

For larger sites (10,000+ pages), crawl budget becomes critical. Google allocates a limited number of pages it will crawl per day based on your site's authority and server capacity.

Optimize crawl budget by:

• Fixing redirect chains and loops
• Eliminating duplicate content
• Blocking low-value pages (filters, search results, session IDs)
• Improving server response times
• Using strategic internal linking to prioritize important pages

Step 2: Site Speed & Performance

Page speed is a confirmed ranking factor and directly impacts user experience. Google's Core Web Vitals have made performance optimization more important than ever.

Core Web Vitals Assessment

Google measures three key performance metrics that reflect real user experience:

• Largest Contentful Paint (LCP): Measures loading performance. Should occur within 2.5 seconds.
• First Input Delay (FID) / Interaction to Next Paint (INP): Measures interactivity. Should be less than 100ms (FID) or 200ms (INP).
• Cumulative Layout Shift (CLS): Measures visual stability. Should be less than 0.1.

Test your Core Web Vitals using Google PageSpeed Insights, which provides both lab data (simulated) and field data (real user measurements from Chrome User Experience Report).

Performance Optimization Checklist

Image optimization:

• Compress images without quality loss (use WebP or AVIF formats)
• Implement lazy loading for below-the-fold images
• Use responsive images with srcset attributes
• Specify width and height attributes to prevent layout shifts
• Consider using a CDN for image delivery

Code optimization:

• Minify CSS, JavaScript, and HTML
• Remove unused CSS and JavaScript
• Defer non-critical JavaScript
• Inline critical CSS for above-the-fold content
• Enable text compression (Gzip or Brotli)

Server and hosting:

• Enable browser caching with appropriate cache headers
• Use a Content Delivery Network (CDN)
• Upgrade to HTTP/2 or HTTP/3
• Optimize database queries and server-side code
• Consider upgrading hosting if server response time exceeds 200ms

Our Page Speed Analyzer provides detailed recommendations for improving each Core Web Vital metric with specific code examples.

Rendering and JavaScript Issues

Modern websites often rely heavily on JavaScript, which can create indexing problems if not implemented correctly.

Check for:

• Content that only appears after JavaScript execution
• Important links hidden in JavaScript that Googlebot might miss
• Excessive client-side rendering that delays content visibility
• JavaScript errors that prevent page functionality

Use Google Search Console's URL Inspection tool to see how Googlebot renders your pages. Compare the rendered HTML to what you see in your browser's developer tools.

Step 3: Mobile-Friendliness

Google uses mobile-first indexing, meaning it primarily uses the mobile version of your site for ranking and indexing. Mobile optimization isn't optional — it's essential.

Mobile Usability Testing

Run your site through Google's Mobile-Friendly Test and check Search Console's Mobile Usability report for issues like:

• Text too small to read
• Clickable elements too close together
• Content wider than screen
• Viewport not set correctly
• Incompatible plugins (Flash, etc.)

Responsive Design Verification

Test your site at multiple viewport sizes to ensure content adapts properly:

• 320px (small phones)
• 375px (iPhone standard)
• 768px (tablets)
• 1024px (small laptops)
• 1440px+ (desktop)

Common mobile issues to fix:

• Hidden content in accordions or tabs (make sure it's still crawlable)
• Different content between mobile and desktop versions
• Intrusive interstitials that block content
• Slow mobile page speed (often worse than desktop)
• Unplayable videos or inaccessible resources

Mobile Page Speed

Mobile connections are often slower and less reliable than desktop. Optimize specifically for mobile by:

• Reducing image sizes for smaller screens
• Minimizing third-party scripts
• Using adaptive serving to deliver lighter resources to mobile devices
• Implementing AMP (Accelerated Mobile Pages) for content-heavy pages
• Testing on real devices with throttled connections

Step 4: Security & HTTPS

HTTPS is a confirmed ranking signal and essential for user trust. All modern websites should use HTTPS exclusively.

SSL/TLS Certificate Validation

Verify your SSL certificate:

• Certificate is valid and not expired
• Certificate covers all subdomains you use (or use a wildcard certificate)
• Certificate is from a trusted authority
• No mixed content warnings (HTTP resources on HTTPS pages)
• HSTS (HTTP Strict Transport Security) is enabled

Use SSL Labs' SSL Server Test to get a comprehensive security grade for your certificate configuration.

HTTPS Migration Checklist

If you're migrating from HTTP to HTTPS, follow these steps to avoid ranking drops:

1. Install SSL certificate and test HTTPS version works correctly
2. Update all internal links to use HTTPS
3. Implement 301 redirects from HTTP to HTTPS versions
4. Update canonical tags to point to HTTPS URLs
5. Update XML sitemaps with HTTPS URLs
6. Update Google Search Console and Analytics properties
7. Update social media profiles and external links where possible
8. Monitor Search Console for crawl errors after migration

Security Headers

Implement security headers to protect against common vulnerabilities:

• Content-Security-Policy: Prevents XSS attacks
• X-Frame-Options: Prevents clickjacking
• X-Content-Type-Options: Prevents MIME sniffing
• Referrer-Policy: Controls referrer information
• Permissions-Policy: Controls browser features

Step 5: Structured Data & Schema

Structured data helps search engines understand your content and can unlock rich results in search listings, dramatically improving click-through rates.

Schema Markup Implementation

Priority schema types to implement:

• Organization: Company information, logo, social profiles
• Article: Blog posts and news content
• Product: E-commerce items with pricing and availability
• Review: Customer reviews and ratings
• FAQ: Frequently asked questions
• HowTo: Step-by-step guides
• LocalBusiness: Physical location information
• BreadcrumbList: Site navigation hierarchy

Use JSON-LD format (Google's recommended approach) rather than microdata or RDFa. JSON-LD is easier to implement and maintain since it's separate from your HTML markup.

Structured Data Validation

Test your structured data using:

• Google's Rich Results Test for specific rich result eligibility
• Schema.org Validator for general schema validation
• Google Search Console's Rich Results report for site-wide monitoring

Common structured data errors:

• Missing required properties (e.g., image for Article schema)
• Invalid date formats
• Mismatched content between schema and visible page content
• Multiple conflicting schema types on the same page
• Schema markup for content not visible to users

Our Schema Generator helps you create valid JSON-LD markup for common content types without coding.

Rich Results Opportunities

Identify which rich results your content qualifies for and implement appropriate schema:

• Recipe cards: Cooking time, ingredients, ratings
• Event listings: Date, location, ticket information
• Job postings: Salary, location, requirements
• Video results: Thumbnail, duration, upload date
• FAQ accordions: Expandable Q&A in search results
• Product snippets: Price, availability, reviews

Rich results can increase click-through rates by 20-40% compared to standard blue links, making schema implementation one of the highest-ROI technical SEO tasks.

Step 6: On-Page Technical Elements

These foundational elements appear on every page and directly impact how search engines interpret and rank your content.

Title Tag Optimization

Title tag best practices:

• Keep length between 50-60 characters (approximately 600 pixels)
• Include primary keyword near the beginning
• Make each title unique across your site
• Write for users first, search engines second
• Include brand name (usually at the end)
• Avoid keyword stuffing or excessive punctuation

Check for duplicate, missing, or truncated title tags using Screaming Frog or similar crawling tools.

Meta Description Optimization

While not a direct ranking factor, meta descriptions significantly impact click-through rates from search results.

Meta description guidelines:

• Keep length between 150-160 characters
• Include primary and secondary keywords naturally
• Write compelling copy that encourages clicks
• Make each description unique
• Include a call-to-action when appropriate

Header Tag Structure

Proper header hierarchy (H1, H2, H3, etc.) helps search engines understand content structure and importance.

Header tag checklist:

• One H1 per page containing the primary keyword
• Logical hierarchy (don't skip from H2 to H4)
• H2s for main sections, H3s for subsections
• Headers accurately describe the content that follows
• Include relevant keywords naturally in headers

Canonical Tags

Canonical tags tell search engines which version of a page is the "master" when duplicate or similar content exists.

Canonical tag audit:

• Every page should have a self-referencing canonical tag
• Canonical URLs should be absolute, not relative
• Canonical should point to the HTTPS version
• Avoid canonical chains (A→B→C)
• Don't canonicalize to pages that return 404 or 301
• Ensure paginated pages don't all canonicalize to page 1

URL Structure

Clean, descriptive URLs improve both user experience and search engine understanding.

URL best practices:

• Use hyphens to separate words, not underscores
• Keep URLs short and descriptive
• Include target keywords when natural
• Use lowercase letters only
• Avoid unnecessary parameters and session IDs
• Maintain consistent structure across the site
• Remove stop words (a, the, and, etc.) when they don't add value

Step 7: Internal & External Links

Link structure affects how authority flows through your site and how easily search engines can discover your content.

Internal Linking Audit

Internal linking best practices:

• Ensure every page is reachable within 3 clicks from the homepage
• Use descriptive anchor text that includes relevant keywords
• Link to important pages from multiple locations
• Avoid excessive links on a single page (keep under 100-150)
• Fix broken internal links immediately
• Remove or update links to redirected pages
• Use breadcrumb navigation for hierarchical sites

Create a strategic internal linking plan that funnels authority to your most important pages. High-authority pages (like your homepage) should link to key landing pages you want to rank.

Broken Link Detection

Broken links waste crawl budget and create poor user experience. Regularly scan for:

• 404 errors (page not found)
• 500 errors (server errors)
• Redirect chains (A→B→C→D)
• Redirect loops (A→B→A)
• Links to external sites that no longer exist

Use our Broken Link Checker to automatically scan your site and identify all broken links with suggested fixes.

External Link Quality

While you can't control who links to you, you can control who you link to. Outbound links to low-quality or spammy sites can negatively impact your rankings.

External link checklist:

• Link only to authoritative, relevant sources
• Use rel="nofollow" for paid links or user-generated content
• Use rel="sponsored" for affiliate links
• Use rel="ugc" for user-generated content links
• Regularly audit external links for broken or compromised sites
• Open external links in new tabs (target="_blank") with rel="noopener"

Orphan Pages

Orphan pages have no internal links pointing to them, making them difficult for search engines to discover and crawl.

To find orphan pages:

1. Compare your XML sitemap URLs to pages found during a site crawl
2. Check Google Analytics for pages receiving traffic but no internal links
3. Review Search Console for indexed pages not in your sitemap

Either add internal links to orphan pages or remove them from your sitemap if they're not important.

Step 8: International SEO

If your site targets multiple countries or languages, proper international SEO implementation is critical for ranking in the right markets.

Hreflang Implementation

Hreflang tags tell search engines which language and regional version of a page to show users based on their location and language preferences.

Hreflang best practices:

• Use ISO 639-1 language codes (en, es, fr, etc.)
• Include country codes when targeting specific regions (en-us, en-gb, es-mx)
• Implement bidirectional hreflang (if A links to B, B must link to A)
• Include self-referencing hreflang tag
• Add x-default for fallback version
• Ensure hreflang URLs return 200 status codes

Example hreflang implementation:

<link rel="alternate" hreflang="en" href="https://example.com/page" />
<link rel="alternate" hreflang="es" href="https://example.com/es/page" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/page" />
<link rel="alternate" hreflang="x-default" href="https://example.com/page" />

International Site Structure

Choose the right URL structure for your international content:

• ccTLDs: example.co.uk, example.de (strongest geo-targeting signal, but expensive and complex)
• Subdirectories: example.com/uk/, example.com/de/ (easiest to manage, consolidates domain authority)
• Subdomains: uk.example.com, de.example.com (treated as separate sites by Google)
• Parameters: example.com?country=uk (not recommended, difficult for users and search engines)

Most sites should use subdirectories unless they have specific technical or business reasons for other approaches.

Geographic Targeting

Set geographic targeting in Google Search Console for:

• Country-specific subdirectories
• Subdomains targeting specific countries
• Generic TLDs (.com, .org) targeting specific regions

Don't set geographic targeting for ccTLDs (they're automatically associated with their country) or for sites targeting multiple countries.

Content Localization

True localization goes beyond translation:

• Adapt content for cultural relevance and local preferences
• Use local currency, date formats, and measurement units
• Translate meta tags, alt text, and structured data
• Consider local search behavior and keyword variations
• Host content on local servers or use CDN for faster delivery
• Build local backlinks and citations

Step 9: Advanced Technical Checks

These advanced checks are particularly important for larger sites or those with complex technical requirements.

Log File Analysis

Server logs reveal exactly how search engines interact with your site, providing insights you can't get from other tools.

What to analyze in log files:

• Crawl frequency and patterns
• Pages Googlebot can't access
• Server errors and response codes
• Crawl budget waste on low-value pages
• Bot traffic vs. human traffic