How to Redesign Your Website Without Losing Your Google Rankings

Why redesigns often hurt rankings

A new website should bring more customers, not fewer. Yet many businesses see their Google traffic drop after a redesign. The cause is rarely the new design itself. It is usually what got lost along the way: pages deleted without redirects, URLs changed, text cut down, titles rewritten, or a staging setting that blocks Google left on at launch.

The good news is that these problems are predictable and avoidable. Here is the process we recommend for any redesign or platform change, whether you are moving from Wix to WordPress, rebuilding a Shopify store or simply refreshing your theme.

Preparation: inventory, content and URL mapping

Step 1: Take a complete inventory before touching anything

Before the design work starts, record what you have and what is working. Gather:

• Every URL on the current site, using a crawler, your XML sitemap and your CMS page list.
• Your top pages by traffic and conversions from Google Analytics and the Performance report in Google Search Console.
• The queries each important page ranks for, also from Search Console.
• Pages with external links, from the Links report in Search Console.
• Titles, meta descriptions, headings and structured data for your key pages.

Save this as a spreadsheet and keep a full backup of the old site. This is your baseline for comparing results after launch.

Step 2: Keep what ranks, improve what does not

Pages that bring traffic rank because of their content. If the new design replaces a detailed service page with three lines of text and a big photo, expect to lose ground. For each high-value page:

• keep the main content, or improve it, rather than shortening it;
• keep the same topic and search intent;
• carry over or improve the title tag and meta description;
• keep internal links pointing to it from relevant pages.

Low-value pages, such as outdated news or thin duplicates, can be merged or removed, but each one still needs a redirect to the most relevant remaining page.

Step 3: Map old URLs to new URLs

The safest choice is to keep your existing URLs whenever possible. If the structure must change, build a redirect map: one column with every old URL, one with its new equivalent. Google’s own site-move guidance recommends redirecting each old URL to its most relevant new page, not sending everything to the homepage.

Also list images and PDF files that receive traffic or links, since they need redirects too if their addresses change. A shared spreadsheet makes it easy for your web team to review the mapping before anything goes live.

For bilingual sites, map French and English pages separately, and make sure hreflang annotations on the new site point to the correct language versions.

Redirects and staging

Step 4: Set up 301 redirects correctly

A 301 is a permanent redirect. It tells browsers and Google that the page has moved for good, and it passes visitors and most ranking signals to the new address. Good practice:

• use server-side 301 redirects, not JavaScript or meta refresh;
• redirect directly to the final page and avoid chains (A to B to C);
• keep redirects in place for at least a year, and ideally indefinitely;
• update internal links so they point straight to the new URLs instead of relying on redirects.

Step 5: Build and test on a staging site

Work on a copy of the site that the public and Google cannot see. Block it with a password or a noindex setting. Before launch, test:

• every redirect in your map;
• mobile display and loading speed;
• forms, checkout, phone links and booking tools;
• analytics and conversion tracking;
• French and English versions, including the language switcher.

Step 6: Launch day checklist

1. Remove the staging password and any noindex tags or “discourage search engines” setting.
2. Check that robots.txt does not block important sections.
3. Activate redirects and spot-check your top 20 old URLs.
4. Confirm HTTPS works and the non-www and www versions redirect to one version.
5. Submit the new XML sitemap in Google Search Console.
6. If the domain changed, use the Change of Address tool in Search Console.
7. Update your Google Business Profile and other listings if URLs changed.

Step 7: Monitor after launch

Some ranking movement in the first weeks is normal while Google recrawls the site. Google notes that for a medium-sized site it can take a few weeks or more for new URLs to fully replace old ones. During that time, check Search Console at least weekly:

• Page indexing report: watch for new 404 errors, blocked pages or pages excluded by noindex.
• Performance report: compare clicks and impressions for key pages and queries with your baseline.
• Sitemaps: confirm the new sitemap is read without errors.

Fix any 404 on an old URL that had traffic or links by adding the missing redirect. Most problems found in the first month can be corrected before they cause lasting damage. Also keep an eye on your leads and sales, not just rankings: if contact form submissions or phone calls drop, test your forms and tracking right away.

Common redesign mistakes

The bottom line

A redesign does not have to cost you your Google rankings. Inventory your existing pages, keep the content that works, redirect every changed URL to its true equivalent, test on staging and watch Search Console closely after launch. Treat SEO as part of the project from day one, not an afterthought. Loubane builds this migration process into every website redesign we deliver.

Read also