Technical SEO Strategy: A Sequenced How-To for Crawl, Index, Render, and Serve

What a Technical SEO Strategy Actually Decides (and What It Doesn't)

A technical SEO strategy is not a list of fixes. It is a sequenced set of decisions about how search engines crawl, index, render, and reward your site. It does not decide content quality or brand positioning. It does decide which URLs compete, how fast new content is discovered, and whether Googlebot sees what a user sees.

Scenario: a South African multi-brand publisher on a headless stack, six months post-migration, traffic plateaued. They need an order of operations - fixing performance on an estate with broken indexation rules is wasted effort.

Prerequisites: What Has to Be in Place Before Step 1

You need three data sources: Google Search Console (Performance, Page Indexing, Crawl Stats, Core Web Vitals), server log files with user-agent filtering, and CrUX field data. You also need a staging environment for testing render behaviour and status codes.

Two organisational prerequisites: a named developer who owns the render path, and agreement that SEO sits in the release calendar, not in post-launch tickets.

The Sequencing Rule: Why Crawl and Indexation Come Before Performance

Performance work on a URL Google cannot index or renders as a blank shell is invisible. Google's crawl budget documentation clarifies there is no fixed number to spend - only a crawl rate limit and a host load limit. Reducing crawl waste (parameter URLs, redirect chains) increases the crawl rate Google applies. Indexation rules decide eligibility; rendering decides what is seen; performance decides tie-breaks. Do them in that order.

Step 1: Establish the Baseline With Field, Crawl, and Log Evidence

Capture a frozen baseline: export Page Indexing status codes and reasons, pull Crawl Stats for host status and response codes, and run 30 days of log-file analysis for Googlebot. Segment by template, not URL - a publisher might have 12 templates and 80,000 URLs. Record CrUX LCP, INP, and CLS at the 75th percentile by device; test on throttled 3G because field data reflects real networks.

Step 2: Stop the Bleeding - Indexation Rules, Status Codes, Canonicals, Redirects

Three rules cause most migration damage:

• robots.txt blocks crawling, not indexing. A disallowed URL can still appear in results if linked. For removal, use noindex - but only on crawlable pages.
• Canonicals must point to indexable, 200-status URLs. A canonical pointing at a noindexed page sends mixed signals.
• Redirect chains older than one hop waste crawl rate. Flatten to single 301s and check for redirects to soft 404s.

Audit hreflang for SA/international markets: missing return links are a frequent silent failure.

Step 3: Make Primary Content Renderable for Googlebot (and AI Crawlers)

Headless stacks often inject primary content via JavaScript. Google's JavaScript SEO guidance notes rendering is not guaranteed immediately, and lazy-loaded primary content delays indexing. Compare rendered HTML to raw HTML via the URL Inspection live test. If the article body is missing from initial HTML, move it to server-side or pre-render it. AI crawlers like GPTBot generally do not execute JavaScript, so server-rendered content is not optional if AI visibility matters.

Which Report Answers Which Question: A Tool-to-Decision Table