Website redesign SEO: how to redesign without losing rankings

A redesign should make your website better for visitors and for Google, but some relaunches lose a big share of their search traffic in the first weeks. The cause is almost never the new design itself. It is changed URLs without redirects, deleted pages and missing technical settings. This is the checklist we follow on every redesign so rankings survive the move.

Does a website redesign affect SEO?

Yes. Google has to recrawl and re-evaluate every page that changed, so some movement is normal. Google's own site move guidance says to expect temporary fluctuation in rankings, and that for a medium-sized site it can take a few weeks or more before the new URLs settle in search results.

How much risk you take depends on what changes. A visual refresh on the same platform with the same URLs is low risk. A new platform with new URLs and rewritten content is the riskiest version, because every ranking page has to be found, redirected and judged again.

Google recommends making these changes one after the other rather than all at the same time where you can. If you are moving platform and domain, move one first and let it settle.

Before design starts: record what already ranks

You cannot protect pages you do not know about. Do this before anyone opens Figma, because it changes the sitemap of the new site.

1. Export every URL. Crawl the live site with a crawler such as Screaming Frog or Sitebulb, and add the URLs from your sitemap. Old blog posts and landing pages that are not in the menu are often the ones with links pointing to them.
2. Export Search Console data. In Google Search Console, export the Performance report by page and by query for the longest period available (16 months). This shows which pages bring clicks and for which searches.
3. Mark your keeper pages. Flag pages with clicks, conversions or backlinks from other sites. These keep their URL, their topic and most of their text unless there is a strong reason to change them.
4. Save the old metadata. Keep a copy of every title tag, meta description and H1. After launch you will compare against it.
5. Take a speed and tracking baseline. Note your Core Web Vitals in Search Console and how analytics and conversion tracking are set up, so nothing gets lost in the rebuild.

Put the keeper list in the project brief. Our guide on how to write a design brief shows where it fits with the rest of the requirements.

Plan URLs and build a redirect map

The safest URL is the one that does not change. Keep existing URLs wherever the page still exists, even if the new structure looks a little less tidy. Change a URL only when there is a real reason, such as a platform that forces a folder (Webflow CMS items live inside a collection folder, for example).

For every URL that changes or disappears, add a row to a simple spreadsheet: old URL, new URL, redirect type. Rules we follow:

• Use permanent redirects. Google recommends server-side 301 or 308 redirects for pages that moved for good. A 302 tells Google the move is temporary, so it keeps showing the old URL.
• Redirect to the closest match. An old service page goes to the new service page, not to the homepage. Sending everything to the homepage throws away the relevance the old page had.
• One hop only. If page A already redirects to B and B now moves to C, update A to point straight to C. Google advises avoiding redirect chains.
• Merge, do not just delete. If two thin pages cover the same topic, combine them into one better page and redirect both old URLs to it.
• Keep redirects for at least a year. Google suggests keeping them as long as possible. In practice we never remove them.

Where you add redirects depends on the platform. In Webflow they live in Site settings, Publishing, 301 redirects, need a paid site plan and only work after you publish. On WordPress, a plugin such as Redirection or your SEO plugin handles them. Our Webflow vs WordPress comparison covers the other differences if you are switching.

Carry the on-page SEO into the new design

Design changes can quietly remove the things a page ranks for. Check each keeper page in the new design against your saved baseline:

• Content depth: a page that ranks with 1,200 useful words will struggle as a short hero section and three icons. Shorten design, not substance.
• Headings: one H1 per page that still matches the search intent, with H2s for the main subtopics.
• Titles and meta descriptions: carry them over or improve them on purpose. Do not let the platform generate defaults.
• Internal links: keep links between related pages and point them at the new URLs, not at redirects. Important pages should stay reachable from the main navigation.
• Images: keep alt text and compress new images, since large hero images are a common reason a redesign gets slower.
• Structured data: if the old site had schema for FAQs, products or reviews, rebuild it and test it with Google's Rich Results Test.

From the studio: before launch we open the old and new version of the top 20 pages side by side and read them, not just scan them. Almost every time we find one page where a section that answered a key question got cut because it "did not fit the layout". That section is usually why the page ranked. We put it back as an accordion or a FAQ block instead of deleting it.

Launch day checklist

A lot of SEO damage happens on launch day, when a setting from the staging site goes live. Run through this list in order:

1. Remove staging blocks. Turn off noindex, password protection and any robots.txt rule that blocked crawling during development. Then check robots.txt on the live domain.
2. Publish all redirects and test a sample of old URLs in the browser. Each should land on the right page in one step with a 301.
3. Check canonical tags point to the live domain, not to the staging or webflow.io address.
4. Submit the new sitemap in Search Console. It should list only live pages that return a 200 status, not redirects or 404s.
5. Request indexing for the homepage and your most important pages with the URL Inspection tool.
6. Confirm tracking works: analytics, conversion events and form notifications on the live site.
7. Crawl the new site once to catch broken internal links and missing titles.

After launch: what to monitor and when to worry

Check Search Console daily for the first two weeks, then weekly for two to three months. Look at:

• Pages report: new "Not found (404)" or "Page with redirect" problems usually point to gaps in the redirect map. Fix them by adding the missing redirect.
• Performance report: compare clicks per page against your baseline. A small dip that recovers over a few weeks is the normal fluctuation Google describes.
• Keeper pages: if one of them drops and does not recover, compare it with the saved version. Usually something was removed: text, a heading, internal links or the redirect itself.

A sharp drop across the whole site that does not start recovering within a couple of weeks is rarely "Google adjusting". It is usually a technical issue such as a leftover noindex, a blocked robots.txt or missing redirects, and it is worth checking those first. If you are on Webflow, our article on whether Webflow is good for SEO lists the settings to check.

Related guides

• How long does it take to build a website?
• How much does a website cost
• Our website redesign service