WordPress rebuilds & new sites
When another patch
isn’t the right plan.
Compare repair, remediation, and a new WordPress build. Start with the current site, the business requirements, and the foundation your team needs to maintain.
Choose the appropriate scope
A new site should solve the underlying problem.
The decision should follow a review of the existing site and what the business needs next. An error message alone is not enough to recommend a rebuild.
Repair or remediate
Keep a sound foundation.
A targeted fix may be the appropriate route when the core structure still meets your needs and the problem can be traced to a manageable update, configuration issue, or component.
- A clear and bounded cause
- Maintainable themes and plugins
- Useful functionality worth retaining
- A compatible path to supported software
Rebuild or new site
Plan a more maintainable starting point.
A rebuild may be worth scoping when the existing stack creates recurring blockers or no longer supports the business. Include migration and ongoing ownership in that comparison.
- Unmaintained components or extensive workarounds
- Requirements the current site no longer meets
- Content and integrations that need restructuring
- A need for clearer editing and maintenance ownership
What we scope
Build around the work
the website needs to do.
Discovery and requirements
Review the existing site, content, users, integrations, and operational constraints. Agree what should be retained, replaced, or retired and what success looks like for the new site.
Structure and implementation
Define the content structure, page and template requirements, editing experience, and required functionality. Select a theme and plugin approach that the intended maintenance team can support.
Migration and launch
Plan content and data migration, important URL redirects, form and integration checks, hosting requirements, and the release sequence. Agree how the result will be validated before launch.
Handover and maintenance
Document the agreed build, access, editing responsibilities, and follow-up work. Establish who will own updates and ongoing maintenance after the project.
For WordPress Agencies
Your client relationships.
Our specialist support.
Add PHP security and remediation expertise alongside your team. Coordinate client-site assessments, compatible updates, and white-label support around the way your agency works.
Questions, answered
A little more clarity.
Every environment is different. These answers help set the starting point.
Discuss your situationDoes a PHP security advisory mean I need a new website?
No. An advisory is a reason to confirm patch status and plan appropriate updates. A rebuild decision depends on maintainability, requirements, and the scope of the existing problems.
Can useful content and functionality be retained?
That is part of discovery. Identify what should move to the new site, what needs improvement, and what should be retired before setting the migration scope.
Can this be a white-label project for our agency?
White-label options can be agreed around the client relationship, responsibilities, communication, and deliverables. Start with how you want specialist support to fit around your team.
Can you quote a fixed cost or launch date from this page?
No. Timing and cost depend on the content, functionality, integrations, and migration requirements. Those commitments follow an agreed scope.
Ready to protect your sites?
Find the right next step for your WordPress site.
Discuss whether a targeted fix, broader remediation, or a new site is the appropriate way forward.