Technical SEO Audit Checklist: 40 Checks for 2026

Updated October 31, 2026

Great content can’t rank if search engines can’t crawl it, render it, or decide which version to index. A technical SEO audit finds the problems that silently cap your organic traffic: pages blocked by accident, duplicate versions competing with each other, redirects that lead nowhere, slow templates, and structured data that no longer matches the page.

This technical SEO audit checklist is the one we use as a starting point, organized by layer: crawling, indexing, rendering, performance, site structure, structured data, and international SEO. You don’t need expensive tools to begin. Google Search Console, a crawler, and a browser go a long way.

Before You Start: Tools and Baseline

Gather these first:

• Google Search Console access for the domain property, which covers all subdomains and protocols.
• A site crawler that can render JavaScript, to see your site the way a search engine does.
• Google Analytics 4 or your analytics tool, to see which pages bring traffic and conversions.
• Server log files, if available, especially for large sites.
• A list of your most important pages: top landing pages, key service or product pages, and pages that generate leads or sales.

Record your baseline: indexed pages, organic clicks and impressions from Search Console, and Core Web Vitals status. You’ll want to measure the effect of your fixes.

1. Crawlability and Indexing: Can Google Reach Your Pages?

Crawlability and indexing come first, because nothing else matters if pages aren’t in Google’s index.

1. Check robots.txt. Make sure it doesn’t block important sections, CSS, or JavaScript files. Remember: robots.txt controls crawling, not indexing. A blocked URL can still appear in search results if other pages link to it.
2. Find accidental noindex tags. Crawl the site and list every page with a noindex meta tag or X-Robots-Tag header. Staging settings left on after a launch are a classic cause of traffic loss.
3. Don’t combine noindex and robots.txt blocking. If Google can’t crawl a page, it can’t see the noindex tag.
4. Review server response codes. Important pages should return 200. Look for unexpected 4xx and 5xx errors and pages that return 200 while showing “not found” content (soft 404s).
5. Check internal links to important pages. Pages with few or no internal links (orphan pages) are crawled less and rank poorly.
6. Worry about crawl budget only if it applies. Google’s guidance says crawl budget is mainly a concern for very large sites, roughly a million or more unique pages, or sites with 10,000+ pages that change daily. For most businesses, it’s not the issue.

2. The Search Console Page Indexing Report

The Search Console page indexing report shows which URLs Google has indexed and why others aren’t. Review each reason:

7. “Excluded by noindex tag”: confirm every URL listed is supposed to be excluded.
8. “Blocked by robots.txt”: confirm these are intentional.
9. “Duplicate without user-selected canonical” and “Duplicate, Google chose different canonical than user”: investigate why Google disagrees with your canonical choice.
10. “Crawled, currently not indexed”: often a quality or duplication signal. Improve or consolidate these pages.
11. “Discovered, currently not indexed”: Google knows the URL but hasn’t crawled it yet. Common on new or weakly linked pages.
12. “Page with redirect” and “Not found (404)”: check that these are expected and that no important links point to them.
13. Use URL Inspection on key pages to see the indexed version, the canonical Google selected, and the rendered HTML.

3. XML Sitemap Best Practices

14. Submit a sitemap in Search Console and reference it in robots.txt.
15. Include only canonical, indexable URLs that return 200. No redirects, no noindex pages, no 404s.
16. Respect the limits: 50,000 URLs or 50MB uncompressed per sitemap file. Use a sitemap index for larger sites.
17. Keep lastmod accurate. Google uses the lastmod date when it’s consistently reliable, and ignores the priority and changefreq values.
18. Split sitemaps by type (pages, posts, products) to spot indexing gaps by section.

4. Canonicals, Duplicates, and Redirects

19. One canonical URL per piece of content. Check for duplicates caused by HTTP and HTTPS, www and non-www, trailing slashes, uppercase letters, and tracking parameters.
20. Self-referencing canonical tags on indexable pages, pointing to the exact preferred URL.
21. Remember canonicals are hints. If internal links, sitemaps, and redirects contradict your canonical, Google may pick a different URL.
22. Use 301 redirects for permanent moves, and update internal links to point directly to the final URL.
23. Eliminate redirect chains and loops. Google follows up to 10 redirect hops, but each one wastes crawl resources and slows users.
24. Map redirects after any migration or redesign, and recheck high-value old URLs, especially those with backlinks.
25. Control faceted navigation and parameters on ecommerce and listing sites, so filter combinations don’t create thousands of thin URLs.

5. Rendering, Mobile, and JavaScript

Google completed its move to mobile-first indexing years ago: it crawls and indexes sites primarily with a smartphone user agent.

26. Check mobile and desktop parity. Content, links, structured data, and metadata should be the same on mobile. Anything missing on mobile may be invisible to Google.
27. Test JavaScript rendering. Compare the raw HTML with the rendered HTML in URL Inspection. Critical content and links should be present after rendering, and ideally in the initial HTML.
28. Use real links. Navigation should use standard anchor tags with href attributes, not click handlers that Google can’t follow.
29. Don’t block resources that pages need to render.
30. Avoid content that loads only after user interaction, such as text that appears only after a click, for anything you want indexed.

6. Performance and Core Web Vitals

31. Open Search Console’s Core Web Vitals report, which groups URLs by pattern, to find the templates that fail.
32. Check field data, not just lab tests: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint within 200 milliseconds, and Cumulative Layout Shift below 0.1.
33. Fix template-level issues first: oversized hero images, render-blocking scripts, heavy third-party tags, layout shifts from late-loading banners.
34. Confirm HTTPS everywhere, with no mixed content warnings.
35. Check the Security issues and Manual actions reports. A hacked site or a manual penalty overrides every other optimization.

7. Site Architecture, Structured Data, and International SEO

36. Keep important pages within a few clicks of the homepage, with descriptive internal link text.
37. Use breadcrumbs on deep sites, with BreadcrumbList markup.
38. Validate structured data with the Rich Results Test and fix errors in Search Console’s enhancement reports. Stop spending effort on rich results Google has retired.
39. Check hreflang on multilingual or multi-regional sites: reciprocal links, correct language and region codes, and an x-default where useful.
40. Review title tags and meta descriptions at scale for duplicates and missing values. That overlaps with on-page work; see our on-page SEO guide.

How to Prioritize What You Find

Working through a technical SEO audit checklist usually produces a long list. Rank each issue by:

• Impact: does it affect important pages, many pages, or revenue-generating pages?
• Effort: a setting change, a template fix, or a development project?
• Risk: could it cause deindexing or a security problem?

Fix critical indexing and security issues immediately. Then tackle template-level fixes that improve many pages at once, and finally smaller page-level items. After fixes, monitor Search Console for several weeks to confirm Google has recrawled and reprocessed the affected pages.

If traffic has dropped and you’re not sure whether the cause is technical, our guide on how to tell if your SEO is still working helps separate technical issues from algorithm changes and shifts in search behavior.

Want a Professional Technical SEO Audit?

A checklist finds symptoms; experience tells you which ones matter. Our SEO agency team runs technical audits with a prioritized action plan and can work directly with your developers. We’re based in Belgium and Luxembourg and support U.S. companies remotely, walking through findings with you on a shared screen. Request a free assessment and start with your site’s biggest technical issues.

Frequently Asked Questions About Technical SEO Audits