A technical SEO audit checks the parts of your site that search engines and AI crawlers rely on but visitors never see — crawling and indexing, site architecture, speed and Core Web Vitals, mobile, HTTPS, structured data, and duplicate content — then prioritizes the fixes by impact. This is the technical SEO audit checklist we actually run, grouped by category, with the tool for each check and a note on why it matters.
Work it top to bottom and you’ll catch the issues quietly holding your rankings back — including a 2026 layer most older checklists miss: whether AI crawlers can access your content at all.
The short version
- Start with crawling and indexing — nothing else matters if pages can’t be found
- Check architecture, speed, mobile, and HTTPS in that order of blast radius
- Validate structured data and resolve duplicate content with canonicals
- Confirm AI crawlers (like GPTBot) can reach the content you want cited
- Prioritize every fix by impact — don’t treat all issues as equal
Tools you’ll need
You can run a thorough audit with a small, mostly free toolkit: Google Search Console for indexing and coverage, a crawler like Screaming Frog for site-wide issues, PageSpeed Insights for Core Web Vitals, and a site-audit tool (Sitebulb, Semrush, or similar) to tie it together. You don’t need all of them — but Search Console and a crawler are non-negotiable.
1. Crawling and indexing
This is the foundation. If search engines can’t crawl and index a page, nothing else you do to it counts. Check that your robots.txt isn’t blocking anything important, that your XML sitemap is present and lists your real pages, and that Search Console’s coverage report isn’t full of unexpected exclusions. Watch for index bloat — thin or duplicate pages clogging the index — and confirm no critical page is accidentally set to noindex.
2. Site architecture and internal linking
A good structure keeps important pages a few clicks from the homepage and uses internal links to pass authority where it’s needed. Look for orphan pages with no internal links in, overly deep pages buried too far down, and broken internal links or redirect chains. Clean architecture helps both crawlers and users — and it’s where on-page and technical work meet, as our guide on technical vs on-page SEO explains.
Audit in order of blast radius
- Crawl & indexConfirm pages can be found and indexed at all — the issue that invalidates everything downstream.
- Architecture & speedFix structure, broken links, slow loads and shaky Core Web Vitals that drag down whole sections.
- Markup & duplicatesValidate schema and resolve duplicate content with canonicals — the precision fixes that sharpen everything else.
3. Page speed and Core Web Vitals
Speed is both a ranking factor and a conversion factor. Run your key page templates through PageSpeed Insights and check the three Core Web Vitals — loading, interactivity, and visual stability. Common wins: compress and properly size images, cut unused scripts, and lean on caching. Fix the templates (home, service, product, blog) rather than chasing individual pages, since templates repeat across the whole site.
4. Mobile-friendliness
Google indexes the mobile version of your site, so the mobile experience is the experience that gets ranked. Confirm your pages render cleanly on a phone, tap targets aren’t cramped, text is readable without zooming, and nothing important is hidden or broken on small screens. A site that’s fine on desktop but awkward on mobile is leaving rankings on the table.
5. HTTPS and security
Every page should load over HTTPS with a valid certificate, and HTTP versions should redirect cleanly to the secure ones. Check for mixed content — secure pages pulling in insecure resources — which quietly undermines trust signals. This one is usually quick to verify and important to get completely right.
6. Structured data and schema
Structured data helps search engines understand your content and can unlock rich results. Validate that the schema you’ve implemented is error-free and matches what’s actually on the page — mismatched or invalid markup does more harm than none. Prioritize the schema types that fit your content, like Article, LocalBusiness, FAQ, or Product, and keep the values consistent with your visible content.
7. Duplicate content and canonicals
Duplicate or near-duplicate pages split your signals and waste crawl budget. Use canonical tags to point variations at the preferred version, watch for parameter-based duplicates and www/non-www or trailing-slash inconsistencies, and consolidate pages that overlap heavily. If you run many location pages, this is where you make sure they’re genuinely distinct — our local landing page blueprint covers how to avoid the doorway-page trap.
A technical audit isn’t about fixing everything you find — it’s about fixing the few things that are actually costing you rankings, in the right order.
8. Crawlability for AI search
This is the 2026 addition older checklists skip. AI answer engines use their own crawlers, and if your robots.txt or firewall blocks them, you can be invisible in AI Overviews and chat answers even while you rank fine in classic search. Decide deliberately whether to allow crawlers like GPTBot, confirm your content is accessible to them, and make sure your most citable pages aren’t walled off. The same clean structure and clear answers that help Google help AI engines cite you too.
How to prioritize fixes by impact
An audit that lists a hundred issues with no priority is just anxiety in a spreadsheet. Rank every finding by blast radius: anything blocking crawling or indexing comes first, then issues affecting many pages (template speed, architecture, sitewide duplicates), then page-level refinements. Fix the few things that move rankings before the many that barely register.
A useful habit is to score each finding on two axes — how many pages it touches and how badly it hurts — and start where both are high. A single robots.txt mistake blocking a whole section outranks a dozen cosmetic schema warnings every time. That discipline turns an overwhelming list into a short, ordered worklist you can actually finish.
Score every finding by impact
Fix in this priority
✓ Fix first
- Pages blocked from crawling or indexing
- Broken sitemaps and robots.txt mistakes
- Sitewide speed and architecture problems
- HTTPS and mobile-rendering failures
✕ Can wait
- Minor schema warnings that don’t break results
- One-off page tweaks with tiny reach
- Cosmetic issues with no ranking impact
- Edge-case duplicates behind a canonical already
Frequently asked questions
What is included in a technical SEO audit? At minimum: crawling and indexing, site architecture and internal linking, page speed and Core Web Vitals, mobile-friendliness, HTTPS and security, structured data, and duplicate-content handling with canonicals. In 2026, add a check on whether AI crawlers can access the content you want cited.
How do I do a technical SEO audit? Work category by category with Search Console and a crawler. Confirm pages can be crawled and indexed, check architecture and internal links, test template speed and Core Web Vitals, verify mobile and HTTPS, validate schema, resolve duplicates, then prioritize every finding by impact.
Is there a free technical SEO audit tool? Yes — Google Search Console and PageSpeed Insights are free and cover a lot, and crawlers like Screaming Frog have a free tier for smaller sites. You can run a solid audit before paying for anything.
How often should I run one? Run a full audit a couple of times a year and a focused one after any major site change — a redesign, migration, or platform switch. Regular checks keep small issues from compounding into a traffic drop.
Do I need to fix everything the audit finds? No. An audit surfaces far more than is worth acting on. Fix what’s blocking crawling or indexing first, then sitewide issues, then page-level refinements. Many minor warnings can safely wait or be ignored.
Make the audit a habit
A technical SEO audit isn’t a one-time cleanup — run it on a schedule and after any big site change, so small issues never compound into a traffic drop. If you ever do take a hit, our guide on recovering from a Google update starts with the same diagnostic mindset. And if you want to watch practitioners run a live audit — the checks they hit first and why — come learn it at our conference. It’s no theory, just the plays that work, and 2027 tickets are open now.