Yes. We build the new site on a separate, password-protected staging environment while your current site keeps running, taking calls and ranking, untouched. You review it privately, we test everything, then we switch over in one short cutover — usually with no visible downtime and your search rankings carried across.
- The rebuild happens on a separate staging environment — your live site is never edited, taken down, or put into 'maintenance mode' during the build.
- Staging is password-protected and noindexed, so Google never sees or indexes the unfinished version and your current rankings are unaffected.
- You review and approve the new site privately, on real URLs, before a single visitor or customer sees it.
- The switchover (cutover) is a short, deliberate step — typically scheduled at a low-traffic time and usually with no visible downtime.
- Rankings carry across when the cutover includes a complete 301 redirect map and preserved content — the rebuild itself doesn't cost you traffic.
Yes — Here's How a Parallel Rebuild Works
Yes, and it's how a rebuild should always be done. We don't touch your existing website. Instead, we stand up a separate staging environment — a private copy of the new site at its own temporary address — and build there from scratch. Your current site stays exactly where it is: live, indexed, taking phone calls, capturing form fills, and ranking on Google the entire time. Nothing about your day-to-day changes while we work.
This matters because your website is usually a working asset, not a side project. It's generating leads and sales right now. The old, risky way to rebuild was to take the site down, throw up a "we'll be back soon" page, and rebuild in place — which means lost enquiries, frustrated visitors, and Google crawling a broken site. A parallel build removes all of that. The new site is fully assembled and tested in private before it ever replaces the old one.
The staging site is locked behind a password and set to noindex, so two things are guaranteed: no member of the public can stumble onto a half-finished page, and Google never indexes the unfinished version (which would otherwise confuse your rankings or create duplicate-content issues). You get a private link to review progress whenever you like. Only at the very end — after you've signed off and we've tested everything — does the new site go live, replacing the old one in a single deliberate step. From your customers' point of view, the site simply gets better one day.
What Stays Untouched While We Build
While the rebuild is underway, every revenue-driving part of your current setup keeps running normally. Your existing pages stay indexed and rank exactly as they did. Your Google Ads keep pointing at your live pages and converting. Your forms, booking widget, live chat, and phone numbers all keep working. Nothing is paused, redirected, or degraded — because we're not editing the live site at all.
That separation also protects you if a rebuild takes longer than planned, or if priorities shift mid-project. There's no pressure to rush a launch to "get the site back," because the site was never gone. We can take the time to get the new build right, gather your feedback across several review rounds, and adjust scope, all without a ticking clock on lost traffic.
We also use the staging period to get the unglamorous-but-critical things right before launch: a complete inventory of your current URLs, a 301 redirect map so every old page points to its new equivalent, preserved page titles and content where they're ranking, and analytics and conversion tracking rebuilt and verified on the new site. (Tracking breaking on launch day is one of the most common rebuild mistakes — we test it on staging so it's working the moment you go live.) Because the live site is unaffected, all of this prep happens calmly in the background. The deep mechanics of preserving rankings through a move are covered in our guide on migrating a website without losing rankings or traffic — the redirect map is the single most important piece.
The Switchover: How We Go Live Without Downtime
Going live — the "cutover" — is a short, scheduled, low-risk step, not a leap of faith. By the time we flip the switch, the new site has already been built, reviewed by you, and tested in full on staging. The cutover itself is mostly a DNS or hosting change that points your domain at the new site, with the 301 redirects live from the moment it goes public.
We schedule it deliberately, usually at a quieter traffic time for your business, so that in the rare event something needs a quick adjustment, the fewest possible visitors are affected. In practice most cutovers are invisible to your customers — they visit your domain and simply land on the new, better site. There's typically no "maintenance" window where the site is unreachable, because we're swapping one working site for another, not taking one down to build another.
Immediately after launch we run through a checklist: confirm key pages load and are indexable, spot-check that important old URLs redirect correctly with a 301 (not a 404 or a redirect chain), and confirm forms, tracking, and conversions are firing on the new site. Then we watch Google Search Console and analytics closely for the first few weeks. A small, temporary ranking dip can happen as Google re-crawls the new site, but a clean cutover with proper redirects typically holds rankings — and often improves them, since the new site is usually faster and better structured. If anything needs attention, we catch it early because we're monitoring on purpose, not waiting for you to notice.
What You Need to Provide — and What It Costs
From your side, a parallel rebuild asks for very little while it's in progress. We need access to your domain's DNS (or your hosting/registrar login) so we can prepare and execute the final switch — but only at cutover, not during the build. We'll also want your current content, brand assets, and a clear picture of which pages matter most to you, plus your time for a few review rounds on the staging site. That's it. You keep ownership of your domain, hosting, and all accounts throughout — we never lock your site behind us.
On cost, a website rebuild in Canada typically runs roughly $5,000–$15,000 for a templated or WordPress build, and $15,000–$50,000+ for a fully custom build (we build custom on modern frameworks like Next.js). Where you land depends on page count, custom functionality, e-commerce, and how much content needs to be written or migrated. The parallel-staging approach itself doesn't add a premium — it's simply how a rebuild should be done, and it's built into the project.
We work month-to-month and report transparently, so you can see the build progressing rather than waiting blindly for a reveal. Because we handle the full funnel — website, SEO, Google Ads, and tracking under one team — the rebuild is planned so your ad campaigns and search rankings carry through the move rather than getting orphaned by it. If you'd like to talk through your specific site and timeline, get in touch and we'll map out exactly how your cutover would work.
Related questions
No. Your current site stays live and untouched the entire time we build the new one on staging. The only moment of change is the brief cutover when we point your domain at the finished new site — and that's typically invisible to visitors, with no "maintenance" downtime, because we're swapping one working site for another rather than taking yours down to rebuild in place.
No. The staging site is password-protected and set to noindex, so the public can't reach it and Google won't index the unfinished version. You get a private link to review it, but no customer sees the new site — and your live rankings stay unaffected — until you approve the build and we run the scheduled cutover to go live.
Not if the switchover is done properly. The rebuild itself doesn't cost rankings; lost traffic comes from preventable mistakes. We carry over a complete 301 redirect map, preserve ranking content and titles, and monitor Search Console after launch. Expect at most a small, temporary dip as Google re-crawls; rankings typically hold and often improve on a faster, better-structured site.
Yes. Your ads keep pointing at your live pages and converting normally throughout the build, because we don't touch the live site. At cutover we make sure ad destination URLs and conversion tracking line up with the new site so nothing breaks. Handling the site and the ads under one team is exactly what prevents campaigns from getting orphaned during a rebuild.
It depends on size and complexity — a focused small-business rebuild often takes a few weeks, while a larger custom site with new content or e-commerce takes longer. Because your current site stays live the whole time, there's no pressure to rush the launch. We use review rounds on staging to get it right before scheduling the cutover.
Want a second opinion on your situation?
Get a free, no-obligation proposal. We’ll look at your site and your market and tell you honestly what we’d do — and what we wouldn’t.
Get Free Proposal →