Should You Repair, Redesign, or Replace Your Website?

Broken forms, confusing navigation, and unsupported software call for different solutions. An isolated defect may warrant a repair, persistent customer confusion may justify redesign, and missing platform capabilities may require replacement. The decision also affects retained content, launch risk, and verification.

By McDowell Digital Services · Updated

Start with the Failure, Not the Appearance

Write down what a customer cannot do today: understand the offer, read the page on a phone, submit an inquiry, or complete a purchase. Separate reproducible failures from preferences. A broken form on an otherwise useful site usually calls for a repair; changing the color palette does not fix its delivery problem.

Inventory the pages, accounts, domain, content, integrations, and search URLs before choosing a solution. Keep a copy of the working site and identify who can approve changes. A replacement without this inventory can lose useful search destinations and business processes even when the new screens look better.

Match the Intervention to the Evidence

Choose a focused repair when the platform is supported, ownership is clear, and the defect can be isolated. Choose a redesign when the message, navigation, or page structure repeatedly blocks customers but the underlying platform remains suitable. Consider replacement when essential requirements cannot be met safely on the existing platform or keeping it creates a continuing maintenance burden.

Ask for a written comparison of what is retained, what changes, which URLs redirect, and how forms and integrations are verified. Compare the total transition work, including content migration and postlaunch support, rather than comparing only page counts.

Define Success Before Approving a Rebuild

Use observable outcomes: the inquiry reaches its destination, important old URLs resolve to useful pages, mobile visitors can finish their task, and the owner can maintain the agreed content. The provider should retest the original failure after the change. Keep a rollback path until the replacement has passed production checks.

A template refresh may be sufficient when the problem is presentation alone. A specialist is preferable when the main risk is a platform-specific integration or a regulated requirement. No redesign can promise a particular sales increase without evidence about traffic, demand, and the rest of the sales process.

Where MDS Fits

MDS is a fit for bounded repairs and scoped redesigns, including larger sites that need a content and dependency inventory. The current service catalog distinguishes Website Fixes & Small Improvements, Website Redesign, and Large Website Redesign; an assessment should determine which scope fits rather than defaulting to a rebuild.

McDowell Digital Services is a United States-based remote provider. Communication is by email. The project agreement defines deliverables, dependencies, verification, and handoff. Service information explains the existing working terms.

Relevant Services and Current Pricing

These are the existing public estimates and quote paths for the listed audiences. Final pricing depends on the agreed scope, complexity, requirements, and specific needs. Project reservation deposits, where offered, are shown on the linked service pages.

Prepare a Useful Inquiry

  • The current URL and examples of failed tasks
  • Access and ownership constraints, without sending passwords
  • Pages and integrations that must be preserved

Send a description of the outcome you need. Do not include passwords, payment-card details, or confidential records in an initial inquiry. Discuss this project by email.