Technical SEO Audit Checklist: 50+ Items for 2026

Most technical SEO problems are invisible. Your site looks fine to visitors while it quietly fails search engines for months. This checklist gives you the exact items to inspect, the tools to use, and the thresholds that count, whether you run the audit yourself or use it to vet whoever you are paying to do it.

5 min read7 sectionsJune 22, 2026

Audit order matters: crawl, then index, then everything else

Run the checklist in dependency order, because skipping ahead wastes time. Can Google crawl it? If robots.txt blocks a page, nothing downstream matters. Can Google render it? JavaScript errors can hide content even when the raw HTML loads. Can Google index it? A stray noindex or conflicting canonical kills visibility regardless of content quality. The lean starting stack is Google Search Console (the authoritative index signal, free) plus Screaming Frog SEO Spider (free for 500 URLs, about 199 GBP or roughly 252 USD per year for unlimited). Those two cover 80 percent of technical diagnostic work for under 300 USD a year. Add Ahrefs (from 129 USD per month) or Semrush (from 139.95 USD per month) only when you also need backlink and keyword data. Start every audit by exporting a full crawl and opening the Page Indexing report under Indexing in Search Console.

Crawlability checklist (items 1-12)

  1. robots.txt does not contain a stray Disallow: / left over from staging. 2. CSS and JavaScript resources are not blocked, so Google can render layout. 3. No important directories are accidentally disallowed. 4. Crawl traps (endless calendar pages, session IDs, infinite filters) are blocked. 5. robots.txt is reachable at the root and returns 200. 6. Server returns proper status codes (no soft 404s returning 200 with thin content). 7. Redirect chains are collapsed to a single hop. 8. No redirect loops. 9. Internal links use 200-status canonical URLs, not redirects. 10. Important pages sit within three clicks of the homepage. 11. Orphan pages (no internal links pointing to them) are identified and linked or removed. 12. AI crawlers you want citing you (GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, Google-Extended) are not blocked in robots.txt unless you have a specific reason. Remember: robots.txt controls crawling, not indexing. A blocked URL can still appear in results without a snippet.

Indexing checklist (items 13-26)

  1. XML sitemap contains only indexable, canonical URLs, with no noindex, redirect, or duplicate URLs. 14. Sitemap stays under 50,000 URLs per file; large sites split into segmented sitemaps (blog, products). 15. Sitemap is submitted to Search Console and Bing Webmaster Tools. 16. lastmod dates change only on real content updates (Google ignores lastmod if it learns you are lying). 17. Every page has a self-referencing canonical or points to the correct authoritative version. 18. No canonical conflicts where A points to B and B points to A. 19. Canonicals, redirects, and sitemap all agree on the same URL version. 20. In URL Inspection, Google-selected canonical matches your user-declared canonical on key pages. 21. No accidental noindex on valuable pages (check both meta robots and the X-Robots-Tag HTTP header). 22. No page is both noindex and blocked in robots.txt (Google cannot see the noindex if it cannot crawl). 23. Investigate every URL marked Crawled - currently not indexed for thin or duplicate content. 24. Faceted navigation is not generating tens of thousands of low-value filter URLs that burn crawl budget. 25. HTTPS is enforced site-wide with no mixed-content warnings. 26. Domain variants (HTTP/HTTPS, www/non-www, trailing slash, URL casing) are standardized to one version.

Core Web Vitals checklist (items 27-36)

Core Web Vitals are a confirmed ranking signal, scored on real-user field data at the 75th percentile. A page passes only if at least 75 percent of visits meet the good threshold, and the overall status equals the worst of the three metrics. 27. LCP (Largest Contentful Paint) is 2.5 seconds or less; 2.6-4.0s is Needs Improvement, over 4.0s is Poor. 28. INP (Interaction to Next Paint) is 200ms or less; 201-500ms is Needs Improvement, over 500ms is Poor. INP replaced FID in March 2024. 29. CLS (Cumulative Layout Shift) is 0.1 or less; over 0.25 is Poor. 30. Vitals are measured on mobile over a 4G connection, not just desktop lab scores. 31. Largest element (usually a hero image) is preloaded and properly sized. 32. Images and embeds have explicit width and height to prevent layout shift. 33. Render-blocking JavaScript and CSS are minimized or deferred. 34. Web fonts use font-display: swap or are preloaded. 35. Third-party scripts (chat, analytics, ads) are audited for INP impact. 36. Check the Core Web Vitals report in Search Console and validate fixes with PageSpeed Insights. As context, the 2025 Web Almanac found only about 48 percent of mobile pages pass all three, so passing is a real competitive edge.

Structured data checklist (items 37-44)

  1. Markup uses JSON-LD (Google's recommended format) rather than Microdata or RDFa. 38. Structured data describes only content actually visible on the page (no marking up hidden content). 39. Every rich-result type includes all required properties; missing required fields make a page ineligible. 40. Validate with Google's Rich Results Test for eligibility and the Schema.org Markup Validator for syntax. 41. Use the supported high-value types: Article/BlogPosting, Product, FAQPage, HowTo, VideoObject, LocalBusiness, Organization, BreadcrumbList, Event, Review, and JobPosting. 42. Remove the seven types Google dropped rich-result support for in 2025 (Book Actions, Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement, Vehicle Listing). They will not hurt rankings, but cleaning them up matters before the January 2026 Search Console reporting changes. 43. Organization and WebSite markup is on the homepage to feed Google's Knowledge Graph and AI Overviews. 44. BreadcrumbList markup is present so the SERP shows a clean path instead of a raw URL. Note that valid markup makes a rich result possible, never guaranteed.

Mobile and international checklist (items 45-52)

Mobile-first indexing has been the 100 percent default since July 2024, so Google indexes your mobile version, full stop. 45. Mobile content has full parity with desktop (same body copy, headings, internal links, and structured data). 46. Content hidden in mobile tabs or accordions is still in the rendered HTML so Google can index it. 47. The site uses responsive design with a single URL per page rather than separate m-dot URLs. 48. Tap targets and font sizes are usable without zoom. 49. No intrusive interstitials block content on mobile. For multilingual sites: 50. hreflang tags use absolute URLs and correct language-region codes. 51. Return links are reciprocal (if X points to Y, Y points back to X) or Google ignores the annotation. 52. hreflang URLs are the canonical URLs and an x-default fallback exists for unmatched languages. On llms.txt: it is a low-effort optional readiness layer, not a ranking signal. Google has confirmed it does not support it, so prioritize the fundamentals above and welcome AI crawlers in robots.txt instead.

How to use this to vet a contractor, and where Pineido fits

If you are hiring out the work, ask the contractor to deliver findings against these 52 items with evidence: a crawl export, screenshots of the Search Console Page Indexing report, and before/after Core Web Vitals field data from PageSpeed Insights or CrUX. Be skeptical of anyone who leads with llms.txt, promises guaranteed rankings, or cannot show you the worst-metric logic behind a failing Core Web Vitals score. Prioritization is the real skill: crawl and index blockers first, then performance, then markup polish. If you would rather not run this yourself, our 30-day fixed-price technical SEO sprint works through exactly this checklist, ships the high-impact fixes (redirect cleanups, canonical alignment, Core Web Vitals work, schema repair), and hands you a re-audit so you can verify the result. It is the same helpful-first, evidence-backed approach as this article, just done for you at a known price.

Kostadin Stamboliev

Founder and Imaginator

LinkedIn

Founder and Imaginator at Pineido. Practitioner across IT consulting, app and web development, technical SEO, and AI / automation. Ships production code in 30-day sprints with fixed scope and clear ownership.

Get operations insights weekly

Join service-business operators who get one actionable insight on ops, automation, and growth every week.

Checking that you're human. You can send in a moment.

No spam. Unsubscribe anytime.

You’re subscribed! Look for our next issue in your inbox.

Frequently asked questions

How often should I run a technical SEO audit?

Most teams run a full technical audit quarterly, with lighter monthly checks on Core Web Vitals, the Search Console coverage report, and crawl stats. Always run an audit after a site migration, a CMS change, a redesign, or a major Google update, since those are when silent issues like a stray noindex or broken canonicals tend to appear.

What tools do I need for a technical SEO audit?

The lean stack is Google Search Console (free, the authoritative index signal) plus Screaming Frog SEO Spider (free for 500 URLs, about 252 USD per year for unlimited). Add PageSpeed Insights for Core Web Vitals and Google's Rich Results Test for structured data. Ahrefs (from 129 USD per month) or Semrush (from about 140 USD per month) are worth it only when you also need backlink and keyword data.

What are the current Core Web Vitals thresholds?

Good is LCP 2.5 seconds or less, INP 200 milliseconds or less, and CLS 0.1 or less, all measured on real-user field data at the 75th percentile. A page passes only if at least 75 percent of visits hit those marks, and the overall status equals the worst of the three metrics. INP replaced FID in March 2024.

Why are my pages crawled but not indexed?

Crawled - currently not indexed usually signals thin content, near-duplicate content, or conflicting indexing signals. Check whether the page duplicates a stronger page, whether faceted navigation is generating low-value variants, and whether canonicals point where you intend. Improve content quality and internal linking, and make sure the page is genuinely worth a unique index entry.

Do I need an llms.txt file for AI search?

Not for rankings. Google has publicly confirmed it does not support llms.txt, and no major AI provider has committed to using it as of 2026. It is an optional, low-effort readiness layer that is most useful for documentation and API products feeding AI coding assistants. AI search visibility still comes from authority, structured content, and not blocking AI crawlers in robots.txt.

Which technical SEO issues should I fix first?

Fix anything that blocks crawling or indexing before anything else: a Disallow: / in robots.txt, accidental noindex on money pages, conflicting canonicals, and redirect chains. Then move to Core Web Vitals failures, then structured data and mobile parity. Foundation first, polish last, because rankings cannot exist for pages Google cannot crawl, render, and index.

Ready to ship?

Tell us where you are stuck. We will review it and send a focused recommendation within one business day.