In April 2026, I spoke at BrightonSEO about something that’s saved me (and a lot of projects) more times than I can count:
The technical sitemap. This post is a companion to that talk. If you’ve ever been through a site migration and thought “why is everything on fire?”, this is for you.
And if you just want the template:
Download the technical sitemap here.
The problem with migrations
Let’s be honest. Most migrations don’t fail because of one big mistake. They fail because of lots of small, predictable ones. Things like:
Developers and designers not prioritising SEO,
Nobody knowing what stage the build is at,
URLs being made up on the fly,
SEO getting brought in after everything is already built.
You end up in that familiar situation where the site lands on your desk and someone says:
“Can you just SEO this?”
No. No, we cannot.
And then the site launches…
If the build phase is messy, the launch is worse. The usual suspects show up – there are 404s everywhere, mystery pages appear that nobody signed off, entire sites are accidentally noindexed, everything is missing metadata and there’s internal redirects all over the place. At that point, you’re not doing SEO, you’re doing damage control.
The real issue is that it’s not actually a technical thing; it’s all about communication, and this is the bit people don’t like admitting. Most migration problems aren’t caused by a lack of SEO knowledge. They’re caused by poor communication, teams working in silos, and unclear ownership of certain tasks.
Why SEOs need to be best mates with devs and designers
If you take nothing else away, take this:
If you annoy devs, your SEO won’t get implemented.
If you’re brought in late, you’re fixing instead of shaping.
If teams don’t trust each other, things get missed.
You want to be involved early, not parachuted in at the end. So… how do we fix it? This is where the technical sitemap comes in!
What is a technical sitemap?
A technical sitemap is: A working document that acts as a single source of truth for the entire website build. It brings SEO, dev, design, and content into one place. What does it actually do?
A technical sitemap:
1 – Gives everyone a single source of truth
2 – Acts as a shared working doc across teams
3 – Makes sure that sites are built to SEO standards, without disrupting sprints
4 – Shows content teams the URL structure before upload
5 – Includes pre-written, keyword-targeted metadata, headings, and content direction
6 – Helps project managers track progress
7 – Supports junior SEOs in complex builds
8 – Combines redirects, optimisation, and performance planning in one place
In short, it removes guesswork from your migrations.
Why it works
Because it solves the real problem: alignment & communication.
Instead of SEO teams working in isolation, devs making decisions without context and content teams guessing structure, you get a clear URL structure before build, agreed metadata before launch, clear keyword targeting for important conversion-driving pages, clear, defined responsibilities, and – most importantly – visibility across teams with a single point of truth.
When should you use it?
Pretty much always, but especially:
1 – Large migrations
2 – High-pressure launches
3 – Multi-team or multi-agency projects
4 – When onboarding junior SEOs
5 – When SEO isn’t embedded early (yet)
One of the biggest benefits is simple – it helps avoid performance drops post-launch, which is what clients actually care about.
How to use it in practice
This isn’t a “set-and-forget” document. It works best when it’s actively used:
1 – Between devs and SEOs for build decisions
2 – Between SEOs and designers for structure and templates
3 – Across agencies and teams for consistency
4 – With clients for clarity and accountability
Ideally, you use it as early as possible. But even if you’re late to the project, it’s still useful. It just becomes more about fixing than guiding.
A key part of the benefit of this document is the opportunity to carry out research, apply keyword research, conduct a technical review, and complete a huge bulk of the SEO work in one go…and be able to actually use that data to inform your site structure, content, and objectives.
Want the template?
If you want to try this yourself, I’ve shared the exact template I use:
Download the technical sitemap
You can plug it straight into your next project and adapt it to your workflow.
There’s no magic trick to perfect migrations. Sometimes, they go Pete Tong, even when we do everything possible to mitigate it. But there is a difference between reacting to problems after launch and preventing them before they happen. The technical sitemap helps you do the second. And honestly, once you’ve used one properly, you won’t want to run a migration without it.
Want to know more? Have a chat with us! Contact the footprint team for more info.
We can support you through site migrations, guide you through the document, support with SEO, PPC, and all other types of marketing, whatever your requirements.
