How to Redesign Your Website Without Losing Your Google Rankings

Picture a company that launches its new website on a Monday. The design is a clear step up, the board has signed off, and the marketing team is relieved to finally share the link.

Three weeks later, the inquiries from Google have slowed. Someone checks the old blog posts that used to bring in a steady share of leads, and each one now opens on an error page. The articles were moved to new addresses during the rebuild, and nobody told Google where they went.

The new website was fine. The rebuild left out one piece of work: carrying the old site's standing in search across to the new one. In our experience, most of that work is planning, and it happens before anyone opens a design file.

In short: list every page on your current site before the redesign starts, decide what happens to each one, and point every old address that matters to its new home with a permanent redirect. Then check Search Console closely in the weeks after launch. A short dip is normal. A lasting drop usually means something was left out of that list.

Why do rankings drop after a redesign?

Because Google ranks individual pages, and a redesign tends to change the pages Google knows.

Your current site has built up years of standing one address at a time. A service page ranks for a phrase. An old article picks up links from other sites. When those addresses change, or the pages behind them disappear, Google has to work out the new arrangement from scratch, and some of that standing does not carry over on its own.

The usual causes are ordinary:

• Addresses change without redirects. The new platform uses a different URL structure, or the team renames pages, and the old links lead nowhere.
• Pages are dropped. A content cleanup retires pages that were still bringing in search traffic.
• Content gets thinner. A long, useful page is cut down to a few lines to suit a cleaner design.
• Titles and headings are rewritten. The words that matched what people search for are replaced with brand language.
• Staging settings reach the live site. A test site is usually hidden from search engines, and sometimes that setting goes live with the launch.

Even with all of this handled, Google says to expect temporary fluctuation during a move, and that for a medium-sized site it can take a few weeks or more before the new addresses replace the old ones in search results. So the realistic goal is a short dip that recovers.

What should you do before the new site is designed?

We start with an inventory of the current site.

Before the sitemap for the new site is drawn, list every page on the current one. Your sitemap file is a start, but it often misses older pages. Add the pages that show up in Google Analytics and Search Console over the past year, and the pages that other websites link to. On a site that has been live for several years, this list is usually longer than anyone on the team expects.

Then give each page a decision: keep it as it is, rewrite it, merge it with another page, or retire it. Make these decisions with the search data in front of you. A page the team considers outdated may still be the one bringing in inquiries, and that should be known before it is cut.

This step adds time early in the project, which is why we plan for it from the start. As our website timeline guide notes, migrating years of existing content often takes longer than writing fresh pages.

Which pages need protecting?

The ones doing work for you right now. We usually sort them into three groups:

• Pages that bring in search traffic. Search Console shows which pages appear in Google and which queries lead to them. Sort by clicks over the past twelve months.
• Pages that other sites link to. Links from news sites, partners, government directories and industry associations are hard to earn again. Search Console lists your most-linked pages.
• Pages that lead to inquiries. If a page regularly comes before a contact form submission in your analytics, it is part of how you get business, even when its traffic is modest.

Older articles and resource pages often sit in all three groups. They are also the pages most likely to be left out of a redesign, because nobody on the current team wrote them.

What is a redirect map, and who should own it?

A redirect map is a spreadsheet with two columns: every old address that matters, and the new address it should send people and search engines to.

Each row becomes a permanent redirect, which tells Google the page has moved for good and that its standing should follow it. Google recommends permanent server-side redirects, the kind known as 301 or 308. Webflow lets you import them in bulk, and WordPress does the same through common plugins.

A few rules we follow when building one:

• Send each page to its closest match. An old service page goes to the new page for that service, not to the homepage. Pointing everything at the homepage is the common shortcut, and it gives up what each page had earned.
• Avoid chains. If a page has moved before, point the oldest address straight to the newest one rather than through each step.
• Keep the addresses that do not need to change. If a URL is clean and still describes the page, keep it.

The map needs one owner on the project team, usually the vendor, and a reviewer on your side who knows which pages matter to the business. It should be finished and checked before launch day, not written during it.

Does changing platforms make it riskier?

It adds work, because each platform arranges its addresses differently.

A WordPress blog might keep articles at the root of the site or under the date they were published. Webflow places every content-managed page under a collection folder, which is why the articles on our own site sit under /post/. Moving between the two changes almost every article address, so every one of them needs a row in the map.

This should not keep you on a platform that no longer suits you. Count the migration in the plan from the start. Our comparison of Webflow, WordPress and Shopify covers how we decide when a move makes sense.

What needs checking on launch day?

This is the list we work through, in order:

• Redirects are live. Test a sample of old addresses, including the pages you marked to protect.
• The site is visible to search engines. Confirm that any setting used to hide the staging site has been turned off.
• Titles and descriptions carried over. Each kept page has its search title and description in place.
• A new sitemap is submitted in Search Console. This tells Google where the new pages are.
• Analytics and forms work. Without analytics, you will not be able to tell whether traffic recovered.
• The domain change is reported, if there is one. If the site is also moving to a new domain, Google's Change of Address tool in Search Console applies. It is not needed when the domain stays the same.

Make sure your company holds owner access to Search Console before this day comes. Our website ownership checklist explains why that seat should be yours, not only the vendor's.

What should you watch in the weeks after launch?

We look at three things, every week for the first two months or so:

• Pages that return errors. Search Console reports addresses Google tried to reach and could not. Each one is a missing row in the redirect map, and adding the redirect fixes it.
• Clicks on your protected pages. Compare them with the same weeks before launch. A gradual return is the expected pattern.
• Inquiries. Search traffic matters because of what it leads to. If inquiries hold steady while rankings settle, the move is on track.

Keep the redirects in place for the long term. Google advises keeping them for at least a year, and there is little reason to remove them after that. Old links in emails, documents and other websites will keep sending people to those addresses for years.

Does this add to the cost or the timeline?

Some. The inventory and redirect map are planning work, done mostly by a strategist and a developer, and they scale with the size of the current site. A twenty-page company site is a short exercise. A university or institution with years of news, programs and documents is a project of its own, and should be scoped as one. Our website cost guide covers the typical ranges by type of site, and the website brief guide explains how to describe your current site, including which pages still matter, so vendors can quote this part properly.

If a quote for a redesign says nothing about redirects or existing content, ask about it before you sign.

Questions we get asked

Will we lose our rankings if we redesign?

Some movement in the first weeks is normal, even on a well-planned move. A lasting drop usually traces back to pages or redirects that were missed, which is why the planning matters.

Can we change our page addresses at all?

Yes, as long as each old address redirects to its new one. We change them only when the new address is clearly better.

Should we change our domain at the same time?

Where possible, we do one move at a time. A redesign and a domain change together make it harder to tell what caused any drop, and harder to fix.

We already launched and traffic fell. Is it too late?

Usually not. Redirects can be added after launch. Start with the error report in Search Console and an old sitemap or analytics export, and rebuild the missing ones. The sooner they go in, the better.

Where we stand

This is how we run redesigns: migration is part of planning. We map the current pages, keep what works, retire what does not, and set up redirects so nothing valuable is lost. We review the redirect map with the client before launch, and check Search Console with them through the first weeks after.

If you are planning a redesign or a platform move and want a read on what your current site has built up, send us the address. We will tell you which pages we would protect first, and why.