How to Redesign a Website Without Losing Google Rankings

Will a redesign hurt your rankings?

A redesign can hurt rankings, but the common causes are avoidable: URLs that vanish, content that gets cut, and settings that block Google.

New colors and layouts aren't usually the issue. The risk grows when a redesign also changes addresses, removes pages or rewrites what was working. Google's guidance on site moves with URL changes is the best starting point, and we follow it here. It also advises changing one thing at a time where possible, such as a new domain first and a new layout later.

The steps below are the order we'd work in. Where we've done the same thing on our own site, we'll show you how.

Step 1: Take an inventory

Start by listing every URL your site has now, because you can't protect a page you've forgotten exists.

Google suggests pulling from your sitemaps, your highest-traffic pages, server logs, your content management system and the Links report in Search Console. Include PDFs and images people may link to directly.

Export your Search Console performance data at the same time. That's your baseline, and old data is much easier to save before a move than to piece together after it.

Step 2: Keep what earns traffic

Keep any page that earns search traffic or useful links unless you have a clear reason to drop it.

Mark each URL as keep, merge or remove. A page can look dated and still be bringing in customers, so check the numbers before you decide. A good example is an old "pricing" page nobody on the team likes but which still gets found.

For content you remove on purpose, Google says to return a 404 or 410. Don't redirect it to something unrelated just to avoid an error page.

Step 3: Build the URL map

A URL map is a simple list that pairs every old address with its new one, and it's the document your redirects get built from. Keep existing URLs wherever you can, because a URL that doesn't change needs no redirect at all.

Google allows several old pages to point to one new page when it truly combines them. What it warns against is sending many old URLs to one irrelevant destination, such as the home page, since that may be treated as a soft 404.

Step 4: Set up 301 redirects

Use permanent redirects handled on the server, because those tell Google to show the new address in results. Google treats 301 and 308 as permanent, and 302, 303 and 307 as temporary. With a temporary redirect, the old page can stay in results. JavaScript redirects are a fallback for when nothing better is possible, because Google may never see one if rendering fails.

Point each redirect straight at the final page rather than chaining through old versions. Google also says permanent redirects don't cause a loss in PageRank, so they're worth doing properly.

We've done this on our own site. When we renamed our Blog section to Insights on July 14, 2026, we added rules in our netlify.toml config sending /blog/:slug to /insights/:slug/. The rule goes straight to the final trailing-slash address in one hop, so no chain is created. Retired pages follow the same pattern: /webdevelopment goes to /website-design/, and /pricing goes to our cost calculator, the page that now answers that question.

Keep your redirects for as long as you can. Google says at least a year, and leaving them in place indefinitely is reasonable too.

Step 5: Keep titles and content where they work

If a page already ranks, carry over its title and main content unless you have a reason to change them. Our advice is to treat new design and new words as separate decisions. A page can get a new layout and keep the text that earned its position.

Watch for the common loss here. Designers like shorter pages, so long explanations get trimmed for looks, and they may be the very thing searchers came for. If you do rewrite a top page, keep the questions it answers, and save the old version so you can compare later.

While you're in there, update internal links to point to the new URLs directly. Give each new page a canonical tag that points to itself, as Google recommends.

Step 6: Keep staging out of Google

Mark your staging site noindex so unfinished copies stay out of results, and plan when that rule comes off. Google lists leftover noindex and robots.txt blocks among the common mistakes in a move.

We solved this by tying the rule to the environment instead of relying on memory. In our Layout.astro, deploy previews and branch deploys automatically get noindex, nofollow on every page, and production builds don't. A preview can't be indexed by accident, and no one has to remember to take a tag off at launch.

Step 7: Run launch checks

Launch day comes down to confirming that redirects work and that nothing blocks Google. Work through this list:

1. Turn on the redirects, then test them against your URL map with a script or Search Console's URL Inspection tool.
2. Confirm no page still has a temporary noindex, and read your new robots.txt to make sure it blocks only what you meant to block.
3. Check that canonical tags point to the new URLs. Pick one version of your address and stick with it. Ours is the apex domain with a trailing slash, and our Netlify default hostname 301s there.
4. Submit the new sitemap in Search Console and remove the old one.
5. Keep your analytics and Search Console verification tags on the new site.
6. Test the things that make money: forms, booking and checkout.
7. Update your social profiles, ad landing pages and any high-value links you can get changed.
8. If you changed domain or subdomain, use the Change of Address tool in Search Console.

Google also suggests launching during a quieter traffic period where you can, and making sure the server can handle extra crawling.

Step 8: Monitor Search Console

Check Search Console closely in the first weeks, because that's when a broken redirect can still be fixed before it costs you much. We'd look daily for the first week and weekly after that.

• Sitemaps: the old sitemap's count should fall as the new one's grows, according to Google.
• Indexing and crawl errors: look for a spike, then check the affected URLs against your map.
• Performance: new URLs should start picking up impressions and clicks. Compare them with the baseline you saved.
• Analytics and server logs: watch for 404s on pages that should redirect, and make sure leads are still arriving.

What's normal after a move

Some movement is normal: Google says to expect temporary fluctuation in rankings during a move, and that they should settle over time.

Google says small and medium sites may take a few weeks for most pages to move, and larger sites longer. It also says Googlebot has to visit each old and new URL at least once, and that crawling of the new site temporarily increases. More Googlebot activity in your logs isn't a warning sign.

These do call for action: pages returning errors, redirects pointing to missing pages, a noindex left on live pages, a sitemap still listing old URLs, or one important page dropping while the rest hold steady.

No one can promise that rankings stay exactly where they are, and that includes us. What careful planning does is remove the avoidable causes. If you'd like help with that, here's how our website redesign service works.

Sources

All pages checked on 2026-11-03.

• Google Search Central guide to site moves with URL changes, on URL mapping, redirects, launch steps, monitoring and timing.
• Google Search Central guide to redirects, on permanent and temporary redirects and how Google treats each type.

Written by Romik Hacobian, founder of Media City Design, a Burbank web design studio since 2021.