Website Redesign SEO: How to Redesign Without Losing Rankings

A website redesign does not hurt SEO by itself. Rankings drop when URLs change without redirects, when pages that ranked are removed or rewritten without care, and when design choices hide content from Google. Freeze your URLs early, map a 301 redirect for every URL you change, keep the content that already ranks, then watch Search Console for 8 to 12 weeks after launch.

Most guides on website redesign SEO are written by SEO teams, and they treat the new design as a black box. I am the designer who runs the redesign, so this checklist covers what they skip: the layout, content and navigation decisions that quietly break rankings, plus a redirect map template you can copy.

Does a website redesign affect SEO?

Yes, in both directions. Same URLs, same content and a faster site is low risk and often helps. New URLs, fewer pages and a new platform all at once is where traffic disappears.

What usually causes a drop:

• Changed URLs without redirects. Every link and ranking pointing to the old address now hits a 404.
• Removed or merged pages. The page that ranked for a query no longer exists, or its content was cut in half.
• Rewritten copy. The new headline sounds better but no longer contains the words people search for.
• Weaker internal linking. A simplified navigation stops linking to pages that used to get links from every page.
• Slower templates. A heavy hero video or late-loading fonts push Core Web Vitals out of the good range.
• Hidden content. Text cut from mobile layouts or loaded only on click is invisible to Google.

Some movement is normal even when you do everything right. Google's documentation on site moves says rankings can fluctuate while it recrawls the site, and a medium-sized site can take a few weeks or more before new URLs replace old ones in results. The goal is a dip that recovers, not a cliff.

Redesign or migration: know what you are changing

"Redesign" covers very different projects. Before the first wireframe, name what is actually changing, because the risk and the work are not the same.

When a migration is involved, the redesign becomes a website migration, and website migration SEO is mostly about redirects and parity: every page, title, tag and link has a planned equivalent on the new site.

Google also recommends changing one thing at a time: the domain, then the CMS, then the layout. Founders rarely want three launches, so if you cannot split the work, at least avoid a new domain on top of a new platform, and keep URLs identical wherever the content stays the same.

Step 1: Benchmark before anyone opens Figma

You cannot prove a redesign did not hurt SEO if you never measured the old site. Before design starts, export and save:

• Search Console Performance data over the longest date range available: clicks, impressions and position by page and by query.
• Your top pages by organic clicks and by conversions (demo requests, sign-ups, contact forms). These are the pages you protect first.
• Pages with backlinks, from Search Console's Links report or an SEO tool. A page with few visits but strong links still matters.
• A full crawl of the current site: every URL, its title, meta description, H1, canonical and status code.
• Core Web Vitals from Search Console or PageSpeed Insights, so you know whether the new templates are faster or slower.

This is also the moment to put SEO in the design brief. On a SaaS website design project, I ask for this data in the first week, because it changes the sitemap and the wireframes, not just the launch checklist.

Step 2: Inventory every page and decide its fate

Put every URL from the crawl in a spreadsheet and give each one a decision before the new sitemap is drawn:

1. Keep: same URL, same purpose. Content can be improved, but the topic and key terms stay.
2. Improve: same URL, rewritten or expanded content. Check the queries it ranks for and keep them in the new copy.
3. Merge: two or more thin pages become one stronger page. The old URLs redirect to the new one.
4. Move: same content, new URL. Needs a one-to-one redirect.
5. Remove: outdated pages with no traffic, links or business value. Redirect to the closest relevant page if one exists; otherwise let them return a 404 or 410.

Designers often want to simplify a sitemap, and simplification is usually right. The inventory makes it a conscious decision: you see which pages you are about to delete and what they bring today.

Step 3: Build the redirect map

The redirect map is the single most important SEO document in a redesign. It pairs every old URL that changes with its new destination, and it gets reviewed before launch, not written on launch day.

A redirect map template you can copy

Fill it from the crawl, sort by priority, and test every row on staging before launch. Keep the sheet after launch: it is the first thing you check when a 404 appears.

Redirect rules that protect rankings

• Use permanent, server-side redirects (301 or 308). Google states that permanent redirects do not cause a loss of PageRank.
• Redirect one to one. Each old page goes to its closest new equivalent. Do not send dozens of old URLs to the home page: Google says it can treat that as a soft 404.
• Avoid chains. If an old page was already redirected once, point it straight to the final URL. Google advises keeping chains short, ideally no more than three hops.
• Keep the redirects for at least a year, which is Google's guidance, and longer if old links still bring visitors.
• Update internal links to the new URLs instead of relying on redirects inside your own site.

Step 4: Design choices that quietly break SEO

This is where a designer can protect rankings, or destroy them, without anyone noticing until traffic drops. None of these issues show up in a Figma review.

Content cut or hidden on mobile

Google indexes the mobile version of your site. If the mobile layout drops a section to keep things tidy, that content no longer exists for Google. Its documentation is clear: keep the same primary content on mobile, and if space is tight, use accordions or tabs rather than removing text. Also avoid content that only loads after a click, swipe or typing, because Google does not perform those interactions.

Headings picked for size, not structure

In many redesigns, the H1 becomes a short slogan and the real page title moves into a paragraph styled to look big. Choose heading levels for structure and style them separately in the design system. The H1 should say what the page is about, with the words people search for, and the main sections should be real H2s. Keep the same headings on desktop and mobile.

Text inside images and CSS backgrounds

Headlines baked into images, comparison tables exported as pictures and diagrams with all their labels inside an image are invisible as text. Google also says it does not index images set as CSS backgrounds. Keep text as live text, and use real image elements with descriptive alt text for images that matter, such as product screenshots.

Navigation and cards that are not real links

Clickable cards, mega menus and tabbed sections are often wired with scripts instead of links. Google can generally only follow a link if it is an anchor element with an href. When you design a card grid or a custom menu, ask for real links in the build, and make sure every important page is still reachable through the navigation or the footer.

Heavy hero media and font swaps

A full-screen video hero, an animated illustration on load and three custom font files can push Largest Contentful Paint past the 2.5 second threshold. Fonts that load late and shift the layout hurt Cumulative Layout Shift, which should stay at 0.1 or less. Design with a performance budget: a poster image for the video, fewer font weights, reserved space for anything that loads later.

Merged pages and rewritten copy

Merging five feature pages into one long page looks cleaner, but each old page may have ranked for its own query. If you merge, keep a clearly titled section for each topic and redirect each old URL. When copy is rewritten for the new positioning, compare it with the queries from your benchmark: if a page ranked for "expense reporting software", the new version should still say so, in the title and in the text.

Step 5: Staging and pre-launch QA

Build and review the new site on a staging address, protected by a password and a noindex rule so it does not get indexed early. One detail matters here: a noindex rule only works if Google can crawl the page, and robots.txt does not stop a page from being indexed if other sites link to it. Use password protection and noindex together, and remove both at launch.

Before launch, check on staging:

• Every redirect in the map returns the right destination in one hop.
• Titles, meta descriptions and H1s are carried over or improved, page by page, not left as template defaults.
• Canonical tags point to the new URLs, not to staging or to the old site.
• Structured data (Organization, Article, FAQ, Product) is present on the same pages as before.
• Images have alt text, and important images are real image elements.
• Analytics, tag manager and conversion events fire on the new templates.
• Forms submit and reach the right inbox or CRM.
• The XML sitemap lists only the new, indexable URLs.

Step 6: Launch day

Launch on a quiet day if your traffic has one, then, in order:

1. Switch on the redirects and test the high-priority rows from the map on the live domain.
2. Remove the noindex rule and the password, and check that robots.txt does not block the site.
3. Submit the new sitemap in Search Console.
4. Inspect key URLs with Search Console's URL Inspection tool to confirm Google can fetch and index them.
5. File a Change of Address only if the domain changed. Google says it is not needed for HTTPS moves, www changes or moving paths within the same domain.
6. Update the links you control: social profiles, ad campaigns, help center and in-product links.

Step 7: What to watch in Search Console after launch

"Monitor Search Console" is in every guide. Here is what I actually look at, and when.

First week: the Page indexing report for new 404s and pages "excluded by noindex" by mistake, then the 404s you find against the redirect map. Fix missing redirects the same day.

Weeks 2 to 4: the Performance report, comparing the weeks since launch with the same number of weeks before it, filtered by page. Look at your high-priority pages one by one. A page that loses clicks while its old URL still appears in results is usually just waiting for Google to process the redirect. A page that lost impressions on its main queries usually has a content or heading problem.

Up to week 12: compare clicks and conversions with the benchmark. Expect some fluctuation, which Google describes as normal during a move. Act when a priority page keeps falling after the first month, when 404s keep appearing, or when key pages are not indexed: these do not fix themselves.

Good to know: Seasonality can look like a redesign problem. Compare with the same period last year as well as the weeks before launch before you conclude that the new site lost traffic.

Moving platforms during a redesign

Platform changes are where redesigns turn into migrations, because the new platform rarely reproduces the old URLs exactly. Some impose their own patterns, such as a fixed folder for blog posts, so check what the new platform allows before you design the sitemap, and add every changed path to the redirect map.

Platform moves also reset everything that lived in plugins: SEO titles, schema, existing redirects, image alt text. Treat each one as a line in the QA list, not as something the import will handle. Feedier's rebrand, which came with a move from WordPress to Webflow, was exactly this kind of project. If you are still choosing a platform, my Webflow vs WordPress comparison covers the trade-offs.

The website redesign SEO checklist

Before design

• Search Console export and a full crawl of the current site.
• Top pages listed by clicks, conversions and backlinks.
• Decide keep, improve, merge, move or remove for every URL.
• Name the type of change (refresh, new structure, new URLs, new platform, new domain).
• Freeze the URL structure before templates are designed.

During design and build

• Same primary content on mobile and desktop, real headings, live text, real links.
• A performance budget for hero media and fonts.
• A redirect map, tested on staging.
• Titles, meta descriptions, canonicals and structured data carried over.

At launch

• 301 redirects on, noindex and password off, robots.txt checked.
• New sitemap submitted, key URLs inspected, links you control updated.

After launch

• Check the Page indexing report and 404s daily in the first week.
• Compare Performance by page at two, four and twelve weeks.
• Keep redirects for at least a year.

The bottom line

Website redesign SEO is mostly planning: a benchmark before design, a decision for every page, a redirect map tested on staging and design choices that keep content visible to Google. Done in that order, a redesign is a chance to improve rankings, not a gamble with them. If you are also setting the budget, my guide to what a website costs covers redesign scope and pricing.

I design the site and take it live, with SEO in the brief from the first week, and I stay your single point of contact until launch. If a redesign is on your roadmap, see how I approach SaaS website design and redesigns, or tell me about your current site and I will tell you where the SEO risks are before any design starts.