Technical SEO Audit Checklist: 30 Things to Fix Right Now

Google processes approximately 8.5 billion search queries per day. Ensuring that a website’s pages are crawlable by Googlebot, indexable in Google’s index, and technically sound enough to rank competitively requires addressing a checklist of infrastructure, speed, and signal issues that are entirely separate from content quality. A well-written page that cannot be crawled is invisible. A crawlable page with poor Core Web Vitals scores loses ranking position to equivalent content with better performance. Technical SEO is the foundation on which content and link building produce their results.

The 30-point checklist below covers the most impactful technical SEO issues identified in site audits across a range of website types. Each item includes the specific tool or method for checking it and the most common fix.

Crawlability (Items 1-8)

1. Robots.txt file: Verify the file is accessible at domain.com/robots.txt and does not accidentally block Googlebot from crawling important sections of the site. Common error: disallow rules added during development (Disallow: /) that were never removed for production. Check using Google Search Console’s robots.txt tester.
2. XML sitemap: Verify the sitemap exists, is submitted to Google Search Console, is accessible at the URL listed in robots.txt, and contains only indexable URLs (no noindexed, redirected, or canonicalised-away URLs). Common error: sitemap includes pages with noindex meta tags, confusing Googlebot about which pages should be indexed.
3. Internal link crawl depth: Run a site crawl using Screaming Frog or Sitebulb. No important page should be more than three clicks from the homepage in the internal link structure. Pages buried beyond four to five clicks receive crawl budget allocation issues on larger sites.
4. Crawl traps: Check for pagination chains without rel=”nofollow” or canonical tags that lead to infinite crawlable page sets (e.g. session ID parameters, infinite filter combinations). These waste crawl budget on non-unique pages.
5. Blocked resources: Verify that CSS, JavaScript, and image files used for page rendering are not blocked in robots.txt. If Googlebot cannot render the page as a user would see it, JavaScript-dependent content may not be indexed.
6. Crawl budget waste: Review Google Search Console’s crawl stats report for pages consuming disproportionate crawl budget: internal search result pages, URL parameters generating duplicate content, and staging/test URLs that have become linked from the production site.
7. Site architecture: Verify that the site’s category and subcategory structure produces logical crawl paths. Orphan pages (pages with no internal links pointing to them) are not discovered through crawl and rely entirely on sitemap discovery.
8. Redirect chains: Check for redirect chains (A redirects to B redirects to C) using Screaming Frog. Each additional redirect hop loses link equity and adds latency. Resolve chains to single-hop direct redirects.

Indexability (Items 9-16)

9. Noindex meta tags: Audit pages with noindex meta robots tags. Confirm each noindexed page is intentionally excluded from the index (login pages, thin content, test pages). Common error: noindex tags left on important pages after a site rebuild.
10. Canonical tags: Verify canonical tags are correctly implemented (self-referencing canonicals on canonical pages, canonical tags pointing to the preferred URL on duplicate or near-duplicate pages). Common error: canonical pointing to a different domain or a redirect URL.
11. Duplicate content: Use Screaming Frog’s content analysis or Siteliner to identify pages with duplicate or near-duplicate content. Common sources: www vs non-www variants, HTTP vs HTTPS versions, trailing slash vs no trailing slash URLs, and parameter-generated pages.
12. HTTP to HTTPS redirect: Verify that all HTTP versions of pages redirect to HTTPS with a 301 redirect. Mixed content (HTTPS page loading HTTP resources) is a secondary issue identified in Chrome DevTools.
13. Google Search Console coverage report: Review the Coverage report in Google Search Console for submitted but not indexed URLs. The reasons listed (Crawled but not currently indexed, Discovered but not crawled, Excluded) identify specific indexing problems requiring investigation.
14. Hreflang implementation: For multilingual or multi-regional sites, verify hreflang tags are correctly implemented (matching x-default, correct ISO 639-1 language codes, reciprocal hreflang between page versions). Use hreflang testing tools or Screaming Frog’s hreflang report.
15. Thin content: Identify pages with very low word count (under 200 words) that provide limited value to users. These pages dilute site-wide content quality signals. Consider consolidating, expanding, or noindexing thin pages.
16. Pagination: Verify that paginated page sets do not create duplicate content issues. Since Google deprecated rel=”next” and rel=”prev” in 2019, the standard approach is a self-canonical on each paginated page, load more implementations, or logical pagination with unique content per page.

Site Speed and Core Web Vitals (Items 17-22)

17. Largest Contentful Paint (LCP): LCP measures loading performance. The main content element should load within 2.5 seconds for a good score. Check using PageSpeed Insights (Google’s tool) or Chrome User Experience Report (CrUX). Common fixes: image lazy loading, image compression, serving images in WebP or AVIF format, preloading the LCP element.
18. Interaction to Next Paint (INP): INP replaced First Input Delay as a Core Web Vitals metric in March 2024. It measures responsiveness across all page interactions. Good INP is below 200ms. Check in CrUX or lab testing with Chrome DevTools. Common fixes: reduce JavaScript execution time, break up long tasks, defer non-critical JavaScript.
19. Cumulative Layout Shift (CLS): CLS measures visual stability. Good CLS is below 0.1. Common causes: images without defined dimensions, embeds without set height/width, dynamically injected content above the fold. Check using CrUX and Chrome DevTools Layout Shift debugging.
20. Time to First Byte (TTFB): TTFB is the time from the user’s request to the first byte of response received. Good TTFB is below 800ms. Common fixes: server performance improvement, CDN implementation, caching configuration.
21. Image optimisation: Check that images are served in next-gen formats (WebP, AVIF), correctly sized for the display context (no serving 2000px images in 400px containers), and compressed appropriately. Use PageSpeed Insights for specific image recommendations.
22. Third-party script impact: Audit third-party scripts (analytics, chatbots, advertising, marketing automation) for their performance impact. Each third-party script adds connection overhead and execution time. Load non-critical third-party scripts asynchronously or defer them.

Structured Data and Technical Signals (Items 23-30)

23. Structured data implementation: Verify structured data (Schema.org JSON-LD markup) is correctly implemented for relevant schema types (Article, FAQPage, Product, LocalBusiness, BreadcrumbList). Use Google’s Rich Results Test to validate. Common error: structured data present in the code but not matching the visible page content.
24. Title tags: Verify all pages have unique, descriptive title tags within 50 to 60 characters. Check for missing titles, duplicate titles (particularly common on e-commerce product variants), and titles that do not reflect the actual page content.
25. Meta descriptions: Verify all important pages have unique meta descriptions of 150 to 160 characters that accurately describe the page content. Meta descriptions do not directly affect ranking but influence click-through rate from search results.
26. Heading structure: Verify each page has a single H1 tag that aligns with the page’s target keyword and topic. Check that heading hierarchy (H1, H2, H3) is logical and does not skip levels.
27. Internal linking anchor text: Review internal link anchor text across the site. Descriptive anchor text (the specific topic of the destination page) communicates topical relevance to Googlebot better than generic anchors (“click here”, “read more”).
28. 404 error pages: Identify 404 errors in Google Search Console’s Coverage report and in server logs. External links pointing to 404 pages waste link equity. Redirect to the most relevant existing page or the category page.
29. Mobile usability: Check Google Search Console’s Mobile Usability report for issues: text too small to read, clickable elements too close together, viewport not set, content wider than screen. Google uses mobile-first indexing, making mobile usability issues ranking factors.
30. Core Web Vitals in Search Console: Review the Core Web Vitals report in Google Search Console for real-user performance data aggregated from Chrome User Experience Report. The field data in CrUX is what Google uses for ranking purposes; lab data from PageSpeed Insights is a diagnostic tool, not the ranking signal directly.

AEO FAQ: Technical SEO Audit Questions

What is a technical SEO audit and why is it important?

A technical SEO audit is a systematic review of a website’s technical infrastructure to identify issues that prevent search engines from crawling, indexing, and ranking the site effectively. It covers crawlability (can Googlebot access all important pages), indexability (are the right pages included in Google’s index), site speed and Core Web Vitals (do pages meet performance thresholds that affect ranking), structured data (is schema markup correctly implemented), and various on-page technical signals (title tags, meta descriptions, heading structure). Technical SEO issues are important because they are invisible from a content perspective: a page with excellent content that has a noindex meta tag or is blocked by robots.txt will not rank regardless of its quality.

What tools are used for a technical SEO audit in 2026?

The primary tools for a technical SEO audit in 2026 are: Google Search Console (provides official data on crawl coverage, Core Web Vitals in the field, mobile usability issues, structured data errors, and crawl stats), Screaming Frog SEO Spider (desktop tool that crawls sites and reports on redirects, duplicate content, broken links, meta tags, and hreflang), PageSpeed Insights (Google’s tool for lab-based Core Web Vitals measurement and specific performance recommendations), Ahrefs or Semrush for site audit functions (commercial tools with additional SEO context for crawl issues), and the Chrome User Experience Report (CrUX) for real-user performance field data. Google Search Console is the most important single source because it provides data from Google’s own crawl and indexing system.

What are Core Web Vitals and why do they matter for SEO?

Core Web Vitals are three user experience metrics that Google uses as ranking signals: Largest Contentful Paint (LCP, measuring loading speed of the main content element, target below 2.5 seconds), Interaction to Next Paint (INP, measuring responsiveness to user interactions, target below 200ms, replaced First Input Delay in March 2024), and Cumulative Layout Shift (CLS, measuring visual stability and unexpected layout movement, target below 0.1). They matter for SEO because Google uses field data from real Chrome users (via the Chrome User Experience Report) to assess whether pages provide a good user experience, and pages meeting the Core Web Vitals thresholds receive a modest ranking boost over equivalent pages that do not.

How do you fix crawl budget issues for large websites?

Crawl budget fixes for large websites involve reducing the number of low-value pages Googlebot crawls so it can allocate more crawl budget to important pages. Actions include: adding noindex tags to thin, duplicate, or low-value pages (parameter-generated pages, internal search results, user profile pages) to exclude them from the crawl index, blocking infinite crawl paths from session IDs and filter combinations in robots.txt, consolidating duplicate content under canonical tags, ensuring pagination does not create excessively deep crawl chains, and resolving redirect chains to single-hop direct redirects. The Crawl Stats report in Google Search Console shows pages crawled per day and the response codes Googlebot received, allowing identification of pages consuming disproportionate crawl budget.

What is the most common technical SEO issue found in audits?

The most commonly found technical SEO issues in professional site audits are: missing or incorrect canonical tags (creating unresolved duplicate content signals), broken internal links pointing to redirect URLs or 404 pages (wasting link equity), pages with noindex tags that should be indexed (or vice versa), missing or duplicate title tags, Core Web Vitals failures particularly on LCP and CLS for sites with large images or dynamic content, and structured data errors where schema markup does not match the visible page content. For e-commerce sites specifically, parameter-generated duplicate content from filter and sort functionality is consistently the largest technical issue by scale.

How often should you do a technical SEO audit?

A comprehensive technical SEO audit should be conducted at a minimum of every six months for active websites with regular content publishing. Smaller, stable sites can conduct annual audits. Triggers for an immediate technical audit include: a significant organic traffic drop (indicating a possible technical change or Google update penalty), a major site rebuild or CMS migration, a domain change, a new subsite or subdomain launch, and any deployment that changes the site’s URL structure, navigation, or server configuration. Google Search Console should be monitored continuously (weekly) for emerging technical issues: coverage report anomalies, Core Web Vitals deterioration, and manual action notifications.

Technical Health Is the Floor, Not the Ceiling

Technical SEO does not produce rankings on its own. It produces the floor below which rankings cannot rise regardless of content quality or backlink profile. A site with a clean technical audit, no crawlability issues, good Core Web Vitals, and correct structured data implementation is positioned to benefit fully from content investment and link building efforts. A site with fundamental technical issues is building content and links on an unstable foundation where improvements are partially or fully negated by the technical constraints. Conducting a technical audit and resolving its findings before investing heavily in content or link building is the order of operations that produces the most efficient SEO return on investment.