05 / TECHNICAL SEO
Technical SEO management.
Trace each search decision through the response, rendered page, canonical owner, discovery path and released public state.
SYSTEM BEFORE EXPORT
A list of issues is not a technical decision.
Technical SEO traces an observed state to the route, template, application, cache, JavaScript path or deployment control that produces it. The work is complete when the served result agrees with the intended state.
That producing chain differs across Shopify, WordPress and Webflow. Reporting reads later movement against the verified release.
RESPONSE CHAIN
One URL passes through five different kinds of truth.
A break early in the chain can make every later signal look correct in a report and remain absent from the public page.
- 01Route
The requested URL resolves to the intended status and destination.
- 02Response
Headers and source HTML carry the intended access and ownership controls.
- 03Render
Required content, links and metadata survive the browser and crawler path.
- 04Discovery
Navigation, contextual links and sitemaps expose the intended owner.
- 05Observation
Search Console and business events are read against the exact released change.
CONTROL TABLE
Define the expected state before choosing the fix.
| Control | Question | Release evidence |
|---|---|---|
| Response | Does each intended URL return the correct status, headers and body? | HTTP response, redirect chain, cache behavior and failure states. |
| Crawl | Can a crawler request the resources needed to understand the page? | Robots rules, linked resources, server logs and fetch results. |
| Render | Does the delivered document become the intended visible and linkable page? | Initial HTML, rendered DOM, delayed content and error states. |
| Canonical | Do duplicate or alternate URLs agree on the preferred public owner? | Canonical tags, redirects, internal links and sitemap entries. |
| Discovery | Can useful pages be reached through the site's real navigation and relationships? | Rendered internal links, orphan checks and crawl paths. |
| Indexation | Does the published inclusion decision match what search systems can process? | Robots directives, canonical state, sitemap membership and Search Console. |
Send the URL and expected state.
Include the current behaviour and the business consequence.