Improve the existing website when its structure and editing tools can support the changes your customers need. Consider a rebuild when the foundation prevents those tasks, essential integrations will not fit, or maintaining the current system has become impractical. An old-looking design deserves attention, but first identify what the replacement must do better.
For a business in Formby, Freshfield or L37, begin with a few real journeys: choosing a service, judging your work and making an enquiry, booking or buying. Our web-design and redesign service can assess the scope around those tasks.
Separate appearance, content and technical faults
Write down the problem in a way someone can check. “The website feels dated” describes an impression. “The phone menu hides our main service, the gallery is difficult to use and enquiries go to an old address” identifies three changes a project can address.
If you are unsure where customers get stuck, follow the enquiry-journey review before deciding which pages need work.
Visual quality is part of the decision. Photography, typography, spacing and a coherent layout affect how the business is presented. Ask for a design direction that suits the work and audience, then check it with actual content. A striking demonstration page with short headings may behave very differently when your full service explanation is added.
Keep technical symptoms separate. A slow page, broken form or certificate problem needs diagnosis. Replacing the design before identifying the cause can leave the same fault in the new site. Use our website speed triage for a loading problem and the form-delivery guide for missing messages.
Choose the smallest scope that resolves the problem
| What you find | A sensible starting scope |
|---|---|
| Services, photographs or next steps are unclear, but the site is maintainable | Rewrite and reorganise priority pages; improve the enquiry journey |
| The pages work but the visual presentation is inconsistent | A planned design refresh using representative content |
| A specific form, integration or performance fault blocks customers | Diagnose and repair the fault before deciding on broader work |
| The platform or page structure cannot support essential tasks without extensive workarounds | Compare a rebuild with the full work of adapting the current site |
These are starting points for assessment. A refresh may include content and technical work, and a rebuild may retain useful existing pages. Ask the proposal to identify what stays, what changes and why.
Try the decision on a representative page before applying it everywhere. A service page with photographs and a form will reveal more than a simple text-only page. For a shop, include the awkward product and the actual collection or delivery route.
Check whether the current site can be maintained
Find out what the site runs on, whether it can be updated and who has the required access. Ask the current provider or a developer to identify unsupported dependencies and the work needed to resolve them. A complaint that editing is awkward is useful evidence, but it does not by itself establish that the whole platform must go.
List the edits the business needs to make: add a project, change a practitioner, update a service or maintain products. Ask for a demonstration using one of those tasks. If the current tools can be made suitable with a smaller change, compare that scope with a rebuild.
Record domain, hosting and account ownership before commissioning migration. The website account audit helps identify missing access without sending passwords through an initial enquiry.
Keep hosting and design as separate decisions
A redesign does not automatically require a new host, and moving hosting does not automatically require a new design. Ask which problem each change solves and how it will be checked.
If the project does need a new WordPress hosting arrangement, I recommend considering Krystal’s managed WordPress hosting. Its current offering includes staging and backups, which can support a controlled rebuild. Compare the specific plan and support scope with your site’s requirements, including email, plugins and recovery. Agree who tests the enquiry form, calendar or checkout after updates.
If email shares the existing hosting account, include it in the migration plan. Our WordPress hosting and email migration guide explains why a website move should account for mail separately.
Keep what already helps customers find and use the site
Inventory useful service pages, project explanations, photographs, downloads and web addresses before removing anything. Use Search Console, enquiries and other available evidence to identify pages worth preserving. Low traffic in a small or recent report does not prove a page has no value.
Keep an existing address where the page still serves the same purpose. When a genuine move is needed, map the old address to a relevant destination and agree the redirect checks. Our redesign URL-map guide supplies a practical planning format.
Google’s site-move guidance recommends planning and testing URL changes and notes that search rankings can fluctuate while changes are processed. A redesign proposal should describe preservation and migration work; it should not promise that every ranking will stay unchanged.
Write the brief around what visitors need to accomplish
Give the designer examples of useful customer tasks. Our trade-business website plan connects service pages and project evidence to quote enquiries. The salon website guide shows how service explanations lead to the appropriate booking route.
The professional-services website guide focuses on explaining scope before an initial enquiry. For an online shop, use the retailer website brief to define product choice, fulfilment and staff responsibilities.
For each priority journey, record what the visitor should see, the action they should take and the evidence that it worked. Include message delivery, booking status or order handling where relevant. Separate these acceptance tasks from a list of preferred colours and effects.
Ask the proposal to cover content preparation, account access, design review, technical work, testing, launch and handover. The designer and quote-comparison guide helps compare that scope across proposals.
Agree how the change will be launched and supported
A rebuild should be reviewed away from the live customer site before launch. Agree how forms, booking tools, payments and other integrations can be tested without contacting real customers or creating unintended orders. Check representative pages on phone and desktop, including errors and longer content.
For an active shop or booking site, identify data that can change during the build: orders, appointments, accounts and stock. The launch plan needs a way to account for those changes. A development copy made at the start of the project will not contain later activity automatically.
Use the website handover checklist to agree account control, editing, renewals and support. Decide who checks the live customer routes after launch and how a problem is reported.
Bring the problem to the first conversation
Send your current website, the parts you want to keep, the tasks that are failing and the changes your business now needs. Add two or three examples from the site so the discussion starts with something concrete.
If your business is in Formby, Freshfield or L37, discuss a website improvement or redesign with Formby Web Design. The first useful decision is the scope: a focused repair, a content and design refresh, or a rebuild with a clear reason for the extra work.
