A technical SEO audit catches problems early by checking whether Google can crawl, index, understand and load the right pages before your enquiries vanish. The big checks are indexation, crawl access, redirects, speed, mobile rendering, duplicate URLs, internal links, schema, tracking and local signals. Boring? Yes. Business-saving? Also yes.
If your website has suddenly gone quiet, or your shiny new site is doing absolutely sod all, technical SEO is one of the first places to look. Not because it is glamorous. It is not. It is plumbing. But when the plumbing is blocked, no amount of pretty tiles will save the bathroom.
What a technical SEO audit actually checks
A technical SEO audit is not a magic report with 400 warnings designed to frighten you into a retainer. A useful audit answers one plain question: is your website making it easy for search engines and customers to reach the pages that make you money?
That means checking the foundations before arguing about blog topics, backlinks, or whether your homepage headline sounds exciting enough. If Google cannot crawl a page, index it, render it properly, or understand what it is about, that page is already fighting with one hand tied behind its back.
For small businesses, the best audit focuses on problems that affect leads. Your boiler repair page not being indexed matters. A harmless missing image alt tag on a 2019 blog post probably does not. Context matters, and this is where a lot of automated audits go wrong.
A proper technical SEO audit should separate real commercial risk from software noise. The goal is not a perfect score. The goal is a site that Google can process cleanly and customers can use without swearing at their phone.
Check whether Google can index the right pages
Start with indexation. Always. If Google has not indexed the page, that page cannot rank. Simple as that.
Use Google Search Console and inspect your most important URLs. Check your homepage, service pages, location pages, main category pages and any pages that regularly bring in enquiries. You are looking for pages that should be indexed but are missing, excluded, canonicalised elsewhere, blocked, or marked with a noindex tag.
Google’s own guide to crawling and indexing is worth reading if you want the official version, but the short version is this: Google must be able to discover, access, process and store a page before it can show it in search.
Watch for these early warning signs:
- Important pages showing as discovered but not indexed
- Service pages accidentally set to noindex after a redesign
- Pages indexed under odd URL versions with parameters or duplicates
- Old pages ranking instead of the new page you actually want customers to see
This is where new websites often fall over. A developer launches the site, everyone claps, then six weeks later someone notices half the important pages are not in Google. Lovely.
Check crawlability before you blame your content
Crawlability means search engines can move through your website without hitting unnecessary walls. If your site structure is messy, your robots.txt file is too aggressive, or your XML sitemap is full of rubbish, Google may waste time in the wrong places.
Run a crawl using a tool like Screaming Frog, Sitebulb, Ahrefs, Semrush, or another crawler you trust. You are not trying to admire a sea of coloured warnings. You are checking whether your important pages are easy to reach and whether your site is sending clear signals.
Your robots.txt file should not block key sections of the site. Your sitemap should include live, indexable URLs, not redirected pages, 404s, staging URLs, or random thin pages nobody cares about. Internal links should help crawlers find important pages within a few clicks, not bury them like treasure nobody asked for.
| Crawl check | What you want to see | What causes trouble |
|---|---|---|
| Robots.txt | Key pages allowed | Service areas blocked by mistake |
| XML sitemap | Live indexable URLs only | Redirects, 404s and noindex pages included |
| Crawl depth | Money pages reached quickly | Important pages buried too deep |
| Orphan pages | Few or none | Useful pages with no internal links |
If your crawl shows Google has to fight its way through junk, fix that before writing another 1,200-word blog post nobody will find.
Find broken pages, redirects and soft 404s
Broken pages are not just untidy. They waste crawl budget, annoy users and can quietly kill rankings when important URLs disappear after a redesign or site migration.
Check for 404 errors, 500 server errors, redirect chains, redirect loops and soft 404s. A soft 404 is a page that technically loads but behaves like a dead page, usually because it has little or no useful content. Google can spot that sort of nonsense.
The big danger is when old URLs with links, traffic, or rankings are deleted without proper redirects. This happens constantly when businesses get a new website. The designer builds a cleaner structure, the old pages vanish, and nobody maps the redirects properly. Then the business owner wonders why enquiries fell off a cliff.
A redirect should usually go from the old page to the closest relevant new page. Not everything should be dumped on the homepage. That is lazy and often unhelpful.
Check your top linked pages in Search Console or your SEO tool, then make sure any changed URLs are handled properly. If you have had a redesign recently, this is not optional. It is one of the first checks I would run.
Test speed and Core Web Vitals on real pages
Speed matters because slow websites lose people. Google also uses page experience signals, including Core Web Vitals, as part of its ranking systems, but do not get lost chasing perfect lab scores while your enquiry form takes six seconds to load.
Test your homepage, main service pages, product categories and key landing pages. Do not only test the homepage. A site can have a decent homepage score while the pages that actually make money are crawling along like they have had a big lunch.
Look at real-world data in Search Console where available, then test individual URLs with PageSpeed Insights or Lighthouse. Focus on common problems like oversized images, bloated themes, too many scripts, poor hosting, render-blocking files and third-party widgets that add very little apart from drag.
For WordPress sites, speed problems are often caused by plugin overload. One plugin for forms, one for popups, three for sliders, two for tracking, something installed in 2021 nobody remembers. Before long, the site is carrying more baggage than a budget airline check-in desk.
Speed fixes should be practical. Compress images. Remove what is not needed. Improve hosting if it is genuinely weak. Do not spend three days chasing a score improvement nobody will notice.
Check mobile rendering and JavaScript problems
Most local customers will hit your site on a phone. If your mobile experience is awkward, slow, broken, or stuffed with popups, you are making people work too hard. They will not write you a polite letter about it. They will leave.
Use your phone like a customer would. Search for your business, open the site, tap through to a service page, read the content, use the menu, click the phone number, submit the form and check whether anything breaks. This sounds obvious, which is probably why so many businesses do not do it.
Also check whether Google can render the content properly. JavaScript-heavy sites can hide important content, links, navigation or product information if built badly. Search Console’s URL inspection tool can show what Google sees, and a crawler with JavaScript rendering can help find bigger issues.
Common mobile and rendering problems include:
- Menus that do not open properly
- Buttons too close together
- Phone numbers that are not clickable
- Lazy-loaded content that search engines struggle to see
- Forms that fail on certain devices
- Cookie banners blocking the page like an overexcited bouncer
If your site looks fine on your office desktop but falls apart on a customer’s phone, that is not fine. That is lost money with nicer branding.
Fix duplicate URLs, canonicals and template bloat
Duplicate content is not always dramatic. You usually will not get some cartoon-style Google penalty. The real problem is confusion. If five URLs show the same or very similar content, Google has to decide which one matters. It might not pick the one you care about.
Check for duplicate titles, duplicate meta descriptions, repeated H1s, URL parameters, trailing slash variations, http and https versions, www and non-www versions, printer pages, filtered category pages and thin tag archives. E-commerce sites are especially good at creating thousands of near-identical URLs without anyone noticing until rankings start looking weird.
Canonical tags help tell search engines which version of a page is the main one. But they are often implemented badly. I have seen canonical tags pointing every page to the homepage, staging domains left in templates, and service pages canonicalised to irrelevant category pages. All absolute nonsense, and all avoidable.
Your page templates matter too. If every service page has the same title structure, same intro, same thin content and only swaps the town name, you are not building useful local pages. You are making a location sausage machine.
This is where technical SEO and on-page SEO overlap. The page needs to be technically clean, but it also needs to deserve a place in search results.
Audit internal links, schema and local SEO signals
Internal links are one of the easiest things to improve and one of the most ignored. They help users move around your site and help search engines understand which pages matter. If your main services are only linked from a dropdown menu, you are probably missing opportunities.
Look for pages with strong authority or traffic that could link to important commercial pages. Blog posts, guides, case studies and FAQs can all support your service pages if the links make sense. Do not force it. A useful internal link should feel like a helpful next step, not a random SEO trick stapled into a paragraph.
Structured data, also called schema, gives search engines extra context about your business, services, products, reviews, FAQs and local details. It will not rescue a poor website, but it can help search engines understand clean, well-structured pages more confidently.
For local businesses, check your name, address and phone number consistency, service area pages, contact details, embedded maps where appropriate and Google Business Profile signals. If local visibility is the priority, a focused local SEO audit is often more useful than a giant generic audit.
And if your Google listing is messy, incomplete, or pointing people to the wrong page, sorting your Google Business Profile optimisation should be part of the job. Local SEO is not just your website. It is the whole trail Google follows to decide whether you are a real, relevant business.
Set a technical SEO audit schedule that catches problems early
A technical SEO audit should not be a once-every-three-years panic event after leads have vanished. The best time to find a problem is before it turns into a revenue problem. That means setting a simple schedule and sticking to it.
You do not need to crawl your site every morning like a maniac. But you do need regular checks, especially after changes. New website launch? Audit. Major plugin update? Audit. Site migration? Audit. Big drop in enquiries? Definitely audit.
| When to check | What to focus on | Why it matters |
|---|---|---|
| Monthly | Indexation, errors, speed warnings | Catches small issues before they spread |
| After a redesign | Redirects, indexing, mobile, forms | Protects existing rankings and leads |
| After adding lots of pages | Crawl depth, duplication, sitemap quality | Stops site structure getting messy |
| After traffic drops | Search Console, rankings, technical errors | Finds whether the problem is technical |
| Quarterly | Full crawl and priority review | Keeps the site healthy without panic |
Use Search Console alerts, analytics data, rank tracking and crawler reports together. One tool rarely tells the whole story. If traffic drops but rankings are stable, the issue may be demand, tracking, seasonality, or conversion. If rankings drop and Search Console shows indexing errors, that is a different conversation.
The point is to build a habit. Technical SEO is easier when it is boring. Boring is good. Boring means the phone keeps ringing.
Prioritise fixes by money, not by panic
A technical SEO audit will always find issues. Always. The trick is knowing which ones matter. If an audit gives you 700 warnings but does not tell you what to fix first, it has failed you.
Prioritise problems based on commercial impact. A noindexed main service page is urgent. A missing meta description on an old blog post is not. A broken contact form is a five-alarm fire. A few oversized images on a low-traffic archive page can wait.
Sort findings into simple buckets: urgent, important, useful and ignore for now. Then fix the urgent items that block crawling, indexing, conversions, tracking or key page performance. After that, move to important improvements that strengthen the site over time.
This is also where business context matters. If you are a founder-led B2B company, technical SEO should connect to pipeline, sales process and revenue, not sit in a weird marketing silo. For that wider commercial view, the revenue acceleration advice for founder-led B2B businesses from Billionaires in Boxers is a useful reference point.
If you want someone to find the technical mess and explain it without the usual agency fog machine, SEO Bridge offers plain-English technical SEO support for businesses that need the problems found, prioritised and fixed properly.
Frequently Asked Questions
What is included in a technical SEO audit? A technical SEO audit usually checks indexation, crawlability, robots.txt, XML sitemaps, broken pages, redirects, site speed, mobile usability, JavaScript rendering, duplicate URLs, canonical tags, internal links, schema and tracking. A good audit also prioritises issues by business impact, not just by how scary a tool makes them look.
How often should I run a technical SEO audit? Most small business websites should have light technical checks monthly and a deeper audit every quarter. You should also run an audit after a redesign, migration, major content upload, plugin changes, hosting move, or sudden traffic drop. Waiting until enquiries disappear is how small problems become expensive ones.
Can a technical SEO audit improve rankings? Yes, if technical problems are stopping Google from crawling, indexing, understanding, or properly ranking your pages. An audit will not magically make weak content rank, but it can remove barriers that hold good pages back. The biggest wins often come from fixing indexation, redirects, speed, internal links and duplicate content.
Do small local businesses really need technical SEO? Yes, but they usually need practical technical SEO, not a massive enterprise report. A local plumber, solicitor, clinic, tradesperson, or shop still needs indexable service pages, fast mobile loading, clean redirects, working forms and clear local signals. If those basics are broken, competitors can outrank you without being better.
Should I fix technical SEO before adding more content? If your main pages are not indexed, crawlable, fast, mobile-friendly, or technically clear, fix that first. Adding more content to a broken site is like pouring more water into a leaking bucket. Once the foundations are sound, content has a much better chance of bringing in useful traffic and enquiries.
