What is technical SEO? A plain-English guide

Technical SEO is the work that helps search engines and AI crawlers access, understand, and trust your site at a structural level. It is not about what you say on a page (that is content) or who vouches for you (that is links). It is about whether the machine on the other end can read what you published, quickly and without confusion.

Think of it as three guarantees you make to Google: I will let you in, I will render the same thing your users see, and I will tell you clearly what each page is and how the pages relate. Break any of those and rankings suffer no matter how good your content is.

Every page passes through three stages before it can rank. Technical SEO is mostly about removing friction at each one.

1. Crawl

Googlebot discovers URLs through links and sitemaps and decides which to fetch. Problems here look like: important pages buried four clicks deep, crawl budget wasted on infinite filter URLs, or pages blocked in robots.txt by accident.

2. Render

Google executes the page, including JavaScript, to see the final content. If your key content or links only appear after client-side JavaScript that fails or times out, Google may index a near-empty page. Server-side rendering or static generation removes this risk.

3. Index

Google stores the page and decides whether it is worth keeping. Duplicate content, conflicting canonicals, thin pages, and noindex tags applied by mistake all cause valuable pages to drop out of the index entirely.

Core Web Vitals are Google’s measurable thresholds for page experience. You want to pass all three on real-world (field) data, not just in lab tools.

The most common offenders are oversized hero images, render-blocking scripts, heavy third-party tags, and fonts that shift the layout as they load. Field data in Search Console’s Core Web Vitals report is the source of truth; a green Lighthouse score in the lab does not guarantee real users get the same.

A working audit covers these areas in roughly this order of impact:

• Indexation: the right pages indexed, the wrong ones (filters, internal search, staging) excluded.
• Crawlability: clean robots.txt, an accurate XML sitemap, no crawl traps from faceted navigation.
• Canonicalisation: one canonical URL per piece of content, consistent on protocol, www, and trailing slash.
• Site architecture: important pages within a few clicks of the homepage, a logical internal-link graph.
• Structured data: schema that matches visible content (and is not bloated, which can be treated as spam).
• JavaScript SEO: content and links present in the rendered HTML, not locked behind fragile client-side code.
• Hreflang: correct, reciprocal, self-referencing tags if you serve multiple languages or regions.
• Core Web Vitals: passing on field data across mobile and desktop.
• HTTPS and security: site-wide HTTPS, no mixed content, valid certificate.

You probably have technical debt if: Search Console shows lots of "Discovered, currently not indexed" or "Crawled, not indexed" pages; your indexed-page count is wildly higher or lower than your real page count; rankings stalled after a site migration or redesign; or pages load fine for you but Core Web Vitals are failing for real users.

A quick gut check: search site:yourdomain.com in Google. If the number of results is far off from how many real pages you have, something in the crawl-or-index layer needs attention.

Plenty of technical SEO is DIY-able: fixing obvious crawl blocks, compressing images, tightening internal links. The work that benefits from experience is the judgement: which of forty flagged issues actually move rankings, how to migrate without losing equity, and how to fix rendering on a JavaScript-heavy stack without breaking the site.

If you want the diagnosis done properly, that is exactly what a technical SEO engagement or a one-off audit delivers: a prioritised, ranked fix list rather than a 200-line tool export.