Website redesign services should improve a customer task or business outcome. A new visual style may be part of the work, but it is not a sufficient reason to rebuild a functioning site.
Start by proving what is wrong. Then choose the smallest intervention that can fix it.
Redesign or focused improvement?
A full redesign is justified when the architecture, templates, technology or operating model blocks progress across the site. Focused improvement is usually better when the issue is limited to a journey, page type, content gap or performance defect.
Signals for a broader redesign include:
- customers cannot understand the offer or navigate the estate;
- the CMS prevents routine publishing;
- the design system cannot support required content or accessibility;
- integrations and templates are costly to change;
- the site has accumulated overlapping pages and inconsistent journeys;
- a platform or brand change affects most of the experience.
Do not use age alone. An old site that works can be improved. A new site that was built around the wrong assumptions may need structural change.
What redesign services should include
Diagnosis and research
Review analytics, Search Console, conversion data, support questions, sales feedback, content, accessibility, performance and technology. Speak to users where the decision depends on behaviour that dashboards cannot explain.
Strategy and scope
Agree the outcome, audiences, ranked journeys, deliverables, exclusions, budget, responsibilities and definition of done. DreamWeb’s live one-page redesign brief gives a practical structure for this.
Information architecture and content
Inventory existing URLs and assign one owner to each important intent. Decide what to retain, improve, merge, redirect or remove before templates are signed off.
Experience and interface design
Prototype important journeys with realistic content. Test responsive states, errors, long headings, forms, tables and media. Accessibility belongs in the components and content rules, not a final colour check.
Development and integration
Build maintainable components, supported integrations and a publishing workflow the internal team can use. Control environments, versioning, security and third-party dependencies.
Migration and launch
Map changed URLs, preserve useful on-page signals, test redirects, validate analytics, prepare rollback and monitor the release. Google’s site-move guidance recommends direct permanent redirects and careful monitoring.
Handover and improvement
Provide training, documentation, source ownership, warranty terms and a measured post-launch review. Launch is the first live evidence, not the end of the work.
How to compare redesign proposals
Ask every agency to answer the same brief. Compare:
- understanding of the problem;
- assumptions and exclusions;
- research and decision points;
- content and migration ownership;
- accessibility and performance acceptance;
- team roles and senior involvement;
- dependencies on your staff;
- test evidence and rollback;
- price by phase;
- support after launch.
A proposal with the most screens is not necessarily the most complete. Look for control over uncertainty.
Risks to make explicit
The most common risks are late content, unclear approvals, hidden integration work, lost URLs, untested analytics, inaccessible components and a design that only works with ideal assets.
Assign each risk an owner and response. “The agency will handle SEO” is not ownership. Name the inventory, mapping, implementation and verification tasks.
How to measure success
Separate launch acceptance from longer-term outcomes. On launch day you can verify redirects, forms, performance budgets, accessibility checks and analytics. Lead quality, organic visibility and customer behaviour need a review period and context.
DreamWeb treats launch checks and longer-term outcomes as separate evidence. Your redesign should start with its own baseline, acceptance criteria and review period rather than borrowing a headline result from another project.
A short buyer check
Choose one task that pays the bills. It may be getting a quote, finding a product or sending a lead. Put that task at the centre of the brief.
For example, ask an agency to show the old route and the proposed new one. What will change for the user? What proof says it is a real problem? How will the team test it before launch?
Keep a list of what must stay true: the right URLs, key content, search data, forms, payments and access needs. A new look can wait. These cannot.
If the problem is not yet clear, begin with customer journey mapping or ask DreamWeb for a focused diagnosis before commissioning a full rebuild.
Before a redesign changes any URLs, read SEO website migration consultant. Afterwards, a website maintenance plan keeps the new site in good order.