Quick answer
A refresh improves selected parts of a useful existing website. A redesign revisits its structure, templates, content, or platform more substantially. The right choice depends on the cause of the problem, not simply the age of the site.
Before you begin
Write down what works, what causes difficulty, and which business changes the site no longer reflects. Keep concrete examples of visitor or staff problems.
What to do
- Review important journeys, such as finding a service, using a phone menu, submitting an inquiry, or buying a product. Identify where the journey breaks down.
- Check whether the current platform and editing approach support the changes. A dated photograph may need a refresh; an unsuitable content model may require a rebuild.
- Separate cosmetic concerns from functional issues. Note repeated template problems, unsupported software, missing integrations, and content needing substantial rewriting.
- Prioritize pages or improvements that would make a measurable difference. Compare that focused scope with the work required for a wider redesign.
- Ask for a recommendation stating what stays, what changes, and what remains outside the project. Include migration and redirects when URLs or platforms change.
How to check the result
You should understand the selected approach and how it addresses the original problem. A refresh should not quietly expand into a complete rebuild without a revised scope and approval.
If you need help
If the decision is unclear, request an assessment of representative pages and journeys first. A site can receive urgent fixes while a larger redesign is planned separately.
Related help
- Prepare a useful brief for a new website
- Create a content inventory before redesigning a website
- Understand website project scope and change requests
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
