Keep every URL that earns visits, or send it with a permanent redirect to the one new page that answers the same question. Keep the content buyers and AI tools rely on. Launch, then watch Search Console for a few weeks. Most traffic lost in a website redesign comes from broken URLs and deleted pages, and both are preventable.
Which redesign are you planning?
| Your situation | Main risk | Start with |
|---|---|---|
| New look, same platform, same URLs | Lost content and metadata | A crawl of the old site |
| New look and new URL structure | 404s and lost rankings | A one-to-one redirect map |
| Moving to another platform | Nearly every URL changes | The URL inventory, then redirects |
| Moving to a new domain | The slowest recovery | Change of Address, plus every redirect |
| Cutting or merging pages | Answers buyers relied on disappear | A list of what each page answered |
Who is this guide for?
It's for anyone whose current site already does a job. That could be a dentist whose booking page brings patients, a B2B marketer whose guides bring demo requests, or a store whose category pages bring sales.
If your site gets almost no visits today, you have little to lose. Redesign freely and skip to the platform you're moving to. If it brings leads, read the whole thing before anyone touches a URL.
How much traffic do redesigns really lose?
A badly planned move can take a long time to recover. A careful one usually settles within weeks.
Google says to expect ranking changes while it recrawls a moved site. A medium-sized site can take a few weeks or more for new URLs to replace the old ones, and bigger sites take longer.1
The bad cases last much longer. Dan Taylor studied 892 domain migrations using third-party traffic estimates, mostly from Ahrefs.2 The average site took 523 days to get back to its old traffic, and 17% hadn't recovered after 1,000 days.2 His earlier study of 171 migrations found 229 days on average, with 42% never coming back.2
Average days for a migrated domain to regain its traffic
Those figures cover domain moves, the riskiest kind. A redesign on the same domain with the same URLs carries far less risk. The numbers show what happens when the basics get skipped.
What actually causes the drop?
Four things cause most of it.
| Cause | What happens | How to prevent it |
|---|---|---|
| Changed URLs with no redirect | Old links and rankings hit a 404 | Keep URLs, or redirect each one |
| Everything redirected to the homepage | Google may treat it as a soft 4041 | Redirect to the closest matching page |
| Pages cut to "simplify" | The answers that ranked are gone | Merge content, then redirect |
| Staging settings left on | Noindex or blocked crawling goes live | Check robots.txt and meta robots on launch day |
The third row matters more now that AI assistants pick businesses. Before an assistant recommends anyone, it works out who the buyer is, what they already run and what they compare.3 The pages that answer those questions are often the plain ones a redesign wants to cut, such as the FAQ, the pricing explainer or the "who I work with" page. Keep them, or move what they say onto the new pages. My AEO determinants entry explains the idea.
What should you do before the redesign starts?
Build the URL inventory first. Everything else depends on it.
- Export every URL. Pull them from your sitemap, a crawler and Search Console's page report. Add URLs with backlinks from your SEO tool.
- Mark what earns visits. Add clicks from Search Console and visits from analytics for the last 12 months. Sort by clicks.
- Decide each URL's fate. Keep it as it is, redirect it to one named new page, or retire it on purpose.
- Save the old site. Keep a crawl of titles, meta descriptions, headings and structured data, so you can compare after launch.
- Note what each top page answers. Write one line per page on which buyer question it covers. The new site has to cover the same questions.
This sheet is the redirect map. The free redesign redirect map turns your old and new URL lists into a redirect file for your platform. Agree in writing who owns it. When I run a redesign on my web design work, the map is my job and it's signed off before design starts.
How should redirects be set up?
Use server-side permanent redirects, 301 or 308, wherever the platform allows.1 Point each old URL straight to its final page. Google can follow up to 10 hops, but it recommends keeping chains short.1
Keep redirects for at least a year, and Google says longer is better for users.1 Then update your own internal links and your best external links to the new URLs, because every redirect slows a visitor down a little.1
If the domain changes too, use the Change of Address tool in Search Console for every verified version of the old domain.1 It isn't needed for moves within one domain.1
What changes if you're on WordPress?
WordPress gives you the most control and the most ways to break things.
- WordPress redirects a post's old slug to its new one by itself, with a 301.4 That covers renamed posts, but it skips pages and other hierarchical post types, and it won't help when the permalink structure changes.4
- For everything else, use a redirect plugin or server rules. The Redirection plugin has over 2 million active installs. It handles 301s, regular expressions and CSV import, and it logs 404s so you can catch misses after launch.5
- A new theme often changes heading levels, breadcrumbs and schema output. Compare a few key pages in the old crawl against the new build.
- Check permalink settings before launch. Changing from dates in URLs to plain post names alone changes every post URL.
What changes if you're on Webflow?
- Redirects live in site settings, under Publishing and 301 redirects. You can import a CSV of old and new paths.6
- A CSV import overwrites every existing redirect. Export the current list first, add your new rows, then import the full file.6
- Webflow recommends about 1,000 redirects at most, because each rule adds to a file browsers download. Use wildcard rules with capture groups, such as
/blogs/(.*)to/articles/%1, to keep the count down.7 - CMS slugs change when you rename a collection's path. Plan the collection URLs before you import content.
What changes if you're on Shopify?
- Product, collection and cart paths are fixed. You can't redirect
/productsor/collectionsthemselves, but you can redirect a single old product URL to a new one.8 - A redirect only works from a broken URL. If the old page still loads, the redirect won't fire.8
- Stores can hold up to 100,000 redirects, and Shopify Plus stores up to 20 million. Bulk import and export by CSV is built in.8
- A theme change keeps your URLs, so the main risks are product page copy, filters that create new URLs, and missing structured data. Run the page weight checker on a product page before and after.
What changes if you're on Wix?
- Redirects live in the SEO dashboard under the URL Redirect Manager.9
- A CSV import takes up to 500 redirects per file, and rows past that limit are skipped.9 Split large maps into several files.
- When you import, choose whether to override redirects that already exist. The default leaves them as they are.9
What if you're moving between platforms?
Move the platform and keep the design changes small, or do the two in separate stages. Changing both at once makes it hard to tell which one caused a drop.
The URL patterns rarely match. WordPress posts often sit at the root, Webflow puts CMS items under a collection path, and Shopify forces its own paths. So nearly every URL gets a redirect, and the inventory matters even more. My platform comparison covers which platform fits which business, and Webflow or WordPress by who updates the site covers the most common move I see.
What should you check on launch day and after?
When to check what in a redesign
Launch day. - The live site is indexable. No noindex tag, and robots.txt doesn't block crawling. - Test the top 50 old URLs by clicks. Each returns a 301 or 308 and lands on the right page. - Submit the new sitemap in Search Console. Keep the old one for a while, since its redirect warnings are expected.1 - Titles, meta descriptions, headings and structured data match or beat the old crawl.
The first four weeks. - Check Search Console's page report and the 404 log every few days. Redirect any real page you missed. - Compare clicks for your top pages against the same weeks before launch. - Ask ChatGPT and one other assistant the buying questions your top pages answered. Check the answers still name you and still describe you correctly.
After a year. Keep the redirects. Clean up only chains and loops.
What should you ask whoever runs the redesign?
| Question | A good answer |
|---|---|
| Who builds and owns the redirect map? | A named person, signed off before design |
| Will URLs change? | Only where there's a reason, each one redirected |
| Which pages are you cutting? | A list, with where their content goes |
| What do you check at launch? | Indexing, redirects, sitemap, metadata, schema |
| How long do you monitor afterwards? | At least four weeks, with a report |
| Who fixes misses after launch? | Included, with a response time |
My guide on how to choose a website designer has more questions for the first call. If you're weighing a new theme against a custom build, read template or custom website design first.
Questions people ask
Will a website redesign hurt my SEO?
It doesn't have to. Keep URLs that earn visits, redirect the rest one to one, and keep the content that answered searchers. Expect a few weeks of movement while Google recrawls.1
How long should I keep 301 redirects?
At least a year, and Google says longer is better for visitors.1 Most sites keep them for good.
Can I redirect all old pages to the homepage?
Avoid it. Google may treat mass redirects to an unrelated page as soft 404s.1 Send each old URL to the closest matching page.
How long does traffic take to recover after a redesign?
Does a redesign affect how AI assistants describe my business?
It can. Assistants judge who you serve and what you offer from your pages and what they retrieve. Cutting pages that answered buyer questions can remove the very facts they used.3
