A technical SEO audit is a health check on everything that determines whether search engines can find, crawl, understand, and rank your website. Content wins rankings, but technical problems — blocked pages, broken links, slow loads, missing structured data — silently cap what your content can achieve.
This guide walks through a complete audit step by step, in the order a professional would run it. You can do most of it with free tools (Google Search Console, PageSpeed Insights) plus one crawler. No prior technical background required — just patience and a spreadsheet.
Before You Start: Set Up Your Toolkit
You need three things:
- A crawler — software that visits your site like Googlebot does and reports every issue it finds. The classic choice is Screaming Frog SEO Spider, a desktop crawler with a free version (up to 500 URLs) and a paid annual licence for unlimited crawling and advanced features like JavaScript rendering and Google Search Console integration. Cloud-based alternatives include the site audit tools in Semrush and Ahrefs.
— Download Screaming Frog SEO Spider (free for up to 500 URLs).
- Google Search Console — free, and the only source of truth for how Google actually sees your site: indexed pages, crawl errors, and Core Web Vitals data.
- PageSpeed Insights — Google’s free speed tester, which reports lab and field data for any URL.
Crawl your full site first, then work through the steps below using the crawl data alongside Search Console.
Step 1: Check Crawlability (robots.txt)
Before anything else, confirm Googlebot is actually allowed to crawl your site. Visit yourdomain.com/robots.txt and check:
- Is there a
Disallow: /rule blocking everything? (Surprisingly common after site launches — staging settings carried into production.) - Are important sections (blog, product categories) accidentally disallowed?
- Is the file returning a 200 status, not a 404 or server error?
One misplaced disallow can deindex an entire site section overnight. This 30-second check belongs at the top of every audit.
Step 2: Check Your XML Sitemap
Your sitemap is the list of URLs you’re asking Google to crawl. Verify:
- It’s submitted in Google Search Console (Sitemaps report).
- It contains only indexable, canonical, 200-status URLs — no redirects, no 404s, no noindexed pages.
- It’s under 50,000 URLs and 50MB uncompressed (split into multiple sitemaps if larger).
- It was updated recently — a stale sitemap signals a neglected site.
Most CMS platforms (WordPress with Rank Math or Yoast, Shopify) generate sitemaps automatically, but they still deserve a manual review.
Step 3: Review Indexation
Now compare what should be indexed with what is indexed:
- In Search Console’s Pages report, look for “Discovered — currently not indexed” and “Crawled — currently not indexed.” Some of this is normal (Google doesn’t index everything), but large numbers point to thin content or crawl budget issues.
- Search
site:yourdomain.comon Google for a rough indexed-page count and compare it against your sitemap total. Big gaps need investigation. - Check for accidental
noindextags on important pages — a common leftover from development.
If thin or duplicate pages are eating your crawl budget, consider consolidating or noindexing them rather than letting Google decide.
Step 4: Audit Site Speed and Core Web Vitals
Speed is a ranking factor and a conversion factor. Run your key templates (homepage, a blog post, a product/category page) through PageSpeed Insights and check Google’s three Core Web Vitals:
| Metric | Measures | “Good” threshold |
|---|---|---|
| LCP (Largest Contentful Paint) | Loading speed | ≤ 2.5 seconds |
| INP (Interaction to Next Paint) | Responsiveness | ≤ 200 milliseconds |
| CLS (Cumulative Layout Shift) | Visual stability | ≤ 0.1 |
Google assesses these at the 75th percentile of real user visits, split by mobile and desktop — so test mobile first, since most traffic is mobile. Common fixes: compress and properly size images, remove render-blocking scripts, set explicit image dimensions (prevents layout shift), and upgrade slow hosting. WordPress users should read our WordPress speed optimization guide for platform-specific fixes.
Step 5: Verify Mobile-Friendliness
Google indexes the mobile version of your site first (mobile-first indexing), so the mobile experience is the SEO experience. Check:
- Content parity: the mobile version must contain the same content, headings, and structured data as desktop. (Sites that strip content on mobile lose rankings for it.)
- Tap targets and font sizes are usable on small screens.
- No intrusive interstitials covering content on mobile.
- Viewport meta tag is set correctly.
Test on a real phone, not just a resized desktop browser — emulators miss touch and performance issues.
Step 6: Confirm HTTPS Everywhere
Every page should load over HTTPS with a valid certificate. In your crawl, look for:
- HTTP URLs that don’t redirect to HTTPS.
- Mixed content: HTTPS pages loading images, scripts, or stylesheets over HTTP (browsers block or warn on these).
- Certificate expiry dates and chain issues.
If you migrated from HTTP to HTTPS, verify every old URL 301-redirects to its HTTPS equivalent — don’t leave redirect chains.
Step 7: Validate Structured Data
Structured data (schema markup) helps Google understand your content and can earn rich results — star ratings, FAQ dropdowns, product prices — in the search results. Check:
- Valid markup on eligible page types: Article on blog posts, Product with offers and reviews on product pages, FAQPage where appropriate, BreadcrumbList sitewide.
- Test with Google’s Rich Results Test; fix errors and warnings.
- Markup matches visible content — marking up content users can’t see violates Google’s guidelines.
Structured data doesn’t directly boost rankings, but rich results raise click-through rates, which is often the cheaper win.
Step 8: Fix Broken Links and Redirect Chains
From your crawl export:
- 404s: Fix internal links pointing to dead pages — either restore the page, link to the closest live equivalent, or remove the link. Also check Search Console for external 404s worth redirecting.
- Redirect chains: A → B → C → D chains waste crawl budget and dilute link equity. Update links to point directly at the final destination.
- Redirect loops: A → B → A. These are emergencies — fix immediately.
Aim for zero internal 404s. It’s one of the simplest trust signals you can send both users and crawlers.
Step 9: Resolve Duplicate Content and Canonical Issues
Duplicate content confuses Google about which page to rank. Look for:
- HTTP vs HTTPS, www vs non-www, and trailing-slash variants all resolving instead of redirecting to one canonical version.
- Printer-friendly, tag, and parameter URLs (
?sort=price) creating duplicate copies — handle with canonical tags or parameter settings in Search Console. - Every page should have a self-referencing canonical tag pointing to its preferred URL.
- Near-duplicate pages (thin location pages, duplicated product descriptions) should be consolidated or differentiated.
Step 10: Review Internal Linking and Site Architecture
Internal links distribute authority and guide crawlers. In your crawl data:
- Important pages should be reachable within 3 clicks of the homepage.
- Orphan pages (no internal links pointing to them) are nearly invisible — link to them or remove them.
- Use descriptive anchor text; “click here” tells Google nothing.
- Check that your most-linked pages align with your most important pages — if not, your architecture is working against your strategy.
Step 11: Prioritize and Report
An audit that finds 200 issues and fixes none is worthless. Score every issue by impact × effort:
- High impact, low effort first: robots.txt blocks, noindex errors, redirect loops, broken key pages.
- High impact, medium effort: Core Web Vitals failures, mass duplicate content, structured data gaps.
- Everything else in descending order.
Document before/after for each fix with dates — when rankings move three weeks later, you’ll want to know which change caused it. Track progress in Search Console and Google Analytics 4; re-crawl after fixes to confirm they’re resolved.
For ongoing monitoring, the audit tools in our best SEO tools for small business roundup and keyword research tools guide cover scheduled crawls and alerts.
FAQ
How often should I run a technical SEO audit?
A full audit quarterly, plus a quick crawl monthly or after any site change (redesign, migration, new template). Set up automated alerts in Search Console for indexing and Core Web Vitals issues between audits.
How long does a technical SEO audit take?
A small site (under 500 pages) takes a few hours with a crawler. A large ecommerce or publisher site can take several days, mostly in analysis and prioritization. The crawl itself is the fast part.
Can I do a technical SEO audit for free?
Yes, mostly. Google Search Console + PageSpeed Insights + Screaming Frog’s free tier (500 URLs) covers the essentials for small sites. Paid crawlers and suites add scale, scheduling, and historical tracking.
What’s the difference between a technical SEO audit and a content audit?
Technical audits check whether search engines can access and understand your site (crawling, speed, structure). Content audits evaluate the quality and performance of the content itself (thin pages, keyword targeting, engagement). You need both; this guide covers the technical side.
Will fixing technical issues improve my rankings?
Fixing blocking issues (accidental noindex, crawl blocks, severe speed problems) can produce fast, dramatic recoveries. Beyond that, technical SEO removes ceilings — it rarely creates rankings on its own, but bad technical health caps everything else you do.
