Updated
Website redesign. What to fix and how to plan the change
Your site has visits but is difficult to use on a phone. Choose the scope of work, preserve important addresses and check the result after launch.
In this article
In short
Start with the problem, traffic data and a contact check on a phone. A targeted fix may be enough. For a rebuild, preserve useful content and addresses. Prepare URL changes with a redirect map and checks after launch.
The site opens on a phone, but the contact button sits outside the screen. People still find the site through Google and call. You want to fix the problem while preserving what already brings enquiries.
The site’s age alone does not determine the scope of work. Record the specific problem and check it before ordering a new design.
When to start with a fix
If a form fails, check the path from submission to message delivery. If the site is slow, find the resources or actions causing the delay. A heavy photo does not automatically require a new system.
Also check the copy and route to contact. Can a visitor understand your offer and see the next step? The problem may affect just one page or a phone screen.
Our free scan helps identify basic technical signals. It does not assess the whole architecture or check delivery of real enquiries. Combine those findings with a functional check before deciding to rebuild.
When to consider a larger change
Consider rebuilding when the required changes affect the foundation shared by many pages. That might be a layout that cannot reasonably adapt to phones or a process the current system cannot support.
First check the available repair options. Compare an update with replacement for an old system version. Look for an existing integration when adding a feature. An unresponsive developer means checking access and documents before deciding on a fresh build.
The domain, code and accounts are separate matters. Use the checklist in website ownership. A new design will not recover control of a domain whose registrant you still do not know.
Prepare addresses and content
Collect URLs from your site system, sitemap, Search Console and analytics before starting. Include visits from ads, Instagram and saved links. Record the current content and intended outcome next to each important URL.
Keep an address when it still fits the page. If it must change, choose the replacement based on its content. Google recommends permanent server redirects, such as 301 or 308, leading to the destination page.
This example uses fictional addresses to illustrate the plan.
| Old address | Plan after the change |
|---|---|
/repair-offer | 301 to /services/repairs with matching content |
/blog/guide | Keep the address and content |
/past-campaign | 404 or 410 if removed without a replacement |
Avoid redirecting every removed page to the homepage. Check whether the destination is relevant. Update internal links, canonical URLs, language versions and the sitemap. Google advises keeping redirects as long as possible, generally at least a year.
Check before launch
Prepare file and data backups and a way to restore the previous version. Your developer should be able to show how restoration works. For orders or bookings, also plan for data created during the switch.
Protect the test version from unauthorised access. Robots.txt alone does not protect private information or guarantee exclusion from the index. Agree on test environment protection with your developer.
Check the important pages on a phone and computer before publication. Test the form, phone link and essential functions. Check redirects and remove indexing blocks from the public version. Find more steps in our website handover checklist.
What to measure after the change
Record the launch date. Check important old URLs, server responses and access to new pages. Do not wait several weeks to fix a broken redirect or form.
In Search Console, watch indexing, clicks and impressions for specific pages. Record genuine enquiries separately. Compare complete periods of similar length and allow for campaign or seasonal changes.
Visibility may fluctuate after URL changes. That processing period is not a guarantee or an explanation for every drop. Check the actual URL status using our indexing guide.
Website redesign questions
Does an old website always need replacing?
No. Check the specific problem, update options and scope of required changes.
Do I need a new domain?
No. A new design can use your existing domain and keep the same page addresses.
Does missing source code mean starting again?
First establish rights, access and whether the files can be recovered. Then compare technical options.
Will a homepage redirect preserve every old address?
It does not ensure a relevant destination. Choose matching content or handle removal properly.
Can a redesign guarantee no SEO decline?
No. You can prepare the change, reduce errors and monitor the outcome. A new design alone offers no such guarantee.
What would you like to change in your business?
Leave your number. We will talk about your process and see whether we can help. The first call is free.
The service this text is about
WebsitesA website made for your company, not from a template. Before you pay, we show a working prototype.