Technical SEO Foundations

Everything covered so far in this playbook - matching keywords to intent, structuring a page with the right titles and headings - assumes the page actually gets crawled, indexed, and rendered by search engines in the first place. Technical SEO is the layer that makes that assumption true or false, and it's invisible from the front end: a page can look complete to a visitor and still be unreadable to a crawler, excluded from the index, or too slow to rank.

Crawlability and Indexation Come Before Everything Else

A search engine has to find and read a page before anything else about it matters. Crawlability issues - a misconfigured robots.txt file blocking pages it shouldn't, a missing or broken XML sitemap, orphaned pages with no internal links pointing to them - quietly keep otherwise-good content out of the running entirely. Indexation problems compound this: a broken or conflicting canonical tag can tell search engines to credit a different URL for the same content, splitting ranking signals across pages instead of consolidating them onto the one that should actually rank.

The practical habit is treating crawl budget as a finite resource, especially on larger sites. Search engines don't crawl every page on a site with equal frequency - duplicate URLs, thin parameter-driven pages, and low-value archive pages can eat crawl budget that should be going to the pages you actually want ranking. Cleaning up what's eligible to be crawled and indexed, rather than leaving everything open by default, is what keeps that budget pointed at the pages that matter.

Site Speed and Core Web Vitals Set a Ceiling on Rankings

Core Web Vitals - loading performance, interactivity, and visual stability - are a direct ranking input, and they're also a genuine user experience problem independent of SEO: a slow, unstable page loses visitors regardless of how well it ranks. The three metrics that matter are Largest Contentful Paint (how fast the main content loads), Interaction to Next Paint (how responsive the page feels), and Cumulative Layout Shift (how much the page jumps around as it loads). Common causes worth checking first are unoptimised images, render-blocking scripts, and third-party embeds that load more than they need to. None of this replaces content or authority work, but a page failing its Core Web Vitals thresholds is competing with a ceiling on it that a technically clean competitor doesn't have.

Site Architecture Determines How Authority Flows

How a site is structured - URL patterns, how deep pages sit in the navigation, how pagination and faceted navigation are handled - affects both how easily a crawler can reach a page and how internal linking (covered in the last lesson) distributes authority across the site. Pages buried many clicks deep in the navigation, with thin internal linking pointing to them, are harder for both crawlers and users to reach. Faceted navigation on larger sites (filters, sort options) can also generate enormous numbers of near-duplicate URLs if left unmanaged, which drags on crawl budget for no ranking benefit.

Structured Data and AI Crawler Access Are Now Part of the Foundation

Two things that used to be optional are now core technical work. Structured data (schema markup, covered in the on-page lesson) gives search engines and AI systems a machine-readable description of a page's content, and pages without it are at a real disadvantage for rich results and AI citations alike. Separately, AI crawler access - whether bots like GPTBot and ClaudeBot can actually reach and parse a site's pages, and whether an llms.txt file is in place - is now worth checking explicitly, since a site can be perfectly crawlable by traditional search engines while still being effectively invisible to the AI systems increasingly generating answers instead of link lists.

Diagnosing Before Fixing

The order that actually works is audit, then prioritise, then fix - not the reverse. A full crawl of the site, run the way a search engine would run it, surfaces the real list of issues; from there, findings should be ranked by how much organic potential each one is actually costing, not by how many issues exist in a category. A single broken canonical tag on a high-traffic page usually matters more than a hundred minor alt-text omissions on low-traffic ones. For a structured starting checklist, see our technical SEO checklist, and re-crawl after any fix to confirm it actually resolved the issue rather than just shipping code that looks correct.

What's Next in This Playbook

With the technical foundation, on-page structure, and keyword targeting covered, the next lesson moves outside the page itself to off-page SEO - how backlinks and other authority signals get built, and why some link-building tactics quietly do more harm than good.