When your website needs a redesign, and when fixes are enough

• Your offer has changed, but the site still describes old services or addresses a different audience.
• Reading, comparing options or completing a form is difficult on a phone.
• Services, conditions and work examples are too scattered to find before making an enquiry.
• Adding each page means working around structural limitations or duplicating material.
• The interface has recurring problems across sections, rather than a single awkward button.

Fewer enquiries alone do not establish a need for a redesign. Check whether traffic sources, demand, advertising or the offer have changed. Test form delivery separately: the issue may be receiving messages even when the page reports successful submission.

These are discussion prompts, not a diagnosis. Start small if the problem affects one block and the rest of the journey works. A wider redesign makes sense when fixes depend on a shared structure or the existing format conflicts with the business’s new needs.

When existing code and structure need many interdependent changes, rebuilding the website may cost no more than a complex redesign. A new implementation lets you plan the required structure and customer journey from the start. Compare the options after reviewing the site, including content migration, URL preservation and checks, as well as its appearance.

Walk through the site as a new customer: find a service, understand the conditions, examine evidence of experience and submit an agreed test enquiry. Record the page, device, obstacle and expected behaviour. Replace “it is awkward” with an observation someone else can reproduce.

• List the pages, languages, forms and external integrations.
• Where data exists, compare search queries and visited pages over comparable periods.
• Match enquiries to the services you actually want to sell, accounting for seasonality and advertising changes.
• Identify who controls the domain, hosting, code and content, and whether a copy of the current version is available.

Without analytics, use a conversation with the person handling enquiries, recurring customer questions and journey checks. Record the limitation: without data, you cannot state a conversion rate or promise a particular percentage improvement.

Inventory the material you still need: service descriptions, answers, case studies, images and documents. Decide whether to keep, improve, merge or remove each page, with a reason for removal. A new layout should not accidentally discard details customers need.

If URLs change, map old addresses to relevant replacements, set permanent redirects and update internal links and the sitemap. Do not send every old page to the homepage. Search visibility can fluctuate during a move; monitor it after launch. Google’s guidance on URL changes.

Check metadata and language versions before publication. For more on structure and search, read our guide to planning an SEO-ready website.

Choose priority journeys and demonstrate them in a simple prototype first. For a service business, this might run from the service list through a specific service’s conditions to the enquiry form. Agree where visitors receive answers, what material is needed and what they should do next.

Set acceptance criteria before detailed visual design: the new offering is reachable from the menu, conditions appear before the enquiry, and the mobile form supports keyboard use and explains errors. List copy, design and technology changes separately so each can be estimated and checked.

Check the new version with real copy and images before replacing the live website. Agree the publication time, launch owner and how to restore the previous version if the main journey fails. Changes to data and integrations may require a separate recovery plan.

• Check key pages on a phone and computer, including keyboard navigation and visible focus.
• Follow an agreed test enquiry through to actual receipt by the responsible person.
• Check old addresses, links, language switches and access to important materials.
• Repeat the main customer journey on the live domain after publication.

Share the website address, a list of problems with examples, and the business’s new goals. Include priority pages, required languages, known integrations, available material and launch constraints. When sharing other websites, explain which particular solution suits your needs.

Describing your existing access is enough for the first conversation; do not send passwords through the enquiry form. Our website redesign service explains the scope and working process. An estimate should account for content migration, checks and launch separately.

At acceptance, check whether the recorded obstacles have been resolved. After launch, compare relevant enquiries and available search data with the starting point, accounting for advertising and seasonality. You can assess the new appearance immediately; evaluating sales impact requires observation and data.

Agree who resolves discovered issues and handles subsequent changes. Our website support guide covers those responsibilities. To discuss your current problem and a suitable scope, contact XEVOR.