Rebuilding a Large Website in Phases So Cash Flow Survives the Project
Short Answer
A phased website rebuild replaces a large site section by section on the same domain, so each phase goes live and starts returning value before the next is paid for. Keep URLs unchanged to avoid a site move.
A full website rebuild can tie up a large budget for months before it earns anything back. For a UAE company paying suppliers and salaries from monthly revenue, that gap hurts. Meanwhile the old site keeps running with known problems nobody wants to fix twice. Phasing the rebuild lets finished sections go live and start working while later ones are still being built.
This guide explains how to split a large rebuild into phases your cash flow can carry. It covers which pages to rebuild first, how old and new sections share one domain and how to protect search rankings throughout. It also covers linking supplier payments to phases. It assumes you have already chosen to rebuild rather than repair.
Why rebuild a large website in phases at all?
Phasing spreads cost across smaller, separately funded stages that each go live on their own. You stop paying for months of invisible work before anything ships. Each finished phase can start recovering its cost while the next is built.
Martin Fowler's description of the strangler fig approach makes the same case for software generally. Replacing small parts at a time carries less risk than one wholesale switch, and it allows an earlier return on investment. The trade-off is real: temporary bridges between old and new systems add cost and time.
Quick Answer
A phased website rebuild spreads cost across smaller stages that each go live separately. It lowers launch risk and returns value sooner, but temporary bridges between systems add some cost.
Which pages should be rebuilt first?
Start with the shared header, navigation, footer and styles, because every later phase depends on them. Then pilot one lower-risk section to prove routing, tracking and templates. Revenue-critical pages come next, once that pilot has proven the whole delivery process.
Rank the revenue pages using your own data, not opinions in a meeting. GA4 key events by landing page show which pages produce enquiries or sales, while Google Search Console shows which ones earn search clicks. Pages that do both deserve the most careful treatment and the earliest real budget.
Quick Answer
Rebuild shared site templates first, then pilot one lower-risk section to prove routing and tracking. Next, rebuild the pages that GA4 and Search Console show earning enquiries and search clicks.
How do old and new sections run on one domain?
A reverse proxy routes each URL path to the system that now owns it. Requests for a rebuilt section, such as /services/, reach the new application, while everything else still reaches the old site. Visitors see a single domain throughout.
Web servers such as nginx handle this with location rules and the proxy_pass directive described in their documentation. Keep one GA4 property and the same key event names on both systems, so phase results stay comparable. Test logins, forms and cookies across the boundary, because sessions can break between applications.
Quick Answer
A reverse proxy lets old and new sections share one domain by routing each path to its owning system. Keep one GA4 property and test forms and sessions across both.
How do you avoid an SEO hit while both sites run?
Keep every URL unchanged wherever possible, so each phase swaps the page behind an address rather than moving it. Google treats URL changes as a site move, which brings redirects and a settling period. Unchanged URLs avoid that process for each phase.
If URLs must change, Google Search Central recommends moving all URLs at once on small and medium sites. For large sites, it suggests moving a test piece first. Keep redirects for at least one year, and never leave old and new versions of the same page live together.
Quick Answer
Keep URLs unchanged during a phased rebuild so Google sees no site move. If URLs change, Google advises small and medium sites to move every URL together, not in sections.
How should payments follow the phases?
Tie each payment to a phase going live and passing agreed acceptance checks, not to calendar dates. That way you pay for working pages, and the supplier has a clear finish line. Scope and estimate each phase separately.
Hold back a modest amount from each phase for fixes found in the first weeks after launch. Log any change to a later phase with its own price, so earlier budgets stay closed. Ask a UAE lawyer to check the payment clauses, since this article offers general guidance and not legal advice.
Quick Answer
Link each rebuild payment to a phase going live and passing acceptance checks, not calendar dates. Hold back a small amount per phase for fixes, and price later changes separately.
Main Takeaways
A phased rebuild replaces a large site section by section, so each stage goes live and earns before the next is funded. Build the shared templates first, pilot a lower-risk section, then rebuild the proven revenue pages. Keep URLs unchanged so Google never sees a site move. Tie each payment to a working, accepted phase rather than to calendar dates.
Planning a rebuild your budget can carry
A big rebuild does not need one big cheque and one risky launch day. Splitting it into working phases protects cash flow and limits the damage any single launch can cause. The cost is some temporary bridging between systems, a price worth weighing honestly for a large site. Decide the order from revenue data, then keep URLs stable throughout.
If you are still weighing whether a rebuild is justified at all, read our rebuild versus refactor comparison first. Auronix Web Studio can plan phase order, routing and payment milestones as part of business website development for UAE companies. Share your current site address and the pages that earn the most. We will propose a phase plan before any build quote.
Sources & References
FAQs
Questions readers usually ask next
These FAQs are written to match the topic of this post and to help readers move from understanding to action.
How many phases should a website rebuild have?
There is no fixed number, but each phase must work on its own once live. Fewer phases mean less temporary bridging, while more phases spread cost into smaller, easier approvals.
Does a phased rebuild cost more than one big launch?
It can, because temporary routing, parallel maintenance and repeated testing all take developer time. You accept that extra cost in exchange for earlier returns and smaller risks at every launch.
Can an old CMS and a new platform share one domain?
Yes, a reverse proxy can send each path to a different system behind one domain. Test cookies, logins and form handling carefully, because each application manages sessions its own way.
Should the homepage be rebuilt first or last?
Rebuild it once shared navigation works in both systems, because it links into every section. Moving it too early can leave links pointing into mismatched templates and confusing visitor journeys.
Will visitors notice two different designs?
They may if templates differ, which looks unprofessional and can erode trust. Build the shared header, footer and core styles first, so old and new sections look like one site.
How do we keep analytics comparable across phases?
Use a single GA4 property and keep key event names identical on both systems. Record each phase launch date, so later reports can compare performance before and after every switch.
What happens if funding stops mid-project?
Every completed phase stays live and usable, which is phasing's main practical benefit. Avoid phases that leave a journey half-rebuilt, such as a new product page feeding an old checkout.
Should content be frozen during each phase?
Only the section being migrated needs a freeze, and only for the final weeks. Our guide on scheduling a content freeze during migration shows how to keep editors working elsewhere.
Can we change URLs during a phased rebuild?
You can, but Google treats URL changes as a site move with a settling period. Our checklist for redesigning without losing search traffic covers the redirect mapping step by step.
Who should decide the phase order?
The business owner should decide, using revenue and search data from GA4 and Search Console. Developers then flag technical dependencies, such as shared templates, that must move earlier in sequence.
Related Resources
Need help rebuilding a slow WordPress site?
We help UAE businesses plan the migration, preserve rankings, and choose the lightest rebuild path that still supports content, forms, and conversion.
Built for UAE websites that need a controlled rebuild, cleaner performance, and safer SEO migration.
