A plain guide to relaunching your website without losing search traffic: redirects, URL structure, sitemaps, and the mistakes that make rankings disappear.

We relaunched our own site this fall, so this post comes with a fresh example. When we opened Google Search Console afterward, the Pages report listed twelve addresses returning "not found." Eleven of them were /products/ URLs from a storefront version of mentee.ca that has not existed for years. Google still remembered them. It had been checking every few months, finding nothing, and quietly counting that against us.
Ten minutes of redirects fixed it. The point is that nobody on our side knew those URLs existed until we looked. That is the whole story of site migrations: the damage is in what you did not list.
The redirect map is the actual project
Before anyone builds anything, pull a complete list of your current URLs. Every page, every post, every PDF. Start from the sitemap, then cross-check against analytics and Search Console, because the sitemap always misses something. Old campaign pages. Tag archives. The 2019 annual report PDF that still gets downloads. The storefront nobody remembers.
Then decide, one row at a time, where each URL goes on the new site. If a page had traffic or links pointing at it, it gets a new home or a permanent redirect to the closest related page. If content is being retired, that should be a decision someone made on purpose and wrote down, not something discovered after launch.
A 301 redirect tells search engines the page moved and that its history should follow it. Skip it and every renamed page starts from zero.
We will defend this opinion: the redirect map deserves more review time than the design. Nobody wants to hear that during a redesign. But migrations rarely lose rankings because a button is the wrong blue. They lose them because forty rows of a spreadsheet never made it into the server configuration.
Keep the URLs you can
When we rebuilt the Knowledge Weavers Hub for First Nations University of Canada, the English and French structure stayed at /en and /fr. Unchanged URLs need no redirect and carry their history untouched. When you genuinely must change one, keep it readable and close in spirit to the old one. A community health page should still say "health" somewhere in the address, not /page?id=4187.
The three mistakes that actually tank traffic
Everything redirects to the homepage. It looks tidy. It is also the fastest way to tell Google that none of your old pages matter, and rankings for those specific topics evaporate. Redirect to the closest equivalent page, every time.
Redirect chains. Old URL points to a 2021 URL, which points somewhere newer, which now returns an error because someone renamed it last spring. Each migration stacked on the last and nobody flattened the chain. Every old URL should reach its final destination in one hop. Crawl the full list before launch and again the morning after, because redirects have a way of behaving differently in production. (Our own site still has one two-hop chain, from http://www to https://www to the main domain, because the hosting platform forces the secure hop first. Harmless, but we know it is there.)
Changing every URL because the new platform prefers it. If you can keep the structure, keep it.
Launch week
The day the new site goes live:
- Submit the new sitemap in Google Search Console. Forgetting this means Google finds your changes by wandering into them over weeks instead of being handed the map.
- Give every page in the sitemap a current "last modified" date, so Google knows they changed. We did this for all 34 of ours.
- Submit the URL list to IndexNow as well, which covers Bing and the other engines in one request.
- Check that
robots.txtis not still carrying a "disallow" line from the staging site. That single leftover can block an entire relaunch. - Use the URL Inspection tool to request indexing on your most important pages. Google allows roughly ten requests a day, so start with the pages that earn you inquiries.
Then expect a dip. Rankings usually wobble for two to six weeks after a migration while everything is re-crawled. With a clean redirect map and a genuinely better site, traffic that sags for a month usually climbs past the old baseline. The dip is normal. The recovery is what you are watching for.
When the dip is not a dip
Check Search Console weekly for the first six weeks. Coverage errors, spikes in "not found," pages falling out of the index. A wobble that levels off and climbs is fine. A steady slide with no floor means something is broken, and it is very often a hole in the redirect map rather than anything mysterious.
Planning a migration and want a second set of eyes on the plan? See our digital platforms work or talk to us.



