What technical SEO covers
The core guides in this section follow the pipeline from the engine's side.
- Crawling and indexing — how crawlers discover and fetch URLs, how indexing decisions are made, and the controls (robots.txt, meta robots, canonical tags, sitemaps, status codes) that shape both. The foundation for everything else here.
- Site architecture — URL hierarchy, click depth, hub pages and navigation: how the shape of a site tells engines what matters and spreads authority to it.
- Core Web Vitals — the loading, responsiveness and stability metrics that make up the page-experience signal, how they are measured in the field, and template-level fixes.
- Structured data — schema.org markup, the rich results it can unlock, what Google documents about each type, and how to validate it.
- JavaScript SEO — how rendering works, what can go wrong with client-side content and links, and rendering strategies that keep pages indexable.
- Site migrations — domain, platform and URL changes: redirect mapping, pre-launch checks and post-launch monitoring that preserve rankings.
- Technical SEO audit — a step-by-step tutorial that finds and prioritises the problems above on an existing site.
Further guides and tutorials go deeper into narrower jobs that the core guides touch on:
- Log file analysis — a tutorial on using server logs to isolate search engine crawlers, label URLs by template, and find crawl waste and the pages crawlers neglect.
- Configuring a site crawl — a tutorial for setting up a site crawler so its results answer the question asked: start points and boundaries, robots rules, a speed agreed with whoever runs the server, plain or rendered fetching, a fence around parameters, access to staging, URL lists and the fields to extract.
- Auditing URL parameters — a tutorial for listing every parameter a site generates, recording what each one does, and giving each class a rule for crawling, indexing and links.
- Index rules for tags, archives and utility pages — which of the pages a CMS creates automatically deserve the index, from tags and date archives to internal search, and how to set the rules.
- PDFs and other files in search — how files end up in search results, when a file should rank instead of a page, and how response headers control indexing and canonical URLs.
- Expired listings, events and offers — whether to keep, redirect or remove pages with an end date, such as property and job listings, events, courses and time-limited offers.
- Page experience beyond Core Web Vitals — what Google's page experience guidance covers besides the metrics: secure connections, mobile display, intrusive interstitials, ads and the main content.
- Microsites and multiple domains — when a brand, product or campaign deserves its own domain, what separate sites cost in search, and how to merge them.
- Choosing a CMS or platform for SEO — the SEO capabilities to require before choosing a content management system or store platform: URL and redirect control, indexing rules, templates and speed.
- Writing SEO requirements for developers — a tutorial for turning the SEO needs of a new template or feature into requirements developers can build and test.
- SEO checks for staging and releases — keeping staging sites out of search, checking SEO-critical settings before and after each release, and monitoring for regressions.
How technical problems show up
Technical issues rarely announce themselves. The symptoms are indirect, and recognising them is half the audit:
- Pages that exist but never appear in search, or appear and disappear — a crawling, rendering or canonical problem.
- Search Console reporting many more "discovered" or "crawled, currently not indexed" URLs than the site has real pages — index bloat from parameters, filters or duplicates.
- Rankings that drop after a redesign, a platform change or a new JavaScript framework — rendering or redirect problems.
- Rich results that stop showing — structured data errors or policy changes.
- Pages that rank but convert poorly on mobile — speed and stability.
- Taps and clicks that feel sluggish on phones — responsiveness, diagnosed on the page about slow interactions in the Core Web Vitals report.
The audit tutorial turns these symptoms into a repeatable diagnosis, using a crawler, Search Console (GSCGoogle's search performance and indexing tool.) and the site's own logs.
Priorities
Not every technical issue matters equally. The order that usually pays:
- Anything that blocks indexing of important pages (robots directives, noindex, broken canonicals, server errors) — these are total losses.
- Duplicate and near-duplicate URLs competing with each other (parameters, trailing slashes, HTTP/HTTPS, www/non-www, facetsFilters on a listing page that narrow results by attributes such as brand, size or price, often creating a URL for each combination.) — these dilute signals and waste crawl.
- Architecture: important pages buried deep, orphaned or linked only through navigation that crawlers cannot follow.
- Rendering: content or links that exist only after client-side JavaScript runs.
- Page experience: Core Web Vitals on templates with the most traffic.
- Structured data: correct and complete on the page types that have rich results.
Fixes are made at the template level wherever possible, so one change improves every page built from it.
How this section connects
Technical work makes the rest of SEO possible rather than replacing it: the on-page guides assume the page is indexable, the content section assumes new pages will be crawled, and measurement is where technical changes are confirmed in Search Console. The e-commerce guide on faceted navigation is the most common large-site technical problem in practice and lives in its own section. The SEO page checker reads the on-page technical basics of a single URL; the technical SEO expertise page describes how the author approaches this work and includes a Core Web Vitals simulator.
