How to keep SEO rankings when you rebuild or move a client site
Short answer: To keep your search traffic when you rebuild or move a site, keep every URL the same where you can, map each changed URL to its replacement with a 301 redirect (a permanent forward from the old address to the new one), keep titles, headings and text for pages that rank, submit a fresh sitemap, and check analytics and Google Search Console (Google's free tool that shows how a site performs in search) before and after launch. Some dip is normal, and no process guarantees rankings, so promise the process and not the result.
The new site looks great, the launch date is Friday, and nobody has checked what happens to the 200 pages Google already knows.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
Keep rankings by changing as little as possible that search engines already understand. Same URLs, same titles, same page text for the pages that bring in traffic, and a 301 redirect for every address that must change. Then test before launch and watch the numbers for at least two months after. That is the whole approach. The rest of this page is the checklist to run it.
It is written for agencies that run client sites. The checklist works for a redesign on the same platform, a move to a new platform, and a rebuild with an AI tool such as Ploy, an AI platform that rebuilds and hosts sites. This is practical information from vendor and Google documentation, not a promise of results. For the sales and pricing side of migration work, see website migration as a service.
This page may contain affiliate links from which Blur Studio earns commissions.
First, which kind of move is it?
The risk is different for each, and most guides mix them up.
- Same domain, same URLs, new design or platform. The lowest risk. Search engines see the same addresses with new pages behind them. No dataset covers this case, so state it as lower risk, not safe.
- Same domain, some URLs change. Medium risk. Every changed address needs a redirect.
- New domain. The highest risk. Studies cover this case only. A Search Engine Journal study of 892 domain migrations found an average of 523 days for the new domain to match the old one's estimated traffic, with 17 percent not back after 1,000 days. SALT.agency reported a median of 304 days across 1,052 moves. Samples and methods differ, so do not average them.
Google's guide for moves with URL changes says the same things in plain steps: prepare the new site and test it, map old URLs to new ones, set permanent server-side redirects, and monitor traffic. It adds that for medium-sized sites it can take a few weeks or more for Google to start showing new URLs, and longer for large sites.
The checklist
Phase 1: Before you build
- Get access. Search Console, analytics, domain registrar, hosting and the old platform, all in the client's name.
- Take a baseline. Export 12 months of clicks, impressions and average position per page and per query from Search Console. Save it as a file. Without this you cannot prove what changed.
- Crawl the old site. Use a crawler (software that follows links and lists every page, such as Screaming Frog) and the old sitemap. List URLs, titles, meta descriptions (the text shown under a result), headings, canonical tags (a tag that names the preferred version of a page), status codes and internal links.
- Include more than pages. Google says to include images, videos, JavaScript and CSS URLs in the mapping. Squarespace, for one, cannot redirect image or file URLs, so plan for that.
- Rank the pages. Mark pages by traffic and by links from other sites. Protect the top 20 percent first.
- Decide per page: keep, improve, merge or retire. Do not retire a page with traffic or links without a redirect to the closest match.
- List what is not a page: forms, tracking tags, booking tools, schema (structured data that describes a page to search engines), cookie banners and robots.txt rules (a file that tells crawlers what to skip).
Phase 2: Build on staging
- Keep URLs. Use the same slugs (the last part of an address) wherever the page still exists. Platforms often add a prefix, such as a different blog path, so check.
- Keep titles, descriptions and headings for pages that rank, unless you have a reason to improve them. Change one thing at a time where you can.
- Keep the text. A shorter or reworded page can lose the query it ranked for.
- Keep internal links. Update navigation, footer and in-text links so none points to a redirected address.
- Block staging. Keep the staging site out of Google with noindex (a tag that tells Google not to list a page) or a password. Remember to remove it at launch. A leftover noindex is a classic cause of traffic loss.
- Check canonicals point at the new URLs, not the old ones or staging.
- Rebuild forms and tracking and test each one by submitting it.
- Check speed. Wix's migration guidance says the new site should be no slower than the old one.
Phase 3: The redirect map
A redirect map is a sheet with one row per old URL. Use this template.
| Old URL | New URL | Type | Traffic (12 months) | Tested |
|---|---|---|---|---|
| /services/plumbing | /services/plumbing | Same, no redirect | 1,420 clicks | Yes |
| /blog/2019/boiler-tips | /blog/boiler-tips | 301 | 380 clicks | Yes |
| /old-offer | /services | 301 to closest match | 12 clicks | No |
| /staff-login | none | Retire (410 or 404) | 0 | n/a |
(The rows are made-up examples.) Rules for the map:
- One hop. Old address to final address, never a chain of redirects.
- Send each old page to its closest match, not to the home page for everything.
- Use 301, the permanent kind. Google recommends server-side permanent redirects, and says 301 and other permanent redirects do not cause a loss in PageRank (its link-strength measure).
- Know the platform limits. Wix's help center says each redirect CSV file can hold at most 500 redirects, so a large site needs several files. Squarespace's move guide says to set 301s where the new URLs differ and to keep your domain name. Ploy's docs say to keep URLs the same where you can and add 301s in its Path routing for any that change.
- Keep the redirects for a long time. For domain changes, Google says to keep them at least 180 days, longer if you still see traffic through them, and to keep paying for the old domain for at least a year.
Phase 4: Launch day
- Remove noindex and any staging password. Check robots.txt does not block the site.
- Switch the domain or publish. Confirm https works and every version (with and without www) goes to one address.
- Publish the new XML sitemap (a file listing the pages you want found) and submit it in Search Console. Google says a sitemap helps discovery but does not guarantee crawling or indexing.
- Test 50 old URLs from the map in a browser or crawler. Each should land on the right page in one hop.
- Check Search Console's URL Inspection tool on the home page and two key pages.
- Confirm analytics fires, forms deliver, and phone and booking links work.
- If the domain changed, use Search Console's Change of Address tool after the redirects are live. It applies to domain-level moves only, and not to moving paths, www changes or http to https.
What an AI migration tool can do, and what you must check by hand
AI rebuild tools save time on the build. They do not remove the SEO checks. Take Ploy as an example, because its own docs are clear about the limits. Per its WordPress migration docs, you paste a public URL into its Agent, it inventories the site, shows a plan, and rebuilds the pages on a design system, importing posts into its database. Nothing goes live until you approve. The docs call it a rebuild, not an identical copy, so review every page. Forms, plugins, shortcodes, embeds, custom code and private pages may need separate work.
| Task | A tool can help | You must check by hand |
|---|---|---|
| Find the old pages | Inventory from the sitemap and links | Pages not linked or not in the sitemap, images, files |
| Rebuild content | Copy text and layout into the new design | That headings, text and links match what ranked |
| URLs | Keep the same slugs when told to | Every changed URL and its 301 |
| Titles and descriptions | Carry over metadata | Missing, duplicate or rewritten ones |
| Schema and canonicals | May generate some | That they are correct and point at new URLs |
| Forms and tracking | Native forms, some integrations | Every form submission and every tag |
| Speed and mobile | Builds on its own components | Real page speed and mobile layout |
A tool's marketing claims, such as a fast import, are not a test result. Test your own site. If you use a Ploy workspace for the rebuild, run the redirect and metadata checks above on its output as you would for any new build. Ploy's migration uses AI credits and larger sites use more, so check the usage page before you commit a client. Google's guidance is that it judges content on quality and value, not on how it was made, so review AI output for accuracy before it goes live. See whether Google penalizes AI-written pages.
Post-launch monitoring
Set pass and fail rules before launch, so you do not argue about them later. These figures are one practitioner's experience from a Search Engine Journal article, not a dataset, so treat them as guides: a 10 to 30 percent temporary dip is typical, a 10 to 20 percent dip often recovers in 2 to 6 weeks if there are no errors, and a loss of half or more that does not settle is a "migration hangover" to investigate. Use this plan.
| When | Check | Pass | Fail, so do this |
|---|---|---|---|
| Day 1 | 50 sample old URLs | All reach the right page in one hop | Fix the map and redeploy |
| Day 1 | Search Console coverage and sitemap | Sitemap read, no sudden spike in excluded pages | Check noindex, robots.txt, canonicals |
| Week 1 | 404 errors in Search Console and server logs | No top-20 page returns an error | Add the missing redirect |
| Weeks 2 to 4 | Clicks per page versus the baseline | Within your agreed band | Compare titles, text and links on dropped pages |
| Week 8 | Total organic clicks and leads | Back near the baseline or trending up | Run a full audit and look for chains, thin pages, speed |
Common causes of loss, from a Search Engine Journal piece by StudioHawk: missing or wrong redirects, redirect chains, leftover noindex, canonicals pointing to old URLs, changed content, slower pages, URL changes that did not need to happen, and SEO checks done too late. Our guide on fixing old links after a redesign shows one way to set up the redirects on Netlify, a hosting service.
Worked example (made-up numbers)
A dental clinic has 85 pages and gets 2,400 organic clicks a month. The agency moves it from an old WordPress site to a new build.
- Audit: 85 pages, 12 with no traffic and no links, so retire them. 60 keep the same URL. 13 change URL and get a 301.
- Protected list: the top 15 pages bring 80 percent of clicks. Their titles, headings and text are kept word for word.
- Launch checks: 13 redirects tested, all one hop. A leftover noindex on the staging copy is caught on day 1 and removed.
- Agreed band: clicks may fall by up to 20 percent for 4 weeks, so no alarm until clicks are below 1,920 a month. If they are below that after week 4, the agency reviews the dropped pages.
The numbers are invented, but the method is real: a baseline, a protected list, a band, and a date to review.
Common mistakes
- Redirecting every old URL to the home page.
- Changing the URL structure for style, not need.
- Rewriting every page at the same time as the move, which makes any traffic change impossible to explain.
- Forgetting images, PDFs and old blog posts.
- Letting the old host or platform plan lapse, which turns off the old redirects.
- Telling the client it will be fine, with no band or review date.
How I'd approach this
I would put this checklist into your project template so it runs on every rebuild, and I would never launch without a baseline file and a signed-off redirect map. Pick the rebuild tool after the audit, not before. A tool like Ploy's AI site platform fits a simple marketing site you are happy to rebuild. A site with heavy plugins, ecommerce or membership features is often safer on another route. If you want the checklist, the status updates to the client and the monitoring alerts to run themselves, Blur Studio builds the custom version, including AI agents that use your business knowledge, CRM and calendar connections, and ongoing care.
First-week plan. Day 1: copy the four phases into your project tool. Day 2: build the redirect map template and the baseline export routine in Search Console. Day 3: run phase 1 on one real client site and agree the band with the client in writing. Day 4: on a test site, run a rebuild, including a pilot with a free Ploy workspace if you want to compare, and check every row of the "by hand" table. Day 5: set up the day-1, week-1, week-4 and week-8 reminders. Decision rule: do not launch until the top 20 pages are mapped, tested and signed off.
If a new site is not appearing at all, see what to check when a new site is not on Google.
You may also want moving a Bubble marketing site to a faster stack.
Related guide: refreshing an old website without starting over.
Questions people ask
Will I lose rankings if I move a website to a new platform?
Some movement is normal and no process guarantees the result. Google says permanent redirects do not cause a loss in PageRank, but it can take a few weeks or more for new URLs to replace old ones in results. Keep URLs, titles and text where you can, and agree a review plan with the client.
How long do 301 redirects need to stay in place?
For a domain change, Google says to keep them at least 180 days, longer if you still see traffic through them, and to keep paying for the old domain for at least a year. For same-domain URL changes, keep them as long as the old URLs have links or traffic, which usually means indefinitely.
What is the most common cause of traffic loss after a migration?
Missing or wrong redirects, redirect chains, a leftover noindex from staging, and canonicals that still point to old URLs are the usual causes, according to a Search Engine Journal article by StudioHawk. That is one practitioner's list, not a dataset, but each item is easy to test before launch.
Can an AI tool keep my SEO safe during a migration?
It can speed up the rebuild, but not replace the checks. Ploy's migration docs describe a rebuild, not an identical copy, and say forms, plugins, custom code and private pages may need separate work. Check URLs, redirects, metadata, canonicals and tracking by hand. See how Ploy site migration works.
Do I need Search Console's Change of Address tool?
Only for moving from one domain to another, after the redirects are live. Google's help page says it does not apply to http to https, www to non-www, or moving paths within a site. You must own both properties in Search Console.
How many redirects can Wix handle?
Wix's help center says a redirect CSV file can hold at most 500 redirects, so a large site needs several files. Check the current limit on the Wix page before you plan a large move. See leaving Wix or Squarespace without losing traffic.
Should I redesign and move at the same time?
It is easier to explain any traffic change if you do one thing at a time. If you must do both, keep the URLs and the text of top pages unchanged on launch, and improve them after the numbers settle.
What do I tell the client about traffic after launch?
Tell them before launch that a temporary dip is possible, give the review dates, and agree what band is acceptable. Do not promise rankings or traffic. A written band and a monitoring plan builds more trust than a promise. See website migration as a service.
More in this topic: Websites: AI, client sites and agency delivery (7 guides) →
Sources
- Google Search Central: site move with URL changes (updated 2026-08-20)
- Google Search Console Help: Change of Address tool
- Google Search Central: sitemaps overview
- Ploy docs: migrate from WordPress
- Wix Help Center: importing or exporting URL redirects with a CSV file
- Wix SEO hub: site migration fundamentals
- Squarespace Help: moving your site and SEO
- Webflow blog: SEO checklist for site migration
- Search Engine Journal: how long should an SEO migration take (Dan Taylor study)
- SALT.agency: domain migration recovery study (June 2026)
- Search Engine Journal: what is a migration hangover (StudioHawk)