How to Tell If Your Website Needs a Fix or a Full Rebuild (5-Minute Test)

If your website's platform is still alive (supported, patched, maintainable), fix it. If the platform is dead, can't be made mobile-friendly, or costs more to maintain than rebuild — rebuild. That's 90% of the decision. The rest of this article gives you the checklist to be sure.

Score yourself honestly on each question. Tally the yeses at the end.

• Platform alive: Is your CMS or framework still maintained and receiving security patches? (WordPress yes, custom PHP from 2014 no.)
• Mobile works: Does the site look and function well on a phone without horizontal scrolling?
• Speed is acceptable: Does the homepage load in under 3 seconds on a mobile connection?
• You can edit it: Can you update a page, add a blog post, or change a photo without calling a developer?
• It ranks somewhere: Does the site appear in Google for your business name or key services?
• No repeated hacks: Has the site been compromised more than once in the last two years?
• Content is current: Has any page been updated in the last 90 days?
• You trust the codebase: Would a developer look at it and not immediately say 'rewrite this'?

Six to eight yeses: your site is healthy. Fix what's broken — speed, SEO, a broken form — and keep going. A $500–$2,500 fix is the right move. Four to five yeses: your site is aging. A targeted fix still makes sense for the problems that matter most, but start budgeting for a rebuild in the next 12 months. Three or fewer yeses: the foundation is gone. Patching a dying platform costs more than rebuilding it. A full rebuild ($3,000–$10,000+) is the honest answer.

If you're on the fence, a free scored audit removes the guesswork — it scores your site across speed, SEO, accessibility, security, and content, and tells you whether the problems are surface-level fixes or structural.

Two mistakes cost the most — and both are avoidable if you know what to look for.

• Rebuilding when you should fix: you pay $5,000–$10,000 for a new site, lose your existing rankings during the transition, and end up with a site that looks different but has the same fundamental problems. The fix was $800. This happens most often when the symptoms (slow, ugly, hard to edit) look structural but the cause is actually surface-level — a bad hosting plan, unoptimized images, or a bloated plugin stack.
• Fixing when you should rebuild: you spend $2,000 patching a platform that's heading out of support, and within a year the patches stop working, security holes open up, and you rebuild anyway — having paid for both. This happens when the platform is dying (Adobe Flash, custom PHP from 2012, an unsupported CMS) and every fix is a band-aid on a broken foundation.
• The cheapest path is the right one: fix what's fixable, rebuild what isn't. The audit tells you which bucket each problem falls into — and the five-minute test above gives you the framework to decide.

Some problems are surface-level. Others mean the foundation itself is gone. Here's how to tell the difference:

• No security patches: the CMS or framework hasn't received an update in 6+ months, or the vendor has announced end-of-life.
• Plugin incompatibility: essential plugins (SEO, forms, e-commerce) no longer work with your version, and updating breaks the site.
• Developer scarcity: you can't find anyone willing to work on it, or every quote includes a 'migration' line item.
• Editing is miserable: publishing a page takes hours, the admin panel crashes, or you need to edit raw HTML for basic changes.
• Repeated hacks: the same vulnerability keeps getting exploited despite patches — the platform's architecture is the problem.
• Fixed-width layout: the site has a max-width container that doesn't adapt to screen sizes, and CSS can't fix it without a rewrite.

The biggest fear with a rebuild is losing your Google rankings. Here's how to protect them:

• Keep your URLs: if possible, rebuild at the same paths. If URLs must change, set up 301 redirects for every old URL to its new home.
• Migrate your best content: don't silently drop pages that rank. A free audit before you rebuild tells you which pages earn traffic.
• Set up redirects before launch: test every redirect chain. One broken redirect can wipe out months of ranking.
• Keep your analytics running: record your traffic baseline before the rebuild so you can prove it helped — and catch a drop the week it happens.
• Submit the new sitemap immediately: tell Google the site has changed. Don't wait for it to discover the pages naturally.
• Don't change everything at once: if possible, keep the same domain, the same URL structure, and the same content hierarchy. Change the foundation, not the address.

Fix and rebuild aren't the only two options. If your site's design and content are fine but the platform underneath is old, you can replatform: move to a modern CMS without redesigning. Same look, same pages, same URLs — new foundation.

Replatforming is the right call when the front of the house looks good but the back is broken: nobody can edit it, updates stopped years ago, or the CMS is heading out of support. It costs less than a full rebuild ($1,500–$5,000) and takes 3–8 weeks.

How long each path actually takes — and what to budget for:

• Fix (1–3 weeks): diagnose the problems, apply targeted fixes (speed, SEO, security), test, and launch. Budget $500–$2,500.
• Replatform (3–8 weeks): migrate the site to a modern CMS, keep the same design and URLs, update the admin experience. Budget $1,500–$5,000.
• Full rebuild (6–16 weeks): new platform, new design, new content structure, URL redirects, testing, launch. Budget $3,000–$10,000+.
• The fastest way to compress any timeline: have your content ready before work starts. Pages, copy, images, and the URLs they live on. A free audit hands you that inventory in 30 seconds.

Some fixes you can handle yourself. Others need a developer. Here's the split:

• DIY-friendly: update plugins, compress images, rewrite title tags, fix broken links, add meta descriptions, update stale content.
• Needs a developer: speed optimization (server config, caching, CDN), responsive layout fixes, security hardening, plugin conflict resolution, platform migration.
• Always hire: full rebuilds, platform migrations, e-commerce setups, anything involving payment processing or user data.
• Red flag in a quote: if a developer recommends a full rebuild without first running a diagnostic audit, get a second opinion. Many rebuilds are unnecessary — a targeted fix costs 10–20% of a rebuild.

A fix targets specific, solvable problems on a platform that's still sound. The goal is to make the existing site work better, not to start over:

• Speed: compress images to WebP/AVIF, cut render-blocking scripts, add browser caching, optimize server response time. These changes alone can cut load time by 40–60%.
• Mobile: responsive CSS pass, touch-friendly navigation, viewport meta tag, tap-target sizing. A mobile-friendly pass costs $300–$800 and fixes the most common conversion killer.
• SEO: title tags, meta descriptions, canonical tags, XML sitemap, structured data, internal linking. These are the low-hanging fruit that move rankings fastest.
• Security: update plugins and CMS, fix mixed content, add security headers (HSTS, CSP, X-Content-Type-Options), remove exposed files. A security pass costs $200–$500.
• Content: rewrite thin pages, update stale copy, fix broken links, consolidate duplicate content, add clear calls to action. Content work costs $50–$150 per page.
• Forms: fix validation, deliverability, confirmation flows, and spam protection. Broken forms are the silent conversion killer — visitors fill them out and never hear back.

A rebuild replaces the foundation — new platform, new code, often a new design. The goal is to start with a modern stack that won't need patching in two years:

• New CMS or framework: move from an unsupported platform (old WordPress, custom PHP, Flash) to something modern and maintainable (headless CMS, static site generator, managed platform).
• Responsive from scratch: build mobile-first instead of retrofitting. A rebuild starts with the phone layout and scales up — no CSS hacks needed.
• Speed by design: modern architecture, lazy loading, CDN, optimized assets, code splitting. A well-built site loads in under 2 seconds on mobile.
• SEO preserved: URL redirects, content migration, structured data from day one. The rebuild protects what Google already knows about you.
• Editable by you: a CMS you can actually use without a developer. The admin experience should be as clean as the public-facing site.
• Future-proof: built on a stack that will be supported for years. No more worrying about plugin compatibility or security patches.

If the audit says 'fix,' our Website Fix service turns the findings into a fixed-price plan. You see exactly what's broken, what it costs to fix, and approve the plan before any work starts. No surprises, no scope creep — just the fixes your site actually needs.

The service covers speed, mobile, SEO, security, and content fixes on sites that are fundamentally sound. If the audit reveals structural problems (dead platform, can't be made responsive), we'll tell you a rebuild is the better path — and point you to the resources to make that happen.

For the full price breakdown across fixes, rebuilds, freelancers, and agencies — plus the monthly costs everyone forgets — our guide to what a small business website costs in 2026 walks through it with real numbers.

The short version: a fix runs $500–$2,500. A rebuild runs $3,000–$10,000+. If the fix is under half the rebuild cost and the platform is alive, fix. Otherwise, rebuild. Write the two numbers down before you decide.

Skip the guesswork. A free scored audit of your current website tells you in about 30 seconds whether your problems are fixable tweaks (speed, mobile, missing SEO tags) or structural (a platform that can't be salvaged). Paste your URL, get the score, and know which path to take.