Table of Contents
A technical SEO audit is a systematic review of your website’s infrastructure to identify issues that prevent search engines from crawling, rendering, or indexing your pages correctly. Most SEO problems that look like content problems or link problems are actually technical problems in disguise: pages that cannot be crawled, content that cannot be rendered, signals that contradict each other.
This guide walks through a complete technical SEO audit for 2026, organized into the order you should run the checks, the tools to use for each one, and what to do when you find issues.
Executive Summary
Here’s what you need to know before diving in:
- Technical SEO audit scope depends on site size. A 50-page service business site takes two to three hours to audit manually. A 50,000-page e-commerce site requires automated crawl tools and systematic prioritization.
- Most technical issues fall into four categories: crawlability (can bots access your pages?), indexation (are the right pages indexed?), performance (do pages load fast enough?), and structured data (are your schema signals accurate?).
- Core Web Vitals became a confirmed ranking factor in 2021 and have gained weight since. In 2026, sites with poor CWV scores in competitive queries are at a measurable disadvantage.
- Rendering issues are the most underdiagnosed technical problem. JavaScript-heavy sites often show Google an empty page that looks fine in a browser.
Before You Start: Establish a Baseline
Before running any crawl tool, pull your current position baseline. Note your current organic traffic level (Google Search Console, 90-day view), your crawl stats (GSC Coverage report), and any manual actions or security issues flagged in GSC. This baseline lets you measure whether your audit fixes are producing results in the weeks after implementation.
Primary tools for a technical SEO audit:
- Google Search Console (free): Coverage, Core Web Vitals, manual actions, URL inspection
- Screaming Frog SEO Spider (free up to 500 URLs, paid beyond): Crawl simulation, redirect chains, duplicate content, broken links
- PageSpeed Insights / Lighthouse (free): Core Web Vitals lab data, performance diagnostics
- Google’s Rich Results Test (free): Structured data validation
- Ahrefs or Semrush (paid): Backlink profile, site audit, ranking position data
A thorough audit of a mid-size site requires at minimum GSC, Screaming Frog, and PageSpeed Insights. The paid tools add efficiency and depth but are not required to find the most impactful issues.
Step 1: Crawlability Check
Crawlability is whether search engine bots can access your pages at all. A page that cannot be crawled cannot rank, regardless of how good its content is.
Check your robots.txt file. Your robots.txt lives at yourdomain.com/robots.txt. Open it and confirm you are not accidentally blocking key sections of your site. The most common error is a leftover “Disallow: /” from a staging environment that was never removed when the site went live. Also confirm that your sitemap URL is listed in robots.txt.
Crawl your site with Screaming Frog. Run a crawl of your domain and look for: 4xx errors (pages that return “not found” or similar), 5xx errors (server errors), pages blocked by robots.txt that should not be, redirect chains longer than two hops, and orphan pages (pages with no internal links pointing to them).
Review your XML sitemap. Confirm your sitemap is submitted in GSC. Check that it includes only indexable, canonical pages. Sitemaps that include noindex pages, redirect targets, or 404 URLs confuse crawlers and waste crawl budget.
Check crawl stats in GSC. The “Crawl stats” report in GSC shows you how often Googlebot visits your site and whether it is encountering errors. A sudden drop in crawl rate often signals a server problem or a robots.txt change.
“A technical audit is not a checklist exercise. It is a diagnostic process. The goal is not to check every box but to find the three to five issues that are actually suppressing your rankings and fix those first. Most sites have one or two critical technical problems and dozens of minor ones. Treat them accordingly.” – ARC Marketing
Step 2: Indexation Audit
Indexation is whether Google has chosen to include your pages in its search index. Crawlability is a prerequisite for indexation, but crawled pages are not automatically indexed.
Use the site: operator. Type “site:yourdomain.com” into Google. The result count is a rough indicator of how many pages are indexed. Compare this to your total page count. Significant discrepancies (100 pages on your site, 30 in the index) signal indexation problems.
Review GSC Coverage report. The Coverage report shows you exactly which pages are indexed, which are excluded, and why. The most important sections to review:
- Valid pages: Should match your intended indexable page count
- Excluded: Crawled, currently not indexed: Google crawled these pages but chose not to index them. This is often a quality signal issue (thin content, duplicate content) or a crawl budget issue
- Excluded: Discovered, not crawled: Google knows these pages exist but has not crawled them yet. Can indicate crawl budget problems on large sites
- Errors: Pages that returned errors during crawl
Check for unintentional noindex tags. A noindex tag in a page’s meta robots tag or in its X-Robots-Tag response header tells Google not to index the page. CMS plugins (especially SEO plugins like Yoast or Rank Math) sometimes apply noindex tags to categories, tags, author archives, or paginated pages by default. Verify your important pages do not have noindex applied accidentally.
Check canonical tags. Canonical tags tell Google which version of a page is the “official” version. Canonical chains (page A canonicals to B, which canonicals to C), self-referencing canonicals on the wrong URL, or missing canonicals on paginated content are common issues.
Step 3: Core Web Vitals Assessment
Core Web Vitals are Google’s user experience metrics: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). All three are confirmed ranking factors, and the thresholds Google considers “good” are specific.
LCP (Largest Contentful Paint): The time it takes for the largest visible element on the page to load. Google’s threshold: under 2.5 seconds is “good,” 2.5 to 4.0 seconds is “needs improvement,” above 4.0 seconds is “poor.” The most common causes of poor LCP are unoptimized hero images, render-blocking resources, and slow server response times.
INP (Interaction to Next Paint): Replaced First Input Delay (FID) in March 2024. Measures how quickly a page responds to user interactions. Google’s threshold: under 200ms is “good,” 200 to 500ms is “needs improvement,” above 500ms is “poor.” JavaScript-heavy pages and third-party scripts are the most common causes of poor INP.
CLS (Cumulative Layout Shift): Measures visual stability. A score under 0.1 is “good.” Common causes of poor CLS include images without explicit dimensions, ads that load above content, and web fonts that cause text to reflow.
How to audit CWV:
Run PageSpeed Insights (pagespeed.web.dev) on your highest-traffic pages. PSI shows both “lab data” (simulated, from Lighthouse) and “field data” (real user data from the Chrome User Experience Report, when available). Field data is what Google actually uses for ranking, but lab data is actionable for diagnosis.
Also check your CWV data in GSC under “Experience > Core Web Vitals.” This shows which URL groups are classified as Good, Needs Improvement, or Poor across your real user base.
Step 4: Rendering and JavaScript Audit
A page that looks correct in a browser can look completely empty to a search engine if the content is rendered by JavaScript and Google cannot execute that JavaScript before indexing.
Use Google’s URL Inspection tool. In GSC, paste any URL into the URL Inspection tool and select “View Crawled Page” to see what Googlebot actually saw. If the rendered HTML is empty or missing major content visible in a browser, you have a rendering problem.
Test with JavaScript disabled. In Chrome DevTools, you can disable JavaScript and reload your page. If your page content disappears, it is JavaScript-rendered. That does not automatically mean Google cannot see it (Googlebot does render JavaScript), but it means you should verify with the URL Inspection tool.
Common JavaScript rendering issues:
- Content that only loads after user interaction (scroll-triggered, click-triggered)
- Dynamic content populated by API calls after the page loads
- Single Page Application frameworks (React, Vue, Angular) without server-side rendering (SSR) or pre-rendering configured
- Lazy-loaded images without explicit dimensions that cause CLS
If you have a SPA without SSR, adding server-side rendering or using a pre-rendering service (Prerender.io or similar) is the structural fix. Partial fixes include ensuring critical content is in the initial HTML and adding an explicit preload link for the largest image.
Step 5: Structured Data Audit
Structured data is machine-readable code you add to your pages that tells search engines what kind of content they contain. In 2026, structured data does two things: it enables rich results in traditional search (star ratings, FAQ dropdowns, how-to steps) and it provides explicit signals to AI systems for inclusion in AI Overviews and AI-powered answers.
Validate existing schema. Run your key pages through Google’s Rich Results Test (search.google.com/test/rich-results). This shows you whether your structured data is valid and what rich results it qualifies for.
Audit for schema errors in GSC. The “Enhancements” section of GSC shows any structured data types Google has detected on your site, along with errors and warnings for each type.
Common structured data gaps for business websites:
- LocalBusiness or relevant subtype (Plumber, LegalService, MedicalBusiness): Should be on your homepage and contact page
- FAQPage: On any page with a FAQ section. High-value for AI Overviews extraction
- Service: On individual service pages
- BreadcrumbList: On all pages with navigation depth
- Review/AggregateRating: If you display reviews on your site and have the rights to mark them up
A schema error in GSC means the markup is invalid and will not enable rich results. A schema warning means it is valid but potentially incomplete.
Step 6: Internal Linking and Architecture Audit
Internal linking tells search engines which pages are important and how your content is organized. A site where all pages are equally linked has no topical hierarchy. A site where content clusters link through to pillar pages concentrates authority where it matters.
Check for orphan pages. Pages with no internal links pointing to them are invisible to Googlebot unless they are in your sitemap. Run a crawl in Screaming Frog and filter for pages with zero inlinks.
Audit anchor text distribution. In Screaming Frog, review the anchor text used for internal links to your most important pages. Descriptive, keyword-relevant anchor text (“technical SEO audit guide”) transfers more topical relevance than generic text (“click here” or “learn more”).
Check link depth. Important pages should be reachable in three clicks or fewer from the homepage. Pages buried six levels deep are crawled less frequently and rank with less authority. If your blog posts are in a folder structure like /blog/category/year/month/post-title/, consider flattening the URL structure.
Frequently Asked Questions
How often should I run a technical SEO audit?
For most business websites, a full technical audit once per year with quarterly spot-checks of the highest-priority areas (GSC Coverage report, CWV scores, any new pages added) is sufficient. Large sites with frequent content changes or ongoing development benefit from continuous monitoring through automated crawls.
What is the most common technical SEO issue?
Based on site audits across industries, the most common impactful issues are: 1) slow LCP caused by unoptimized hero images, 2) unintentional noindex tags applied by SEO plugins, 3) redirect chains that lose link equity through multiple hops, and 4) missing or misconfigured canonical tags on paginated content or filtered views.
Can I run a technical SEO audit without paid tools?
Yes. Google Search Console (free), Screaming Frog up to 500 URLs (free), Google’s Rich Results Test (free), and PageSpeed Insights (free) cover the most critical audit areas for most business websites. Paid tools like Ahrefs Site Audit or Semrush’s technical audit add efficiency and depth but are not required to find the highest-impact issues.
How do I prioritize technical SEO fixes?
Prioritize by impact and effort. Highest priority: anything that prevents key pages from being indexed or crawled (noindex errors, robots.txt blocks, crawl errors on important URLs). Medium priority: CWV failures on high-traffic pages, schema errors that suppress rich results, redirect chains. Lower priority: minor crawl warnings, image alt text, metadata optimizations on low-traffic pages.
What is the difference between a technical SEO audit and an SEO audit?
A technical SEO audit specifically examines the infrastructure layer: crawlability, indexation, page speed, rendering, and structured data. A broader SEO audit also covers on-page content quality, keyword targeting, backlink profile, and competitor analysis. Most agencies run a technical audit first because technical issues suppress the impact of content and link-building work.
Sources
- Google Search Console Help: Search Console reports — Coverage report, Core Web Vitals report, URL Inspection tool documentation
- Google Web Developers: Core Web Vitals — LCP, INP, and CLS thresholds and ranking factor confirmation
- Screaming Frog SEO Spider — Crawl data capabilities and site audit methodology
- PageSpeed Insights — Field data vs. lab data distinction and Core Web Vitals measurement
- Google Search Central: Robots.txt — Robots.txt specification and crawl guidance
- Google Search Central: Canonical tags — Canonical tag guidance and indexation documentation
- Google Search Central: Structured data — Schema markup and rich results documentation
- Ahrefs Blog: Technical SEO audit guide — Technical SEO audit methodology and common issue prioritization
- Search Engine Journal: JavaScript SEO — JavaScript SEO rendering best practices and SPA indexation research