Website redesign without losing Google rankings: a site migration checklist
How to redesign or move a website without losing Google traffic: URL inventory, 301 redirects, meta tags, sitemaps and post-launch checks, step by step.
Short answer: to keep a redesign from wiping out your Google traffic, before launch you collect every old URL, map each one to a new page with a permanent 301 redirect, and carry over the titles, descriptions, headings and copy that already rank. After launch you lift any indexing block, submit the new sitemap and watch for errors for several weeks. Most post-redesign ranking drops aren’t a Google mystery — they’re one of these steps skipped.
A fresh design, a faster site and an easier admin are all good reasons to redesign. But a site that has spent years earning rankings holds them through specific URLs, content and links. If the URLs change and the copy gets “trimmed for the design”, Google sees a different website. Below is the migration checklist we use ourselves, plus the parts a business owner can verify without a developer.
Why sites lose rankings after a redesign
| Cause | What happens | Prevention |
|---|---|---|
| URLs changed without redirects | Old URLs return 404, links and accumulated value are lost | A 1:1 redirect map before launch |
| The site launched blocked from indexing | A staging noindex or “Disallow: /” in robots.txt made it to production | A dedicated launch-checklist item |
| Copy was cut or removed | The page no longer answers the query it ranked for | Move ranking copy over and improve it, don’t cut it |
| Titles and descriptions were lost | The template puts the same title on every page | A meta-tag sheet and a post-launch check |
| Internal linking broke | Key pages are hidden in menus or reachable only via JavaScript | Plain HTML links, click depth of 3 or less |
| The new site is slower | Heavy sliders and video above the fold hurt Core Web Vitals | Speed tests before and after, image optimisation |
| Language versions lack hreflang | Google mixes up languages and shows the wrong version | hreflang on every page pair |
How risky is your redesign?
Not every redesign carries the same SEO risk. Place your project before work starts:
| Scenario | Risk | What matters most |
|---|---|---|
| New design, same URLs and copy | Low | Keep titles, headings and copy; don’t slow the site down |
| New menu and URL structure on the same platform | Medium | A full redirect map and updated internal links |
| Moving to another CMS (e.g. from a site builder to WordPress or Shopify) | High | The platform dictates URL patterns, so nearly every page needs a redirect |
| Changing domain | High | Redirects for the whole old domain, Change of Address in Search Console, every external profile updated |
| Merging several sites or language versions | High | Decide which page becomes the main one for each topic to avoid duplicates |
Pre-launch checklist
1. Inventory the old site
- Collect every URL: from the sitemap, from a crawl (Screaming Frog, for example) and from Google Search Console’s Performance report for the last 12–16 months, so you see which pages get impressions and clicks.
- Add pages with external backlinks if you have Ahrefs, Semrush or Search Console’s Links report.
- For each URL, save the title, description, H1, canonical and clicks. This is your control sheet.
- Make sure the domain, hosting, DNS and Google Search Console are registered to you, not to a previous contractor. If you do not have access, get it back first: see your web developer disappeared: how to take back your website.
- Record a baseline: indexed pages, clicks and impressions in Search Console, speed of key pages.
2. The redirect map
- Each old URL → the closest matching new page. Never everything to the homepage.
- Permanent redirects — 301 (or 308) — in one hop, with no “old → interim → new” chains.
- Pages you remove with no replacement deliberately return 404 or 410.
- Cover the variants: www and non-www, http and https, trailing slash or not, old category, tag and pagination URLs, and linked images and PDFs.
A sample redirect map
| Old URL | New URL | Action |
|---|---|---|
| /services/kitchen-remodeling.html | /services/kitchen-remodeling/ | 301 |
| /index.php?page=contact | /contact/ | 301 |
| /news/spring-sale-2019/ | — | 410, the promotion ended long ago |
| /shop/tiles/?sort=price | /shop/tiles/ | canonical URL without the parameter |
Keep this sheet in Google Sheets: the redirects are set up from it and the launch is checked against it.
3. Content and meta tags
- Copy on pages that drive traffic is carried over in full or improved — not reduced to two lines under a nice image.
- A unique title and description per page, one H1, a logical H2/H3 structure.
- Image alt text, schema.org markup, hreflang for language versions, self-referencing canonicals. Clean markup and clear copy also help AI search quote you correctly: see how to show up in ChatGPT and Google AI answers.
- Internal links updated to the new URLs, so neither visitors nor Google bounce through redirects.
4. Staging
- The staging site is password-protected or noindexed so Google doesn’t index a duplicate.
- Crawl the staging site: broken links, missing titles, duplicates, stray noindex tags.
- Test redirects from a list: every old URL should return one 301 and then a 200.
- Compare the speed of key pages on the old and new site.
Launch-day checklist
- Remove the indexing block. Check robots.txt, the robots meta tag and the X-Robots-Tag HTTP header. This is the most common and most expensive mistake.
- Switch on redirects and spot-check the 20–30 most important old URLs.
- Check analytics: GA4, Tag Manager, ad pixels and goals work on the new site and don’t fire twice.
- Submit the new sitemap in Google Search Console and Bing Webmaster Tools.
- Inspect key pages with Search Console’s URL Inspection tool: reachable, indexable, correct canonical.
- If the domain changed, use the Change of Address tool in Search Console and update links in your Google Business Profile, social profiles, directories and ads.
After launch: what to monitor for 4–8 weeks
- Search Console indexing report: new 404s, “Discovered – currently not indexed”, pages with noindex.
- Clicks and impressions per page against the baseline. Short-term swings are normal; a steady drop on specific pages means something to investigate.
- 404s in server logs or analytics — add the missing redirects.
- Core Web Vitals and mobile speed.
- Leads and sales: a redesign should improve conversion, not just looks.
If traffic does drop, don’t roll everything back. First find the pages that lost the most clicks and check each one: does the old URL redirect, is the new page indexed, did the copy and headings survive? The cause is usually there, and the fix is targeted.
Google’s site-move documentation recommends keeping redirects for at least a year. We suggest never removing them: external links to old URLs live on for years.
Platform specifics
- WordPress. Under Settings → Reading, make sure “Discourage search engines from indexing this site” is unchecked. Redirects live in your SEO plugin, the Redirection plugin or at server level.
- Shopify. Product and collection URLs have fixed prefixes (/products/, /collections/), so moving to Shopify almost always needs redirects. Add them under URL Redirects, including by CSV import.
- Webflow. Permanent redirects are set in site settings; check that the webflow.io staging domain isn’t open to indexing.
- Squarespace. Redirects are configured through URL Mappings; the sitemap is generated automatically.
What the owner can check without a developer
| Check | How |
|---|---|
| The site is open to Google | Open yourdomain/robots.txt — there should be no “Disallow: /” for all user agents |
| Old pages don’t lead to 404 | Take 10 URLs from old bookmarks, emails or ads and open them |
| Pages are indexed | The Pages report in Google Search Console a week or two after launch |
| Traffic hasn’t collapsed | Compare Search Console clicks for the same weeks before and after launch |
| Leads still arrive | Send a test enquiry from every form, including on your phone |
From our work
Migrations are a regular part of our work, and the rule is always the same: move the data in full and prove it with a check, not a promise. A few real projects from our portfolio:
- Policy institute website on Webflow. We rebuilt the CMS, splitting programmes, calendars and reports into separate collections; the data was migrated without loss and verified with the client.
- Veterinary store migration. A full catalogue export — products, brands, pages, images and settings — with a verification log.
- Shopify store for a supplements brand. Besides the checkout and integrations, we built a bulk SEO-field update script and a tool to migrate data between Shopify stores; every change was tested on a staging store first.
Our own website works the same way: each page can list its old URLs, and the system serves a 301 from them to the current address automatically.
When to bring us in
If your website is outdated and a redesign is coming, build SEO migration into the plan from day one — it’s far cheaper than rescuing rankings afterwards. We do website development and redesigns with rankings carried over. Whoever builds your new site, ask for the SEO migration to be listed as a separate item in the proposal; more questions worth asking are in how to choose a web agency. If the redesign has already happened and traffic dropped, start with a technical audit: we’ll find missing redirects, blocked pages and lost content. Ongoing search work is covered by technical and local SEO, and if you’re barely visible at all, see “Not showing up on Google” and run the 15-minute check for a website missing from Google.
Send us your website and redesign plan and we’ll tell you what to sort out before launch.
FAQ
Will my rankings drop after a redesign?
Short fluctuations after a big change are normal while Google recrawls and re-evaluates pages. A sharp, lasting drop usually means a migration error: missing redirects, a site blocked from indexing, or lost content and headings. The checklist is there to prevent exactly that.
How long should I keep 301 redirects from old URLs?
As long as possible. Google recommends keeping redirects after a site move for at least a year; in practice it’s better never to remove them, because external links and bookmarks keep pointing to old URLs.
Can I just redirect all old pages to the homepage?
Better not. Google often treats mass redirects to the homepage as soft 404s, and the value of the old pages is lost. Each old URL should point to the closest matching new page; pages removed without a replacement should return 404 or 410.
What should I do in Google Search Console after launch?
Submit the new sitemap, test a few key pages with the URL Inspection tool and watch the indexing and 404 reports for several weeks. If the domain changed, use the Change of Address tool.
How much does SEO support for a redesign cost?
If we do the redesign, migration is part of the job; redesigns start at €1,200. If another team builds the site, we can prepare the redirect map and check the launch as a technical audit, from €300.