How to move your website one section at a time
Short answer: Moving a site one section at a time means your domain stays put while one group of pages, such as the blog, is served by the new host and everything else is still served by the old one. A routing rule (a reverse proxy, a server that fetches pages from another place and shows them under your address) decides which host answers each path. Google says small and medium sites generally move all at once and large sites may move in sections, so treat phased moves as a way to lower risk, not as a Google requirement.
You are afraid that moving the whole website in one night will break pages, lose traffic or leave you with a surprise bill, so you want to move it in pieces.
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.
It can be done, and it is a sensible way to cut risk for a large or business-critical site. The trick is that visitors must keep seeing one website at one address while two hosts quietly share the work. You do that with path routing: a rule that says "pages under /blog come from the new host, everything else from the old host."
This guide gives the order to move sections in, how routing works, what to check at every step, how to roll back in about a minute, and when you should skip phasing and move once. It also covers where Ploy, an AI website builder that can rebuild a site from its public address and route paths between hosts, is one option. As of November 2026; check each vendor's current docs before you act.
This page may contain affiliate links from which Blur Studio earns commissions.
Should you move in sections at all?
Google's page on site moves with URL changes says that large sites can move in sections, and that the test section should be one that changes less often. It also says a partial test does not fully predict a whole-site move, and that small and medium sites generally move all at once. So do not tell yourself Google recommends phasing. It is a risk-management choice.
Vercel, a hosting company, makes the case for incremental moves in its incremental migration guide: the old and new sites run at the same time, you get a smoother rollback path, you find problems earlier, and you avoid a maintenance window. It lists late discovery of issues and a point of no return as the drawbacks of a one-time move.
| Situation | Better choice |
|---|---|
| A small site with a simple structure | Move once, with a full redirect sheet |
| Hundreds of pages or heavy daily changes | Phase it |
| A shop, booking system or members area attached | Phase it, and leave the store on the old host |
| Leads depend on one section you cannot lose | Phase it, and move that section last |
| You cannot keep paying for the old host | Move once |
Phasing has a cost: two hosts to pay for and keep healthy, and more settings to get wrong. Keep the old host paid until the last section is done and its traffic is near zero, which is what Google's guide for moves without URL changes advises.
How section-by-section routing works
There are two common patterns, both described in the Vercel guide.
- Point the domain at the new host first. The new host answers every request, and a fallback rule sends anything not yet moved to the old host. As each section moves, you remove it from the fallback.
- Keep the domain on the old host. You add a reverse proxy rule on the old server for each moved path, which fetches that path from the new host.
The first pattern is simpler for owners without a developer, because there is one place to manage rules. The second suits a team that already runs the old server and can edit it.
Whichever you pick, check the difference between a rewrite and a redirect. Vercel's rewrites page says a rewrite keeps the address in the browser unchanged, while a redirect changes it. For phased moves you want rewrites (proxying), so visitors stay on your domain, and redirects only for URLs that really change. It also says the first matching rule wins, so list specific paths before a catch-all.
A tool like Cloudflare can also route by path, but its Workers examples page lists hostname-based examples and no ready path-routing recipe, so path routing there is something you or a developer would write. See how to keep your blog or shop on a sub-path of your main site for a worked proxy example on Netlify.
Pick the order: which section goes first
Google says to test with a section that changes less frequently and is not affected by frequent or unpredictable events. In practice, use this order, adjusting to your site.
- A low-stakes, low-change section. A help centre, an old blog archive or a team page. Mistakes here cost little.
- The blog or resources. Many pages, mostly text, easy to compare before and after.
- Service or product pages. Move them in groups that share a template.
- The homepage and key lead pages. Last, when everything else has proved the process.
- Stores, logins and apps. Often stay on the old host indefinitely. Ploy's docs say stores, accounts and apps can stay on the current host with path routing.
Never start with the page that brings most of your leads. If you do not know which that is, check Google Search Console and your analytics first.
Before you start: the inventory
- List every URL in a sheet: address, section, traffic, who owns it, and what happens to it (stay, move, redirect, delete). Our guide on redirecting old links after a redesign shows how to build the redirect part.
- Record the baseline. Export Search Console performance, analytics and a crawl of your current site (status code for each URL). You will compare against these.
- Find what is not just pages. Forms, bookings, logins, embeds, plugins and tracking scripts. Ploy's WordPress and Webflow migration pages list items such as forms, plugins, shortcodes, embeds, interactions, custom code and private pages as things that may need separate work.
- Check who controls DNS (the address book for your domain) and who can log into the registrar. If that person is unreachable, fix that before anything else.
- Lower the DNS TTL early. TTL is how long other computers remember the old address. Google's page on site moves without URL changes suggests lowering it to a low value, for example a few hours, at least a week ahead. Ploy's checklist says to lower it to 300 seconds before migration day. Do not take one number as law; lower it early.
- Do not touch email records. Change only the website records (the A and www records). Leave MX and TXT records alone, because they run your email.
Step by step: moving one section
- Build the section on the new host. Use the same URLs where you can. Vercel's guide also says to maintain the same routes for migrated features.
- Test it on a preview address. Block search engines on the preview and remember to remove that block before the real switch. Google's site-move guidance says to remove any temporary noindex or blocking before updating DNS.
- Compare the old and new page for page. Titles, headings, text, images, internal links, forms. Review desktop and mobile.
- Add the routing rule for that section only.
- Wait for the rule to take effect, then crawl. Crawl both the new section and a sample of old pages. Every URL should return the same status as before, 200 for live pages.
- Check the signals Google cares about. Each page should have one canonical address (the preferred URL for the page), a working title, and no stray noindex. Google's canonical guidance says to use absolute URLs and a self-referencing canonical on the preferred page. How a proxy treats canonical tags on proxied pages is not documented by every host, so check the canonical tag on each proxied page yourself.
- Watch for a week. Search Console coverage, crawl errors, analytics, form deliveries. Then move the next section.
Redirects are for URLs that change. Google says to use permanent server-side redirects (301 or 308), avoid chains (ideally three hops or fewer), not send many old URLs to one unrelated page, and keep redirects in place generally at least one year. Our guides on rankings that dropped after a migration and migration cost cover recovery and budgets.
Rollback: set the trigger before you start
A phased move is only safer if going back is easy and decided in advance. Write this down before the first move.
- Trigger. For example: more than 2 percent of crawled URLs returning errors, a form that stops delivering, or a key page missing from Search Console for a week.
- Action. Delete or reorder the routing rule so the old host answers again.
- Time. Ploy's routing page says changes usually take effect within 60 seconds, which it describes as typical, not guaranteed. Plan on about a minute and verify on a test address.
- Proof. If the rule shows "edge sync failed", Ploy says to retry and not to assume the new routing is live.
The percentages in the trigger are examples to adjust, not standards.
A worked example with made-up numbers
A 180-page WordPress site for a regional accountancy: 40 blog posts, 25 service and location pages, 10 core pages, and 105 older news items. The owner wants a new site but cannot risk the 12 pages that bring most enquiries.
| Week | Move | Pages | Check before next move |
|---|---|---|---|
| 1 | Inventory, baseline crawl, lower TTL, point domain to new host with fallback to old | 0 | Whole site still loads; email works |
| 2 | Old news archive | 105 | Crawl shows 105 pages returning 200; no new errors in Search Console |
| 3 | Blog | 40 | Titles and internal links match; forms on posts deliver |
| 4 | Service and location pages | 25 | Enquiry form tested; call tracking still counts |
| 5 | Core pages including home | 10 | Full crawl, sitemap check, redirect sheet applied |
| 6 to 8 | Watch, then retire old host | 0 | Old host logs near zero traffic |
If week 4 shows the form breaks, the owner deletes the service-page rule, waits a minute, and the old pages return. Only 25 pages were ever exposed, not 180.
Sitemaps, robots and Search Console during the split
- Ploy's migration-readiness page says it builds a sitemap index for its own pages automatically, that the old sitemap does not carry over, and that if part of the site stays on the old host you should keep both sitemaps listed in robots.txt.
- Google's site-move page says to submit the new sitemap, and suggests submitting both the old and new sitemaps while you monitor indexing, then removing the old one. It also says warnings about redirecting URLs in the old sitemap are normal.
- Check production robots.txt has no
Disallow: /left over from testing. - Trailing slashes: Ploy's prerendered pages drop a trailing slash by default, so "/about/" becomes "/about" unless you change the setting. Make sure redirects cover the difference.
- Keep Search Console verification in place on both hosts during the move.
Where Ploy fits
Ploy is one option for people who also want the new site built for them. Its migration docs describe a rebuild, not an identical copy: you give it your public address, it shows a plan, and nothing changes on your live site until you approve the switch. Moving from an address uses AI credits, bigger sites more, and Ploy does not publish a credit cost per page.
- Routing. In Ploy's routing rules, paths are checked top to bottom and the first match wins. Match types are "this page and every page under it", "only this page" or a custom pattern, and the last row ("Everything else") catches the rest. Each destination can be a Ploy site, another address proxied with your domain kept in the address bar, or a redirect (301 by default). Changes have Undo and a History of saved versions.
- Staged moves from other platforms. Ploy's guides say to keep unmoved pages on an old-host subdomain such as www2 for Webflow, or the old address for Framer, and route unmoved pages there with "Everything else". For WordPress, a "Ploy Connect" plugin serves chosen Ploy pages through WordPress and needs a paid plan.
- Canonicals. Ploy's launch checklist says it handles canonicals automatically once your domain is set as primary, for pages it serves. How proxied pages from the old host are treated is not documented, so check them.
- Plans. Per ploy.ai/pricing: Free $0, Starter $50 a month, Pro $300 a month, Enterprise by quote, and Enterprise adds white-glove onboarding. Per Ploy's credits docs, unused credits do not carry over. Check the pricing page and Ploy's migration docs for what each plan includes, because custom domains need a paid plan, Starter or higher.
To try it, start with the Free plan and rebuild one small section as a test. Per Ploy's WordPress guide, free sites publish to a ploy.build address, and using your own domain needs a paid plan, so a real phased move will need Starter or higher. Read more at Ploy site migration and best website migration tools and services.
When to skip this approach or the tool
- Small sites. Google says small and medium sites generally move all at once, and one move has fewer moving parts.
- If you cannot keep the old host paid until the end. Phasing needs both hosts.
- If the old site cannot be reached by a proxy (login-only, blocked by firewall, or no stable HTTPS address). Ploy says the origin needs a stable HTTPS address.
- Sites with a store, bookings or members area as the core. Move the marketing pages and leave the app where it is.
- Teams that need a pixel-perfect copy. Ploy's migration is a rebuild, so a developer-led copy or a service may fit better. See website migration as a service.
Copy-ready checklist
- URL sheet complete, with a status for each page.
- Baseline crawl and Search Console export saved.
- TTL lowered; MX and TXT records left alone.
- Rollback trigger, action and owner written down.
- Section built, previewed, compared and unblocked.
- Routing rule added; crawl compares status codes.
- Canonical, sitemap, robots and forms checked.
- One week of watching before the next section.
- Redirects kept for at least a year.
How I'd approach this
I would phase only if the site is large or business-critical, and I would use the smallest first step that proves the routing works. A test with a few low-traffic pages teaches you more than a week of planning. If the site is small, I would spend the effort on a clean redirect sheet and a careful single cutover instead.
First-week plan. Day 1: build the URL sheet and baseline. Day 2: write the rollback trigger. Day 3: lower TTL and confirm who holds DNS. Day 4: pick one low-change section and build it on the new host. Day 5: route it and crawl. If the work stalls, if you have a store or booking system attached, or you want a custom migration, Blur Studio builds that custom version and can finish a move that stopped half way, with ongoing care afterwards.
Related guide: How to Move Your Site and Keep the Forms You Already Use.
A closely related page covers the same ground from another angle: Can My Site Be Moved? How to Check Before You Commit.
For the next step, see How to Move a Client Domain With Zero Downtime.
Questions people ask
Can I move my website one section at a time without losing SEO?
You can lower the risk but no one can promise zero loss. Keep the same URLs where you can, use permanent redirects for URLs that change, and keep them generally at least a year, as Google's site move guidance says.
Does Google recommend moving in phases?
Not for most sites. Google says small and medium sites generally move all at once, and that large sites can move in sections. A phased move is a risk choice, and Google notes a partial test does not fully predict a whole-site move.
What is a reverse proxy in plain words?
It is a server that fetches a page from another place and shows it to the visitor under your own address. In a phased move it lets some paths come from the new host while others still come from the old one.
How fast can I roll back a section?
With Ploy, routing changes usually take effect within 60 seconds per its routing docs, and there is Undo and a History list. Confirm the change is live before you assume it. See Ploy's routing rules.
Should I keep paying for the old host?
Yes, until the last section is moved and the old host's traffic is close to zero. Google's guide for moves without URL changes says to keep the old hosting up and shut it down only when traffic reaches zero. Keep redirects for at least a year.
What about my forms, store and email during a move?
Test every form after each step. Stores, accounts and booking apps can stay on the old host with path routing. Leave email (MX and TXT) records untouched when you change website records.
Does Ploy move a site one section at a time?
Ploy's docs describe switching one path at a time or the whole domain, with unmoved pages routed to the old host. Its migration is a rebuild that uses AI credits, not an identical copy. See Ploy site migration and check ploy.ai/pricing.
Are redirects and proxying the same thing?
No. A redirect changes the address in the browser, a proxy rewrite keeps it. Use proxying to serve moved sections under your domain and redirects for URLs that really change.
More in this topic: Websites: moving a site without losing traffic (5 guides) →
Sources
- Site moves with URL changes (Google Search Central)
- Site moves without URL changes (Google Search Central)
- Consolidate duplicate URLs and canonicals (Google Search Central)
- Incremental migration (Vercel docs)
- Rewrites (Vercel docs)
- Routing rules (Ploy docs)
- Migration readiness (Ploy docs)
- Migrate from WordPress (Ploy docs)
- Migrate from Webflow (Ploy docs)
- Launch checklist (Ploy docs)
- Ploy credits (Ploy docs)
- Ploy pricing (Ploy)