---
title: "How to Redesign a Website Without Losing Rankings"
description: "Rankings survive a redesign when you keep or 301-redirect every URL, keep the substance of your best pages and submit the new sitemap at launch."
category: "UX & Redesign"
question: "How do I redesign my website without losing rankings?"
datePublished: 2026-10-15
dateModified: 2026-10-15
readingMinutes: 6
status: published
author: "UXPro Design Studio"
authorType: "Organization"
editorialProcess: "Prepared with AI assistance and checked against the listed sources."
authorUrl: https://uxpro.ca/about
canonical: https://uxpro.ca/blog/redesign-without-losing-rankings
image: https://uxpro.ca/covers/redesign-without-losing-rankings.webp
license: "Quote freely with a link to the canonical URL."
---

# How to Redesign a Website Without Losing Rankings

## Key facts

| Fact | Value |
|---|---|
| Redirect type | 301 or another permanent redirect for every changed URL; Google says permanent redirects don't cause a loss in PageRank |
| Redirect target | Page-to-page, matched by closest topic, never a blanket redirect to the homepage |
| How long to keep redirects | Google: "as long as possible, generally at least 1 year" (site-move guide, last updated 20 August 2026) |
| Launch-day step | Submit the new sitemap in Search Console; use Change of Address only if the domain itself changes |
| A common, avoidable cause of traffic loss | A missing or wrong redirect, not the new design itself |

**Rankings usually survive a redesign when you keep your URLs, or 301-redirect every old URL to its closest match on the new site, keep the substance of the pages that already earn traffic, and submit the new sitemap on launch day. When traffic drops after a redesign, a missing or wrong redirect is a common and avoidable cause, so plan the redirects before the design.**

## What should you inventory before the redesign starts?

Before any design work starts, pull three lists. From Search Console, export every URL that has received impressions over the available history (Search Console keeps about 16 months of performance data), plus your top pages by clicks. If you have access to a backlink tool, add every URL that has an external link pointing at it.

This inventory tells you which pages can't quietly disappear. A page with no clicks and no backlinks can usually be dropped or merged with little risk. A page with steady clicks or a referring site needs a redirect, even if the new structure has no obvious place for it.

Do this before a single [wireframe](/glossary#wireframe) is drawn, not after the new sitemap is finished. A redesign usually starts from "what should the new site say", which is the right question for content and the wrong first question for search risk. The export answers a different question: what is the current site already earning, and what happens if that page moves or disappears? That answer should shape the new sitemap, not the other way around.

## Should you keep your existing URLs?

Yes, where you can. The safest redesign changes the design and keeps the URLs. If `/services/web-design` currently ranks and the new site still has a page about web design, leave that URL alone and change everything else about the page. Every URL you keep is one redirect you don't have to get right, and one link on someone else's site that keeps working.

Change URLs only for a concrete reason: a rebrand, folding several thin pages into one better page, or a platform migration that forces new paths. If the reason isn't concrete, it's usually not worth the redirect risk.

## How do you build the redirect map?

For every URL that changes, point the redirect at the closest topical match on the new site. Google's [site-move guide](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) warns against redirecting many old URLs to one irrelevant destination, such as the new homepage. If you consolidate content, redirect the old URLs to the new consolidated page.

| Old URL | Good redirect target | Bad redirect target |
|---|---|---|
| A merged blog post | The new post covering the same topic | The blog index |
| A renamed service page | The equivalent new service page | The homepage |
| A discontinued location page | The nearest current location page, or the location hub | The homepage |
| A junk or accidental URL | The most relevant real page, or let it return a 404 on purpose | Left without a decision |

Use 301 or another permanent redirect. Google's site-move guide says "301 and other permanent redirects don't cause a loss in PageRank". Its [redirects documentation](https://developers.google.com/search/docs/crawling-indexing/301-redirects) explains that a temporary (302) redirect is not treated as a signal that the target should be canonical, so the old URL tends to stay the one shown in results.

## How long should redirects stay in place?

Keep them "for as long as possible, generally at least 1 year", in the words of Google's site-move guide (last updated 20 August 2026). The guide also suggests considering keeping them indefinitely for users. The 180 days you may have read about is the period during which Search Console's [Change of Address tool](https://support.google.com/webmasters/answer/9370220) forwards signals for a domain move. It is not a redirect lifetime. Leaving redirects in place is cheap, so the safest default is to never remove them.

## What content has to stay the same on your best pages?

A URL that redirects correctly can still lose rankings if the content underneath it changes too much. On your highest-value pages, the ones from the inventory that bring in enquiries, keep the core topic, the intent of the main heading and the substance of the content. Rewrite sentences and redesign the layout around it.

For example, a page that currently answers "how much does a law firm website cost in Ontario" and is replaced by a vaguer, generic paragraph will likely do worse at the same URL, redirect or not. Redesign the presentation; keep the substance of the pages that already work.

## What do you do on launch day?

1. Test the redirect map: request every old URL from the inventory, or a large sample on a big site, and confirm each one lands on its intended page with a single permanent redirect.
2. Keep the Search Console property verified (and verify the new one if the domain changed).
3. Submit the new sitemap in Search Console.
4. If the domain itself changed, use the Change of Address tool. Google says not to use it for an http-to-https change, a www change on the same domain, or moving pages within the same site.
5. Remove any `noindex` tags or robots.txt blocks that were only there for the staging site.

## How long does Google take to process the move?

Google says that to consider a move complete, Googlebot has to visit every URL on the old and new site at least once, and that rankings may fluctuate while it recrawls and reindexes. For a medium-sized site it can take a few weeks or more. So expect normal movement in the weeks after launch, not a final set of numbers on day one.

Google also says larger sites can move one section at a time, and that small and medium sites can move everything at once. Moving one section first lets you catch a broken redirect pattern while it's still small. For a five-to-fifteen page small-business site, a single move is usually fine.

## FAQ

### How long until traffic recovers after a redesign?

Google says rankings can fluctuate while it recrawls and reindexes a moved site, and that for a medium-sized site it can take a few weeks or more before the new URLs replace the old ones in results. If a drop persists well beyond that, look for a specific missing redirect or lost content before assuming you just need to wait.

### Should I change my URL structure?

Only if you have a real reason to, such as a rebrand, a genuinely better [information architecture](/glossary#information-architecture), or a platform migration that forces it. Changing URLs for no reason adds redirect risk for no benefit. If you are changing them, the redirect map becomes the most important document in the project.

### Do I need to tell Google?

Not by email, but yes in Search Console: keep the property verified, submit the new sitemap, and if the domain itself changed, use the Change of Address tool. None of that replaces the redirects. It helps Google discover the move.

## Next step

Migrations are where a redesign most often goes wrong without anyone noticing. If you're planning one, [book a free consultation](/contact) and we'll look at your current URL inventory and what a redirect map needs to cover before design starts. [Website design and build](/services/website-design-build) covers how we run the migration itself, and [SEO and content](/services/seo-content) covers the pages around it. For the platform side of the decision, see [WordPress or Next.js in 2026](/blog/wordpress-vs-nextjs). To find the problems on your current site first, [request a Redline](/redline).

*Reviewed 15 October 2026 against the sources listed below.*

## Sources

- [Site moves with URL changes](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) (accessed 2026-10-15)
- [Redirects and Google Search](https://developers.google.com/search/docs/crawling-indexing/301-redirects) (accessed 2026-10-15)
- [Change of Address tool](https://support.google.com/webmasters/answer/9370220) (accessed 2026-10-15)