Home/Website/SEO Website Migration and URL Mapping for B2B Sites
Keep your pages findable after the move
An SEO website migration needs a destination for each old URL, redirects in the code and search checks after launch. We plan that work with you as experienced founders and engineers, updating the links, canonical tags and sitemap to follow the new addresses.
What is an SEO website migration?
The SEO site migration records where a website's old pages go. URL mapping pairs those addresses with destinations, and permanent server-side redirects such as 301 or 308 send requests there. Google also calls for updated internal links, self-referencing canonicals and the new sitemap in Search Console. Submit a Change of Address for a domain move. Its guidance says to retain redirects generally at least a year; rankings may fluctuate during recrawling and reindexing.
The website builder can include redirects in the launch work. A founder can coordinate the move using a checklist of migration tasks. We use the old site's search data to map its pages, implement the changes and inspect Search Console once the new site is live. The question to ask of each arrangement is who checks afterward that the searches reaching the old pages still lead to relevant new ones.
A move without a URL map loses pages from Google
The new site opens with different URLs, while unreviewed links and tags continue referring to addresses from the old site.
- Pages fall out of search. For a recruiting-research firm, we found no pages in Google: its sitemap and canonicals still named an old domain.
- Links send visitors backward. An old internal address can lead through a redirect or reach a dead page.
- Rankings move during reindexing. Google says search positions may fluctuate as it processes the changed URLs.
We can trace those old addresses through a URL map and inspect their new destinations.
We map every URL and ship the redirects
The redirect work starts with the old URLs and what people search for to find them. We use that record to build the map and update the site.
Gather the old URLs
We collect the pages and their Search Console searches and impressions, so the migration map includes addresses still receiving attention from buyers.
Pair the destinations
We choose the closest new page for each old URL, using the question it answers to guide where a searcher should arrive.
Write the redirects
Our engineers implement permanent redirects alongside new internal links, canonicals and sitemap entries, then deliver those changes in the site's repository.
Update Search Console
We submit the sitemap for the new site and, when the domain changes, submit its Change of Address through the same account.
We keep checking Search Console after launch
The URL map links our inspection before launch to the checks afterward. We return to both sets of addresses to see how Google is processing the move.
First
Capture the current pages
We run the read-only public-site audit, covering up to 100 pages per run, and collect the search data those URLs have earned.
Then
Check each destination
Our people review the map row by row, and the founder approves the important steps as we prepare the changes for launch.
At launch
Release the redirects
Your team merges the pull request containing the redirect rules and updated tags, putting those changes into the new site's launch.
After launch
Read the index changes
We inspect old and new URLs in Search Console each week and discuss what to continue, change or stop as the evidence develops.
Example: mapping our old landing pages to new ones
We are using a redirect map for the tin.computer redesign. Each landing page from our earlier product is paired with its closest page on the new site, with a permanent redirect specified for that move. The old pricing page is mapped to the booking page. The redesign is still planned, so these are destinations to implement at launch.
We let search data choose each redirect
Search impressions can reveal a reason to keep a page a company has retired. After a compliance startup pivoted, we found that its former comparison post still appeared in searches. Restoring that post became the first task. The same kind of evidence helps us choose where an old URL belongs in a migration.
- Inspect the search history. We read the queries and impressions before deciding what should happen to an old page.
- Choose a close match. We use the nearest relevant destination for each redirect, including on our own site.
- Keep the map and work. The redirect map, your accounts, the data and our migration workflows stay with you.
It suits startups changing domain, platform or design
Startups moving domains
We examine the redirects and tags that connect the previous domain to the new one, including addresses left in the sitemap.
Startups rebuilding their sites
We account for existing URLs when a larger site adds pages and changes the way buyers find their way around.
Services revising their offer
We help AI-enabled service companies decide where retired pages should lead, using the searches those pages still attract.
Talk to Tin
Let's talk about what your move changes and which old URLs buyers still find. We can handle the migration work with no long-term commitment.
FAQ
How long should the redirects stay in place?
Generally at least a year, and as long as possible, is Google's guidance. The redirect map stays with the site's records and the rules stay in its code. Internal links and the sitemap should use the new destinations directly once the move is complete.
Will our rankings drop after the move?
A move can bring ranking fluctuations while Google recrawls and reindexes the site. We prepare the URL map and address changes, then inspect Search Console to see how the new pages are being processed. Those observations tell us what needs attention after launch; rankings themselves remain uncertain.
Can you also plan and build the new site?
Yes, we plan site maps and build pages as part of our website work. We can consider the old URLs while planning the new page families. That connects the questions your existing pages answer to the places buyers will find them on the rebuilt site.
We already moved and lost traffic. Can you still help?
We can investigate after a move as well. We use Search Console to reconstruct the old pages, match them against the new site and examine the redirects, tags and sitemap. The findings identify code changes to make, with further checks of the affected pages after those changes go live.
Talk about your move before launch day
Discuss your planned move with the founders and engineers who run the experiments. We can talk about the launch date, what will change and which existing pages matter most to the buyers finding your site today.