Skip to content
Searchpedia SEO field notes Callum Bennett Callum

Site ops

Technical SEO Audit Services

Most technical SEO audits I see try to do too much. I now start with crawlability and indexation before touching page speed or metadata.

Beginner5 min readUpdated 2026-07-27Notes by Callum Bennett

Start here

  • Start with a crawl using Screaming Frog to see every URL's status code, metadata, and redirect chain.
  • Check Google Search Console's index coverage report before touching anything else.
  • Prioritise issues by impact: indexation blockers first, then duplicate content, then performance.
  • Re-run audits quarterly because sites change constantly with new pages, plugins, and redirects.
  • Do not skip mobile usability and Core Web Vitals even if your site is mostly desktop traffic.

Plain-English take

A [technical SEO](/technical-seo/) audit is not about your keywords or backlinks. It is about whether Googlebot can reach every important page, understand what it finds, and index it without creating noise. The audit checks crawlability — can the crawler follow links without hitting dead ends or server errors. It checks indexation — are the right pages in the index and are low-value URLs getting in the way. It also looks at page speed, mobile usability, structured data, internal linking, [duplicate content](/duplicate-content/), redirects, and metadata. I run a crawl with Screaming Frog to get a full picture of URL statuses and metadata. I cross-reference that with Google Search Console for index coverage and crawl errors. For page speed I test a handful of key pages with PageSpeed Insights. I check robots.txt and XML sitemaps to make sure nothing is blocking the wrong content. Then I look at [canonical tags](/canonical-tags/) and [hreflang tags](/hreflang-tags/) if the site has multiple language versions. The output is a prioritised list of fixes: what breaks indexation comes first, then performance, then everything else.

When it actually matters

A technical SEO audit matters most after a site migration. When you change domains, CMS, or URL structure, you can break everything overnight. I have seen a client lose 60% of organic traffic in one week because they forgot the 301 mapping. Run an audit immediately after launch. It also matters before a major content push. There is no point publishing 50 new articles if Google cannot index them because of a rogue robots.txt disallow. When traffic drops unexpectedly, a technical issue is often the culprit. I once spent two weeks rewriting content only to find a stray noindex directive on the blog archive. A quarterly audit catches these things. For large sites with 50,000+ pages, crawl budget becomes relevant. If Googlebot wastes time on thin pages or infinite parameter URLs, your important pages get less attention. An audit shows you which pages to noindex and which to consolidate. Mobile usability is now a ranking factor, so I always check it even if most traffic comes from desktop. [Core Web Vitals](/core-web-vitals/) matter too, but I treat them as a secondary priority behind indexation.

What I got wrong

I used to treat technical SEO audits as a one-time checklist. Run it once, fix the issues, move on. But sites change constantly — new pages, plugins, redirects, changes to the CMS. An audit is only a snapshot. I now schedule quarterly audits for every client site. I also focused too much on page speed and metadata early on, ignoring crawl budget and indexation. You can have the fastest pages in your industry, but if Google is not crawling them because of a bad robots.txt or too many low-value parameter URLs, none of that speed matters. I remember one ecommerce site with 50,000 products. Page speed was fine, but Google was only indexing 12% of them because every filter variation created a duplicate URL with a rel="canonical" pointing to the wrong page. Indexation had to come first. Another mistake was not separating issues by impact. I would list all 200 problems in a spreadsheet. Developers would get overwhelmed and fix the easy ones first — like missing meta descriptions — while the crawl issue that mattered most sat for months. I now prioritise by indexation impact first, then user experience, then everything else.

Next step

Quick answers

How often should I run a technical SEO audit?

I recommend quarterly for most sites. Monthly if you are migrating, launching a new section, or deploying new code frequently. A lot changes with plugins and redirects between audits.

What tools do I need for a technical SEO audit?

You need a crawler like Screaming Frog or Sitebulb, Google Search Console for index coverage and crawl errors, and PageSpeed Insights for performance. Server logs help if you can get them.

Can a technical SEO audit fix traffic drops?

It depends on the drop. If it is from a technical issue like a broken robots.txt or a canonical misconfiguration, yes. If the drop is from algorithm changes or competition, the audit helps you rule out technical causes first.

Sources

Primary documentation is linked directly. Anything commercial is marked nofollow.

Notes from Callum Bennett.