Guide
Move Your Website in Stages, and Your Own Words Stay Accurate to Search and to Assistants
A fall in search traffic cannot be diagnosed when everything changed at once. We separate the move from the redesign, and treat the map of old and new addresses as the real project.
4-minute read5 November 2026
In Brief
- A rebrand, a new domain, a new content system and fresh copy launched on one date leave you unable to tell which change cost you visitors. Years of accumulated search value are at risk.
- We see four actions: change one thing at a time, map every address that carries value, include links inside shipped software, and keep redirects in place long after launch.
- Thinqmesh structures your words as one source in week one, moves your existing content across in week three, and takes the site live on a defined scope in four weeks.
A website move at a technology company rarely arrives alone. A rebrand or an acquisition prompts a new domain, the new domain justifies a new content system, the new system invites a new design, and the marketing team takes the chance to rewrite the copy. All four are scheduled for one launch, because one launch is easier to announce and to fund.
Bundled Changes Hide Their Own Cause
If search traffic falls after a combined launch, no one can say which of the four changes was responsible. Each is plausible, and each calls for a different fix. In our view this bundling is the largest avoidable risk in a migration, larger than any technical detail of redirects, and it is worth accepting a longer programme to avoid it.
The value you have built sits in more places than the navigation shows: documentation, release notes, comparison pages and old technical articles that collect links from people solving a particular problem. We start by structuring your words as a single source, then move the existing content across on a defined scope, so what search engines and assistants read is the account you approved.
Four Actions That Protect What Search Has Learned About You
Each one can be done before a single page is redesigned, and each makes the eventual move easier to diagnose.
Change One Thing at a Time
Move the domain, then the content system, then the design, then the copy, with a pause between each.
When traffic falls after a staged change, the cause is known. After a combined launch, the cause could be any of four things, and fixing it becomes guesswork. A longer programme costs less than that uncertainty.
Get started
- List every change your launch plan bundles together.
- Put them in an order, with a review date after each.
Map Every Address That Carries Value
Build the list from your sitemap, server logs, analytics and the search console.
Include pages, images, documents and scripts. Send each old address to the closest equivalent on the new site, and avoid sending many old pages to the home page, which a search engine may treat as an error.
Get started
- Export your top 200 addresses by traffic.
- Write the new destination beside each.
Include the Places You Cannot Edit
For a technology company, documentation, release notes and old technical articles often carry the most value.
These pages attract links from repositories, forum answers and package listings that no one at your company can change. Help links inside shipped software and error messages keep requesting old addresses for as long as old versions run, and they must still resolve.
Get started
- Search your repositories and product for hard-coded links to your site.
- Add each one to the address map.
Keep Redirects in Place for as Long as You Can
Temporary dips are normal during a move, and the redirects carry the signal while they settle.
Leave them in place well beyond launch, and review the list after each stage. A redirect carries the old address's value to the new page. It cannot help if the page behind it has been rewritten or merged into something different.
Get started
- Record the date each redirect was created.
- Set a review reminder for one year after launch.
How Thinqmesh Solves This
We build the machine-readable layer first, alongside the pages, from one source your team edits. A sentence changed once updates the page, the structured data and the machine layer together.
- Week 1
Words as the Source
Your words are structured as the single source for the site, so that people and software read the same account.
- Week 2
Design and Pages
Pages are designed and built for a defined scope, with speed and accessibility treated as requirements.
- Week 3
Migration and Forms
Existing content is moved across, and contact forms are connected to the systems you already use.
- Week 4
Go-Live
The site goes live on a defined scope, with words your own team can change.
You finish with a site on your own domain, a handover session and a short written guide. The code is yours and sits in your own account.
