You are about to redesign your website and someone warns you that a new site could wipe out your Google rankings overnight. Here is the honest version: a website change does not automatically cost you visibility, but a careless one can. Rankings usually slip for one reason, that old page addresses stop working and nothing redirects them to the new pages, or the words Google used to understand your pages get stripped out in the redesign.
This is for an established business whose site already gets found on Google and who does not want to hand that back. Below is what actually breaks rankings, how to map your URLs, the redirect checklist to run, and what not to touch. It does not cover whether to redesign or rebuild in the first place, or how to test the finished site.
TL;DR
- The core rule: every old URL should either stay the same or redirect with a permanent 301 to its closest match, and the content Google already ranks should survive the change.
- The biggest killer: changing page addresses with no redirects, or redirecting everything to the homepage.
- Map first: list every current URL and note which ones actually get traffic before you design anything.
- Preserve, do not rewrite: keep page titles, headings and body content for pages that already rank.
- Watch, do not panic: some movement in the weeks after launch is normal; a total drop that does not recover is a redirect or indexing problem to fix.
The short answer
A website change keeps its Google visibility when every old URL either stays the same or is redirected with a permanent 301 to its closest matching new page, and the titles, headings and body content Google already ranks are preserved. Rankings are lost mainly through broken URLs with no redirect, removed content, or accidentally blocking search engines on the new site. Redirects pass the old page's ranking signals across, but recovery is gradual, not instant.
What actually breaks rankings when a website changes
Most ranking loss during a redesign is not mysterious. It comes from a short list of preventable mistakes. This table is the one to keep next to you while the new site is being built.
| What changes | Why it hurts rankings | How to avoid it |
|---|---|---|
| Page addresses change with no redirect | The old URLs return an error, so the pages and their ranking history effectively disappear | Map every old URL to a new one and set a 301 redirect for each that moves |
| Everything redirects to the homepage | Search engines often treat a mismatched redirect as a removal, so page value is not carried over | Redirect each URL to the closest matching page, not a catch-all |
| The new site is left blocking search engines | A noindex tag or a robots.txt block carried over from the staging site tells Google not to list your pages | Remove the staging block before launch and confirm pages are indexable |
| Page titles and headings are rewritten | You lose the exact wording Google used to match your pages to searches | Keep titles and headings for pages that already rank; edit lightly, not wholesale |
| Body content is cut to look cleaner | Thin pages give Google less to rank, so relevance drops | Migrate the substance of ranking pages, even if the design changes around it |
| Internal links still point to old URLs | Visitors and crawlers hit dead links and redirect chains inside your own site | Update internal links to the new URLs, do not rely on redirects to patch them |
None of these are about design taste. They are about keeping the plumbing intact while the paint changes.
Map your URLs before anyone touches the design
The single most useful thing you can do is build a URL map before the redesign starts. It is a simple spreadsheet, and it is the document that saves your rankings.
- Export every current URL. Pull your existing addresses from your sitemap, your content management system, or a site crawl. You want the full list, not just the pages you remember.
- Mark which pages actually earn visibility. In Google Search Console, look at which pages get impressions and clicks. These are the ones that must not break. A page nobody finds matters far less than your top service page.
- Decide the fate of each page. For every URL, choose: keep the same address, change the address, merge into another page, or remove. Most of your important pages should stay or map cleanly to a close equivalent.
- Write the new URL next to each old one. This becomes your redirect list. Where a page is disappearing, note the closest surviving page it should point to.
With that map in hand, the redesign team knows exactly what to preserve and what to redirect. Without it, redirects get invented at the last minute, and that is where visibility leaks.
The redirect checklist to run at launch
Redirects are the mechanism that carries your existing rankings from the old site to the new one. Run this list as part of go-live, not as a fix weeks later.
- A 301 (permanent) redirect is set for every old URL whose address is changing
- Each redirect points to the closest matching new page, not a blanket homepage catch-all
- Redirects go straight to the final URL in one hop, avoiding chains of one redirect leading to another
- The staging
noindextag and anyrobots.txtblock are removed so the new pages can be indexed - An updated
sitemap.xmlis generated and submitted in Google Search Console - Internal links, menus and buttons point to the new URLs directly
- Redirects are tested after launch by visiting the important old addresses and confirming they land on the right pages
- Search Console coverage and impressions are watched over the following weeks for anything that drops and does not recover
The point of a 301 rather than a 302 is permanence. A 301 tells search engines the page has moved for good, so the signals the old URL earned move with it. A 302 says the move is temporary, which is not what you mean when a page is replaced.
What not to break on the pages themselves
Redirects protect the addresses. You still have to protect what lives at those addresses. For any page that already ranks:
Keep the page title and main heading close to what they were. That wording is part of how Google matched the page to searches, so a full rewrite for style reasons can cost you the match. Keep the substance of the body content, even as the layout, images and design change around it. A cleaner-looking page with half the text is a thinner page to rank. Keep the meta description sensible and specific, and keep image alt text where it described something useful.
You do not have to freeze your content forever. You can improve it. The distinction is between editing a page and gutting it. Improving a ranking page is fine. Replacing it with a shorter, prettier shell is how visibility quietly disappears.
What "losing visibility" really looks like
It helps to know what is normal and what is a warning sign, because a redesign almost always produces some short-term wobble.
Search engines have to recrawl the new URLs, follow the redirects, and reindex the pages. That happens over time, not at the moment you launch, and Google does not publish a guaranteed timeframe for it. So some movement in impressions and positions in the weeks after a change is expected, and it is not proof that something is broken.
A real problem looks different. If important pages return errors, if impressions for your main pages fall to almost nothing and stay there, or if Search Console reports pages excluded by a noindex tag, those point to a redirect gap or a blocking setting rather than normal settling. Catching that early is the whole reason you keep the URL map and watch Search Console after launch.
No one can promise an exact recovery timeline or that every position returns identically. What you can do is remove the avoidable causes of loss, which is most of them.
How this fits a TechTribe redesign
The reason to treat all of this as one job is that a redesign and its SEO preservation are the same project, not two. If the URL mapping and redirects are handled while the new site is being built, the pages that already rank keep pointing somewhere sensible from the first day the new site is live.
TechTribe redesigns established websites and handles content migration and redirects as part of the work, rather than leaving you to reconstruct a redirect map afterwards. If you want the wider picture first, our guide on redesign versus rebuild helps you choose the path, and once the new site is live our post-redesign testing checklist covers confirming that forms, WhatsApp, email and the redirects themselves all work. If you want to understand the ranking side more deeply, our SEO guide for Zimbabwe businesses sits alongside this one.
Your next step
Before you approve any redesign, build the URL map. List every current address, mark the pages that actually earn visibility in Search Console, and decide for each one whether it stays, moves, or merges. That single spreadsheet, plus a 301 redirect for everything that moves, prevents most of the ranking loss people fear from a website change.
If you would rather have the mapping and redirects handled as part of the build, talk to us about your redesign and we will plan the change around the pages that already work. If you have a specific question about your current site first, contact us and we will point you in the right direction.
Author: Simon Updated: May 2026
Redesign without losing your Google visibility
TechTribe redesigns established Zimbabwe websites with URL mapping and 301 redirects handled as part of the migration, so the pages that already rank keep pointing somewhere. Tell us about your current site and we will plan the change around what already works.
About the author
Simon
Simon writes about websites, lead capture, and digital growth for real estate agencies in Zimbabwe.
