A broken contact form and a website that no longer represents your business are different problems. The first may need a focused repair. The second may justify changes to the content, page structure and design.
Before comparing website redesign services in the UK, write down what is failing and what you want to improve. That gives you a basis for deciding whether a repair, a limited update or a rebuild is worth considering.
When a website repair is the sensible starting point
A repair is worth investigating when you can identify a specific fault and the rest of the site still meets your needs. Examples include an enquiry form that shows an error, a menu that cannot be opened on a phone or an image upload that has stopped working.
Record the affected page, the steps that trigger the problem and any error message. Include when you first noticed it and whether anything changed around that time. Avoid assuming that the last update caused the fault until someone has checked.
My website repair service starts by assessing the issue, available access and the technology involved. Whether a repair is practical depends on what that assessment finds. WordPress repair work is not currently part of my service.
When a wider redesign is worth discussing
A redesign may be useful when the problem affects the whole customer journey. Perhaps your services have changed but the navigation still reflects the old business. Perhaps visitors need to read several unrelated pages before finding the information required for a quote.
Other reasons to review the wider site include:
- Important service information is missing or repeatedly out of date.
- Mobile layouts make several key tasks difficult.
- The current structure cannot accommodate the content you need.
- Routine updates depend on a process you can no longer maintain.
- A new feature requires substantial changes to the underlying site.
None of these automatically means replacing everything. An assessment should identify what can stay. My website redesign service considers existing content, usability and functionality before setting the scope.
Distinguish a website problem from a traffic problem
Few enquiries do not, by themselves, prove that the design is wrong. Check the path leading up to the enquiry: are relevant people reaching the site, are they finding the right page, and does the contact process work?
For example, a site with very few relevant visits gives limited evidence about whether its form or page layout discourages customers. A form that consistently fails during testing is a confirmed fault. Those findings call for different actions.
Start with a website audit if you need help identifying the problem. Search visibility and content work can then be discussed through SEO and local-search support where appropriate.
Keep an inventory of what must survive
Before agreeing a rebuild, list the important pages and functions. Include enquiry notifications, uploads, galleries, payment steps, customer accounts, downloads and the tools you use to manage them.
For each item, record whether it will be retained, changed or removed. Name the person who will check it. A screenshot of the old homepage does not capture the email sent after a customer submits a form.
Use a practical acceptance test. For a quote form, for example: the customer can submit the agreed fields, sees a confirmation, and the intended recipient receives the information. Test this on the replacement and again after launch.
Plan URL changes before launch
Where page addresses change, map each old URL to its relevant replacement and use a permanent server-side redirect where possible. Update internal links, canonical URLs and the sitemap. Avoid sending unrelated removed pages to the homepage.
Google’s site-move guidance recommends keeping redirects for as long as possible, generally at least a year, and warns that search rankings can fluctuate during a move. These steps reduce avoidable migration problems; they do not guarantee unchanged rankings.
If hosting or domain records are also changing, scope that work separately enough to identify email and database dependencies. My website migration service covers planning a move around the existing setup.
Compare quotes against the work required
A useful redesign quote should name the pages, content responsibilities, retained features, URL changes and launch checks. Ask what requires new work and what will be reused.
As a simple example, refreshing the layout while keeping the same pages and form is a different project from adding a shop, moving customer accounts and changing hosting. Pricing both as “a website redesign” hides the difference.
You can send me your current website and the three things that frustrate you most. I’ll discuss whether the next step is a targeted repair, a review or a wider redesign, with the work and price agreed before changes begin.