A website redesign is meant to make a site better. Too often, organic traffic drops in the weeks after launch, and the business blames the new web design. In most cases the design is not the cause. The cause is a handful of migration steps that were skipped: pages that moved without a 301 redirect, a block left over from the test site, or content that was cut. All of these can be avoided, and a redesign that ignores SEO can undo months of SEO efforts in a few days.
This post explains how to redesign your website without losing SEO rankings, in plain steps: what really causes ranking losses, what Google says about site moves, a baseline to take before you start, a redirect map, a launch-day checklist and what to watch afterwards. We re-read Google’s site move documentation on 9 October 2026. Where something is our own experience, we say so. If you are close to launch, run it alongside our website launch checklist.
Quick summary, if you’re short on time:
- Google says to expect temporary ranking fluctuation: with any significant change to a site, rankings may move while Google recrawls and reindexes it.
- For a medium-sized site, Google says it can take a few weeks or more for new URLs to replace old ones in search results, and longer for larger sites.
- If any URL changes, Google recommends server-side permanent redirects (301 or 308) from old URLs to new ones, and says permanent redirects do not cause a loss in PageRank.
- Keep the redirects for as long as possible, generally at least 1 year. Avoid redirect chains, and keep them ideally to no more than 3 hops.
- If you used robots.txt blocks or noindex rules on the test site, Google says to prepare how to remove them when the move starts.
Jump to a section:
- Why redesigns lose rankings
- What Google says about site moves
- Which type of redesign do you have?
- Before you start: take a baseline
- Build the redirect map
- Keep the test site out of search
- The launch-day checklist
- What to watch after launch
- What we check after our own pushes
- A prompt to draft your redirect map
- Questions about redesigning without losing rankings
Why redesigns lose rankings
Google is open about some movement being normal. After that, losses usually trace back to one of these causes, which are ordered here by how often we would check them first:
- URLs changed with no redirect. Old addresses that carried rankings and links now lead to a “page not found” error.
- The new site is blocked from search engines. A noindex tag or a robots.txt block, added to the test site, goes live with it.
- Pages were removed or merged. A page that used to rank for a service is gone, or its content was cut down until it no longer answers the search.
- Titles, headings and copy were rewritten without checking what the page ranked for.
- Internal links were not updated, so the redesigned site links through redirects or to old addresses.
- The new site is slower. Heavy images, sliders and scripts can make the redesigned site worse for visitors than the old one, and basic image optimization is often skipped.
- Technical SEO errors creep in, such as missing canonical tags, duplicate pages and broken links.
- Tracking and tags were left out, so you cannot even see what changed.
None of these are caused by a better look. They are caused by missing steps around the redesign process, and each has a fix below.
What Google says about site moves
Google’s closest guidance for a redesign is its documentation on site moves with URL changes, last updated on 20 August 2026, and a separate page on changing your hosting without changing URLs. Here are the points that matter for a redesigned site:
- Expect fluctuation. Google says rankings may fluctuate while it recrawls and reindexes your site, and that for medium-sized websites it can take a few weeks or more for Google to gradually show the new URLs instead of the old ones. For larger sites it takes longer.
- Use server-side permanent redirects. Google recommends HTTP permanent redirects such as 301 and 308 from old URLs to new URLs, following your mapping.
- Don’t worry about link credit. Google says 301 and other permanent redirects don’t cause a loss in PageRank.
- Avoid chains. Googlebot can follow up to 10 hops, but Google advises redirecting to the final destination directly, and if that is not possible, keeping a chain ideally to no more than 3 and fewer than 5.
- Keep redirects a long time. Keep them for as long as possible, generally at least 1 year, so Google can transfer signals, including links from other sites to your old URLs.
- Give each new URL a self-referencing canonical, and update your internal links to the new URLs.
- Return the right error for removed pages. If you are not moving all old content, Google says the removed URLs should return a proper 404 or 410 on the new site.
- Move in sections if the site is large. This makes problems easier to spot and fix.
Which type of redesign do you have?
| What is changing | What it means for SEO |
|---|---|
| Only the look and layout. Every URL stays the same | No redirects needed. Protect titles, headings and content, remove any test-site blocks, and check speed |
| Some URLs change or pages merge | Build a redirect map and use 301 or 308 redirects for each changed URL |
| Hosting or platform changes, URLs stay the same | Follow Google’s hosting guidance: test a copy of the new site and make sure Googlebot can reach it |
| You move to a new domain or subdomain | Redirects plus a Change of Address request in Search Console for the old site |
| Only HTTP to HTTPS, www to non-www, or paths inside the same domain | Redirects are needed, but Google says you don’t need the Change of Address tool for these |
Redesigning a website is also a chance to improve on-page SEO, such as titles, headings and internal links, as long as you plan each change. Clear navigation and a fresh sitemap also help search engines find the new pages. Most small business redesigns land in the second row: the design changes and a few URLs change with it. Check which row you are in before anything else, because it decides how much work the migration needs.
Before you start: take a baseline
You cannot tell whether a redesign worked unless you know where you started. Do these things while the old site is still live:
- Set your SEO goals first. For most small businesses the goal is simple: keep organic enquiries steady through the move, then grow. Write it down so that you can judge SEO performance afterwards.
- Export your top pages and queries from Google Search Console. Save clicks, impressions and average position for the last three months. Our post on branded vs non-branded search shows how to read those numbers properly.
- Save your Google Analytics data for organic landing pages, so you can compare organic search traffic and enquiries before and after.
- Crawl the old site. A free tool like Screaming Frog’s free version, which crawls up to 500 URLs, gives you the full list of old URLs, titles and headings. This list is the starting point of your redirect map.
- List the pages that matter most. These are the pages with the most organic traffic, the most enquiries and the most links. They get the most careful treatment.
- Record your key rankings for your main service keywords, with the date.
- Do a quick SEO audit. Fix broken links and thin pages on the old site first, so you do not carry problems across.
Build the redirect map
The redirect map is a two-column list: every old URL, and the new URL that replaces it. Write it before anyone sets up a redirect, and use it to check the finished site.
- One old URL, one best new URL. Send each old page to the page that now serves the same purpose. Do not send everything to the homepage.
- Use a 301 redirect or 308, set on the server, not in JavaScript. Google’s page on redirects says to use JavaScript redirects only if you cannot do server-side or meta refresh redirects.
- Point links at the final address. Avoid chains such as old page to a second page to the new page.
- Handle pages with no replacement. If a page is gone and nothing replaces it, Google says it should return a proper 404 or 410. Our view is that a closely related page is a better redirect target than a blank error when a real match exists.
- Include variants. Cover http and https, www and non-www, and trailing slashes, so that all versions end on one address.
Our post on building a keyword-to-URL map pairs well with this step, because it makes sure each new page still targets the search its old page won.
Keep the test site out of search
A test or staging copy of the new site should not be indexed. Many teams block it with robots.txt or a noindex tag. That is sensible, but it is also the most common reason a new site is invisible in the first week. Google’s guidance is to prepare what robots.txt should look like when the move starts, and, if you use noindex rules during development, to prepare a list of URLs from which you will remove them. Put this on the launch checklist as its own line.
The launch-day checklist
- robots.txt allows crawling of the live site, with no leftover block from the test site.
- No noindex tag on pages that should rank. Check the homepage and your top service pages by viewing the page source.
- Redirects work. Test a sample of old URLs from the map, and confirm each lands on the right page in one step.
- Each new page has a self-referencing canonical tag.
- Titles, meta descriptions and H1s on key pages match the plan, and you have not lost your keyword in the title.
- Internal links point to the new URLs, not to old ones through a redirect.
- The new XML sitemap is live and lists only the new URLs. Submit it in Search Console.
- Analytics and tag manager are installed and receiving data, and form and call tracking still work.
- Forms and phone links are tested on a phone and a desktop.
- Speed check. Run PageSpeed Insights on your homepage and main service page and compare with your old numbers.
- Search Console properties for every address variant are verified. If you changed domain, submit the Change of Address for the old site.
- Remove the “coming soon” or maintenance page, if one was used.
What to watch after launch
| When | What to do |
|---|---|
| Launch day | Run the checklist above, submit the sitemap, and inspect your homepage with the URL Inspection tool |
| First week | Watch the Sitemaps and Page indexing reports. Check that old URLs are redirecting and new ones are getting indexed. Look for new 404 errors and fix them |
| Weeks 2 to 4 | Compare clicks and impressions for your top pages with your baseline. Expect movement, and look for pages that disappeared |
| Months 2 and 3 | Compare enquiries and rankings for your main keywords. Fix any page that lost its search by restoring the missing content or fixing its redirect |
| After a year | Review the redirects. Google says to keep them at least a year, and from users’ perspective to consider keeping them indefinitely |
Google says its Search Console reports can help during a move. It names the Sitemaps report for seeing how many submitted URLs have been indexed. Do not judge the result in the first few days. Google’s own wording for a medium-sized site is “a few weeks or more”.
What we check after our own pushes
We move our own site with a full-site migration plugin, and one lesson is worth sharing. After a full-site replace, the SEO plugin settings and its link to Google were wrong, and we had to reconnect and check them. So we now check these after each push: that the SEO plugin is still connected, that the site type and schema settings are still correct, and that titles and descriptions are still in place. If you move a site with a plugin or a new host, check your SEO plugin first, because it is a common thing for a migration to reset. We have seen this on our own site, and we have not tested other plugins.
A prompt to draft your redirect map
Matching hundreds of old URLs to new ones by hand is slow. An AI tool can draft the first pass if you give it your real lists. It cannot see your site, so you must check every line.
Act as a careful site migration assistant. Match my old website URLs to my new website pages and draft a redirect map.
My details:
– Old URLs, one per line, with each page’s title: [paste the list from my crawl]
– New pages, one per line, with each page’s title and address: [paste the list]
– Pages I know are deleted or merged: [list, or say none]
– My top 10 pages by organic traffic: [list]Please do the following:
1. Make a table with these columns: old URL, best new URL, confidence (high, medium or low), and a one-line reason.
2. Mark every old URL that has no good match, and say whether it should return a 404 or 410, or redirect to a related page.
3. Flag any case where several old pages could map to one new page, in case content was merged.
4. List my top 10 pages first, and mark any that have a low-confidence match.Rules:
– Use only the URLs I gave you. Do not invent addresses or pages.
– Do not send everything to the homepage.
– If two matches are possible, show both and say which you prefer.
– Write in plain, simple English.
Check the low and medium matches by hand, and test a sample of the final redirects on the live site before and after launch.
Questions about redesigning without losing rankings
Will a website redesign hurt my SEO?
Not by itself. Google says rankings may fluctuate for a while during any significant change, but lasting losses usually come from missing redirects, blocked pages or removed content. A redesign that keeps URLs and content, or redirects them properly, can hold its rankings.
Do I need 301 redirects if my URLs don’t change?
No. If every URL stays the same, there is nothing to redirect. You still need to remove any test-site blocks, keep your titles and content, and check speed and tracking.
Do 301 redirects lose ranking value?
Google says 301 and other permanent redirects don’t cause a loss in PageRank. It recommends server-side permanent redirects such as 301 and 308 for moved URLs.
How long does it take to recover rankings after a redesign?
Google says a medium-sized site can take a few weeks or more for the new URLs to replace the old ones in results, and larger sites take longer. We cannot promise a date, so compare against your baseline over weeks, not days.
How long should I keep the old redirects?
Google says to keep them for as long as possible, generally at least 1 year, and that from the user’s perspective you may want to keep them indefinitely.
Should I redirect every old page to the homepage?
No. Send each old page to the new page that serves the same purpose. If a page has no replacement, Google says it should return a proper 404 or 410.
Do I need to use the Change of Address tool?
Only if you move to a new domain or subdomain. Google says you do not need it for HTTP to HTTPS, switching between www and non-www on the same domain, or moving paths within the same domain.
What should I check if traffic drops after launch?
Check, in order: whether the site is blocked by robots.txt or a noindex tag, whether the redirects work, whether top pages lost content or titles, whether the site got slower, and whether tracking is still firing. Then compare against your baseline in Search Console.
Where this matters
A website without a migration plan is the real risk, and a redesign does not have to cost you traffic. Take a baseline, map every old URL to a new one, keep the test site out of search until launch, run a launch-day checklist and watch Search Console for weeks. The step most often skipped is the one that costs the most.
Planning a redesign? See our website development service, or send us your site address and we will tell you what we see.
