How to Redesign Your Website Without Losing Your Google Rankings

A redesign is one of the most common reasons a small business suddenly drops in Google. The new site looks better, but calls slow down, and weeks later someone notices the traffic graph fell off a cliff on launch day.

It’s almost always preventable. Search engines don’t punish redesigns. They lose track of pages that moved or disappeared. Here’s how to make sure that doesn’t happen.

Why do rankings drop after a redesign?

Google ranks individual pages, each at its own address. When a redesign changes those addresses or the content on them, Google has to work out what happened. If you don’t tell it, it may decide the pages are simply gone.

The usual causes are:

• URLs that changed without redirects. The old page returns an error, and whatever ranking it had goes with it.
• Content that got cut. A long, useful page becomes a short, pretty one, and stops answering the question it used to rank for.
• Search engines blocked by accident. Settings from the development site come along to the live one.
• Lost internal links. A page that used to be linked from the menu and footer ends up buried.
• A slower site. Heavier pages can hurt the experience on mobile. See why website speed matters for Sedona businesses.

Each of these is fixable, and most are avoidable with a bit of planning.

Which pages do you need to protect?

Before any design work, export a list of every URL on your current site. Your XML sitemap is a good start, but it may not list everything, so also check Google Search Console. Our Search Console guide explains where to find each report.

Mark the pages that matter:

• Pages that bring in search traffic. The Performance report, filtered to the Pages tab, shows which URLs get impressions and clicks.
• Pages other websites link to. The Links report in Search Console lists your most-linked pages.
• Pages people reach directly. URLs printed on signs, cards, menus or packaging, linked from your Google Business Profile, or used in old email campaigns and ads.

If you’re planning the project now, add this inventory to the rest of your prep. Our website planning checklist has a short section on exactly this.

Keep, redirect or remove: what should happen to each URL?

Go through the list and decide what happens to every marked page:

Situation	What to do	Why
Page stays, same topic	Keep the exact same URL	Nothing for Google to relearn
Page stays, URL must change	301 redirect old URL to new URL	Passes visitors and signals to the new address
Two pages merged into one	Redirect both old URLs to the merged page	Combines their value in one place
Page removed, close equivalent exists	Redirect to the closest equivalent	Keeps visitors on a relevant page
Page removed, no equivalent	Let it return a 404	Honest, and better than a misleading redirect

The simplest way to protect a page’s rankings is to keep its address. If /services/wedding-photography ranks well today, the new site should use the same URL unless there’s a strong reason to change it.

Do this: redirect /our-tours/sunset-jeep-tour to the new sunset tour page.

Not this: redirect every old tour page to the homepage. Google may treat those as if the pages no longer exist, and visitors land somewhere that doesn’t answer what they clicked for.

How do you build a redirect map?

A redirect map is a simple spreadsheet with two columns: old URL and new URL. Every page you marked in your inventory should have a row.

A few habits make it reliable:

• Use full paths consistently, such as /about-us rather than a mix of full and partial addresses.
• Point straight to the final page. If an old URL already redirects somewhere, update the original redirect rather than adding another hop. Chains slow things down and make mistakes harder to spot.
• Use permanent redirects. A 301 tells search engines the move is permanent. A temporary (302) redirect says the old address will come back, which isn’t what you want for a redesign.
• Update internal links too. Menus, footers and in-text links on the new site should point directly to new URLs, not rely on redirects.

How you add redirects depends on the platform. Squarespace, Wix and Shopify have redirect settings built in. On WordPress it’s usually a plugin or a rule on the server. Google’s own guide to redirects explains the options in more detail. If you’d rather hand off the inventory, redirect map and launch checks, that’s what our website redesign service is for.

What content and on-page details should carry over?

Shorter pages often look cleaner in a redesign mockup, but if a page ranks because it thoroughly answers a question, cutting most of its text can cost you that ranking. Improve how the content is presented instead of deleting it: better headings, shorter paragraphs, a table or an FAQ.

For each important page, check that the new version keeps or improves:

• The page title and meta description
• One clear H1 heading that describes the page
• Internal links pointing to it from other pages
• Image alt text
• Structured data, if the old site had it (local business schema is the most common type on small-business sites)

A redesign is also a good moment to make weak pages stronger. If your service pages are thin, our guide to building SEO service pages shows what a page that ranks and converts usually includes.

What are the most common launch-day mistakes?

Most redesign ranking drops trace back to a handful of launch-day slips:

• A leftover noindex setting. Development sites are often hidden from search engines, and that setting can survive the move to live. On WordPress, check the “Discourage search engines” option under Reading settings.
• A robots.txt file that blocks everything. Same problem, different file.
• Canonical tags pointing to the staging address. The live pages then tell Google the “real” version is somewhere else.
• A mix of HTTP and HTTPS, or www and non-www. Pick one version and redirect the others to it.
• Forms and tracking that didn’t come across. Not a ranking issue, but you’ll lose leads and the data to spot problems.

Then test a sample of old URLs to confirm they redirect correctly, and submit the new XML sitemap in Search Console.

Is changing your domain or platform different?

A platform move, such as Wix to WordPress, is a redesign with a high chance of URL changes, because platforms structure addresses differently. Map every URL; don’t assume they’ll match.

A domain change is a bigger move. Every URL changes, so every page needs a redirect from the old domain to the matching page on the new one. Keep the old domain registered so those redirects keep working, and use the Change of Address tool in Search Console. Google’s guide to site moves with URL changes walks through the process. Update your Google Business Profile website link as well; see Google Business Profile and your website.

If you can, avoid changing the domain in the same project as a full redesign. Fewer changes at once make problems easier to trace.

What should you watch after launch?

For the next few weeks, check Search Console regularly, or make sure whoever handles your website care does:

• Page indexing for new errors, especially “Not found (404)” on URLs you meant to redirect
• Performance, comparing impressions and clicks on your key pages with the period before launch
• URL Inspection on your most important pages, to confirm Google can crawl and index them

Some movement is normal right after launch. A sustained drop on specific pages usually points to a missing redirect or lost content you can fix. Keep an eye on leads too: calls, bookings and form submissions are the numbers that matter most.