If you’ve read our guide on the signs your website needs a redesign, you might already know your site needs to change. What stops a lot of Uganda businesses from actually doing it isn’t the redesign itself. It’s the fear of what happens to the Google rankings and traffic the old site already has.
That fear is reasonable. A badly handled migration can genuinely tank a site’s traffic. But “badly handled” is the key phrase. A migration that follows a proper checklist rarely loses meaningful ground, and what ground it does lose is usually temporary. This is the checklist we use ourselves.
Key Takeaways
What Actually Counts as a “Migration”
People tend to picture “migration” as moving to a brand new domain, but the term covers a wider set of changes than that. Any of the following puts your existing Google rankings at risk in the same basic way:
- A full redesign that changes your page URLs, even if the domain stays the same.
- Switching platforms, for example from a page builder to WordPress, or from WordPress to a custom build.
- Changing your domain name entirely.
- Moving from HTTP to HTTPS, or from a non-www to a www address (or the reverse).
- Restructuring your navigation or URL slugs, even without a full visual redesign.
If your redesign is only changing colors, images, and layout while every URL stays exactly the same, most of this checklist doesn’t apply to you. The risk shows up specifically when URLs change, because that’s what breaks the connection between what Google has already indexed and what now lives at that address.
Before You Launch Anything
1. Get a full list of every URL on the old site
You can’t redirect what you haven’t accounted for. Pull a complete list from your sitemap, your CMS’s page list, and Google Search Console’s indexed-pages report, since these three sources sometimes disagree, and the gap between them is often where forgotten pages hide.
2. Check which of those pages actually bring in traffic or rankings
In Google Search Console, look at which pages get clicks and impressions. These are the pages that need the most careful handling in your redirect map. A page with zero traffic and zero rankings can often be retired without a redirect at all, but a page quietly bringing in steady search traffic needs a direct, accurate 301.
3. Build a one-to-one redirect map, not a blanket redirect
This is the step that determines whether a migration goes smoothly or badly. Every old URL should point to its closest topical match on the new site. A page about “website hosting Uganda” should redirect to the new page that covers website hosting, not to your homepage. Redirecting everything to the homepage is the single most common migration mistake, and it throws away most of the ranking value those pages had built up.
[PERSONAL EXPERIENCE] We’ve done exactly this on our own blog. When we consolidated three older posts that were competing with each other for the same keyword into one stronger article, we didn’t just delete the weaker posts. We set up permanent redirects from each old URL straight to the post that replaced it, so any backlinks or bookmarks pointing at the old pages still land somewhere relevant instead of hitting a dead end.
4. Use 301 redirects specifically, not 302
A 301 tells Google “this page has permanently moved, transfer its ranking signals to the new address.” A 302 says “this is temporary,” and Google treats it that way, largely withholding those signals from the new URL. If your developer or platform defaults to 302 redirects, that’s worth catching before launch, since it’s an easy mistake with a real cost.
5. Avoid redirect chains
A redirect chain happens when page A redirects to page B, which then redirects to page C. Each hop leaks a little ranking value and slows down how quickly search engines can follow the chain. Point every old URL directly at its final destination in one hop.
6. Note every page’s title, meta description, and header structure before you tear it down
If a page currently ranks well, its existing title and heading probably have something to do with that. Carrying the working elements of a high-performing page into its redesigned version, rather than rewriting everything from scratch out of habit, protects rankings you’ve already earned.
On Launch Day
7. Submit your new sitemap in Google Search Console
This tells Google where to find your new page structure without waiting for it to be discovered naturally, which speeds up recrawling.
8. Use the Change of Address tool only if you’ve actually changed domains
Google Search Console’s Change of Address tool flags a domain move directly to Google and speeds up recrawling, but it only applies when the domain itself has changed (moving from an old domain to a new one). A redesign or replatform on the same domain doesn’t use this tool. Submitting your redirect map and new sitemap is what matters there instead.
9. Test a sample of your redirects manually
Before assuming the redirect map worked, spot-check a handful of old URLs yourself, especially the highest-traffic ones. Confirm each one lands on the correct new page and returns a real 301 status, not a soft 404 that just displays an error page while technically returning a 200.
10. Update your internal links
Redirects protect external backlinks and old bookmarks, but they shouldn’t be your permanent internal linking strategy. Go through your own site’s navigation, footer, and in-content links and point them directly at the new URLs. Relying on redirect hops for your own internal links adds unnecessary load and signals a less carefully maintained site.
After Launch: What to Expect and What to Watch
Some traffic dip is normal, even when you do everything right
Search engines don’t instantly transfer rankings the moment redirects go live. Googlebot typically acknowledges a change within one to two weeks, and rankings can fluctuate for several weeks after that while Google re-evaluates the new URLs. A short-term dip somewhere in the 20-30% range that recovers within a few weeks is within the range of normal. It doesn’t automatically mean something went wrong.
Keep old redirects live for at least 180 days
Google’s own guidance is to maintain redirects for a minimum of 180 days, longer if you’re still seeing search traffic arrive through the old URLs. Removing redirects too early, because the old hosting contract expired or someone assumed the migration was “done,” is a common way migrations quietly lose ground months after launch.
Monitor Search Console weekly, not daily
Checking rankings every day during a migration mostly just adds stress, since normal week-to-week fluctuation can look alarming in isolation. A weekly check of impressions, clicks, and average position in Search Console gives a clearer picture of the actual trend.
Full recovery is measured in months, not days
Most well-executed migrations stabilize within a few weeks to a couple of months. Larger or more complex sites can take longer, and Google has described some site moves as a gradual transition that can continue settling for months afterward. Going in with that timeline in mind, rather than expecting an overnight bounce-back, makes the normal dip far less alarming when it happens.
The Single Biggest Mistake to Avoid
If there’s one thing worth repeating: don’t redirect your whole old site to your new homepage “to keep it simple.” It feels like the fast option, and it’s the one that does the most damage. Each of your old pages built its own individual signal with Google over time. A blanket homepage redirect throws all of that away at once instead of transferring it to where it actually belongs.
Frequently Asked Questions
Will I lose my Google rankings during a website migration?
You’ll likely see some temporary fluctuation, even with a well-executed migration, but a proper redirect map and correct technical setup should preserve your rankings over the following weeks to months. Losing rankings permanently is usually a sign that redirects were missing, incorrect, or pointed at the wrong pages.
How long should I keep my old website’s redirects active?
At least 180 days, per Google’s own guidance, and longer if you’re still seeing traffic coming through the old URLs after that point. After roughly six months without redirects, Google stops treating the old and new sites as related.
Do I need to use the Change of Address tool for a redesign?
No. That tool is specifically for a full domain change, old domain to new domain. A redesign or replatform that keeps the same domain doesn’t need it; your redirect map and updated sitemap do the equivalent job in that case.
Should I redirect low-traffic pages too?
If a page genuinely has no traffic and no rankings, it’s reasonable to let it 404 or retire it without a redirect. But check Search Console first. A page that looks unimportant in your own analytics can still be quietly ranking for a keyword you’re not tracking closely.
If you’re weighing whether your site needs this kind of change at all, our guide on the signs your website needs a redesign is the place to start. And if speed or mobile performance is part of what’s driving the redesign conversation, our guide to mobile-first design in Uganda covers what the rebuilt site should get right from day one.