The Technical SEO Audit Checklist That Actually Moves Rankings

Technical SEO audits have a reputation problem. Most produce sprawling reports full of warnings that do not matter — broken hreflang on a page with zero traffic, missing alt text on decorative icons, suboptimal heading hierarchy on the 404 page. The result: hundreds of "issues" and no clarity on what actually needs fixing.

This checklist takes a different approach. Every item is prioritized by its potential impact on crawl efficiency, indexation, and ranking. Fix these in order, and you address the technical issues that actually move organic performance.

Priority 1: Crawlability and Indexation

If Google cannot crawl or index your pages, nothing else matters. These issues have the highest urgency because they directly prevent pages from appearing in search results.

Robots.txt Audit

• Check for accidental blocking. Run site:yourdomain.com and compare indexed pages against your sitemap. Large discrepancies often trace back to robots.txt misconfiguration.
• Verify crawl-delay directives. Overly aggressive crawl-delay settings can throttle Googlebot, especially on large sites. Google does not officially support crawl-delay, but other search engines do — and misconfigurations can signal issues.
• Check for inconsistency across environments. Staging robots.txt ("Disallow: /") accidentally deployed to production is more common than it should be.

XML Sitemap Audit

• Only include indexable, canonical URLs. Sitemaps containing redirected, noindexed, or non-canonical URLs waste crawl budget and send mixed signals.
• Validate sitemap size. Max 50,000 URLs or 50MB per sitemap file. For large sites, use a sitemap index file with logical segmentation (by content type, language, or section).
• Check lastmod accuracy. Google uses lastmod to prioritize crawling. If every URL shows the same lastmod date, or dates are inaccurate, you lose this prioritization signal.
• Submit via Search Console. Verify your sitemap is submitted and check for reported errors (URL not found, URL blocked by robots.txt, etc.).

Indexation Coverage

• Review Search Console's Pages report. Focus on "Not Indexed" categories: "Crawled — currently not indexed" and "Discovered — currently not indexed" pages are your priority.
• Audit noindex tags. Crawl your site and check for unintentional noindex directives in meta tags, HTTP headers, or the X-Robots-Tag.
• Check for orphan pages. Pages not linked from anywhere in your internal linking structure may not get crawled. Cross-reference sitemap URLs with internal link data.

Priority 2: Site Architecture and Internal Linking

Site architecture determines how link equity flows through your site and how efficiently Google can discover and understand your content hierarchy.

Crawl Depth

• Keep critical pages within 3 clicks from the homepage. Pages buried 5+ clicks deep receive less crawl priority and less link equity. Flatten your architecture where possible.
• Audit navigation and breadcrumbs. Every page should be reachable through at least one persistent navigation path. Breadcrumbs provide both user navigation and structured data signals.

Internal Linking

• Link from high-authority pages to priority targets. Your homepage and top-traffic pages pass the most equity. Ensure they link to your highest-value conversion pages.
• Use descriptive anchor text. "Learn more" and "click here" waste link equity. Use anchors that describe the target page content.
• Fix broken internal links. Unlike external broken links (which are a minor issue), broken internal links waste your own crawl budget and link equity.

URL Structure

• Consistent, descriptive paths. /services/technical-seo/ is better than /page?id=47&cat=3. URL structure should mirror your site hierarchy.
• No duplicate URL paths. Trailing slashes, mixed case, www/non-www, HTTP/HTTPS — all should resolve to a single canonical version with proper 301 redirects.
• Parameter handling. If your site generates URL parameters (filters, sorting, session IDs), ensure they are handled via canonical tags or robots.txt, not left to generate thousands of duplicate URLs.

Priority 3: Page Speed and Core Web Vitals

Core Web Vitals are a confirmed ranking signal. Beyond rankings, page speed directly impacts user engagement, conversion rates, and crawl efficiency.

Largest Contentful Paint (LCP)

• Target: under 2.5 seconds. The most common causes of poor LCP: unoptimized hero images, render-blocking CSS/JS, slow server response time (TTFB), and heavy web fonts.
• Preload critical assets. Use <link rel="preload"> for above-the-fold images, critical fonts, and CSS.
• Optimize images. Use WebP/AVIF formats, responsive srcset, and appropriate dimensions. A 4000px hero image on a 1200px container is wasted bandwidth.

Interaction to Next Paint (INP)

• Target: under 200ms. INP replaced FID as the interactivity metric. It measures the worst-case responsiveness across the entire page session, not just the first input.
• Reduce main thread blocking. Large JavaScript bundles, synchronous third-party scripts, and heavy DOM manipulation are the primary causes. Defer non-critical JS and break up long tasks.

Cumulative Layout Shift (CLS)

• Target: under 0.1. Layout shift is caused by images without explicit dimensions, dynamically injected content (ads, banners), and web fonts that trigger reflow.
• Set explicit width/height on all media elements. Use CSS aspect-ratio for responsive containers.
• Reserve space for dynamic content. If you inject ads, notifications, or consent banners, use min-height or skeleton placeholders.

Priority 4: Canonical Tags and Duplicate Content

• Every indexable page needs a self-referencing canonical. This is defensive SEO — it prevents future duplication issues from URL parameters, tracking codes, or syndication.
• Audit canonical chains. Page A canonicalizes to Page B, which canonicalizes to Page C. Google may ignore the signal entirely. Keep canonical references direct.
• Check for conflicting signals. A page with a canonical tag pointing to URL A while the sitemap lists URL B sends contradictory signals. Align all signals (canonical, sitemap, internal links, hreflang) to point to the same URL.

Priority 5: Structured Data

• Validate with Google's Rich Results Test. Schema.org markup is only useful if it is syntactically valid and eligible for rich results.
• Implement schema types relevant to your business. Organization, LocalBusiness, Product, FAQ, HowTo, BreadcrumbList, Article — choose based on your content and rich result eligibility.
• Do not over-mark. Adding schema that does not match visible page content can result in manual actions. Only implement structured data for content that actually appears on the page.

Priority 6: HTTPS and Security

• Full HTTPS migration. No mixed content warnings, no HTTP resources loaded on HTTPS pages. Check images, scripts, fonts, and iframe sources.
• HSTS header. Implement HTTP Strict Transport Security to prevent protocol downgrade attacks and signal security to browsers.
• Security headers. X-Content-Type-Options, X-Frame-Options, Content-Security-Policy, and Referrer-Policy. These do not directly impact SEO rankings but protect site integrity, which indirectly supports trust signals.

Priority 7: International and Multilingual (If Applicable)

• Hreflang implementation. Self-referencing hreflang tags, reciprocal tags between language versions, and an x-default for the fallback. Test with Aleyda Solis's hreflang generator or Merkle's tool.
• Content parity. Each language version should have equivalent (not necessarily identical) content. Thin translation pages or missing pages create crawl and indexation inconsistencies.
• URL structure. Subdirectories (/de/, /fr/) are generally preferred over subdomains for consolidating domain authority. ccTLDs are appropriate when targeting specific countries.

Running the Audit

Do not try to fix everything at once. The most effective approach:

1. Crawl your site with a tool like Screaming Frog, Sitebulb, or Ahrefs Site Audit
2. Cross-reference with Google Search Console data (indexation, CWV, manual actions)
3. Prioritize by impact: crawlability > indexation > architecture > speed > schema
4. Implement fixes in batches and monitor Search Console for indexation and performance changes
5. Re-crawl after each batch to verify fixes and catch regressions

Technical SEO is not a one-time project. Schedule quarterly audits to catch regressions from site updates, CMS changes, plugin updates, and new content that may introduce technical debt.