Should You Rebuild Your Website or Fix the One You Have?

Rebuild when the platform blocks the fix, when the content is invisible to crawlers, or when the site cannot be edited without a developer. Fix when the structure is sound and the problems are content, speed or schema. Most UK SME sites we review need fixing, not replacing.

FlowGenix Automations is an AI automation consultancy for UK SMEs. We run fixed-fee website reviews that end in one of two recommendations, and we say fix more often than rebuild.

Key takeaways

• Rebuild when the platform itself blocks the fix. Fix when the platform is fine and the problems sit in content, speed or schema.
• A rebuild puts existing rankings at risk. Every live URL needs a 301 redirect row before the new site goes live.
• Google Search Central documents that URL changes need mapped redirects, not a blanket redirect to the homepage.
• A £195 FlowGenix review answers rebuild or fix in writing before anyone spends £400 or £4,000.
• Sites built as JavaScript-only single page apps are the most common genuine rebuild case, because GPTBot and ClaudeBot read the raw HTTP response.

When is rebuilding a website the right call?

Rebuild when the underlying platform prevents the fix. Four cases qualify: the site renders content only in JavaScript, the CMS is abandoned or unpatched, nobody has admin access, or the information architecture maps several services onto one page. Each of these costs more to patch than to replace.

The JavaScript case is the one owners miss. A Vite or React single page application serves a near-empty HTML document, then assembles the page in the browser. Googlebot renders JavaScript and usually copes. GPTBot, ClaudeBot, PerplexityBot and CCBot read the raw response, so they see nothing. Content written this way is invisible to the systems answering questions about your sector.

The architecture case is the most expensive to ignore. A site with one page covering six services cannot rank for any of them, because the page has no single subject. Splitting that page later means new URLs, new redirects and new internal links, which is most of a rebuild anyway. The website audit guide sets out how we test for both cases.

When is fixing the existing site the better option?

Fix when the platform is sound and the failures are content, speed, schema or internal linking. A WordPress site on a maintained theme, a Shopify store, or a server-rendered build can almost always be repaired. Repair costs a fraction of a rebuild and carries none of the ranking risk, because the URLs do not move.

Most problems on a three-year-old UK SME site are repairable in a day or two. A stale meta description naming a product the firm no longer sells. No Organization or LocalBusiness schema. Images at 4,000 pixels wide loading on mobile. No internal links between the service pages. None of those need a new site.

Repair also preserves earned assets that a rebuild puts at risk. Backlinks point at specific URLs. Google Business Profile links to a specific page. Directory listings and supplier sites carry old paths. FlowGenix quotes improvement work against the existing site first, and only recommends a rebuild when the review shows the platform is the constraint.

How do rebuild and repair compare on cost and risk?

Repair costs £195 to £900 for a typical UK SME site and carries no ranking risk. A rebuild costs £400 upward and carries real risk until every old URL redirects correctly. Repair is faster to value. Rebuild is the only route when the platform, not the content, is the problem.

The table hides one asymmetry worth naming. A repair that fails costs the fee. A rebuild that fails costs the fee plus the traffic, and traffic recovery after a botched migration takes months. The asymmetry is why FlowGenix sells the review separately from the build.

What happens to your Google rankings when you rebuild?

Rankings transfer when every old URL redirects with a 301 to its closest equivalent on the new site. Rankings drop when old URLs return 404, or when everything redirects to the homepage. Google Search Central documents that a site move with URL changes requires mapped redirects and a fresh sitemap submission.

Expect a temporary dip regardless. Google recrawls the new URLs over days to weeks, and positions move while it does. A clean migration usually recovers inside four to eight weeks. A migration with unmapped URLs may never recover, because the signals attached to those pages have nowhere to go.

Two other assets need handling. Google Search Console needs the Change of Address tool when the domain changes, and Google Analytics 4 needs its measurement ID reinstalled on the new build. Both get missed often enough that FlowGenix puts them on the launch gate rather than trusting memory.

How do you rebuild a website without losing traffic?

Export every live URL before touching the new build, map each one to a destination, then verify the redirects after launch. The sequence takes about two hours on a twenty-page site. Skipping it is the single most common cause of traffic loss after a UK SME rebuild, and it is entirely avoidable.

1. Export every live URL. Export every indexed URL from Google Search Console, plus every URL in the existing sitemap.
2. Identify high-value pages. Pull the top pages by organic traffic and by referring domains, so the high-value URLs are known.
3. Build the redirect map. Build a redirect map with one row per old URL: old path, new path, redirect type.
4. Handle orphaned pages. Map orphaned pages to the closest topical match, never to the homepage by default.
5. Launch and resubmit. Launch, then request the new sitemap in Google Search Console and run the Change of Address tool if the domain moved.
6. Verify the redirects. Crawl the old URL list after launch and confirm every row returns a 301 to a live page.
7. Monitor for six weeks. Watch Search Console coverage and impressions weekly for six weeks.

Step six is the one firms skip. A redirect rule that looks correct in the hosting panel can still return a 404 in production, and nobody notices until the enquiries stop. FlowGenix runs the post-launch crawl as part of the build rather than as an extra.

What does a website rebuild cost a UK SME?

A UK SME rebuild costs £400 for a five-page template build and £1,500 to £4,000 for a bespoke design. Migration work adds nothing at FlowGenix on sites under fifty pages, because the redirect map is part of the build standard. Larger sites with legacy blog archives take longer and are quoted per URL count.

Compare that with the cost of the repair route before deciding. A review at £195 plus a day of fixes at £450 gets most three-year-old sites into working order. The rebuild only pays when the review finds a platform-level blocker, and the website cost guide sets out where each band lands.

There is one case where a rebuild is cheaper than a repair. Sites built on abandoned page builders, or on a WordPress install two major versions behind, cost more in developer hours to untangle than to replace. The review reports that finding explicitly rather than leaving it as a judgement call.

Frequently asked questions

How do I know if my website is a JavaScript single page app?

Run curl -s https://yourdomain.co.uk | wc -c in a terminal. A server-rendered page returns tens of thousands of bytes including your headings and body copy. A JavaScript app returns a few hundred bytes with an empty div and a script tag. One curl command answers the biggest rebuild question in under five seconds.

Will I lose my Google reviews if I rebuild my website?

No. Google reviews attach to the Google Business Profile, not to the website. The profile survives a rebuild untouched. Update the website URL in the profile if any page address changes. Check that the business name, address and phone number on the new site match the profile exactly.

Can I keep my domain when I rebuild?

Yes, and you should. The domain carries the age, the backlinks and the brand recognition. Keeping the same domain removes the largest source of migration risk, because no cross-domain signal transfer is needed. FlowGenix rebuilds on the existing domain by default and only changes it when the client is rebranding.

How long does a website rebuild take?

A five-page FlowGenix rebuild goes live in seven working days once copy and images are supplied. A bespoke agency rebuild takes eight to sixteen weeks. Migration adds a day for the redirect map and the post-launch crawl. The seven day build guide sets out what fits inside that window.

Should I rebuild if my site just looks dated?

Usually not on its own. Dated design costs credibility with visitors but does not cost search visibility. Retheming a sound WordPress or Shopify site preserves every URL and costs less than a rebuild. Rebuild when the platform blocks a fix, and retheme when the only complaint is how the site looks.

What if my developer has disappeared and I cannot access the site?

Recover the domain first, through the registrar, using the registrant email on the WHOIS record. Hosting access can often be recovered through the billing card on file. If neither works, a rebuild on the same domain is the cleanest route, and the existing URLs can be reproduced exactly so redirects are unnecessary.

Sources

• Google Search Central, site moves with URL changes, developers.google.com
• Google Search Central, Change of Address tool, support.google.com
• Information Commissioner's Office, guide to PECR, ico.org.uk

About the author

Kieran Hale is technical co-founder of FlowGenix Automations Ltd (company number 16555743), a UK automation consultancy building websites and operational automation for SMEs. He holds a BEng in Mechanical Engineering from UWE Bristol and works as a senior technical designer in residential ventilation.