Short answer: A redesign doesn’t hurt SEO by itself. Traffic drops when the new site changes URLs without redirects, cuts content that was ranking, or launches with the staging block still on. Map every old URL to its new home with a 301, keep what ranks, and watch Search Console closely for the first few weeks.
A new design goes live on Monday. By the end of the month, enquiries from Google have halved, and nobody can say why, because the site looks better than it ever has.
It’s almost never the design. It’s the URLs that changed without redirects, the long service page that got cut to three lines because it “looked cluttered”, or the noindex tag from the staging site that shipped with everything else. All of it is preventable, and almost all of it is decided before launch day.
Does a website redesign affect SEO?
Yes, a website redesign can affect SEO in either direction. A new look on the same URLs with the same content barely registers with Google. A redesign that changes URLs, removes ranking content or rewrites titles is a site move as far as Google’s concerned, and rankings will fluctuate while it recrawls.
Google doesn’t rank a colour scheme. It ranks URLs, and what’s on them. So the question for any redesign is how much of that changes:
| What changes | SEO risk | Why |
|---|---|---|
| Visual design only, same URLs and copy | Low | Google sees the same pages at the same addresses |
| Templates, navigation, internal links | Medium | Pages can lose internal links or become harder to reach |
| Copy rewritten or pages merged | Medium to high | The content that earned the rankings is gone |
| URL structure, platform or domain | High | Every old URL needs a redirect, and Google has to recrawl the lot |
Most redesigns I’m asked to look at are in the bottom two rows without anyone having decided that. A move from WordPress to anything else usually changes the URL pattern by default. Once URLs change, the job is a migration, and the SEO work becomes mostly about redirects.
Why do websites lose traffic after a redesign?
Websites lose traffic after a redesign for a small set of reasons: old URLs that now return 404s, redirects that point everywhere except the right page, ranking content cut or rewritten, and a staging block left on at launch. Each one is visible in Search Console within days.
In the order I find them:
Missing redirects. The old URL had the links and the rankings. The new URL has neither, and nothing tells Google they’re the same page. Google’s documentation on HTTP status codes says indexed URLs that start returning a 4xx are removed from the index.
Redirects to the homepage. Quicker than mapping, and it doesn’t work. Google’s guidance on site moves with URL changes says redirecting many old URLs to one irrelevant destination such as the home page can confuse users and “might be treated as a soft 404”.
Lost content. The designer wanted less text. The long answer that matched the search went, and the ranking went with them.
A leftover block. The robots.txt Disallow or noindex that protected the staging site came across with the build.
Too much at once. Google advises planning changes one after the other, not everything at the same time. New domain, new platform and new copy in one weekend leaves no way to tell which one did the damage.
What should you do before a website redesign?
Before a website redesign, crawl the current site and benchmark it. Export Search Console performance data by page and by query, crawl every URL, and build one list of every URL with traffic, rankings or links pointing at it. That list is what the redirect map and the content plan are built from.
It’s the one step you can’t do after launch, because by then the old site’s gone.
- Export Search Console. Performance → Pages and Queries, over the longest range it gives you. Google’s guide to debugging traffic drops suggests looking at a 16-month range to see seasonal patterns, and you’ll want the same view to compare against after launch.
- Crawl the site. Screaming Frog, Sitebulb, whatever you use. You want every URL, its status code, title, meta description, H1 and canonical.
- Pull the old sitemap. It catches pages the crawl missed because nothing links to them.
- Export your backlinks from Ahrefs, Semrush or the Links report in Search Console. A page with no traffic but good links still needs a redirect.
- Merge it into one sheet. One row per old URL: clicks, top query, links, and a column for where it’s going.
Any page with clicks, rankings in the top 20, or links from other sites is a page that has to survive the redesign, either unchanged or redirected.
How do you redesign a website without losing SEO?
To redesign a website without losing SEO, keep URLs the same wherever you can, 301 redirect every old URL that mattered to its closest new equivalent, keep the content that ranks, carry titles and meta descriptions across, rebuild internal links, and keep the staging site out of Google with a password rather than a tag you might forget.
Keep URLs where you can. An unchanged URL needs no redirect and loses nothing. Change a URL only when there’s a reason, and a new CMS’s default isn’t one.
Use permanent redirects. Google’s redirects documentation says a permanent redirect (301 or 308) is a signal that the target should be canonical, while a temporary one (302, 303 or 307) isn’t, so the old URL can stay in search results. Redirect each old URL once, straight to its final address: no chains.
Keep the content that ranks. Design around the copy on your top pages, not the other way round. If a page ranks for twenty queries, the new version needs to answer all twenty.
Carry the metadata over. Titles, meta descriptions and H1s from the crawl go into the new build deliberately, not left to the template default.
Rebuild internal links. Point navigation and in-content links at the new URLs directly, not through redirects. Each new page should carry a self-referencing canonical.
Block staging properly. Google’s guidance on controlling what you share says private content needs password protection. Robots.txt alone isn’t a mechanism for keeping a page out of Google, and a noindex is the thing most likely to ship by accident. A password can’t come across with the build.
Figure
Redirects are the step that decides whether your rankings move with the redesign
- 01BeforeCrawl, export Search Console, list every URL that matters
- 02DuringMap every old URL to its new home with a 301
- 03LaunchRemove staging blocks, test redirects, submit the sitemap
- 04AfterWatch Pages and Performance for 404s and drops
The redirect map is the part that takes the time. The tool below does the first pass: paste the old URL list and the new one, and it keeps exact matches, pairs the rest by the words in each URL, and flags anything that only matches the homepage.
Free tool · Redirect map checker
Match your old URLs to the new site
Paste every old URL, one per line: from the old sitemap, or the Pages export in Search Console. Then paste the new site’s URLs. Full URLs or paths both work. Your lists stay in your browser.
Suggestions match on the words in each URL, not on what the pages say. Check every suggested redirect against the page it lands on before it goes live.
| Old URL | Suggested new URL | Status |
|---|
What goes on a website launch checklist?
A website launch checklist for SEO covers four things on the day: remove every staging block (robots.txt Disallow, noindex tags, password), test that old URLs redirect in one hop to the right page, submit the new XML sitemap in Search Console, and spot-check key pages with URL Inspection.
In the order I run them:
- Robots.txt. Open yourdomain.com/robots.txt. A
Disallow: /left over from staging blocks the whole site. - Noindex. View source on the homepage and three key pages and search for “noindex”. Check the platform setting too: WordPress, Squarespace and Wix each have a site-wide switch, covered in why a website isn’t showing up on Google.
- Redirects. Run the old URL list through a crawler in list mode. Every row should be one 301 to a 200. Google’s site move guidance mentions the URL Inspection tool for individual URLs and scripts or command-line tools for large numbers.
- Sitemap. Submit the new sitemap in Search Console. Google also suggests submitting a sitemap of the old URLs so you can watch the redirects get processed.
- Canonicals. Each new page should point at itself, not at the staging domain.
- Analytics and Search Console. Confirm tracking fires and Search Console is verified for the live domain.
What should you check after a website redesign launches?
After a website redesign launches, check Search Console daily for the first two weeks: the Pages report for new 404s and “Not found” errors, and the Performance report for clicks by page against your benchmark. A small, broad dip that levels off is normal. A steady slide, or losses concentrated on a few pages, is a problem to fix.
Google says outright that the visibility of your content in Search may fluctuate temporarily during a move, and that this is normal. What isn’t normal:
Use the Compare option in the Performance report to set the weeks after launch against the same weeks before, and year on year if the business is seasonal. Filter by page: a site-wide dip of a few percent is Google recrawling, while one page losing all its clicks is almost always a broken redirect or missing content on that page. Check it with URL Inspection, fix it, and request indexing.
If the drop won’t explain itself, it’s worth a technical SEO review before it becomes months of lost enquiries.
How long does it take to recover SEO after a website redesign?
Google says a small to medium-sized site usually takes a few weeks for most pages to move to their new URLs, and larger sites take longer. That’s the timeframe for a redesign done properly, with redirects in place. Google doesn’t publish a recovery timeline for one done badly.
That few-weeks figure is from Google’s site move guidance, and it assumes the redirects work. If URLs were lost, the clock only starts when they’re fixed.
Keeping the redirects matters here too. Google recommends keeping them for as long as possible, generally at least a year, because that’s how long it allows for transferring all signals to the new URLs.
A redesign that dropped rankings because content was cut is a different problem. Restoring the content is the fix, and Google’s traffic-drop guidance says that after a large ranking drop, it may take months for its systems to recognise the improvement. I’d give any redesign at least a month before judging it, and compare against the same period last year rather than last month.
Can a website redesign improve SEO?
Yes. A redesign improves SEO when it fixes something that was holding the site back, such as a slow, bloated build, pages that don’t match what people search, or a muddled structure, and the old URLs are carried across without losses.
One of my clients, a vehicle customisation studio in Arizona, had a slow WordPress site built on a heavy commercial theme with a page builder. I rebuilt it by hand in Astro, rewrote the service pages around what people search for, and cleaned up the URL structure and sitemap.
Google Search Console, 12 months to August 2026. Search Console had only partial data for the 68-day migration window, so those months are left out of both averages.
That’s the case for a redesign done with SEO built into the design and build from the start: the redirect map, the content plan and the benchmark all exist before the first template does.
What’s on a website redesign SEO checklist?
A website redesign checklist for SEO runs from benchmark to follow-up: export Search Console, crawl the old site, map every URL, keep ranking content and metadata, block staging with a password, remove every block at launch, test redirects, submit the sitemap and monitor for four weeks.
Website redesign SEO checklist
0/ 11
That is the whole list. Anything still unticked is your next job.
Most of this is the same ground as any technical SEO check, done at the one moment it matters most. The benchmark and the redirect map are the two steps that can’t be done after the fact, so if you do nothing else, do those before the old site comes down.
Common questions
Should I change my domain name at the same time as the redesign?
Not if you can avoid it. Google's site move guidance says to plan changes one after the other rather than all at the same time, because a new domain, a new platform and a new layout at once make it much harder to tell which change caused a drop. If you do move domain, use the Change of Address tool in Search Console, which Google says you only need when moving from one domain or subdomain to another.
How long should I keep 301 redirects after a redesign?
At least a year, and ideally for good. Google's guidance is to keep redirects for as long as possible, generally at least one year, so it can transfer all signals to the new URLs. Links from other sites keep pointing at the old addresses for far longer than that, so I leave redirects in place permanently unless they're causing a problem.
What's the difference between a website redesign and a website migration?
A redesign changes how the site looks and is built. A migration changes where the pages live: new URLs, a new domain, or a move from http to https. Plenty of redesigns quietly become migrations because the new build changes the URL structure, and that's the part that carries the SEO risk.
Should I keep the old sitemap submitted after launch?
For a while, yes. Google's site move guidance suggests submitting a sitemap of the old URLs alongside the new one so you can watch Google process the redirects, then removing the old sitemap once the move has settled, since Google uses the new sitemap from then on.
What should I do with old pages that have no equivalent on the new site?
If the page had no traffic and no links pointing at it, let it return a 404. Google drops 404 URLs from its index and that's the correct outcome for a page that's gone. If it did have traffic or links, redirect it to the closest relevant page, never to the homepage by default.