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

A thorough technical SEO audit is the foundation of any serious search optimization strategy. While content and links get most of the attention, technical issues silently drain visibility for thousands of websites every day — crawl errors, slow load times, duplicate content, and broken indexing pipelines all prevent even great content from ranking. This comprehensive technical SEO audit checklist is the exact framework used at Over The Top SEO when onboarding enterprise clients. It covers 80 points across 8 categories that every professional SEO audit must address.

How to Use This Checklist

Work through each section systematically. Use a spreadsheet to track Pass / Fail / Warning for each item. Prioritize fixes by impact (Critical → High → Medium → Low). A complete audit on a 500-page site typically takes 6–12 hours; enterprise sites with 50,000+ pages may require 40+ hours and dedicated crawling infrastructure.

Category 1: Crawlability (10 Items)

1. Verify robots.txt is accessible and correct

Fetch yourdomain.com/robots.txt and verify it loads, contains no unintentional global Disallow rules, and properly blocks staging, admin, and parameter-driven duplicate pages.

2. Check for crawl budget waste

Use Google Search Console’s Crawl Stats report. If Googlebot is spending significant time on URL parameters, faceted navigation, or low-value pages, add proper canonical tags or robots directives.

3. Validate XML sitemaps

Ensure sitemaps are submitted in Search Console, return HTTP 200, contain only canonical URLs, exclude noindex pages, and are under 50MB / 50,000 URLs per file.

4. Audit internal link structure

Run a full crawl with Screaming Frog or Sitebulb. Identify orphan pages (no internal links pointing to them), pages with excessive crawl depth (more than 3–4 clicks from homepage), and pages with no outbound internal links.

5. Test crawl depth for key pages

Your most important pages should be reachable within 2–3 clicks from the homepage. Any priority page beyond 4 clicks risks being crawled infrequently.

6. Check for crawl traps

Faceted navigation, infinite scroll, calendar archives, and session ID parameters can create infinite URL spaces. Identify and block or canonicalize these.

7. Verify Googlebot user-agent access

Use curl -A "Googlebot" to test critical pages. Some servers block bot user-agents, returning different content or errors to crawlers.

8. Check for nofollow on critical internal links

Audit your internal links for unintentional nofollow attributes. Navigation menus and footer links added by plugins sometimes carry nofollow, limiting PageRank flow.

9. Review hreflang implementation for multilingual sites

Each hreflang tag must include a self-referencing tag, have reciprocal tags on all referenced pages, and use valid ISO 639-1 language codes with optional ISO 3166-1 region codes.

10. Confirm disavow file is current

If you have a disavow file, review it annually. Remove domains you’ve had manual removal success with; ensure no legitimate links are being disavowed.

Category 2: Indexability (10 Items)

11. Audit noindex tags

Export all noindex pages from a crawl. Verify each is intentionally excluded. Common mistakes: noindex left on after site migration, staging content accidentally made live with noindex, or CMS plugins adding noindex to important categories.

12. Check canonical tag implementation

Every page should have a self-referencing canonical tag. Paginated pages should canonicalize to themselves (not to page 1). Parameter variations should canonicalize to the clean URL.

13. Verify no canonical conflicts with noindex

A page that has a canonical pointing to Page A but noindex on itself sends contradictory signals. Resolve all canonical-noindex conflicts.

14. Check Google’s index coverage

In Search Console, review the Indexing report. Investigate any URLs in “Discovered but not indexed” or “Crawled but not indexed” — these signal quality or authority issues at the page level.

15. Identify thin content pages

Pages with fewer than 300 words of meaningful content (excluding navigation, footers, boilerplate) are candidates for consolidation, noindex, or expansion. Use Screaming Frog’s word count filter.

16. Check for duplicate content

Use Copyscape, Siteliner, or Screaming Frog’s duplicate content reports. Internal duplicates (from parameter URLs, trailing slashes, www vs non-www) are fixable with canonicals. External duplicates require investigation.

17. Verify www/non-www redirect

Only one version of your domain should be accessible. The other should 301-redirect permanently. Test both http://www., https://www., http://, and https:// versions.

18. Check for soft 404 errors

Pages that return HTTP 200 but display “no results” or “page not found” content confuse crawlers. Search Console’s Indexing report flags many of these; also check programmatically.

19. Validate structured data indexability

If you use JavaScript to inject structured data, verify it’s present in the rendered DOM before indexing. Use Google’s URL Inspection tool to check the rendered HTML.

20. Check for accidental noindex in HTTP headers

Some servers or CDNs add X-Robots-Tag: noindex headers. Fetch your pages with curl and inspect response headers, not just meta tags.

Category 3: Site Speed & Core Web Vitals (10 Items)

21. Measure Largest Contentful Paint (LCP)

Target: under 2.5 seconds. Common causes of slow LCP: unoptimized hero images, render-blocking resources, slow server response times, and client-side rendering delays.

22. Measure Interaction to Next Paint (INP)

Target: under 200ms. INP replaced FID in March 2024. Test with Chrome DevTools Performance panel and real user data from CrUX.

23. Measure Cumulative Layout Shift (CLS)

Target: under 0.1. Common causes: images without explicit dimensions, ads loading dynamically, web fonts swapping, and embeds without reserved space.

24. Audit Time to First Byte (TTFB)

TTFB above 800ms indicates server-side issues. Check hosting infrastructure, database query times, caching implementation, and CDN configuration.

25. Verify image optimization

All images should be served in WebP or AVIF format, compressed without visible quality loss, sized to display dimensions (not oversized), and lazy-loaded below the fold.

26. Check render-blocking resources

Identify CSS and JavaScript files blocking initial render. Move critical CSS inline; defer or async non-critical JS; preload critical fonts and hero images.

27. Audit JavaScript bundle sizes

Use Chrome’s Coverage tab to identify unused JavaScript. Total page JavaScript should ideally be under 300KB parsed; any single bundle over 100KB warrants review.

28. Test mobile speed separately

Google indexes mobile-first. Run all speed tests on mobile emulation. Mobile performance often differs dramatically from desktop due to CPU throttling and connection simulation.

29. Verify CDN implementation

Static assets (images, CSS, JS) should be served from a CDN with cache headers. Verify CDN cache hit rates in your CDN dashboard — anything below 80% suggests cache configuration issues.

30. Test server response under load

Use tools like k6 or Apache Bench to simulate concurrent traffic. Pages that perform well under normal conditions may degrade during traffic spikes — a common cause of crawl issues.

Category 4: On-Page Technical Signals (10 Items)

31. Audit title tags

Every page needs a unique, descriptive title tag between 50–60 characters. Check for duplicates, missing tags, empty tags, and titles that are too long or too short.

32. Audit meta descriptions

While not a direct ranking factor, meta descriptions affect click-through rates. Target 150–160 characters. Check for duplicates and missing descriptions on key pages.

33. Check H1 tag usage

One H1 per page, matching or closely related to the title tag. Check for pages with no H1, multiple H1s, or H1s that don’t reflect the page’s primary topic.

34. Review heading hierarchy

H2s should be direct subtopics; H3s should be sub-subtopics. Skipping heading levels (H1 → H4) is both an accessibility and a semantic clarity issue.

35. Verify image alt text

All meaningful images need descriptive alt text. Decorative images should have empty alt attributes. Check for stuffed, missing, or filename-as-alt text implementations.

36. Check internal link anchor text diversity

Over-optimized internal anchor text (repeating exact-match keywords on every link) can trigger spam signals. Use natural, descriptive anchor text that varies naturally.

37. Audit URL structure

URLs should be short, descriptive, lowercase, use hyphens (not underscores), and not contain unnecessary parameters or session IDs.

38. Check for open graph and Twitter card tags

Every page shared on social should have og:title, og:description, og:image, and twitter:card tags. Missing or broken social metadata hurts referral traffic from social shares.

39. Verify pagination implementation

Paginated content should not use rel=prev/next (Google discontinued this), should use self-referencing canonicals on each page, and ideally implement a “load more” or single-page approach where feasible.

40. Check for keyword cannibalization

Multiple pages targeting the same keyword compete against each other. Use Search Console performance data to identify queries where multiple URLs rank and consolidate or differentiate them.

Category 5: Structured Data (10 Items)

41. Implement Article or BlogPosting schema

All editorial content should have Article schema including datePublished, dateModified, author, and publisher fields.

42. Implement Organization schema on homepage

Include legal name, URL, logo, sameAs (social profiles), contactPoint, and address fields.

43. Implement BreadcrumbList schema

Breadcrumb structured data helps AI and search engines understand site hierarchy and improves SERP display.

44. Add FAQ schema to Q&A content

FAQ schema can trigger rich results and is increasingly used by AI systems for citation extraction.

45. Implement Product schema for e-commerce pages

Include price, availability, review, and sku fields. Missing price or availability fields disqualify pages from Shopping rich results.

46. Add LocalBusiness schema for location pages

Include name, address, phone, hours, geo coordinates, and sameAs fields for each location.

47. Validate all schema with Google’s Rich Results Test

Check every schema type for errors and warnings. Even technically valid schema can fail rich results eligibility for policy violations.

48. Check for schema implementation consistency

Schema should be implemented server-side or visible in rendered HTML. JSON-LD in the page head is preferred over Microdata.

49. Monitor rich results performance

Use Search Console’s Search Appearance filters to track impressions and clicks from FAQ, HowTo, Review, and other rich result types. Drops signal implementation changes or policy issues.

50. Avoid schema spam or manipulation

Don’t add schema for content not visible on the page. Don’t use Review schema with only five-star ratings. Google actively penalizes manipulative schema use.

Category 6: Security & Technical Fundamentals (10 Items)

51. Verify HTTPS implementation

All pages should serve over HTTPS with a valid SSL certificate. Check for mixed content warnings (HTTP resources on HTTPS pages) using browser dev tools or a crawl tool.

52. Verify 301 redirects for moved content

All significant page moves should have permanent 301 redirects. Avoid redirect chains longer than 2 hops. Check for redirect loops.

53. Audit 404 errors

Export 404 pages from Search Console. Prioritize fixing or redirecting 404s that had significant traffic or backlinks. Leave true 404s (pages that never existed) alone.

54. Check for www/HTTPS redirect chains

The ideal redirect path is: http://www. → https://www. in a single hop. Chains (http → https → www → canonical) waste crawl budget and dilute link equity.

55. Verify canonical domain consistency

Ensure internal links, sitemaps, and canonical tags all reference the same canonical domain version consistently.

56. Check for Google Search Console manual actions

Log into Search Console and review the Manual Actions report. Any active manual action requires immediate attention and a reconsideration request after remediation.

57. Review security headers

Check for Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options headers. These don’t directly affect SEO rankings but signal trustworthiness and affect browser behavior.

58. Test site on mobile devices

Use Google’s Mobile-Friendly Test and real device testing. Check for tap targets too close together, text too small to read, and horizontal scrolling.

59. Verify AMP implementation (if applicable)

If using AMP, validate pages with the AMP Validator. Ensure canonical pages are properly linked to AMP versions and vice versa.

60. Check for third-party scripts impacting performance

Chat widgets, analytics tags, advertising scripts, and social embeds all add load time. Audit all third-party scripts and defer or remove unnecessary ones.

Category 7: International SEO (5 Items)

61. Verify hreflang tag correctness

Every language version must link to every other. Use an hreflang validator tool to check for missing reciprocals and invalid language codes.

62. Check for geo-targeting in Search Console

If using a ccTLD (.co.uk, .de), geo-targeting is automatic. For subfolders (/en/, /de/), verify geo-targeting is set correctly in Search Console’s International Targeting report.

63. Audit content localization vs. translation

Machine-translated content without localization often underperforms. Check key international pages for cultural relevance, local search intent alignment, and idiomatic language use.

64. Check local keyword targeting for each market

Search behavior differs by market. “SEO” searches in the UK, Australia, and Canada have different modifier patterns than US searches. Use local keyword research for each market.

65. Verify CDN delivers localized content correctly

Some CDN configurations serve cached English content to international users. Test pages in VPN-simulated international locations to verify correct language serving.

Category 8: Monitoring & Maintenance (15 Items)

66. Set up Google Search Console for all properties

Verify all domain variations (www, non-www) and protocol variations (HTTP, HTTPS) in Search Console. Use the domain property for unified reporting.

67. Set up Bing Webmaster Tools

Bing powers significant search volume and is increasingly used to train AI models. Submit sitemaps and monitor for Bing-specific crawl issues.

68. Configure uptime monitoring

Use tools like UptimeRobot or Pingdom. Set alert thresholds at 99.5% uptime. Downtime during a Googlebot crawl causes coverage drops that can take weeks to recover.

69. Schedule monthly crawls

Run a full site crawl with Screaming Frog or Sitebulb monthly for sites under 10,000 pages. Larger sites should crawl continuously or at minimum quarterly.

70. Monitor Core Web Vitals in Search Console

The CWV report shows field data (real user measurements). Address any URLs flagged as “Poor” immediately; address “Needs Improvement” on a rolling basis.

71. Track index count changes

Use site:domain.com searches or Search Console’s Indexing report to monitor total indexed pages. Sudden drops indicate indexing problems.

72. Monitor backlink profile monthly

Use Ahrefs, Majestic, or Semrush to track new and lost backlinks. Investigate sudden loss of high-authority links — they may indicate manual removal, site moves, or content changes by linking sites.

73. Track keyword ranking changes

Use position tracking tools with daily updates for your top 50 keywords. Ranking drops of 10+ positions require immediate investigation of algorithm updates and technical changes.

74. Set up Google Alerts for brand mentions

Monitor for brand mentions that aren’t linking to your site — these are link building opportunities. Also monitor for negative mentions requiring reputation management.

75. Verify log file analysis capability

Server access logs reveal what Googlebot actually crawls. Ensure you have log access and analyze monthly for crawl patterns, blocked URLs, and unexpected crawler behavior.

76. Test site after every major CMS update

WordPress, Shopify, and other CMS updates frequently break custom schema, redirect plugins, or caching configurations. Run a post-update crawl after every major version update.

77. Document all technical changes

Maintain a technical SEO changelog. Correlating ranking changes with technical changes is only possible if you document what changed and when.

78. Conduct quarterly link audit

Review your disavow file, identify any toxic links that have appeared, and submit or update disavow if necessary. Never disavow without strong evidence of harm.

79. Run annual competitor technical analysis

Compare your Core Web Vitals, schema implementation, crawl depth, and mobile experience against top 3 competitors annually. Gaps reveal priority improvement areas.

80. Produce monthly technical SEO report

Summarize: crawl errors found/fixed, indexing changes, Core Web Vitals scores, ranking changes, new technical issues identified. Share with stakeholders to maintain organizational priority for technical work.

How to Prioritize This Checklist

Not all 80 items deserve equal urgency. Use this framework:

Tools You’ll Need

• Screaming Frog SEO Spider — Full site crawls and on-page analysis
• Google Search Console — Indexing, CWV, and performance data
• Sitebulb — Visual crawl reports and technical issue scoring
• Ahrefs or Semrush — Backlink analysis and keyword tracking
• GTmetrix / PageSpeed Insights — Speed and Core Web Vitals testing
• Google’s Rich Results Test — Structured data validation
• Cloudflare or Fastly — CDN and performance infrastructure

Conclusion

A comprehensive technical SEO audit is not a one-time project — it’s an ongoing operational discipline. This 80-point checklist covers every dimension of technical health that affects crawlability, indexability, page experience, and authority signals. Running through it systematically, prioritizing critical issues, and maintaining monthly monitoring creates the technical foundation that makes all other SEO investment pay off. At Over The Top SEO, we execute this framework for every enterprise client engagement because we know that technical excellence is the multiplier that makes content and link strategies work.