Quick Answer
Choose the smallest website scope that can resolve the verified problems and support the required functions. A repair can address a bounded defect; a redesign can change presentation and page structure; a rebuild can replace the implementation beneath them. Those tasks can overlap. Inventory the content, URLs, platform, integrations and editing needs before deciding what must be replaced.
“We need a new website” can mean an unclear homepage, a broken form or a platform that cannot support an essential workflow. Each creates different work. Start by describing what fails and what a completed result should do.
Describe the change rather than relying on a label
Providers can use “redesign” and “rebuild” differently. In the proposal, identify the page types, content, templates, functions, data and infrastructure being changed. A visual redesign may require development, while a technical rebuild may preserve the public content and URLs.
Ask what can be retained and how that decision was reached. Keeping an existing domain does not establish that the current templates are suitable. Replacing templates does not require discarding useful service explanations or customer evidence.
Build a problem and dependency inventory
- Content: Which facts are missing, inaccurate or difficult to maintain?
- Visitor tasks: Where do people struggle to find, understand or complete something?
- Shared components: Does the problem affect one page or the navigation, forms or templates used across the site?
- Platform: Can the supported installation and extensions implement the required behavior?
- Business connections: Which payment, scheduling, CRM, inventory or other integrations must continue working?
- Ownership: Who controls the accounts, assets, configuration and ongoing support?
Record the affected page and evidence alongside each observation. Keep a suspected cause separate from a verified one. A slow page, for example, needs investigation before concluding that the CMS must be replaced.
Use a practical decision path
Can a bounded repair resolve the problem?
If the platform and shared structure remain suitable, consider a targeted change with an acceptance check. An illustrative example is correcting one form’s delivery route and testing submission through receipt. Replacing every page would add work without demonstrating that the form needed it.
Does the shared presentation or structure need to change?
Repeated navigation problems, unsuitable service templates or content that no longer fits the layout may justify a redesign. Prototype representative real pages and important states before applying the new treatment broadly.
Include accessibility evaluation during the work. W3C’s planning and managing guidance includes responsibilities, early evaluation and continued review. A new appearance alone does not establish that an interaction works for every visitor.
Is the required behavior blocked by the implementation?
A rebuild may be appropriate when a supported, maintainable implementation cannot meet the verified requirements without extensive replacement. Compare the work needed to correct the current system with the work, data changes and dependencies created by the proposed one.
Ask the technical owner to explain the constraint in concrete terms. “The platform is old” is incomplete; identify the unsupported component, missing capability or maintenance problem and the available alternatives.
Record what should survive
Preserve the inventory of useful content, established URLs, approved imagery, business facts, account ownership and important configuration. Identify data that changes during the project, such as orders or submissions, and plan how the final transition will account for it.
The website content guide helps gather those inputs. The redirect-mapping guide supports projects where public addresses change.
Compare scope, disruption and ongoing work
For each option, record deliverables, dependencies, approval points, migration work, acceptance checks and postlaunch responsibilities. Include the cost of the business’s content and decision-making time without assuming a universal price or schedule.
Use the proposal-comparison worksheet to resolve unclear inclusions. If the cause or scope is still uncertain, commission the appropriate website investigation before committing to a full replacement.
Key Takeaways
- Choose scope from verified problems and requirements.
- Distinguish a bounded repair, shared redesign and implementation replacement.
- Inventory content, URLs, data, accounts and integrations before removing anything.
- Compare disruption, verification and future maintenance alongside initial work.
Frequently Asked Questions
Can I improve a website without starting over?
Often a specific content, template or functional problem can be addressed within the current system. Verify the cause and the wider dependencies before deciding the scope.
Does an old website always need a rebuild?
Age alone does not establish that. Review supported software, actual functions, editing needs and the cost of resolving verified problems.
Can a rebuild keep the same domain and URLs?
It can be planned that way when the destinations still make sense. Record the preservation requirement and verify the actual implementation and any necessary redirects before launch.
Bring the problem inventory to an Interactive Online website redesign discussion so the proposed work can explain what changes and what is retained.

