Website redesign: renovate or rebuild?

A website redesign question usually boils down to one choice: renovate or rebuild. You don't want to do a full rebuild if targeted fixes will do. But sticking patches on a rotten base is often more expensive later.

This article gives a practical decision framework you can apply now. I go through technical health, conversion and maintenance. You'll get clear checks, a decision table and a step-by-step checklist. There are indicative cost ranges — they vary per project.

The framework in short

Rate three things: technical state, conversion & content, and maintenance burden. Score each as low, medium or high. Use the combined result to decide.

• Technical state: outdated platforms, code quality, modularity, security issues.
• Conversion and content: are problems template-related or structural?
• Maintenance burden: how long do small changes take and how often do they fail?

Technical health: common failure points

Technical debt often hides. Look for:

• End-of-life runtimes or frameworks.
• Monolithic code with no reusable components.
• Many custom plugins that conflict.

If updates are unsafe or impossible, rebuild is usually the right choice. Make a blockers list: outdated libraries, EOL versions, known security issues. More than three serious blockers should push you toward rebuilding.

Conversion and content: fix or rethink?

Sometimes the tech is fine but conversion is bad. Typical issues: product pages without clear CTAs, content not aligned to user intent.

Measure:

• Bounce and exit pages.
• Conversion funnel drop-offs.
• Degree to which conversion depends on templates or on content quality.

If templates or a page builder cause the problem and can be replaced, renovate. If the data model or content architecture must change (for example combining several services into dynamic product pages), rebuilding is more realistic.

Maintenance burden and cost

Maintenance takes time and money. Ask:

• How long for a small content change?
• How many skills are needed?
• How often are changes blocked by dependencies?

If small edits regularly take more than 4 hours due to bugs, that's a warning. Calculate annual maintenance: internal hours plus external support. Many small fixes add up. Sometimes rebuilding is cheaper within 12–24 months.

SEO, performance and accessibility

SEO and indexability should affect your decision. Crawlability and meta structures influence visibility. Check the basics from Google Search Essentials: https://developers.google.com/search/docs/essentials and the SEO starter guide at https://developers.google.com/search/docs/fundamentals/seo-starter-guide.

Performance matters. Core Web Vitals are standard metrics for user experience. Measure LCP, INP and CLS and address large issues: https://web.dev/articles/vitals and https://web.dev/articles/lcp.

Accessibility is not optional. Non-compliance with WCAG can have legal and usability consequences. Review the guidelines at https://www.w3.org/TR/WCAG22/.

Decision table: renovate vs rebuild

Note: numbers are indicative and will vary per project.

Practical step-by-step decision process

1. Inventory blockers: security, updates, performance. Document examples and time estimates.
2. Measure conversion to find whether issues sit in templates, content or structure.
3. Estimate maintenance cost (monthly hours × rate) and project over 12–24 months.
4. Run a basic SEO check using Google Search Essentials: https://developers.google.com/search/docs/essentials.
5. If two of three main criteria (tech, conversion, maintenance) are 'high', consider rebuild.

Checklist for execution

• Make a list of security and update blockers.
• Measure Core Web Vitals on key pages.
• Identify which templates block conversions.
• Calculate average time for content changes.
• Prepare redirects and URL mapping for migration.
• Plan accessibility tests aligned with WCAG.
• Prepare rollback and backup plans before launch.

Indicative costs and team composition

Indicative ranges (they differ per project):

• Small renovation: €2.000–€10.000 (UI, speed, a few templates).
• Full rebuild small site: €15.000–€40.000 (configuration, migration, testing).
• Midsize rebuild with integrations: €40.000–€120.000.

Example team for a 3–6 month rebuild: project manager, 1–2 front-end devs, 1 back-end dev, UX designer, QA, SEO specialist. Senior-led agencies like DevCru commonly work this way and also provide maintenance and support.

A practical caveat

No framework covers every case. Business constraints, compliance deadlines or temporary marketing goals can shift the decision. A visual refresh might boost conversions short-term while you schedule a rebuild later. That can be a valid, pragmatic choice.

Next steps

If you want a quick audit, start by reading our notes on website-redesign. For a tailored plan or to commission work, see website-laten-maken.

If you want a short quote or a project conversation, request a quote at /quote.