
Rebuild your WordPress website when its underlying structure prevents the business from moving forward. Improve it when the foundations are sound and the problems can be identified and fixed. A dated homepage, a disappointing speed score or a quiet enquiry form deserves investigation. None, on its own, is a convincing reason to replace the whole website.
At Webheads, we bring over 30 years’ experience of designing, developing and supporting business websites to that decision. The useful question is what your current site can reasonably become, what is holding it back and whether the proposed investment will address those limits.
These terms often get bundled together in proposals. Ask an agency to explain precisely what it means, because the amount of work, disruption and ongoing responsibility can be very different.
| Approach | What changes | When it makes sense |
|---|---|---|
| Targeted improvements | Selected content, journeys, templates or technical faults. | The website is maintainable and the main problems are specific. |
| Visual and UX redesign | Presentation, navigation and how people use the site. Some development may be needed. | The business or brand has moved on, but useful technical foundations can remain. |
| Technical rebuild | The theme, editing system, data structure or integrations. Design may change too. | Existing limitations make essential improvements impractical or disproportionately costly. |
A rebuild can still use WordPress. It does not automatically mean changing your domain, replacing every page or abandoning content that already brings in business.
Start with the tasks the website needs to perform. For a professional services firm, that might be explaining a complex offer and generating suitable enquiries. For a membership organisation, it may be publishing content and managing access. Judge the website against those tasks.
Record a baseline before changing anything. Use a representative period and account for seasonal demand or changes in marketing spend. A single slow page or a handful of weak enquiries will not tell you where the underlying problem sits.
If the site can be maintained safely, supports the content you need and lets your team work effectively, begin with the highest-value problem. That could be a vague service proposition, an awkward mobile menu, oversized images or a form asking for too much information.
For example, a business receiving relevant search traffic but poor enquiries should review the landing pages and enquiry journey. Explain who the service suits, answer buying questions, show relevant projects and make the next step clear. Replacing the theme without addressing those gaps leaves the commercial problem intact.
Agree a short, prioritised improvement programme with a clear purpose for each change. Measure completed enquiries and their quality, not just button clicks. If the technical work reveals deeper limitations, you can then scope a rebuild with evidence behind it.
A rebuild is worth serious consideration when routine changes repeatedly expose the same structural problem. Perhaps the theme cannot support accessible layouts, the page builder makes content fragile, or an essential feature depends on software that no longer has a credible maintenance route.
Growth can create a different set of requirements. Multilingual publishing needs a manageable relationship between language versions. A large service catalogue needs consistent page structures. Member areas and business-system integrations need clear rules for data, access and ownership.
Ask the agency to demonstrate the constraint and compare the work needed to resolve it in the existing site with a replacement. “It would be easier for us to start again” is not enough on its own. Our WordPress development agency in London plans the platform around those business and editorial requirements.
For Ocean Re’s multilingual website, we explored CMS alternatives before recommending WordPress. The project brought together content structure, design, development and translation support, with an eight-week delivery window ahead of Miami Reinsurance Week. The important decision was whether the implementation could support the organisation’s international needs and its team.
Our work with Adaptive involved a different brief: a custom WordPress site following a rebrand, combining clearer content journeys with video and animation. These projects illustrate why a rebuild needs a specific business case. Two organisations using the same platform can need very different websites.
A page count is a poor substitute for a scope. Twenty pages using a consistent structure can involve less work than a small site with complicated account access, multilingual content or a difficult integration.
Compare proposals against the same requirements, including:
Ask for the cost and expected limitations of improving the current site alongside the rebuild option. Include the time your own team will spend and compare likely ownership costs over the next couple of years. A lower initial fee can still leave substantial content or maintenance work outside the proposal.
The timetable needs the same discipline. Agree when content, approvals and integration access will be available. A development estimate is not necessarily a complete project schedule.
Treat existing search visibility as an asset. Before deciding which pages to remove or combine, record their traffic, relevant queries, useful links and contribution to enquiries. A page looking old is not evidence that it has no value.
Keep established URLs where they still serve the same purpose. For necessary URL changes, prepare a page-by-page redirect map to relevant replacements. Update internal links, canonical URLs and sitemaps, and check that launch pages are indexable. Do not redirect every retired page to the homepage.
Google’s site migration guidance warns that rankings can fluctuate while changed URLs are processed. No agency should promise a risk-free migration or an automatic ranking increase simply because the design is new.
Include a technical SEO review in the scope before launch, with named responsibility for redirects and post-launch checks. Preserve useful service detail and client evidence when rewriting copy. Clearer design should make that information easier to find.
Test complete journeys on a separate staging site, then check them again on the live site. That includes mobile navigation, keyboard access, forms and their email delivery, downloads, search and any purchases or account functions. Confirm that analytics records successful actions accurately.
Ask the people who will maintain the website to carry out normal editing tasks before sign-off. Agree a backup and recovery plan, who handles launch-day issues and how content added to the old site will be carried across.
After launch, monitor errors, search performance and enquiry quality against the baseline. Keep the team responsible for development involved long enough to address what real use reveals. A website remains a working part of the business after the project is marked complete.
So give us a call on 0207 287 7060 or email info@webheads.co.uk, or complete the form below.
We will use your email address to contact you regarding your query. We will not pass this on to any 3rd parties, in accordance with our privacy policy.