What Is Technical SEO? A Practical Guide

Technical SEO is the work that determines whether search engines can reach, render, understand and index your pages. It sits underneath everything else: a page Google cannot process will not rank no matter how good the writing is.

It is also invisible from the front end, which is why it goes unnoticed for years. The site looks fine to you and to your customers while quietly failing in ways that only appear in a log file or a coverage report.

The five areas

1. Crawlability

Can search engines reach your pages at all? This covers robots.txt directives, internal linking, redirect chains, and crawl budget — the finite attention Google gives your site. Crawl budget only matters at scale, but at scale it matters enormously.

2. Indexability

Can they store the pages once reached? Noindex directives, canonical tags, duplicate clusters and index bloat all live here. The most common serious problem we find is bloat: a site with 800 real pages reporting 140,000 indexed URLs because filters and internal search results are crawlable.

3. Rendering

Can they see the content? On JavaScript-heavy sites what Googlebot receives frequently differs from what a browser shows. This gap is where a surprising amount of unexplained ranking failure lives, and it is only visible if you test for it specifically.

4. Structured data

Can they understand what the page is about? Schema.org markup in JSON-LD tells search engines the page describes a product, an article, an organisation. Worth noting: FAQPage rich results were retired in mid-2026, so FAQ markup should now be built for users and AI extraction rather than for a rich result that no longer appears.

5. Performance

Is the experience good enough? Core Web Vitals measures Largest Contentful Paint (under 2.5s), Interaction to Next Paint (under 200ms) and Cumulative Layout Shift (under 0.1). INP replaced First Input Delay and is materially harder to pass, particularly on sites carrying heavy third-party tag loads.

What we find on almost every established site

• Index bloat from faceted navigation, internal search and parameter URLs.
• Redirect chains inherited across two or three migrations — A redirects to B redirects to C.
• Canonical tags pointing at redirects, or at pages that then canonical elsewhere.
• Orphan pages that exist in the sitemap but are not linked from anywhere.
• Lab-versus-field mismatch — a good Lighthouse score while CrUX field data fails, usually from third-party scripts.
• Mixed signals — a page blocked in robots.txt but also carrying a noindex tag, which means Google cannot crawl it to see the noindex.

Is technical your constraint?

Some quick checks:

• Search Console coverage: does the indexed count roughly match the number of pages you want indexed? A large gap in either direction is a problem.
• Core Web Vitals report: are URLs failing on field data, not lab data?
• site:yourdomain.co.uk in Google: does it return roughly what you expect?
• URL Inspection on an important page: does the rendered HTML contain your main content?

If all four look clean, technical is probably not your bottleneck and the constraint is relevance, authority or conversion. That is worth knowing before you commission a technical audit you do not need.

Sequence matters

Fix in this order: crawlability, then indexability, then rendering, then performance, then structured data. Each depends on the ones above it. Optimising Core Web Vitals on pages Google cannot index is effort spent on nothing.