How to redesign a website without losing your search rankings

Why do websites lose rankings after a redesign?

Rarely because of the design. Rankings drop when the things search engines rely on change or disappear: the URLs, the content on them, the links between them and access for crawlers. Each cause has a known fix.

The pattern is clear: treat a redesign as a migration with a design attached, not a design project with SEO at the end.

What should you record before you change anything?

Take a full snapshot of the current site, because you can't compare against a baseline you didn't save. Do this before design starts, and again just before launch.

• Every URL. Crawl the site and export every live URL, including PDFs and images that earn traffic. Add URLs from your XML sitemaps, analytics and server logs; Google's site-move guidance suggests all three as starting points.
• Search performance by page. Export clicks, impressions and top queries per page from Search Console for at least the last 12 months.
• Conversions by page. Which pages bring enquiries, bookings or sales. These matter more than traffic.
• Backlinks. Pages that other sites link to. Losing them is the most expensive mistake.
• On-page elements. Titles, meta descriptions, headings, canonical tags, structured data and hreflang for each important page.
• Speed. Current Core Web Vitals for key templates, so the new site can be held to at least the same standard.

Mark your "protected pages": the ones that bring most of the clicks, conversions or links. Those pages get the most care in every step that follows.

How do you map old URLs to new ones?

Build a redirect map: a spreadsheet with one row for every old URL and the new URL it should go to. Google's site-move guidance calls mapping old URLs to new ones an important step, and it is the single most useful document in a redesign.

The best redirect is no redirect. Keep URLs the same wherever the page still exists. Change a URL only when there's a clear reason, such as a restructured service section or a URL that describes something you no longer offer.

Redirect map template. The example rows show the kinds of decisions you'll make across different types of business.

How to fill it in:

1. List every old URL from your crawl, sitemaps, analytics and backlink data.
2. Match each to its closest new page by intent, not by convenience. A service page goes to the same service, not the services overview.
3. Decide what has no equivalent. Google's guidance says URLs you are not carrying over should return a 404 or 410 on the new site.
4. Flag protected pages and check their content line by line.
5. Test every row on staging before launch, then again on the live site.

Which redirects should you use?

Permanent, server-side redirects: HTTP 301 or 308. Google says permanent redirects lead it to show the new target in search results, while temporary redirects (302, 303 and 307) keep the source page in results. Server-side redirects are the most reliably understood; Google advises using JavaScript redirects only when server-side or meta refresh redirects aren't possible.

Rules that save rankings:

• Redirect directly to the final URL. Avoid chains, where A goes to B and B goes to C. Google's guidance recommends sending each old URL straight to its destination and keeping any unavoidable chain short, ideally three hops or fewer.
• Don't send everything to the home page. Google warns that redirecting many old URLs to one irrelevant destination, such as the home page, can confuse users and may be treated as a soft 404. Combining several old pages into one new page that covers them is fine.
• Keep redirects for a long time. Google recommends keeping them for as long as possible, generally at least a year.
• Update your own links anyway. Change internal links, canonical tags and sitemaps to the new URLs, so redirects only catch outside links and old bookmarks.

How do you keep content parity during a redesign?

Keep the content that earned your rankings, on the pages that earned them, unless you're deliberately improving it. A new layout can hold the same words; a "cleaner" design that cuts a detailed ranking page down to a headline and a few icons usually loses the searches that page matched.

What to carry across for every protected page:

• The main copy, including the sections that answer specific questions.
• The title tag and main heading, unless you have evidence a change will help.
• Internal links to and from the page, rebuilt to new URLs.
• Structured data, such as business details, products, reviews or FAQs, where you use it.
• Images with their alt text, and videos with their transcripts.
• Canonical tags: Google's guidance says each new URL should have a self-referencing canonical.
• Hreflang annotations for multilingual sites, updated to the new URLs.

What you can change with less risk: the visual design, the layout of content on the page, navigation styling, imagery and the copy on pages that bring no search traffic. Improving content is welcome too, but change protected pages deliberately, and preferably not all on launch day, so you can tell what helped and what hurt.

The same crawlable content that ranks in search is what AI answer engines read and cite, so content parity protects your visibility there as well. Our guide to GEO explains how that works.

How do you keep the staging site out of Google?

Password-protect it. Google's guidance says that confidential or private content needs password protection to keep it out of search, while a noindex rule only stops the content from appearing in results. A login on staging also stops competitors and customers from finding an unfinished site.

If you can't use a password, use noindex on every staging page, through a robots meta tag or an X-Robots-Tag HTTP header. Two traps:

• robots.txt does not remove pages. Google says that if robots.txt blocks a page, the crawler never sees its noindex rule, and the URL can still appear in results if other pages link to it. Google also doesn't support noindex inside robots.txt.
• Blocks travel to production. Google's site-move guidance reminds owners to remove any noindex or robots.txt blocks that were only needed for the migration. A staging noindex left on the live site can remove it from search entirely.

Add "check robots.txt and noindex on the live site" as the first item on your launch-day list, and test it within the first hour.

When do you need Search Console's Change of Address tool?

Only when the domain or subdomain changes. Google's Search Console help says the tool is for moving a site from one domain or subdomain to another, works at domain level and not for paths, and stays in effect for 180 days.

For a domain change, verify every version of the old and new sites in Search Console first, and keep redirects in place for well beyond the 180 days.

What should you do on launch day?

Follow a written sequence and keep the team available. Most launch-day problems are found in the first hour by someone who checks.

1. Remove staging blocks. Check robots.txt and noindex on the live site.
2. Put the redirects live and test the redirect map with a script or crawler, starting with protected pages.
3. Submit the new XML sitemap in Search Console. Google's guidance notes the old sitemap can be removed once Google uses the new one, and that redirect warnings on old-URL sitemaps can be ignored.
4. Inspect key URLs with Search Console's URL Inspection tool.
5. Check analytics and conversion tracking fire on the new templates, especially forms, calls and bookings.
6. Submit the Change of Address if, and only if, the domain changed.
7. Ask for key backlinks to be updated where you have a relationship with the linking site.

What should you monitor after launch?

Watch daily for the first week, then weekly for about three months. Google says to expect temporary fluctuation, and that it may take a few weeks or more for new URLs to replace old ones in results, longer for large sites.

When a page drops, check in this order: does the old URL redirect to the right page; is the new page indexable; did its content or title change; did it lose internal links. Fix the cause rather than waiting, because Google's own guidance treats crawl errors as something to check for regularly during a move.

What does a complete redesign SEO checklist look like?

Use this as the working list for your team or your agency.

If you're planning a redesign, see how Worcia builds websites with the migration planned from day one, and how SEO & GEO protects and grows your visibility in search and AI answers afterward. For budgeting, our guide to website costs covers what drives the price.