Website Redesign Without Losing Your Google Rankings

The old website looks dated and the developer has a fresh design ready, perhaps on Wix or Shopify instead of WordPress. Some time after launch, enquiries from Google thin out and nobody is sure why.

The design is rarely the cause. More often, old addresses changed with no redirects, or pages that ranked lost most of their text in the rebuild. Sometimes a setting meant for the test site comes along to the live one. Each of these can be avoided, mostly with work done before launch.

First, decide whether your URLs need to change at all

If only the look changes and every page keeps its address, much of the risk goes away. Google splits site moves into two guides, one for moves that keep the URLs (a new host, say) and one for moves that change them. If your current addresses are clean and readable, keep them and have each page rebuilt at its existing URL.

Sometimes a change can't be avoided. Shopify puts pages in fixed folders such as /pages/ and /products/, and a new domain changes every URL. Even then, change as little as you can at once. Google's Change of Address help page says keeping the same site architecture helps pass signals across, while a move combined with a redesign will probably cost some traffic.

Before launch, list every page and protect the ones that rank

You can't redirect pages you have forgotten about. List every current URL in a spreadsheet, using your sitemap, a crawl of the live site and an export of the Pages tab in the Search Console Performance report over the longest date range it offers. Google's site move guide suggests the same kind of list, starting with your most important URLs.

Next to each URL, note its clicks and, if you track them, the enquiries it brings. The pages at the top of that list need the most care, because a new design often arrives with less text. A service page with 800 useful words can turn into three lines and a slider, and if it ranked because it answered real questions about cost or recovery time, that reason is gone. Keep the content or improve it, along with any title tag or heading that already wins clicks.

Map each old address to its closest new one

Add a column with the new URL for every old page. Most rows are simple: old service page to new service page, old post to the same post at its new address. Merged pages can both point to the page that replaced them.

Don't send everything to the home page. Google's site move guide warns that redirecting many old URLs to one irrelevant destination, such as the home page, might be treated as a soft 404. That is Google's term for a page that loads but looks empty, or says "not found" without returning a real 404 code. Where an old page has nothing to replace it, the guide says to return a 404 or 410.

Use permanent, server-side redirects

Google recommends permanent server-side redirects, meaning a 301 or 308. After a permanent redirect Google shows the new address in results; after a temporary 302 it usually keeps showing the old one. WordPress can do this with a plugin, and Wix and Shopify have redirect settings built in. Load them from your mapping sheet and test them before launch.

Point each old URL straight at its final address, as Google advises, rather than through a chain. If some URLs already redirect from an earlier redesign, update them to skip the middle step. The site move guide says to keep redirects for as long as possible, generally at least a year. We would leave them in place for good.

Keep the test site out of Google, then unblock the real one

Developers usually build the new site on a temporary address first. Google says private content should be password protected, and a noindex tag tells Google not to show a page in results. A robots.txt block alone is weaker: Google says a blocked URL might still be indexed if other pages link to it.

The bigger risk is the block travelling to the live site at launch. A leftover noindex tag can keep the whole new site out of results, and WordPress's "Discourage search engines" box, left ticked, asks search engines not to index it. A robots.txt file still saying Disallow: / stops Google crawling the site. On launch day, open yoursite.com/robots.txt yourself, then run the URL Inspection live test on the home page and your main service page.

If the domain changes, use the Change of Address tool

Moving to a new domain, say from .in to .com, means extra work in Search Console. Verify every version of both sites in Search Console, www and non-www included. Once the redirects are live, submit a Change of Address from the old site's property, once for each version of the old domain. You must own both properties under the same Google account, and the old home page must 301 redirect to the new one.

Google says the tool forwards signals for 180 days and asks you to keep the redirects at least that long. It also recommends paying for the old domain for at least a year. Renew it for longer, because a lapsed domain takes every redirect with it.

Launch week checklist

1. Open 15 or 20 old URLs from your sheet and confirm each lands on the right new page in one step.
2. Submit the new sitemap in the Sitemaps report in Search Console.
3. Update menus and in-text links to point at the new URLs directly, as the internal links article explained.
4. Change the website link on your Google Business Profile. Google reviews edits before they go live, so check that it updated.
5. Point Google Ads final URLs and Meta ad links at the new pages. After a domain change, Google's destination policy treats a final URL that redirects to another domain as a mismatch (unless Google approved it in advance), and such ads can be disapproved.
6. Update social profiles, directory listings and email signatures, and check that printed QR codes still land on the right page.
7. New themes often drop tracking code, so confirm conversion tracking and analytics tags still fire. On a real phone, tap the call and WhatsApp buttons and send a test enquiry.

What to watch over the following weeks

Google's site move guide says to expect temporary ranking fluctuation during a move, and that rankings settle down over time. It adds that a small to medium-sized site can take a few weeks for most pages to move. An early dip is not, by itself, proof that something broke.

Check the page indexing report covered earlier every few days at first. A rising "Page with redirect" count is expected: those are your old URLs pointing to the new ones. "Not found (404)" can show addresses that slipped through the mapping, so redirect any that had clicks or links. "Redirect error" can mean a chain that is too long or a loop. A "Soft 404" may be a page that lost its content in the redesign, or old URLs sent to the home page.

In the Performance report, compare clicks page by page against your pre-launch export. If a page that used to bring enquiries dropped and stayed down, check its redirect first, then its content against the old version. Fix that one cause rather than reworking the whole site.

FAQ

Do I need the Change of Address tool if I'm only moving from WordPress to Wix?

Not if the domain stays the same. The tool is for moving to a different domain or subdomain. On the same domain, redirect any URLs that changed and submit the new sitemap.

Should I request indexing for every new page?

No. URL Inspection has a daily limit on indexing requests, so save it for your most important pages. For the rest, Google suggests a sitemap, which you submitted at launch.

Will a new design hurt my rankings if the URLs stay the same?

It can, though the risk is lower. Common causes are text cut from pages that ranked, a slower site on phones, broken internal links or a leftover noindex tag. If the content and the page speed hold up, a fresh design on its own is rarely a problem.