1920 Agency Talk to us
ServicesWorkHow we workContact

Web design and development

How to Redesign a Website Without Losing SEO Rankings

By 1920 Agency Editorial Team · Reviewed by Rana Zain Usman · Published

The short answer

To redesign a website without losing SEO rankings, keep every URL that earns traffic, give each address that must change a server-side 301 redirect to its closest match, and change only one thing at a time. Google's own guidance says to keep those redirects for at least a year, to expect ranking swings for a few weeks, and not to send many old pages to the home page. Most losses come from broken URLs, lost content or a staging block left on, not from the new look.

A redesign loses rankings when the addresses, text and links that earned them disappear, not because a page looks different. The fix is a short, ordered job: record what ranks today, keep as much of it unchanged as you can, redirect what must move, and watch Search Console after launch. This guide follows Google's own documentation, checked on 4 November 2026, and adds the redirect rules from the day we replaced our own site.

What actually causes ranking loss in a redesign?

Ranking loss almost always comes from the mechanics of the change: URLs that stop working, pages that no longer say what they said, links that disappear, or a block left on at launch. Google's site-move guide is written for domain moves, but its rules apply to any redesign that changes how pages are addressed or built.

What changes in the redesign What can go wrong Where it is fixed
URL structure Old addresses return an error, rankings and links are lost URL map and 301 redirects
Page text and headings The words people searched for are removed Content carry-over
Navigation and internal links Pages lose the links that told Google they matter Link audit before launch
Titles, descriptions, canonical tags Metadata is blank, duplicated or points at staging Template check
Staging settings A noindex rule or password stays on the live site Launch-day check
Speed and layout The new design loads slower or shifts as it loads Pre-launch test

Pages that rank for the same ideas on the first page of results mostly agree on this list. What they rarely do is quote the Google rules behind it, which is where the details below come from.

Step 1: Record what ranks before you touch anything

Before any change, export what the site earns now, so you can tell afterwards whether it lost anything. Google's guide tells you to build the old-URL list from several places: your sitemaps, top-traffic URLs from logs or analytics, links data in Search Console, your CMS export and recent server logs, including images, video, scripts and stylesheets.

Save three things:

  1. A full URL list with each page's title, heading and status.
  2. Search Console data for as far back as it goes: clicks, impressions and queries per page.
  3. The pages that bring enquiries, not just visits. Those get the most care.

Without this baseline you cannot answer the question every owner asks three weeks later: "Did we lose traffic, or is this normal?"

Step 2: Keep every URL that earns traffic

The safest redirect is the one you never need. If a page ranks and its address can stay the same, keep it, and keep the content that earned the ranking. Change a URL only when there is a real reason, such as a clearer structure or a page being merged.

Google's advice on timing and scope is plain:

  • Change only one thing at a time. Do not combine a domain move with a CMS or layout change.
  • Pick a quieter period for the switch if you can.
  • Expect swings. For a medium-sized site, Google says it "can take a few weeks or more" for new URLs to appear.

If the redesign is a rebuild on a new platform, plan it as a project with a rollback copy. Our web design and development service starts from this inventory, because the build and the redirect map depend on each other.

Step 3: Map every old URL to its closest new page

Every address that changes needs one row in a map: old URL, new URL, and the reason. Google tells you to map each old URL to its new destination, then update self-referencing canonical tags and internal links on the new site, and save a sitemap of the new URLs.

Use this decision for each old page:

Situation What to do Why
Same page, same address Keep it, no redirect Nothing to lose
Same page, new address 301 to the new address Passes the old address to the new one
Merged into another page 301 to the page that now covers it Closest equivalent
No relevant replacement Return 404 or 410 Do not send it somewhere unrelated
Page not rebuilt yet Temporary 302 for now, then change it Keeps the old URL as the one in search

The 301 versus 302 difference matters. Google's redirect documentation says permanent redirects make the target the canonical URL in search, and that temporary redirects keep the source page in results. Use a permanent redirect only when you are sure it will not be reversed.

Do not send everything to the home page

A common shortcut is one rule that sends every old URL to the home page. Google's site-move guide says not to redirect many pages to an irrelevant URL such as the new home page. A visitor who clicked a result about one topic lands on a page about everything, and the old page's relevance is lost.

Step 4: Write the redirects correctly

Use server-side permanent redirects. Google recommends 301 or 308 where possible, and calls server-side redirects the most reliably interpreted kind. JavaScript redirects are a last resort, because if the page is not rendered, Google may never see the redirect.

Check these before launch:

  • One hop. Google's guide says Googlebot can follow up to 10 hops, but to keep chains ideally to no more than 3 and fewer than 5. Point each old URL straight at the final address.
  • Redirect to the page that exists after other redirects. If you also change https, www or trailing slashes, test the combined path, not each rule alone.
  • Canonical tags agree with the redirect. Google lists redirects and rel="canonical" as strong signals, and a sitemap as a weak one. Do not send a redirect to one address while the canonical tag names another.

How long to keep the redirects

Keep them for at least a year. This is where two Google pages differ. The site-move guide says to keep redirects "generally at least 1 year". The Change of Address help page says at least 180 days, longer if the old URLs still get Google Search traffic. A guide that quotes one number without the other is leaving out part of the picture. Take the longer one, and do not remove a redirect while the old address still gets visits or links.

Step 5: Build and test on a protected copy

Build the new site where search engines and customers cannot reach it. A password is the safest block. Google's noindex documentation adds a trap: for a noindex rule to work, the page must not be blocked by robots.txt, because if Google cannot fetch the page it never sees the rule.

Before launch, test on the staging copy:

  1. Every URL in the map returns the right redirect or status.
  2. Each page has one H1, a title, a description and a self-referencing canonical.
  3. Internal links use the new addresses and none points at staging.
  4. Forms, tracking and phone links work.
  5. Pages load at least as fast as before and do not shift as they load.

For a longer rebuild, do not take the live site offline. Google says a 503 error page is for urgent shutdowns of 1 to 2 days; for longer closures it suggests an indexable placeholder page returning 200. While a page returns 503, its title, description and structured data cannot be refreshed.

Step 6: Launch day

Do these in order:

  1. Turn on the redirects.
  2. Remove the staging password and any noindex rule, and check robots.txt allows crawling.
  3. Confirm canonical tags point at the new URLs.
  4. Test a sample of old URLs, and use the URL Inspection tool in Search Console on key pages.
  5. Submit the new sitemap and remove the old one.
  6. Update links you control: social profiles, business listings, email signatures and ad destinations.

Only a domain or subdomain move needs the Change of Address tool. Google says not to use it for http to https, www to non-www or path-only changes. It works on domain-level properties and you need to own both the old and new ones.

Step 7: Watch Search Console after launch

Check Search Console every few days for the first month. Google's guide says the old sitemap's indexed count should fall while the new one rises, that sitemap warnings about redirects are expected, and that new URLs should start earning impressions and clicks over time.

Watch Healthy sign Act when
Indexed pages (new sitemap) Rising Flat for weeks while old pages drop
Page indexing errors No new spikes New 404s on URLs that used to rank
Clicks and impressions for the top pages Return toward the baseline A page that ranked drops out entirely
Enquiries from organic search Steady Falls while traffic holds: check forms and tracking

Google gives no recovery date and neither can anyone else. A short dip is expected; a page that vanishes needs its redirect or content checked.

What we did when we replaced our own site

When we replaced our old WordPress site with the current static one on 25 October 2026, the redirect map followed the rule above: nothing was sent to the home page. It sits in one server rules file and has three kinds of answer:

  • 301 to a matching page. For example the old services page, about-us and contact-us addresses now go to their new equivalents, and old posts with a genuinely matching service page go there.
  • 302 for case studies not yet rebuilt. Those old case-study addresses go temporarily to the portfolio, and each moves to a 301 when its page returns.
  • 410 for pages with no replacement. Theme demo posts, category, tag, author and feed addresses and WordPress internals return "gone" rather than being pointed at something unrelated.

We have not published traffic results from the move, and this guide does not claim any. The point is the process: we kept a written map, picked a status for every old address, and kept the temporary redirects marked so they are revisited. If you want a second pair of hands on a redesign, the SEO service covers the baseline, redirect map and post-launch checks.

When to bring in help

Do it yourself if the site is small, URLs stay the same and you can export your data. Ask for help when the platform changes, hundreds of URLs move, or the site brings in enquiries you cannot afford to lose for weeks. For what such work costs in one market, see our website development cost in Pakistan guide; for what ongoing SEO costs, see SEO cost for a small business. Once the new site is live, check that pages can also be found through AI answers, covered in getting your business recommended by ChatGPT.

Sources

Frequently asked questions

Will a website redesign hurt my SEO?

It can, but the design is rarely the cause. Google says a site move can cause ranking fluctuation while it re-crawls, and losses usually come from changed URLs without redirects, removed content, lost internal links or a noindex rule left on after launch. A redesign that keeps URLs and content stable carries much less risk.

How long should I keep 301 redirects after a redesign?

At least a year. Google's site-move guide says to keep redirects generally at least 1 year. Its Change of Address help page says at least 180 days, longer if the old URLs still get search traffic. Use the longer figure, and keep them as long as old URLs still receive visits or links.

How long until rankings recover after a redesign?

Google says that for a medium-sized site it can take a few weeks or more for new URLs to appear, and that it must visit every old and new URL at least once. It gives no recovery date. Track impressions and clicks in Search Console for the new URLs and compare against your pre-launch export.

Should I redirect all old pages to the home page?

No. Google's guide says not to redirect many pages to an irrelevant URL such as the new home page. Send each old URL to its closest equivalent. If nothing relevant exists, return a 404 or 410 so the old address can drop out.

Do I need Google's Change of Address tool?

Only if you move to a different domain or subdomain. Google says not to use it for http to https, www to non-www or path changes inside a site. A redesign on the same domain needs redirects and an updated sitemap instead.

Is a 410 better than a 404 for deleted pages?

For Google Search they are treated the same: Google says all 4xx errors except 429 are handled alike. A 410 tells people and tools the page was removed on purpose. Pick either, as long as you use a 301 wherever a relevant replacement exists.

Can I redesign and change my domain at the same time?

You can, but Google advises changing only one thing at a time, for example not combining a domain move with a CMS or layout change. If you do both at once, a drop is much harder to diagnose. Launch the design first on the same domain, then move the domain later.

Should I show a maintenance page while I rebuild?

Only for one or two days. Google says to use an informational page returning a 503 status for a very short shutdown, and an indexable placeholder returning 200 for longer. Better still, build on a protected staging copy and switch over at launch so the live site never goes dark.