How to Audit Your Website's Technical SEO in 30 Minutes

Technical SEO gets overcomplicated. Entire agencies sell "comprehensive audits" that run to 80 pages and tell you your H2 tags are out of order. That is not helpful. What you actually need is a focused review of the things that stop Google from crawling, indexing, and ranking your pages properly. This checklist gets you there in 30 minutes.

We use a version of this process with every new partner who comes to us at ASPIRED Digital's SEO service. It catches the issues that actually suppress rankings, not the theoretical ones that fill reports.

Before You Start: Tools You Need Open

Have these ready in separate tabs:

• Google Search Console (verified for your site)
• PageSpeed Insights or Chrome DevTools Lighthouse
• Your site's robots.txt file (yourdomain.com/robots.txt)
• Your XML sitemap (usually yourdomain.com/sitemap.xml)
• A crawl tool if you have one. Screaming Frog's free tier covers up to 500 URLs

Step 1: Check Crawlability (5 Minutes)

If Google cannot crawl your pages, nothing else matters. Start here.

Robots.txt Review

Open yourdomain.com/robots.txt in your browser. You are looking for three things:

• Accidental disallows. Is anything blocked that should not be? A surprisingly common mistake is blocking /wp-content/uploads/ or entire subdirectories that contain important pages. If you see Disallow: / without it being targeted at a specific bot, your entire site is blocked from crawling.
• Missing sitemap reference. Your robots.txt should contain a line pointing to your XML sitemap: Sitemap: https://yourdomain.com/sitemap.xml
• AI bot access. If you want to appear in AI search results, check you are not blocking GPTBot, ClaudeBot, or PerplexityBot. This is increasingly relevant for generative engine optimisation.

Crawl Errors in Search Console

In Google Search Console, go to Pages (under Indexing). Look at the "Why pages aren't indexed" section. The errors that matter most:

• Crawled, currently not indexed. Google saw your page and chose not to index it. This usually signals thin content or quality issues.
• Discovered, currently not indexed. Google knows the URL exists but has not bothered to crawl it yet. Often a crawl budget problem on larger sites.
• Blocked by robots.txt. Self-explanatory. Fix your robots.txt.
• Server errors (5xx). Your server is failing when Googlebot visits. This needs immediate attention.

Step 2: Verify Indexation (5 Minutes)

Crawling and indexing are different things. Google can crawl a page without indexing it.

Site: Search Operator

Type site:yourdomain.com into Google. Compare the number of results to how many pages your site actually has. A big gap in either direction is a red flag. Fewer indexed pages than expected means content is not getting indexed. More indexed pages than expected often means duplicate content, parameter URLs, or staging environments leaking into the index.

Canonical Tag Check

Pick five of your most important pages. View source and search for rel="canonical". Each page should have a canonical tag pointing to itself (the self-referencing canonical). If your canonical tags point to different URLs, or if they are missing entirely, Google might be consolidating your pages in unexpected ways.

Common canonical mistakes:

• HTTP canonical on an HTTPS page (or vice versa)
• Trailing slash inconsistencies (yourdomain.com/page vs yourdomain.com/page/)
• Canonical pointing to a paginated page instead of the main page
• Multiple canonical tags on the same page (plugins sometimes cause this)

Step 3: Core Web Vitals (5 Minutes)

Google uses Core Web Vitals as a ranking signal. The three metrics that matter:

Largest Contentful Paint (LCP)

This measures how quickly the biggest visible element loads. Target: under 2.5 seconds. If your LCP is slow, the culprit is almost always an unoptimised hero image or a render-blocking resource. Convert images to WebP or AVIF format. Preload your LCP image with <link rel="preload">.

Interaction to Next Paint (INP)

INP replaced First Input Delay in March 2024. It measures responsiveness across the entire page session, not just the first interaction. Target: under 200 milliseconds. Heavy JavaScript is the usual cause of poor INP scores. Third-party scripts like chat widgets and analytics tags are frequent offenders.

Cumulative Layout Shift (CLS)

CLS measures how much the page layout shifts unexpectedly while loading. Target: under 0.1. The fix is almost always adding explicit width and height attributes to images and embeds so the browser reserves space before the content loads.

Run your homepage and your highest-traffic landing page through PageSpeed Insights. Focus on the field data (real user metrics from the Chrome User Experience Report), not the lab data. Field data reflects what actual visitors experience.

Step 4: Site Structure and Internal Linking (5 Minutes)

Google follows links to discover and understand your site. A flat, well-linked structure helps every page get crawled and passes authority where it needs to go.

Click Depth

No important page should be more than three clicks from your homepage. If a page is buried five levels deep, Google treats it as less important. Use your crawl tool to check maximum click depth, or manually navigate your site and count.

Orphan Pages

Pages with no internal links pointing to them are orphans. Google struggles to find them, and they receive no internal authority. Check your sitemap URLs against your crawl data. Any URL in the sitemap that was not discovered during the crawl is likely an orphan.

Internal Link Distribution

Your most commercially important pages should have the most internal links pointing to them. Open Screaming Frog's "Internal" tab, sort by "Unique Inlinks", and check whether your priority pages are near the top. If your blog posts have more internal links than your service pages, your link equity is flowing in the wrong direction.

Step 5: XML Sitemap Health (3 Minutes)

Your XML sitemap tells Google which URLs you consider important. Open it and check:

• Only indexable URLs. Every URL in your sitemap should return a 200 status code and should not have a noindex tag. Sitemaps containing 404s, redirects, or noindexed pages send mixed signals.
• No bloat. Do not include parameter URLs, paginated pages, or tag/category archives unless they carry unique content.
• Sitemap is submitted in Search Console. Go to Sitemaps in Search Console and confirm your sitemap is submitted and shows a recent successful fetch.
• Size limits. Each sitemap file can contain up to 50,000 URLs. If your site is larger, you need a sitemap index file that references multiple sitemaps.

Step 6: HTTPS, Redirects, and Duplicate Content (5 Minutes)

HTTPS Everywhere

Type your domain with HTTP (not HTTPS) into your browser. It should redirect to HTTPS. Do the same with the www vs non-www version. All four variations (http://domain.com, http://www.domain.com, https://domain.com, https://www.domain.com) should resolve to a single version via 301 redirects.

Redirect Chains

A redirect chain is when URL A redirects to URL B, which redirects to URL C. Each hop loses a small amount of link equity and slows down crawling. Use your crawl tool to find chains longer than one hop and fix them so they point directly to the final destination.

Duplicate Content

Common sources of duplicate content:

• HTTP and HTTPS versions both accessible
• www and non-www versions both accessible
• Trailing slash and non-trailing slash versions both returning 200
• URL parameters creating multiple versions of the same page (e.g., ?sort=price)
• Print-friendly or AMP versions without canonical tags

Step 7: Quick Wins to Fix First (2 Minutes to Prioritise)

After running through this checklist, you will have a list of issues. Prioritise them in this order:

• First: Anything blocking crawling or indexing (robots.txt errors, noindex on important pages, server errors)
• Second: Canonical and duplicate content issues
• Third: Core Web Vitals failures
• Fourth: Internal linking and site structure improvements
• Fifth: Sitemap cleanup

The first two categories can completely prevent pages from ranking. The rest improve performance on pages that are already indexed. Fix the blockers before optimising the details.

If your audit reveals deeper problems than a 30-minute check can solve, you may want to look into a professional SEO audit. We do these regularly for partners across the UK, Europe, and the Middle East, and the technical layer is always where we start.

Frequently Asked Questions

How often should I run a technical SEO audit?

Run this quick checklist monthly. Do a deeper audit with a full crawl tool quarterly. Also run it after any major site change: CMS migration, redesign, new plugin installations, or domain changes. Problems introduced during site updates are the most common source of sudden ranking drops.

Can I do a technical SEO audit without paid tools?

Yes. Google Search Console is free and gives you crawl errors, indexation status, and Core Web Vitals data. PageSpeed Insights is free. Screaming Frog's free version crawls up to 500 URLs. For most small to mid-sized sites, that is more than enough. Paid tools like Ahrefs and Sitebulb add convenience and depth, but the fundamentals are all available at no cost.

What is the difference between a technical SEO audit and a full SEO audit?

A technical audit focuses on how well search engines can crawl, index, and render your site. A full SEO audit also covers content quality, keyword targeting, backlink profile, competitor analysis, and on-page optimisation. Technical SEO is the foundation. If it is broken, content and link building work cannot perform at their best. Start with the technical layer, then build on it.

Do Core Web Vitals really affect rankings?

Google confirmed Core Web Vitals as a ranking signal in 2021. The effect is real but modest compared to content relevance and backlinks. Think of it as a tiebreaker: when two pages are equally relevant and equally authoritative, the faster one wins. Where it matters most is user experience. A slow, janky site loses visitors regardless of its ranking position.