Quick answer: A technical SEO audit checks the foundation your rankings stand on: crawlability, indexation, site speed, mobile usability, HTTPS security, structured data, and duplicate content issues. This 2026 checklist gives you 20 checks you can run with free tools, ordered by impact, so you fix what moves rankings first and stop guessing about hidden technical problems.
Great content cannot rank if search engines cannot reach it, read it, or trust it. Technical SEO is the plumbing of your website: invisible when it works, catastrophic when it breaks. A single misconfigured setting can block your entire site from Google, while slow load times quietly bleed visitors every day.
This checklist walks through 20 technical checks in order of impact. Run them with free tools like Google Search Console, PageSpeed Insights, and Screaming Frog free tier. Fix the failures at the top first, because a crawl blocking issue outweighs every other optimization combined.
Crawlability and Indexation
Before anything else, confirm Google can access your site. Check your robots.txt file for accidental blocks, especially broad disallow rules that took down whole sections. Then review the Indexing report in Google Search Console for pages that are crawled but not indexed, which often signals thin content or crawl budget waste.
Submit an XML sitemap and keep it clean: only live, indexable, canonical URLs. A sitemap full of redirects and error pages teaches Google to ignore it. Also check that important pages are not buried more than three clicks from the homepage, because deep pages get crawled less often.
Site Speed and Performance
Run your key pages through PageSpeed Insights and note the Core Web Vitals scores. The usual culprits are uncompressed images, render blocking scripts, and slow server response. Compress images, defer non critical JavaScript, enable browser caching, and consider a content delivery network if your audience is spread out.
Speed work has a clear order of operations. Fix server response time first, then images, then scripts. A page that loads in under 2.5 seconds on mobile keeps both visitors and rankings happy. If your site suddenly dropped in rankings, check if your website is penalized by Google before assuming it is a speed issue, since penalties and technical problems look similar from the outside.
Mobile Usability
Open your site on a real phone, not just a desktop preview. Tap every menu item, fill out every form, and read three full articles. Common mobile failures include text too small to read, buttons too close together, content wider than the screen, and popups that cover the whole page.
Google indexes the mobile version of your site first, so a page that works on desktop but breaks on mobile is a page that barely exists. The Mobile Usability report in Search Console lists issues Google found, but your own eyes catch problems the report misses.
Security and HTTPS
Every page must load over HTTPS with a valid certificate. Mixed content warnings, where a secure page loads insecure images or scripts, erode trust and can trigger browser warnings. Check that all internal links point to HTTPS versions and that old HTTP URLs redirect properly with 301 redirects.
While you are here, confirm your site is not flagged for malware or phishing in Search Console. A hacked site can lose all rankings overnight, and the cleanup is far harder than prevention.
Duplicate Content and Canonicalization
Duplicate content splits ranking signals across multiple URLs. Common causes include www and non www versions both accessible, HTTP and HTTPS both live, URL parameters creating endless variations, and printer friendly or AMP duplicates.
The fix is canonical tags pointing every duplicate to the preferred URL, plus 301 redirects for the big structural duplicates. Every indexable page should have a self referencing canonical tag. This is one of the most skipped items on any new website SEO checklist, and one of the most damaging when missed.
Structured Data and Rendering
Validate your schema markup with a rich results test and fix every error. Broken schema is worse than no schema, because errors can disqualify you from rich results entirely. Pay special attention to FAQ, Article, and Organization markup.
Also verify that Google renders your pages the way visitors see them. Sites built heavily on JavaScript sometimes show Google a blank or partial page. Use the URL inspection tool to see the rendered HTML Google actually indexes.
The 20 Check Technical Audit List
Run these in order. Stop and fix failures before moving on.
- Robots.txt review. Confirm no important pages or sections are blocked.
- Indexation status. Check Search Console for excluded pages and fix the causes.
- XML sitemap. Clean, submitted, and containing only indexable canonical URLs.
- HTTPS everywhere. Valid certificate, no mixed content, HTTP redirects to HTTPS.
- Mobile usability. Test on a real phone; fix tap target and readability issues.
- Core Web Vitals. Largest Contentful Paint under 2.5 seconds on mobile.
- Server response time. Time to first byte under 600 milliseconds.
- Image optimization. Compressed, properly sized, modern formats where possible.
- Render blocking resources. Defer or remove scripts that delay first paint.
- Canonical tags. Present and correct on every indexable page.
- Duplicate content. No www, HTTP, or parameter duplicates indexed.
- Redirect chains. No chains longer than one hop; no redirect loops.
- Broken links. No internal 404s; fix or redirect them.
- 404 handling. Custom 404 page that helps visitors, not a dead end.
- Site structure depth. Important pages within three clicks of the homepage.
- Orphan pages. Every valuable page has at least one internal link pointing to it.
- Schema markup. Valid, error free, and matched to the page type.
- JavaScript rendering. Google sees the same content visitors see.
- Hreflang tags. Correct on every multilingual or multi region site.
- Security issues. No malware, phishing, or hacked content flags in Search Console.
Frequently Asked Questions
How often should I run a technical SEO audit?
Run a full audit twice a year and a light check quarterly. Also audit after any redesign, migration, or platform change, since those are when technical disasters happen. Set up Search Console email alerts so Google tells you about new issues between audits.
Can I do a technical audit without paid tools?
Yes. Google Search Console, PageSpeed Insights, the rich results test, and the free tier of Screaming Frog cover about 90 percent of technical checks. Paid crawlers help on very large sites, but small sites can audit thoroughly for free.
What is the most common technical SEO issue?
Accidental blocking and indexation problems top the list: a staging noindex tag left on after launch, a robots.txt disallow copied from development, or thousands of thin parameter URLs eating crawl budget. Always check crawl access before anything else.
How long does it take to see results after technical fixes?
Crawl blocking fixes can improve visibility within days once Google recrawls. Speed and usability improvements typically show impact within a few weeks. Our guide on how long SEO takes to work breaks down realistic timelines for every type of fix.
Should I fix technical SEO before building content?
Fix blocking issues first, then build content and fix the rest in parallel. There is no reason to delay publishing while you perfect image compression, but there is every reason to delay if Google cannot crawl your site at all.
Get a Professional Technical Audit
Some technical issues hide where free tools cannot see them: crawl traps, indexation gaps, and speed killers buried in code. At SEO Spider, our SEO services include deep technical audits that catch what checklists miss. Talk to us and get a clear, prioritized fix list for your site.