Technical SEO Audit: The Complete 2026 Guide

Crawlability

1. Crawlability & Indexation

If search engines can't access your pages, nothing else matters. This is the first area to audit.

Robots.txt configuration

Check your robots.txt file to ensure it's not accidentally blocking important pages. Common mistakes include blocking CSS/JS files (which prevents rendering), blocking entire directories that contain important content, and using overly broad disallow rules.

In 2026, also verify that you're allowing AI crawlers access. GPTBot, ClaudeBot, and PerplexityBot need explicit permission in many configurations. Blocking them means your content won't appear in AI-generated answers.

XML sitemap

Your XML sitemap should include every page you want indexed and exclude pages you don't (admin pages, filter pages, staging URLs). Check these specifics:

• Sitemap is submitted in Google Search Console
• Sitemap is referenced in robots.txt
• All URLs in the sitemap return 200 status codes
• No URLs in the sitemap have noindex tags
• Sitemap is under the 50,000 URL / 50MB limit
• lastmod dates are accurate (not all the same date)

Use our free XML Sitemap Validator to check for these issues automatically, and our Structured Data Tester to validate your schema markup.

Crawl budget optimization

For large sites (10,000+ pages), crawl budget matters. Google allocates a limited number of pages to crawl per session. Reduce crawl waste by:

• Removing or noindexing thin/duplicate pages (filter combinations, pagination, tag pages with minimal content)
• Fixing redirect chains (each hop wastes crawl resources)
• Ensuring server response times are under 500ms
• Using nofollow on links to login pages, internal search results, and admin areas

Index coverage

In Google Search Console, check the "Pages" report (formerly Index Coverage). Look for:

• Excluded pages: Are important pages being excluded? Common reasons: "Crawled - currently not indexed," "Discovered - currently not indexed," and "Duplicate without user-selected canonical."
• Errors: Server errors (5xx), redirect errors, and blocked by robots.txt
• Noindex mismatch: Pages that should be indexed but have noindex tags

Architecture

2. Site Architecture & URL Structure

How your site is organized affects both user experience and search engine understanding.

URL structure

Good URLs are short, descriptive, and consistent. Audit for these issues:

• URLs contain only lowercase letters, numbers, and hyphens
• No query parameters on indexable pages (use path-based URLs instead)
• No session IDs or tracking parameters in URLs
• Consistent trailing slash usage (pick one pattern and stick with it)
• URL depth is 3 levels or fewer from the homepage (homepage > category > page)

Internal linking

Internal links distribute authority and help search engines discover your pages. Check for:

• Orphan pages: Pages with no internal links pointing to them. These are hard for crawlers to discover.
• Deep pages: Important pages that require 4+ clicks from the homepage. Flatten your structure.
• Broken internal links: Links pointing to 404 pages waste crawl budget and confuse users.
• Anchor text variety: Use descriptive, relevant anchor text for internal links — not "click here" or bare URLs.

Internal linking is one of the highest-ROI SEO activities. For a full walkthrough of hub-and-spoke architecture, anchor text optimization, and link equity distribution, see our internal linking strategy guide.

Navigation and breadcrumbs

Implement breadcrumb navigation with BreadcrumbList schema. Breadcrumbs help search engines understand your site hierarchy and appear as rich results in SERPs.

Duplicate Content

3. Duplicate Content & Canonicalization

Duplicate content confuses search engines about which page to rank. It dilutes your authority across multiple URLs instead of consolidating it on one.

Canonical tags

Every indexable page should have a self-referencing canonical tag. Check these common canonical issues:

• Missing canonical tags on any indexable page
• Canonical pointing to a non-existent or redirected URL
• Canonical pointing to a different page that isn't actually the preferred version
• HTTP canonical on an HTTPS page (or vice versa)
• Canonical conflicting with noindex (pick one — don't noindex a page with a self-canonical)

Common duplication sources

• HTTP vs HTTPS: Ensure all HTTP URLs redirect to HTTPS (301 redirect)
• www vs non-www: Pick one and redirect the other
• Trailing slash inconsistency: /page and /page/ should not both return 200
• Parameter variations: /products?sort=price and /products?sort=name are separate URLs with the same content
• Pagination: Category pages with multiple pages of listings
• Print pages: Printer-friendly versions at separate URLs

Hreflang for international sites

If your site serves multiple languages or regions, implement hreflang tags correctly. Every page should reference all its language/region variants, including itself. Hreflang mistakes are among the most common technical SEO errors on international sites.

Performance

4. Page Speed & Core Web Vitals

Page speed is a confirmed Google ranking factor. Core Web Vitals (LCP, INP, CLS) are the specific metrics Google uses to measure user experience. For a complete list of optimization techniques covering server-side, frontend, and caching strategies, see our site speed optimization guide.

Server response time (TTFB)

Your server should respond in under 500ms. Check with performance testing tools. If TTFB is slow, consider: upgrading hosting, enabling server-side caching, using a CDN, or migrating to a faster framework (SSG/ISR with Next.js, for example).

Largest Contentful Paint (LCP)

Target: under 2.5 seconds. Common fixes: compress and resize images, use WebP/AVIF formats, preload LCP images, inline critical CSS, and eliminate render-blocking JavaScript.

Interaction to Next Paint (INP)

Target: under 200 milliseconds. Reduce JavaScript payload, break long tasks, defer third-party scripts, and minimize DOM size.

Cumulative Layout Shift (CLS)

Target: under 0.1. Set explicit dimensions on images/videos, reserve space for ads and dynamic content, use font-display: swap, and avoid injecting content above the fold after page load.

Resource optimization checklist

• Images compressed and served in modern formats (WebP, AVIF)
• CSS minified and critical CSS inlined
• JavaScript minified, code-split, and deferred where possible
• Fonts preloaded with font-display: swap
• HTTP/2 or HTTP/3 enabled on the server
• Browser caching headers configured (Cache-Control, ETag)
• Gzip or Brotli compression enabled

Mobile

5. Mobile-Friendliness

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

Mobile audit checklist

• Viewport meta tag is set correctly: <meta name="viewport" content="width=device-width, initial-scale=1">
• Text is readable without zooming (16px minimum font size)
• Tap targets (buttons, links) are at least 48x48px with adequate spacing
• No horizontal scrolling required
• Mobile and desktop versions serve the same content (critical for mobile-first indexing)
• Interstitials and pop-ups don't block content on mobile
• Forms are usable on mobile with appropriate input types

Structured Data

6. Structured Data & Schema Markup

Schema markup helps search engines understand your content and enables rich results. It's also increasingly important for AI search visibility.

Essential schema types

• Organization: On your homepage — name, logo, social profiles, contact info
• Article: On blog posts — headline, author, dates, publisher
• FAQPage: On pages with FAQ sections — enables FAQ rich results
• BreadcrumbList: On all pages with breadcrumb navigation
• Product: On product pages — price, availability, reviews
• LocalBusiness: For businesses with physical locations
• HowTo: For step-by-step instructional content

Schema validation

Test your structured data with Google's Rich Results Test and Schema.org validator. Check for: missing required properties, incorrect data types, schema that doesn't match visible page content, and deprecated schema types.

Security

7. Security & HTTPS

Security is both a ranking factor and a trust signal. Google has confirmed that HTTPS is a ranking signal, and security headers contribute to your site's trustworthiness.

Security audit checklist

• HTTPS is enforced (HTTP redirects to HTTPS with 301)
• SSL certificate is valid and not expired — use a free SSL checker to verify
• No mixed content (HTTP resources loaded on HTTPS pages)
• HSTS (Strict-Transport-Security) header is set
• Content-Security-Policy header is configured
• X-Frame-Options or CSP frame-ancestors prevents clickjacking
• X-Content-Type-Options: nosniff is set
• Referrer-Policy is configured
• Permissions-Policy restricts unnecessary browser features
• DNS records are properly configured — use a DNS record checker to verify SPF, DMARC, and CAA records
• Domain registration is current and DNSSEC is enabled — verify with a WHOIS lookup

Rendering

8. JavaScript Rendering & Server-Side Rendering

If your content is rendered by JavaScript, Google has to run that JavaScript to see your content. This introduces delays and potential failure points.

Rendering audit steps

• Compare your page source (View Source) with the rendered DOM (Chrome DevTools). If critical content is missing from the source, it depends on JavaScript.
• Use Google's URL Inspection tool to see how Google renders your pages. Check for missing content, broken layouts, or error messages.
• If using a JavaScript framework (React, Vue, Angular), implement server-side rendering (SSR) or static site generation (SSG) for important pages.
• Test with JavaScript disabled — can search engines still see your main content, navigation, and links?

Server-side rendering is also better for AI crawlers. Most AI bots (GPTBot, ClaudeBot, PerplexityBot) don't execute JavaScript, so client-rendered content is invisible to them.

Redirects & Status Codes

9. HTTP Status Codes & Redirects

Incorrect status codes and redirect problems are common technical SEO issues that often go unnoticed.

Status code audit

• 301 vs 302 redirects: Permanent moves should use 301. Temporary redirects (302) don't pass full link equity.
• Redirect chains: A > B > C > D wastes crawl budget and dilutes authority. Maximum one hop.
• Redirect loops: A > B > A creates an infinite loop. Test all redirects.
• Soft 404s: Pages that return 200 but display "not found" content. Use proper 404 or 410 status codes.
• 4xx errors: Fix or redirect broken pages that receive traffic or have backlinks.
• 5xx errors: Server errors indicate hosting or application issues that need immediate attention.

AI Search

10. AI Search Readiness (GEO Audit)

In 2026, a technical SEO audit is incomplete without checking your site's readiness for AI search engines. Generative Engine Optimization (GEO) is now a critical part of technical SEO.

AI crawler access

• Robots.txt allows GPTBot, ClaudeBot, and PerplexityBot
• Server doesn't block AI crawler user agents
• WAF/CDN rules don't accidentally block AI crawlers

Content structure for AI

• FAQ sections with clear question-and-answer format
• Definitive statements that can be extracted as citations
• Structured data (FAQPage, HowTo, Article schema) is implemented
• Content answers specific questions clearly within the first paragraph
• Author and organization authority signals are present

Citation-friendly formatting

AI engines cite content that is well-structured, factually specific, and easy to attribute. Use clear headings, include data points and statistics, and write in a citation-friendly style. See our guides on getting cited by ChatGPT and Perplexity for more details.

Technical SEO Audit Priority Matrix

Not all issues have equal impact. Here's how to prioritize your fixes:

Fix immediately (critical)

1. Pages blocked from crawling that should be indexed
2. Broken canonical tags pointing to wrong URLs
3. Missing or misconfigured robots.txt
4. HTTPS not enforced or SSL certificate issues
5. 5xx server errors on important pages

Fix this week (high impact)

1. Core Web Vitals failures (LCP, INP, CLS)
2. Missing XML sitemap or sitemap errors
3. Redirect chains longer than one hop
4. Duplicate content without proper canonicalization
5. Mobile usability issues

Fix this month (important)

1. Missing structured data on key page types
2. Security headers not configured
3. Orphan pages with no internal links
4. AI crawler access not configured
5. Image optimization (format, compression, alt text)

Tools for Your Technical SEO Audit

• Foglift.io: Instant website scan covering SEO, performance, security, accessibility, and GEO readiness. Free tier available.
• Google Search Console: Crawl data, index coverage, Core Web Vitals, and manual actions directly from Google.
• Google PageSpeed Insights: Lab and field performance data for individual URLs.
• Screaming Frog: Desktop crawler that audits up to 500 URLs free. Essential for finding broken links, redirect chains, and duplicate content.
• Chrome DevTools: Network tab, Performance tab, Lighthouse, and rendered DOM inspection.
• Rich Results Test: Validates your structured data and shows which rich results your pages are eligible for.

Frequently Asked Questions

Bottom Line

A technical SEO audit is the most impactful thing you can do for your search visibility. Content and links matter, but they're useless if search engines can't crawl, render, and index your pages properly. In 2026, add AI search readiness to your checklist — the sites that are technically sound for both Google and AI answer engines will capture the most traffic.

Start with a free Foglift scan to identify your most critical technical issues, then work through this guide systematically to fix them.