The short version: Technical SEO is important because it controls whether search engines can crawl, understand and trust your website at all, and if that foundation is broken, your content, your backlinks and your keyword research are wasted money. I’ve watched a client lose 40 percent of their organic traffic in six weeks purely from a botched site migration that nobody checked technically. Fix the technical layer first, then worry about everything else.
The client story that made me obsessive about this
A few years back I worked with a mid-sized fashion accessories brand, decent traffic, around 30,000 organic sessions a month, ranking well for a handful of solid commercial terms. They rebranded, moved to a new domain, and hired a web agency to do the migration. Nobody on that project had ever heard the phrase “301 redirect map.”
Three months later their organic traffic had dropped to under 18,000 sessions a month. Not because their content got worse. Not because a competitor outranked them. Because hundreds of old URLs now returned 404 errors, their new XML sitemap listed pages that redirected three times before landing anywhere, and Google Search Console was flagging over 200 pages as “crawled, not indexed.” Nobody had looked at Search Console for weeks because nobody thought it was their job.
We spent six weeks rebuilding the redirect map, cleaning the sitemap so it only listed live, indexable URLs, and fixing canonical tags that were pointing to the wrong versions of pages entirely. Traffic came back to 34,000 sessions within four months, higher than before the migration. Nothing about their content strategy changed. That’s the bit people don’t want to hear: the fix was almost entirely plumbing, not writing.
What technical SEO covers
Technical SEO is the unglamorous half of the job. It’s not the keyword research, not the blog calendar, not the backlink outreach. It’s everything that determines whether Google can physically get to your pages, read them, and decide they deserve to rank. If you want the full breakdown of what falls under this umbrella, I go through it in what technical SEO means in plain English, but the short list looks like this:
- Crawlability: can Googlebot reach your pages without hitting broken links, blocked robots.txt rules or infinite redirect loops
- Indexability: once crawled, are the right pages going into Google’s index
- Site architecture: how pages link to each other, and whether important pages are buried five clicks deep
- Page speed and Core Web Vitals: how fast pages load and how stable they feel while loading
- Mobile usability: whether the site works on a phone, since Google indexes the mobile version first
- Structured data: markup that helps Google understand what a page is, a recipe, a product, an article, a review
- Canonicalisation: telling Google which version of a near-duplicate page is the “real” one
- HTTPS and security: whether the site is served securely, which is a confirmed ranking factor since 2014
None of that is exciting. All of it decides whether your other work has any chance.
Why this matters more than most people think
Here’s the uncomfortable bit nobody selling SEO packages wants to say out loud: content and backlinks get you nowhere if the technical foundation is broken, but most technical SEO audits people pay for are theatre. A crawler tool spits out a 40-page PDF listing 300 “issues,” half of which are missing alt text on decorative images that affect nothing, while the three things that matter, like a robots.txt file blocking your entire blog folder, get buried on page 22. I’ve seen agencies charge £1,500 for a report like that and call it a strategy. It isn’t. It’s a scan with a cover page.
Real technical SEO is about triage, not volume. Ten fixed critical issues beat 200 cosmetic ones every time.
Google itself has said plainly that if a page can’t be crawled or indexed, nothing else you do to it matters, a point echoed repeatedly in Google’s own Search Central documentation. That’s not opinion, that’s how the system works. Your beautifully written blog post ranking on page one for zero terms because it’s stuck behind a faulty canonical tag isn’t a content problem, it’s a plumbing problem.
The five most common technical faults I find on client sites
After auditing well over a hundred small and mid-sized business sites, the same handful of problems show up again and again:
- Orphaned pages. Pages that exist, sometimes rank, but have zero internal links pointing to them, so Google struggles to find or trust them.
- Duplicate content from URL parameters. An ecommerce site filtering products by colour or size can generate thousands of near-identical URLs that dilute ranking signals across duplicates instead of consolidating them on one strong page.
- Slow mobile load times. Google’s own research found that as page load time goes from 1 second to 5 seconds, the probability of a mobile visitor bouncing increases by 90 percent. That’s not a rounding error, that’s most of your traffic leaving before the page even renders.
- Broken or missing XML sitemaps. Either the sitemap doesn’t exist, hasn’t been updated in two years, or lists pages that no longer exist. If you’ve never checked, this is worth ten minutes of your time, and I’ve written a step-by-step on how to create an XML sitemap for your website.
- No monitoring at all. The business owner has never logged into Search Console and has no idea Google is telling them, for free, exactly which pages have problems.
A simple step-by-step check you can do this afternoon
You don’t need a £3,000 audit to get a first read on your site’s technical health. Here’s what I’d do, in order, with a coffee and 90 minutes:
- Step 1: Open Google Search Console and check the Coverage/Indexing report. Look specifically for “Crawled, currently not indexed” and “Discovered, currently not indexed.” Any page you care about showing up there is a red flag.
- Step 2: Run your homepage and two key landing pages through PageSpeed Insights. Anything scoring under 50 on mobile needs attention this month, not “eventually.”
- Step 3: Search site:yourdomain.com in Google and scroll through what comes back. If you see pages you didn’t expect, old test pages, tag archives, thin category pages, that’s bloat diluting your site’s authority.
- Step 4: Check your robots.txt file at yourdomain.com/robots.txt. Make sure you’re not accidentally blocking /blog/ or /shop/ from crawlers, which happens more often after a site rebuild than you’d think.
- Step 5: Pull up your XML sitemap at yourdomain.com/sitemap.xml and spot-check ten URLs in it. Do they all load? Do they all return a 200 status, not a redirect or a 404?
If you want a deeper, guided version of step one, I’ve written a full walkthrough on how to use Google Search Console to check your website’s performance that takes you through every tab worth checking, not just the headline numbers.
Why WordPress sites specifically get this wrong
Roughly 43 percent of all websites run on WordPress, and I’d guess a similar proportion assume installing an SEO plugin is the same thing as doing technical SEO. It isn’t. A plugin like Yoast or Rank Math will happily let you set a meta description while your site is running four different plugins that all inject conflicting schema markup, or a theme that loads 2MB of unused CSS on every single page. I’ve covered this in how to improve SEO on a WordPress website without wasting six months on a plugin, because plugin settings are maybe 20 percent of the technical picture on a WordPress build, and most people stop there thinking the job’s done.
The bit people forget: technical SEO feeds your conversion rate too
This is the part that gets missed constantly. Technical SEO isn’t just about rankings, it directly touches how many visitors turn into customers. A page that loads in 1.5 seconds instead of 5 doesn’t just please Google, it keeps a real human from closing the tab before they’ve read your offer. I’ve written before about why conversion rate is the most important number in your business, and the two things aren’t separate conversations. Fixing a broken canonical tag might get a page indexed again. Fixing the page speed on that same page is what stops a warm visitor from leaving before they buy anything.
What good site architecture looks like
One thing I check on every site audit is how many clicks it takes to get from the homepage to a random deep page. If your best blog post from 2023 is seven clicks from the homepage with zero internal links pointing to it, don’t be surprised when it gets no traffic despite being useful. A clean sitemap, both the visual kind for humans and the XML kind for search engines, forces you to see your own site structure honestly. If you’ve never generated one, there are decent free options worth trying before paying for anything, and I’ve listed the ones worth your time in the best free site map tools for your website.
How much this costs to fix, roughly
Small technical fixes, robots.txt corrections, sitemap regeneration, fixing a handful of broken redirects, you can often do yourself in a weekend with the steps above. A proper technical audit from a consultant for a small business site typically runs somewhere between £500 and £2,000 depending on site size, and a full fix-it project on a site with genuine architectural problems, like my fashion client above, can run into several thousand pounds and multiple weeks of work. It’s not cheap, but compare it against the traffic that client lost: 12,000 monthly sessions gone for three months is not a small number when even a modest 2 percent conversion rate on that traffic was worth real revenue every single month it stayed broken.
When to bring someone in rather than DIY it
If you’ve run through the steps above and found tangled problems, redirect chains three or four deep, a sitemap with thousands of URLs nobody can explain, Core Web Vitals scores stuck in the red for months, that’s usually the point where doing it yourself starts costing more in lost traffic than hiring help would. I work through exactly this kind of untangling with clients, and if you’re weighing up whether to bring in outside help, it’s worth reading through what an AI consultant for small business does day to day before deciding, since a lot of technical SEO work now overlaps with how sites get crawled and understood by AI-driven search tools too, not just traditional Google results.
The honest bottom line on all this
Technical SEO doesn’t feel productive. It doesn’t produce a blog post you can share on LinkedIn or a case study you can brag about. It’s the equivalent of checking your car’s brakes rather than putting a new paint job on it. But every ranking, every conversion, every piece of content you’ve ever written depends entirely on Google being able to reach it, read it and trust it first. Skip that layer and you’re building a business on a foundation nobody’s checked in years. Fix it once, and everything else you do afterwards has a chance to work.
Frequently asked questions
Is technical SEO more important than content?
Neither works without the other, but if you have to choose where to spend the next two weeks, fix technical problems first, since broken crawling or indexing means great content never gets seen at all, while flawless technical health with weak content just gets ignored by readers rather than blocked by search engines.
How often should I check my site’s technical SEO health?
Run the basic checks, Search Console coverage report, page speed, sitemap validity, at least once a quarter, and always immediately after any redesign, migration or platform change, since that’s when the most damaging errors get introduced.
Can I fix technical SEO issues myself without hiring anyone?
Yes for most small and mid-sized sites, especially issues like broken sitemaps, blocked robots.txt files and slow images, all of which are fixable in an afternoon using free tools like Google Search Console and PageSpeed Insights, but deeper architectural problems on large or migrated sites usually need experienced hands.
Does technical SEO affect how AI tools like ChatGPT find and cite my website?
Yes, since AI search tools rely on the same crawlable, well-structured, fast-loading pages that traditional search engines need, so a site with broken crawl paths or missing structured data is just as invisible to AI citation as it is to a standard Google ranking.
