Technical SEO is everything that helps search engines find, understand, and trust your site, as opposed to the content that gives them something worth ranking. If on-page SEO is what your pages say, technical SEO is whether anyone can hear you saying it.
It's the least glamorous corner of SEO, and after ten years of doing it I'll defend it as the best value corner. Here's the plain-English version of what it is, what it includes, and why it's usually the cheapest ranking gain available.
The plumbing metaphor that mostly works
Think of your content as water and your site as the pipes. Technical SEO is the pipework: it doesn't make the water better, but a blocked pipe means nobody gets any water at all, and a leaky one wastes pressure everywhere. Most sites I audit aren't short of content. They're short of working pipes, and the content they already paid for is sitting behind blockages nobody's looked at in years.
That's why I call technical work the cheapest ranking gain available. Fixing it unblocks assets that already exist. No new content, no new links, just the value you already created finally reaching the index.
What technical SEO includes
The scope, without the jargon:
Crawling. Can search engines reach every page that matters? This covers your internal linking, your sitemap, robots.txt, and on big sites, crawl budget: whether Google spends its limited attention on your important pages or wastes it on ten thousand filtered duplicates.
Rendering. Once reached, does the page actually work for a crawler? Modern sites lean on JavaScript, and content that only appears after heavy client-side rendering can be seen late, partially, or never. This is why I build sites with rendering in mind from the start rather than fixing it after.
Indexing. Of the pages Google can reach and render, which should be in the index? Deliberate answers here (canonicals, noindex, handling duplicates and parameters) keep the index full of your best pages and empty of your clutter.
Site architecture. How pages relate: the hierarchy, the URL structure, and the internal links that pass authority to the pages that earn money. Architecture is where technical SEO and strategy meet, and it's the part most often wrong on otherwise well-built sites.
Performance and experience. Speed, Core Web Vitals, mobile behaviour, and stability. Modest as a ranking factor, decisive for whether the traffic you win actually converts.
Structured data. Machine-readable labels that tell search engines what things are (a product, a review, an event, a business), unlocking richer listings and, increasingly, feeding the AI systems that summarise the web.
Security and hygiene. HTTPS, redirects that resolve properly, no chains, no broken internals. Small things that erode trust in aggregate.
Why technical SEO matters more than another blog post
Content advice scales infinitely: there's always another post to write. Technical debt is finite. A site has a certain number of real problems, and once fixed they tend to stay fixed. When budgets are limited I'd rather find and clear those problems than add another article to a site that can't make the most of the hundred it already has.
There's a compounding argument too. Every future page you publish inherits the site's technical condition. Fix the template, and every page using it improves at once; I've watched single template fixes move traffic across thousands of URLs, which no single article can do.
How to tell if your site has technical problems
Three checks anyone can run. Search Google for site:yourdomain.com and skim what's indexed; if you see junk pages, duplicates, or way more (or fewer) results than you have real pages, there's work to do. Open Search Console's indexing report and read why pages are excluded. And put a key page through PageSpeed Insights, looking at the real-user data rather than the lab score.
Anything alarming in those three views, and it's worth a proper diagnosis. That's exactly what my SEO audit is for.
Technical SEO FAQs
What's the difference between technical SEO and on-page SEO?
On-page SEO is about matching individual pages to searches: titles, headings, content, intent. Technical SEO is about the site as a system: whether pages can be crawled, rendered, indexed, and served fast. You need both; neither substitutes for the other.
Why is technical SEO important?
Because it gates everything else. The best content on the web ranks for nothing if it can't be crawled or indexed, and it converts nobody if the page takes eight seconds to load. Technical work also compounds: a fixed template improves every page built on it, now and in future.
Do I need to be a developer to do technical SEO?
To diagnose it, no; tools like Search Console surface most problems in readable form. To fix it, often yes, someone needs to touch the code. The scarce skill sits between the two: knowing which of the hundred flagged issues actually matter, which is judgement rather than engineering.
How often should technical SEO be reviewed?
A proper review at least annually, plus around any major change: redesigns, migrations, replatforming. Ongoing monitoring through Search Console catches the rest. Continuous technical retainers, on most small and mid-size sites, are billing in search of a task.
Want a hand with any of this?
Tell me what you're working on and what you're trying to achieve, and I'll give you an honest view of whether I can help and what it would take.
Get in touch