TL;DR: A technical SEO audit checklist organized into three priority tiers: crawlability first, indexation second, performance third. Each item includes what to check, which tool to use, and what a passing result looks like.
What is a technical SEO audit checklist?
A technical SEO audit checklist is a structured list of checks that verify whether search engines can crawl, render, index, and rank your pages correctly. The difference between a useful checklist and a useless one is prioritization. Not all issues are equal.
This checklist is organized into three tiers based on impact:
| Tier | Focus | Why It Comes First |
|---|---|---|
| Tier 1 (Critical) | Crawlability and indexation | If Google cannot reach your pages, nothing else matters |
| Tier 2 (High) | Site structure and content signals | Affects how Google understands and ranks your content |
| Tier 3 (Medium) | Performance and user experience | Core Web Vitals are a confirmed ranking signal |
Fix Tier 1 issues before touching anything else. A page with perfect Core Web Vitals scores that Google cannot crawl generates zero organic traffic.
Tier 1: Crawlability and Indexation
These checks determine whether Google can physically access and store your pages. Every technical SEO audit checklist should start here.
Can Google access your pages?
Check your robots.txt file for unintentional blocks. A single misplaced Disallow rule can hide entire sections of your site from Googlebot.
What to check:
- robots.txt is accessible at
/robots.txt(returns 200, not 404 or 500) - No
Disallow: /blocking the entire site - Important paths (service pages, blog posts, product pages) are not blocked
- CSS and JavaScript files are not blocked (Google needs these to render pages)
Tool: Screaming Frog > Configuration > robots.txt > Test
Pass criteria: All important page types are crawlable. Only admin paths, search results pages, and parameter URLs are blocked.
Are your pages being indexed?
Submit your XML sitemap to Google Search Console and compare submitted pages vs. indexed pages. A large gap indicates indexation problems.
What to check:
- XML sitemap exists and is submitted to GSC
- Sitemap only contains indexable, canonical URLs (no redirects, no noindexed pages)
- “Pages” report in GSC shows no unexpected “Excluded” categories growing
site:yourdomain.comin Google returns a reasonable page count
Tool: Google Search Console > Pages report
Pass criteria: Indexed page count is within 10-15% of your sitemap URL count. No critical page types showing as “Discovered but not indexed.”
Are canonical tags correct?
Canonical tags tell Google which version of a page is the “real” one. Incorrect canonicals can cause Google to ignore your preferred pages entirely.
What to check:
- Every page has a self-referencing canonical tag
- No pages canonicalize to a different URL unintentionally
- Paginated pages do not canonical to page 1 (this was correct pre-2019 but is now wrong)
- HTTP pages canonical to HTTPS versions
- Trailing slash consistency (pick one pattern and stick with it)
Tool: Screaming Frog > Canonicals tab, filter by “Non-Indexable”
Pass criteria: Zero pages with canonical pointing to a different URL unless intentional (e.g., product variants).
Are there crawl errors blocking important pages?
Server errors (5xx), client errors (4xx), and redirect chains waste crawl budget and prevent indexation.
What to check:
- No 5xx errors on important pages
- 404 pages are genuinely deleted content (not broken internal links)
- No redirect chains longer than 2 hops (A > B > C should be A > C)
- No redirect loops
- Internal links do not point to redirected URLs (update them to the final destination)
Tool: Screaming Frog > Response Codes tab
Pass criteria: Zero 5xx errors. All 404s are intentional. No redirect chains longer than 1 hop on high-traffic pages.
Tier 2: Site Structure and Content Signals
Once Google can access your pages, these checks ensure it understands your content and site hierarchy.
Is your site architecture logical?
Crawl depth matters. Pages buried more than 3 clicks from the homepage get crawled less frequently and pass less internal link equity.
What to check:
- Important pages are within 3 clicks of the homepage
- No orphan pages (pages with zero internal links pointing to them)
- Flat architecture for key commercial pages
- Breadcrumbs reflect the actual site hierarchy
- Internal links use descriptive anchor text (not “click here”)
Tool: Screaming Frog > Site Architecture > Crawl Depth
Pass criteria: All service/product pages at depth 2-3. Zero orphan pages among important content. Blog posts at depth 3-4 maximum.
Are there duplicate content issues?
Duplicate content confuses Google about which page to rank. It splits ranking signals across multiple URLs targeting the same query.
What to check:
- No two pages target the same primary keyword
- Parameter URLs (filters, sorts, pagination) are either canonicalized or noindexed
- WWW vs. non-WWW resolves to one version (301 redirect)
- HTTP vs. HTTPS resolves to one version (301 redirect)
- Trailing slash vs. non-trailing slash is consistent
Tool: Screaming Frog > Duplicate Content filter, or Sitebulb > Duplicate Content report
Pass criteria: Zero unintentional duplicate title tags. All parameter URLs handled via canonical or noindex.
Is structured data implemented correctly?
Structured data helps Google understand your content type and can enable rich results. In 2026, it also helps AI systems like Gemini and ChatGPT identify and cite your content.
What to check:
- Organization schema on every page (name, url, logo)
- BreadcrumbList schema matches visible breadcrumbs
- Article schema on blog posts (headline, datePublished, author)
- FAQ schema on pages with FAQ content
- No validation errors in Rich Results Test
- Schema matches visible page content (Google penalizes mismatches)
Tool: Google Rich Results Test, Schema Markup Validator
Pass criteria: Zero validation errors. All page types have appropriate schema. Organization schema present site-wide.
Tier 3: Performance and User Experience
Core Web Vitals are a confirmed Google ranking signal. Pages that pass all three thresholds at the 75th percentile of real user data receive a ranking advantage.
Do your pages pass Core Web Vitals?
The three metrics and their thresholds for 2026:
| Metric | What It Measures | Good Threshold | Common Failure Rate |
|---|---|---|---|
| LCP (Largest Contentful Paint) | Loading speed | Under 2.5 seconds | ~40% of sites fail |
| INP (Interaction to Next Paint) | Responsiveness | Under 200 milliseconds | ~43% of sites fail |
| CLS (Cumulative Layout Shift) | Visual stability | Under 0.1 | ~25% of sites fail |
INP replaced FID (First Input Delay) in March 2024. It measures the full lifecycle of user interactions, not just input delay. It is currently the most commonly failed Core Web Vital.
What to check:
- CrUX field data in GSC (not just lab scores from PageSpeed Insights)
- Check by page type, not just homepage
- Mobile scores specifically (Google uses mobile data for ranking)
- Identify which metric is failing and on which page templates
Tool: Google Search Console > Core Web Vitals report, PageSpeed Insights (field data section)
Pass criteria: All three metrics rated “good” at the 75th percentile in CrUX field data. If field data is unavailable (low traffic), lab data under thresholds is acceptable as a proxy.
Is your site mobile-friendly?
Google uses mobile-first indexing. The mobile version of your site is what Google crawls and indexes, regardless of where your traffic comes from.
What to check:
- Content is identical on mobile and desktop (no hidden content on mobile)
- Text is readable without zooming (minimum 16px font size)
- Tap targets are at least 48x48px with adequate spacing
- No horizontal scrolling required
- Images are responsive and do not overflow containers
- Mobile menu is functional and accessible
Tool: Chrome DevTools device emulation, GSC Mobile Usability report
Pass criteria: Zero mobile usability errors in GSC. All content accessible on a 375px viewport.
Are third-party scripts under control?
Third-party scripts (analytics, chat widgets, ad tags, A/B testing tools) are the most common cause of poor INP and LCP scores. Most sites load 15-30 third-party scripts without auditing their performance impact.
What to check:
- Total number of third-party requests on page load
- Which scripts block rendering (loaded in
<head>withoutdeferorasync) - Total JavaScript execution time on mobile
- Whether any scripts can be removed entirely
- Whether remaining scripts can be deferred or loaded after user interaction
Tool: Chrome DevTools > Network tab (filter by third-party), WebPageTest waterfall
Pass criteria: No render-blocking third-party scripts. Total third-party JS execution under 500ms on mobile. Every script has a documented business justification.
How to prioritize your audit findings
After running through this technical SEO audit checklist, you will likely have dozens of issues. Do not try to fix everything at once. Use this prioritization framework:
| Priority | Fix If… | Example |
|---|---|---|
| P0 (Fix today) | Pages are completely inaccessible to Google | robots.txt blocking entire site, server returning 500 errors |
| P1 (Fix this week) | Important pages are not being indexed | Canonical errors on service pages, noindex on key content |
| P2 (Fix this sprint) | Site structure is hurting rankings | Orphan pages, deep crawl depth, duplicate content |
| P3 (Fix this month) | Performance is below thresholds | CWV failures, slow server response, unoptimized images |
| P4 (Backlog) | Nice to have, minimal traffic impact | Minor schema warnings, non-critical redirect chains |
The key insight: a P0 issue on 10 pages matters more than a P4 issue on 10,000 pages. Prioritize by impact on traffic, not by volume of issues found.
Run your audit in this order
Start with Tier 1 and work down. Do not skip ahead to performance optimization if you have crawlability problems. The sequence matters because each tier depends on the one above it.
- Crawl your site with Screaming Frog or Sitebulb
- Cross-reference with Google Search Console data
- Check robots.txt and canonical tags first
- Review indexation status and fix any blocks
- Audit site architecture and internal linking
- Check for duplicate content
- Validate structured data
- Measure Core Web Vitals with field data
- Audit third-party scripts
- Prioritize findings using the P0-P4 framework
- Create implementation tickets for your dev team
- Re-crawl after fixes are deployed to verify resolution
Frequently asked questions
How often should you run a technical SEO audit?
Run a full audit quarterly for sites under 10K pages. For larger sites or those publishing frequently, run crawl checks monthly and a full audit every 6-8 weeks. Always run one before and after a site migration.
What tools do you need for a technical SEO audit?
At minimum: Screaming Frog or Sitebulb for crawling, Google Search Console for indexation data, and PageSpeed Insights or CrUX for Core Web Vitals field data. Server log access is valuable but not required for smaller sites.
How long does a technical SEO audit take?
A thorough audit of a 5,000-page site takes 2-3 weeks including crawl time, analysis, and report writing. A 500-page site can be audited in 3-5 days. The crawl itself is fast. The analysis and prioritization is what takes time.