SEO infrastructure consulting
Rendering, routing, i18n and CMS decisions made with search in mind, before launch.
- Engagement
- Advisory retainer, priced by the sprint
- Typical timeline
- 4–6 weeks running alongside your build
- Starts with
- A session with your lead engineer and the current architecture diagram.
This month your engineers pick a framework, a rendering strategy and a URL structure. Those three choices set the ceiling on your search traffic for the next four years, and nobody in that room is arguing on behalf of the crawler.
A platform that does not need an SEO rescue in year two.
What we build
Concrete artefacts, handed over and documented.
A review of the proposed architecture against how crawlers fetch, render and index, written as engineering feedback rather than a marketing memo
A rendering recommendation with the trade-offs stated plainly: what static, server and client rendering each cost you in indexing and in build complexity
A URL, routing and internationalisation specification, including the canonical and hreflang rules for every locale on the roadmap
A migration plan if you are replatforming: a redirect map at URL level, a staging crawl, and the checks that run on cutover day
What changes
Search constraints enter the architecture before the code, where they cost nothing to satisfy
A replatform ships without the traffic collapse that usually follows one
Your engineers receive specifications they can implement rather than requests they have to interpret
How it runs
- Weeks 1–2
01Architecture review
We read the diagrams and the repository, then list the decisions that would be expensive to reverse after launch.
- Weeks 3–4
02Specification
Routing, rendering, canonical and locale rules written as acceptance criteria your team can build and test against.
- Weeks 5–6
03Cutover support
We crawl staging, verify the redirect map, and stay available through launch week when the surprises actually appear.
Chosen per project. Named here so you can see the shape of it.
- Screaming Frog
- Google Search Console
- Next.js
Questions we get asked
Tell us the outcome, not the tooling.
Send us the situation you are in. We will tell you which discipline it belongs to, what we would do first and what it costs, including when the answer is to wait.