What goes wrong
Why a website redesign
loses rankings.
Google doesn't rank a website as a whole. It ranks individual URLs for individual searches, based on what's on them and what links to them. A redesign tends to change all of that in one day. These are the six changes behind almost every post-launch traffic drop.
Disallow: / line in robots.txt copied over at launch can remove the whole site from Google.Stage 1 · Before design
Inventory every URL
that earns traffic.
You can't protect what you haven't listed. Before anyone opens a design tool, build one spreadsheet with every URL on the current site, then mark each one keep, merge, redirect or remove. Four sources fill it in.
| Source | What it tells you | Where to get it |
|---|---|---|
| A full crawl | Every URL that exists, including PDFs, images, tag pages and old landing pages nobody remembers. | A crawler such as Screaming Frog, plus the current XML sitemap. |
| Search Console: Pages | Which URLs earn impressions and clicks, and for which searches. These are the pages to protect first. | Performance report, Pages tab, set to the last 16 months and exported. |
| Search Console: Links | Which URLs other sites link to. Each one needs a redirect even if it gets no search traffic. | Links report, "Top linked pages", exported. |
| Analytics landing pages | Pages people arrive on from ads, email and social, which a search report won't show. | GA4, Engagement, Landing page report. |
Merge the four exports on the URL column. Anything with search clicks, a backlink or campaign traffic is marked keep or redirect, never simply removed.
Stage 2 · During build
The redirect map: the most
important file in website redesign SEO.
The redirect map is a two-column list: every old URL that changes, and the new URL it should go to. Get it right and Google transfers each page's history to its replacement. Get it wrong and that history is lost, however good the new site looks.
| Old URL | New URL | Why |
|---|---|---|
| /services/boiler-repair.html | /boiler-repair/ | Same page, new address: one-to-one 301. |
| /combi-boilers/ and /system-boilers/ | /boiler-types/ | Two thin pages merged into one: both redirect to the merged page. |
| /news/2019-trade-show/ | /news/ | No equivalent, no traffic, one old link: closest parent section. |
| /?p=482 | /heating-maintenance/ | Old WordPress ID link still used in an email footer. |
Example · illustrative. Redirect duration: John Mueller, Google, "Ask Googlebot", as reported by Search Engine Journal on 2 December 2021, checked October 2026.
Stage 3 · During build
What to carry across
to the new templates.
A redirect tells Google where a page went. What it finds when it gets there decides whether the page keeps its ranking. For every URL marked keep or redirect, carry these across, or improve them deliberately.
Stage 4 · During build
Build on staging
without it leaking.
The new site should be built on a copy that search engines can't reach, while the current site stays live and earning. The risk runs both ways: staging getting indexed before launch, and staging's blocks reaching the live site after it.
Disallow: / blocks the whole site. The live file should only block what you mean to block.Stage 5 · Launch day
The website redesign
SEO checklist for launch day.
Run these checks on the live domain within an hour of the switch, while the old site is still a backup you can roll back to. Each one has a clear pass.
| Check | How | Pass when |
|---|---|---|
| 1. Redirects work | Crawl the full list of old URLs from the redirect map. | Every one returns a single 301 to the right page, then a 200. |
| 2. Top pages load | Open the 20 pages with the most search clicks. | Each loads on its planned URL with its content intact. |
| 3. Nothing blocks indexing | View the source of key pages and read robots.txt. | No noindex tag, no Disallow: /, no staging password. |
| 4. Canonicals are right | Check the canonical tag on each template. | Points at the live URL of the same page, never staging. |
| 5. Titles and descriptions | Crawl the new site and export titles. | No duplicates, none empty, none left as theme defaults. |
| 6. XML sitemap | Open the sitemap and submit it in Search Console. | Lists only live, indexable new URLs. |
| 7. Internal links | Crawl the new site for broken links. | No links to old URLs or 404s from inside the site. |
| 8. HTTPS and one hostname | Try http://, https://, with and without www. | All four end on the same https address in one hop. |
| 9. Structured data | Test key templates in Google's Rich Results Test. | Valid, with no errors on pages that had rich results before. |
| 10. Analytics and Search Console | Open real-time analytics and the Search Console property. | Visits recorded; property still verified on the new site. |
| 11. Forms and enquiries | Submit every form and complete a test purchase if there's a store. | Each one arrives where it should. |
| 12. Speed on a phone | Run PageSpeed Insights on the homepage and a top page. | No worse than the old site; fix anything that is. |
Planning a redesign with an agency? Put this list in the brief so it's priced in from the start. Our free website redesign RFP template lists the SEO requirements for your redesign RFP so you can tick them through.
Stage 6 · After launch
The first eight weeks
in Search Console.
Some movement while Google recrawls the old URLs and follows the redirects is normal. What matters is catching real problems early. Check these weekly.
Inspect the top pages
Use URL Inspection on your most important new URLs and request indexing, so Google sees them sooner.
Watch for 404s
The Pages report lists URLs Google can't find. Each one is a missing redirect: add it to the map.
Compare like for like
Compare impressions and clicks with the same weeks before launch, page by page, not just the site total.
Decide what to fix
Pages still well below their old numbers need their content or redirect checked against the inventory.
Moving to a new domain as well? Use the Change of Address tool in Search Console after the redirects are live. It's only for domain changes, not for new URLs on the same domain.
Reading the results
What a redesign planned
around search looks like.
We redesigned The Stairlift Company's site for older readers and planned every page around what local buyers search for. The old site was found almost only for its own name, so it had little to lose; what the numbers show is what planning around search adds.
| Measure | Six months before | Six months after |
|---|---|---|
| Search impressions | 364 | 16,900 (46×) |
| Clicks from Google | 9 | 103 (11×) |
| Average position | 4.3 | 31.7 |
Why the average position got "worse". Before the redesign the site appeared mostly for its own name, near the top. Afterwards it appeared for 554 different searches in 28 days, many starting on pages two to five, and 45 of them averaging page one. Judge a redesign on impressions, clicks and the number of searches you appear for, not on average position. Read the Stairlift case study →
Source: the client's Google Search Console, last six months compared with the six before; positions are 28-day averages, checked September 2026.
Beyond keeping rankings
Website redesign for SEO,
not just around it.
Protecting what ranks is the minimum. A redesign is also the cheapest moment to fix the structure that holds a site back, because every template is being rebuilt anyway.
Who wrote this
Written by the engineer
who runs the migrations.

Naveen Kumar
Founder & lead engineer · Based in Chennai, India, working 9am–6pm US Eastern with clients across the US, UK, Europe and Australia
I've built, rebuilt and migrated WordPress, WooCommerce and custom-coded sites for years, and the redirect map is the part of every redesign I check myself. This guide is the process we follow on our own website redesign services. Use it with any developer; if you'd like us to do it, send the URL. More about how I work →
Questions, answered
Website redesign SEO:
common questions.
Will a website redesign hurt my SEO?
Only the parts that change without a plan. Rankings belong to URLs and to the content on them, so a redesign that changes URLs without redirects, cuts the text that ranked, or launches with a noindex tag left on will lose traffic. A redesign that keeps or redirects every URL and carries the ranking content across usually holds its position, and often gains.
Can you redesign a website without losing SEO?
Yes, if the migration is planned before design starts. List every URL that earns traffic or links, keep those URLs where you can, give every changed URL a 301 redirect to its closest new page, carry titles and content across, build on a staging copy search engines can't see, and check Search Console weekly after launch.
How long do rankings take to settle after a redesign?
Most of the movement happens while Google recrawls the old URLs and follows the redirects. On a small site that is usually a few weeks; larger sites take longer. Some fluctuation in that window is normal. A steady fall after it, or a rise in 404 errors, means something in the migration needs fixing.
How long should I keep 301 redirects after a redesign?
At least a year. John Mueller of Google has said Google needs to see a redirect several times before it treats the move as permanent, and recommends keeping redirects in place for at least one year. In practice, keep them for as long as the old URLs might still be linked or bookmarked. They cost almost nothing to leave in place.
Should I redirect old pages to the homepage?
No. Send each old URL to the page that now answers the same question. A redirect to an unrelated page, including the homepage, is usually treated by Google as a soft 404, so the old page's ranking value is lost anyway. If there is genuinely no equivalent, redirect to the closest parent section or let the page return a 404 or 410.
Do I have to change my URLs when I redesign?
No, and keeping them is the safest option. The lowest-risk migration is the one you don't make: if a page keeps its URL and its core content, there is nothing for Google to re-learn. Change URLs only where the new structure genuinely needs it, and redirect every one that changes.
Should a staging site be noindex or password-protected?
Password-protected. A noindex tag only works once a search engine has already found the page, and it is easy to copy onto the live site at launch. A password keeps staging out of search entirely. Whichever you use, remove it at launch and check the live site's robots.txt and robots meta tags on launch day.
Why did my average position drop after a redesign?
Often because the site is now found for more searches, not fewer. New searches tend to start on pages two to five and climb, which pulls the average down while total impressions grow. Compare impressions, clicks and the number of searches you appear for before judging a redesign on average position alone.
Is a redesign a good time to improve SEO?
Yes. Redesigning for SEO, not just around it, means planning each page around a search people make, merging thin pages that compete with each other, fixing slow templates and adding the answers buyers look for. That is what turned a stair lift installer's redesign into 46 times more search impressions.
What should a website redesign SEO checklist include?
A URL inventory, a redirect map, the titles, meta descriptions, headings and schema carried across, staging blocked from search, and launch-day checks for redirects, robots rules, the XML sitemap, canonical tags, analytics and forms. Then weekly Search Console checks for 404s, indexing and impressions for the first two months. The full list is in the launch-day section above.