How to Redesign or Migrate a Website Without Losing Google Rankings

To redesign or migrate a website without losing rankings, record every URL that earns traffic, links or leads before you change anything. Keep those URLs where possible, and give each one that must change a 301 redirect to its closest new equivalent. Carry over the content, titles and internal links, test everything on a staging site, and watch Search Console closely after launch.

Why redesigns lose rankings

Google ranks individual pages, and a redesign can quietly remove or alter the things those pages ranked for. The usual causes are all preventable:

• Changed URLs with no redirects. Old addresses return errors, and the links pointing to them stop counting.
• Everything redirected to the homepage. Google tends to treat these as soft 404s, so the old page’s value is lost.
• Thinner content. Copy gets trimmed to suit a cleaner design, and the detail that matched searches goes with it.
• Rewritten titles and headings that drop the terms people search for.
• Fewer internal links. A simplified menu can leave important pages buried several clicks deep.
• Staging settings carried over. A noindex tag or robots.txt block from the test site ends up on the live one.
• Slower templates, or content that appears only after heavy JavaScript runs.

Inventory everything that ranks now

Build one spreadsheet listing every URL worth protecting. Pull from these sources:

1. A full crawl of the current site with a crawler such as Screaming Frog, capturing each URL’s status code, title, meta description, H1 and canonical tag.
2. Search Console’s Performance report, exported by page over the longest date range available, to see which URLs earn clicks and impressions.
3. Google Analytics landing pages for organic traffic, with the key events (forms, calls, bookings) each page produces.
4. Search Console’s Links report, to find the pages other sites link to most.
5. Your XML sitemap, plus PDFs, images and other files that receive visits.

Add columns for each page’s new URL and any notes. Then save a benchmark of organic clicks, leads by page and positions for your most important searches. You’ll need it to judge the launch and to spot problems quickly.

Keep URLs where you can and redirect the rest one to one

The safest redirect is the one you never need. If the new platform lets you keep the existing URL structure, keep it. When URLs must change because of a new platform, a restructure, a move to HTTPS or a new domain, map them carefully:

• Use permanent server-side redirects (301 or 308) from each old URL to the most relevant new page.
• Map one to one. An old page about water heater repair should redirect to the new water heater repair page. A general services page or the homepage is a poor substitute.
• Merge with care. When two old pages become one, redirect both to the combined page and keep the best content from each.
• Avoid chains and loops. If older redirects already exist, update them to point straight at the final URL.
• Let dead pages go. Pages with no traffic, links or leads can return a 404 or 410 without harm.
• Update internal links so they point to new URLs directly instead of passing through redirects.

Google’s documentation on site moves recommends keeping redirects in place for at least a year, and leaving them permanently is simpler still. If you’re changing domains, also use the Change of Address tool in Search Console. When the redirect map runs to hundreds or thousands of URLs, a dedicated website migration service is worth considering.

Keep content parity on every important page

A new design can change how a page looks without changing what it says. For each page in your inventory, check that the new version keeps:

• The main body copy, or a rewrite that covers the same topics in at least the same depth
• The title tag, meta description, H1 and subheadings, unless you’re deliberately improving them
• Internal links to and from related pages, and a spot in the navigation for pages that had one
• Structured data, image alt text and canonical tags
• FAQs, reviews and other sections that answered searchers’ questions

Content inside tabs or accordions is fine as long as it’s in the page’s HTML. Content that loads only after a click or a scripted request is riskier, so check what Google sees with the URL Inspection tool once the site is live.

Test on a staging site before launch

Build the new site on a password-protected staging server. A robots.txt block alone stops crawling, yet blocked URLs can still be indexed if other pages link to them. Before launch, work through this list:

• Crawl the staging site for broken links, missing titles and pages that are noindexed by mistake.
• Confirm that canonical tags and internal links use the live domain and never the staging address.
• Run every URL from your inventory against the new redirect rules and confirm each one returns a single redirect to a working page.
• Test the mobile templates in PageSpeed Insights.
• Submit every form, tap every phone link and confirm Google Analytics records each key event.
• Generate a new XML sitemap that lists only live, indexable URLs.

Choose the launch date with care. Going live right before your busiest season, or on a Friday afternoon when nobody is around to fix problems, adds avoidable risk.

Launch day and the weeks after

On launch day

1. Remove the staging password and any noindex tags, and check robots.txt on the live site.
2. Switch on the redirects and spot-check a sample of old URLs from your inventory.
3. Submit the new XML sitemap in Search Console and inspect your most important pages with the URL Inspection tool.
4. Update links you control elsewhere: your Business Profile, social profiles, directory listings and ad destination URLs.

In the weeks that follow

• Check the Page indexing report for new 404s, soft 404s and pages dropping out of the index, and add redirects for any old URLs you missed.
• Compare clicks and impressions by page in the Performance report against your benchmark.
• Watch organic key events in Google Analytics, since leads are what you’re protecting.
• Crawl the live site again to catch anything that changed during deployment.

Google’s site move guidance notes that rankings can fluctuate while it recrawls and processes a change, and that larger sites take longer to settle. A temporary dip is normal. A drop that persists after your key pages have been recrawled points to something that didn’t make it across, and your inventory spreadsheet tells you where to look.

When to bring in help

A small site that keeps its URLs and content can usually be redesigned safely by following the steps above. Get specialist help when you’re changing platforms or domains, merging sites, running an online store with thousands of product URLs, or when rankings have already fallen after a launch. An SEO audit before you start shows what’s worth protecting, and our website design team plans every redesign around the redirect map and content inventory.