Technical SEO Audit: The 80-Point Checklist Used by Top Agencies

Most websites are unknowingly bleeding rankings from dozens of technical issues that never surface in regular content audits. A missing canonical tag here, a crawl trap there, a render-blocking resource that slows your LCP by 800 milliseconds — individually they seem minor, but collectively they compound into a ranking penalty that no amount of link building can overcome. Top SEO agencies charge $5,000 to $15,000 for technical audits precisely because the expertise required to catch all 80+ failure points takes years to develop. This guide gives you the complete framework they use — systematically organized, actionable at every step, and calibrated for 2026 Google.

Whether you’re conducting an audit for a new client, troubleshooting a traffic drop, or building a pre-launch checklist for a site migration, this 80-point framework covers every layer: crawlability, indexation, site architecture, Core Web Vitals, structured data, international SEO, mobile optimization, security signals, and more. Work through it section by section and you’ll surface issues that 90% of auditors miss.

How to Use This Checklist

The most effective technical audits follow a layered approach — fix the foundations before optimizing the fine details. A perfectly optimized page means nothing if Googlebot can’t crawl it. A fast page with no canonical tag creates duplicate content problems that dilute its ranking signal. This checklist is organized from foundational (access and crawlability) to advanced (structured data and international SEO), so you can work through it in priority order.

For each section, recommended tools are noted. At minimum you’ll need: Screaming Frog (or Sitebulb), Google Search Console, PageSpeed Insights / Lighthouse, and a structured data testing tool. For comprehensive audits, add Ahrefs or Semrush for backlink and keyword data, and Chrome DevTools for hands-on rendering diagnosis.

Section 1: Crawl Accessibility (Points 1–12)

Before Google can rank your content, it must be able to access it. Crawl accessibility failures are the most severe type of technical issue because they prevent all downstream optimization from having any effect.

Robots.txt

• 1. Robots.txt exists and is accessible — Verify at yourdomain.com/robots.txt. A missing or 404 robots.txt can cause unpredictable crawl behavior.
• 2. Robots.txt is not blocking critical resources — Check that CSS, JavaScript, and important page templates aren’t disallowed. Blocking rendering resources is a common site migration error.
• 3. No accidental Disallow: / in production — This has happened to major sites after staging environment configs were pushed to production. Verify explicitly.
• 4. Sitemap is referenced in robots.txt — Adds a crawl hint even when Google already knows your sitemap URL.

XML Sitemaps

• 5. XML sitemap exists and is submitted in GSC — Check Google Search Console → Sitemaps. Note discovered vs indexed URL counts.
• 6. Sitemap contains only indexable URLs — Non-canonical, noindex, or redirected URLs in sitemaps waste crawl budget and send contradictory signals.
• 7. Sitemap is updated automatically — Verify your CMS or sitemap plugin updates the sitemap when new content is published. Stale sitemaps slow discovery of new pages.
• 8. No 404 or redirect URLs in sitemap — Run Screaming Frog’s sitemap crawler to identify broken sitemap entries.

Crawl Budget

• 9. No crawl traps — Infinite parameter combinations (filters, sort options, pagination), session IDs in URLs, or calendar-generated URLs create infinite crawl loops. Use Google’s URL Parameters tool in GSC and check for parameter-based faceted navigation.
• 10. Faceted navigation is handled correctly — Use noindex on filter/sort pages that don’t merit ranking, or use canonical tags pointing to the base category page.
• 11. Crawl depth is within 3 clicks for important pages — Pages buried 5+ clicks from the homepage rarely get crawled efficiently. Check with Screaming Frog’s crawl depth report.
• 12. Server response is fast (<200ms TTFB) — Slow server response reduces effective crawl budget. Check TTFB in Google Search Console → Core Web Vitals and independently via WebPageTest.

Section 2: Indexation Control (Points 13–22)

Crawlable doesn’t mean indexed. Indexation control ensures that what should rank is indexed and what shouldn’t rank is excluded — a distinction that has major implications for domain authority and ranking efficiency.

• 13. Noindex tags are intentional and correct — Audit all meta name="robots" content="noindex" tags. Tag managers and plugins frequently add these accidentally.
• 14. X-Robots-Tag header noindex checked on key templates — Server-level noindex directives can override meta tags. Check via cURL: curl -I https://yourdomain.com/page/ and look for X-Robots-Tag in headers.
• 15. Canonical tags are implemented on all indexable pages — Every indexable page should have a self-referencing canonical. Missing canonicals on paginated content, filtered pages, or tag archives create duplicate content issues.
• 16. Canonical tags point to the correct URL version — Verify HTTP vs HTTPS, www vs non-www, trailing slash vs no trailing slash consistency. Canonical to the wrong variant dilutes ranking signals.
• 17. Paginated content canonicals are correct — Don’t canonical page 2+ to page 1. Each paginated page should self-canonical, or use rel="next/prev" if you need to signal a series (Google still uses these as hints).
• 18. Thin content pages are managed — Tag pages, author archives with <3 posts, and thin category pages should either be consolidated, enriched, or noindexed.
• 19. Duplicate content is resolved — Run a content duplication audit using Siteliner or Screaming Frog’s duplicate content report. Internal duplication dilutes PageRank concentration.
• 20. URL parameters are handled in GSC — Configure Google Search Console’s URL Parameters tool to tell Googlebot which parameters change page content vs only change page presentation.
• 21. Hreflang URLs are indexed in their target markets — If using hreflang, verify that alternate language/region versions are actually indexed. Pointing hreflang to noindexed pages breaks international SEO.
• 22. Index coverage in GSC is reviewed monthly — Review GSC’s Coverage report regularly. “Crawled — currently not indexed” and “Discovered — currently not indexed” statuses signal quality or crawl budget issues.

Section 3: URL Structure and Redirects (Points 23–32)

URL structure affects both crawl efficiency and user experience. Redirect chains and loops are among the most common technical SEO issues that persist unnoticed for years, steadily bleeding PageRank.

• 23. URL structure is logical and flat — Avoid deeply nested URL structures like /category/subcategory/sub-subcategory/post/. Flatter is better for crawl efficiency and anchor text clarity.
• 24. URLs use hyphens, not underscores — Google treats hyphens as word separators; underscores are treated as word joiners. /seo-tips/ ranks better for “seo tips” than /seo_tips/.
• 25. No redirect chains longer than 1 hop — Each additional redirect hop loses ~15% of PageRank. Crawl your site with Screaming Frog → follow redirects → look for chains of 2+.
• 26. No redirect loops — URL A → URL B → URL A creates an infinite loop that Googlebot abandons. Screaming Frog flags these in the Response Codes report.
• 27. HTTP to HTTPS redirect is 301 — Verify all HTTP URLs 301 redirect to HTTPS. Don’t use 302 (temporary) for permanent HTTP→HTTPS migrations.
• 28. www and non-www canonicalized to one version — Only one variant should serve content; the other should 301 redirect. Configure your preferred domain in GSC.
• 29. Trailing slash consistency is enforced — Pick a pattern (trailing slash or no trailing slash) and enforce it with 301 redirects. Inconsistency creates duplicate content.
• 30. Old URLs from site migrations are properly redirected — Use Google Search Console’s URL Inspection tool to verify historical URLs return 301 to the correct destination. Lost redirects from past migrations silently kill rankings.
• 31. No soft 404s — Pages that return 200 status but display “no results” or “page not found” content mislead Googlebot. Check GSC Coverage for “Soft 404” errors.
• 32. 404 pages return a proper 404 status code — Custom 404 pages must return HTTP 404, not 200 (which creates a “soft 404”). Verify with cURL on a non-existent URL.

Section 4: Site Architecture and Internal Linking (Points 33–42)

Internal linking is PageRank distribution in action. Every internal link you add or remove redistributes ranking authority across your site. A well-architected site maximizes PageRank flow to its most important pages.

• 33. Hub pages exist for primary keyword clusters — Pillar pages or category landing pages should aggregate and link to all related content within a topic cluster. This signals topical authority to Google.
• 34. Every page receives at least one internal link — Orphan pages (pages with no internal links pointing to them) receive no PageRank and are rarely crawled. Run Screaming Frog’s “Orphan Pages” report using your sitemap as input.
• 35. Navigation links use keyword-rich anchor text — Navigation and sidebar links pass anchor text signals. “Learn More” passes no keyword signal; “Technical SEO Services” does.
• 36. High-priority pages have the most internal links — Map internal link counts against your priority page list. If a service page has 2 internal links and a blog post from 2019 has 47, you have a PageRank distribution problem.
• 37. No excessive internal links on a single page — Google’s John Mueller has confirmed excessive links on a page dilute individual link value. Pages with 200+ links pass very little per-link equity.
• 38. Breadcrumbs are implemented and linked correctly — Breadcrumbs improve crawl paths, add internal links to parent pages, and enhance SERP appearance when combined with breadcrumb schema.
• 39. Related post / recommended article modules are functional — These are high-value internal linking opportunities if they point to topically relevant content rather than just “most popular” or “most recent”.
• 40. Pagination is crawlable and not blocked — Paginated content (blog pages, product category pages) should be crawlable. Blocking page 2+ prevents discovery of content only linked from those pages.
• 41. No JavaScript-only internal links — Links rendered only via JavaScript may not be followed by Googlebot. Critical navigation and internal links should be in the HTML source, not injected by JavaScript.
• 42. Site search results pages are noindexed — Internal search result pages are duplicate content that wastes crawl budget. Noindex or block via robots.txt.

Section 5: Core Web Vitals (Points 43–54)

Core Web Vitals became a confirmed Google ranking factor in 2021 and continue to carry significant weight in 2026. The thresholds haven’t changed — LCP under 2.5s, INP under 200ms, CLS under 0.1 — but Google’s measurement is increasingly sophisticated, and competition in most niches has improved baseline scores considerably.

Largest Contentful Paint (LCP)

• 43. LCP element identified and optimized — Use Chrome DevTools → Performance tab to identify the LCP element. It’s typically a hero image or large text block.
• 44. LCP image has fetchpriority="high" — For above-the-fold images that are your LCP element, add fetchpriority="high" to the img tag to prioritize loading.
• 45. LCP image is not lazy-loaded — Never apply loading="lazy" to your LCP image. Lazy loading delays it intentionally, which directly increases LCP time.
• 46. Images are in WebP or AVIF format — Modern image formats reduce file size by 30-50% vs JPEG with equivalent quality, dramatically improving LCP for image-heavy pages.
• 47. Images have explicit width/height attributes — Prevents layout shifts as images load, which also helps CLS scores.

Interaction to Next Paint (INP)

• 48. Long Tasks (>50ms) are identified and resolved — Use Chrome DevTools Performance tab to find Long Tasks that block the main thread and degrade interaction responsiveness.
• 49. Third-party scripts are loaded asynchronously — Analytics, chat widgets, A/B testing tools, and ad scripts frequently block main thread. Load them with async or defer.
• 50. Render-blocking resources are eliminated — Check Lighthouse for “Eliminate render-blocking resources.” Move non-critical CSS to async loading and defer non-critical JavaScript.

Cumulative Layout Shift (CLS)

• 51. Ads, embeds, and iframes have reserved space — Elements that load after the page renders without reserved space cause layout shifts. Pre-define dimensions for ad slots, video embeds, and social media widgets.
• 52. Web fonts don’t cause FOUT/FOIT — Flash of Unstyled Text or Invisible Text causes layout shifts. Use font-display: optional or font-display: swap with preloaded fonts.
• 53. Dynamic content injected above the fold is controlled — Banners, cookie notices, or chat widgets that appear above the fold after load push content down and create CLS. Size them correctly and use fixed positioning where possible.
• 54. CWV scores are monitored in GSC field data — Lab data (Lighthouse) is indicative. Field data (CrUX data in GSC) is what Google uses for ranking. Track both but prioritize fixing field data issues.

Section 6: Mobile Optimization (Points 55–62)

Google switched to mobile-first indexing fully in 2023. Your mobile site is your site in Google’s eyes — desktop performance is secondary.

• 55. Responsive design is implemented — Verify with Google’s Mobile-Friendly Test. The site should serve the same HTML to all devices with CSS adapting the layout.
• 56. Content parity between mobile and desktop — In mobile-first indexing, content hidden on mobile (in collapsed tabs, accordions, or display:none elements) may receive less weight. Ensure primary content is accessible on mobile.
• 57. Touch targets are adequately sized — Buttons and links should be at least 48px × 48px with sufficient spacing. Small touch targets increase bounce rate on mobile.
• 58. Viewport meta tag is correct — Must include <meta name="viewport" content="width=device-width, initial-scale=1">. Missing or incorrect viewport tags break mobile rendering.
• 59. Font sizes are readable on mobile (≥16px body text) — Text smaller than 16px triggers “text too small to read” warnings and degrades mobile UX signals.
• 60. No horizontal scrolling on mobile — Content wider than the viewport forces horizontal scroll, which Google’s mobile usability report flags as a critical issue.
• 61. Intrusive interstitials are avoided — Full-screen popups, app download banners, and interstitials that block the main content on mobile are subject to Google’s intrusive interstitial penalty.
• 62. Mobile performance is tested on real devices — Emulation in Chrome DevTools is useful but doesn’t replicate real-device performance on a 4G connection. Use Google’s PageSpeed Insights for field data and test on actual mobile hardware monthly.

Section 7: Structured Data (Points 63–70)

Structured data doesn’t directly boost rankings, but it enables rich results that dramatically increase click-through rates — and higher CTR correlates with improved ranking over time. It also feeds AI Overviews and featured snippets.

• 63. Article schema on all blog posts — Article schema signals content type, publication date, author, and organization. It’s a prerequisite for Google News and Top Stories eligibility.
• 64. FAQPage schema on pages with Q&A sections — FAQPage schema enables FAQ rich results that expand your SERP footprint. In 2026, it also feeds AI Overviews directly.
• 65. BreadcrumbList schema is implemented — Breadcrumb rich results show site structure in SERPs and improve CTR by showing users where the page sits in your taxonomy.
• 66. Organization schema on homepage — Establishes your brand entity with Google. Include logo, sameAs links to your social profiles, contact info, and founding details.
• 67. LocalBusiness schema for local businesses — Essential for any business serving a geographic area. Enables map pack consideration and localizes search results.
• 68. Product schema on e-commerce product pages — Enables price, availability, and review rich results in product SERPs. Missing product schema is a major missed opportunity for e-commerce sites.
• 69. Schema is validated with Google’s Rich Results Test — Validate schema implementation at search.google.com/test/rich-results. Fix any errors before assuming schema is active.
• 70. No schema violations (review gating, fake reviews) — Google’s structured data policies prohibit using Review schema for internal reviews or using schema to game ratings. Violations can trigger manual actions.

Section 8: Security, HTTPS, and Technical Signals (Points 71–80)

Security signals and technical hygiene affect both rankings and user trust. Google has used HTTPS as a ranking signal since 2014, and security issues can trigger manual actions that override all other SEO work.

• 71. HTTPS is fully implemented with valid SSL certificate — Use SSL Labs (ssllabs.com/ssltest) for a comprehensive SSL check. An A or A+ rating is expected for competitive niches.
• 72. No mixed content errors — HTTPS pages loading HTTP resources trigger browser security warnings. Check Chrome DevTools → Console for mixed content errors and fix all HTTP resource references.
• 73. HTTP Strict Transport Security (HSTS) header is set — HSTS forces all connections to use HTTPS, preventing SSL stripping attacks. Set with max-age=31536000; includeSubDomains.
• 74. No malware, spam links, or security compromise — Check Google Search Console → Security Issues. A hacked site can result in manual action or de-indexing overnight.
• 75. Server response codes are correct — Run a full site crawl and check that all intended pages return 200, redirects return 301/302 correctly, and no pages are accidentally returning wrong status codes.
• 76. Page speed scores are above 50 on mobile in Lighthouse — Below 50 indicates severe performance issues. While the absolute score isn’t a direct ranking factor, the underlying metrics (LCP, INP, CLS) are.
• 77. No spammy external links from the site — Outbound links to low-quality or penalized sites can drag down your own trustworthiness. Audit outbound links annually and use rel=”nofollow” or rel=”sponsored” where appropriate.
• 78. Hreflang is correctly implemented for international sites — Hreflang errors are among the most common international SEO mistakes. Each page must reference all language/region variants, including itself. Use hreflang testing tools to validate the complete set.
• 79. Log file analysis performed — Server log files show exactly which pages Googlebot is crawling, how often, and with what response codes. This is more accurate than GSC data and reveals crawl budget waste that other tools miss.
• 80. GSC manual actions checked and clear — Check Google Search Console → Manual Actions every month. Manual penalties can suppress rankings entirely and require a reconsideration request to resolve.

Prioritizing Your Audit Findings

Not all findings are equal. Use this prioritization matrix to sequence your fixes:

Critical (fix within 48 hours): Any crawl blocking issue, accidental noindex on important pages, active security issues, manual actions, redirect loops, and canonical pointing to wrong URL.

High (fix within 2 weeks): Core Web Vitals failures in field data, missing sitemaps, significant redirect chains, orphaned high-priority pages, missing structured data on commercial pages.

Medium (fix within a month): Internal linking improvements, schema enhancements, image optimization, mobile UX refinements, canonicalization cleanup on low-priority pages.

Low (next development sprint): HSTS headers, log file setup, minor CLS improvements, breadcrumb schema, and above-threshold CWV optimization (going from “good” to “better”).

Tools Reference

Here’s the complete toolstack for running this 80-point audit:

• Screaming Frog SEO Spider — Crawl, redirects, canonical tags, internal links, hreflang, response codes
• Google Search Console — Coverage, Core Web Vitals field data, manual actions, crawl stats, sitemaps, security issues
• PageSpeed Insights / Lighthouse — Core Web Vitals lab data, performance recommendations
• Google Rich Results Test — Structured data validation
• Chrome DevTools — JavaScript rendering, network requests, performance timeline, mixed content
• Ahrefs / Semrush — Backlink profile, site audit, redirect checker, orphan pages
• SSL Labs — HTTPS/SSL certificate quality assessment
• Siteliner — Internal duplicate content detection
• WebPageTest — Detailed performance waterfall analysis with real browser testing

Frequently Asked Questions

Conclusion

Technical SEO is the foundation every other SEO investment depends on. A site with excellent content, strong backlinks, and a poor technical foundation will consistently underperform against technically clean competitors. This 80-point checklist gives you the systematic framework that top agencies use — not as a billable-hour exercise, but as a genuine diagnostic that surfaces the issues suppressing your rankings.

Work through each section methodically. Prioritize fixes using the critical/high/medium/low framework. Document every issue you find with screenshots and URLs so your development team has actionable tickets, not vague instructions. Verify each fix after implementation. Then set up monitoring to catch regressions before they compound.

Technical SEO isn’t a one-time project — it’s ongoing hygiene. Sites that treat it as such consistently outperform those that audit once and consider it done.