Use this checklist to decide whether a 2018-era WordPress, PHP or template website needs maintenance, a redesign or a full rebuild.
If you have a website built around 2018, audit the software and key customer journeys first. Keep and upgrade the site if it can run on supported software and still meets the business need. Plan a rebuild if essential features depend on unmaintained code, the site cannot safely take updates, or your team cannot maintain the new workflows it needs.
What should you check on a 2018-era website?
| Check | What to test | What could justify a rebuild |
|---|---|---|
| Software support | Record PHP and database versions, WordPress core, theme and plugins. Try the required upgrades on a copy. | Essential custom code or a plugin fails on supported software and replacing it affects much of the site. |
| Ownership and recovery | Confirm domain and hosting access. Restore a backup to staging and verify pages, media and any customer data. | The original system cannot be restored or changed reliably. |
| Enquiry or checkout | Complete the main journey on mobile. Confirm that the enquiry, email or payment status reaches the right team. | The existing platform cannot support required integrations or permissions without fragile workarounds. |
| Editing | Ask the staff member who maintains the site to update a page and publish it on staging. | Routine edits depend on a developer or cause repeated layout problems your team cannot fix. |
| Search and speed | Record key URLs, indexed pages, top landing pages and mobile performance. | Multiple page templates need structural changes, and smaller fixes cannot address the main problems. |
Standard WordPress, traditional PHP and templates need different fixes
Standard WordPress. Back up files and the database, then test the update path on staging. Check the theme, forms, plugins and any custom templates against a supported PHP version. If your editors like the admin and the site works after upgrades, a refreshed theme can improve the design while keeping the editing workflow. WordPress update guidance explains the update process.
Traditional PHP. Ask which parts are custom and which depend on libraries or a framework. Identify the rules behind logins, forms and reports before changing them. A supported runtime and targeted repairs may be enough if the code is maintainable. Check the installed runtime against the PHP support schedule.
Template-based sites. Find out if the template is part of WordPress, a builder or plain HTML. Check who owns the template licence and whether it receives updates. A template can be a good fit when your pages follow common patterns. If you depend on custom overrides for ordinary edits, price a replacement template as well as a full redesign.
When would a modern framework help?
Compare the rendering and hosting plan if a rebuild is justified. An Astro site can prebuild public pages and add JavaScript to selected interactive components. Next.js can combine server-rendered output with interactive React components. A client-rendered React single-page app can fit a logged-in dashboard. For public marketing pages, ask the developer to demonstrate the initial page content, links and error responses on a slow connection.
Read the Astro islands guide, Next.js rendering documentation and React framework guidance when comparing proposals.
Protect your leads and search visibility when moving
- Export old URLs, page content, images and relevant account settings. Save a verified backup and agree who can restore it.
- Keep useful URLs where possible. For pages that move, map old addresses to the closest replacement and test redirects.
- Test the new site on staging with real content. Include call buttons, forms, notifications, checkout and any reporting your team relies on.
- After launch, check key URLs, analytics and incoming enquiries. Use Search Console to verify pages Google can crawl and monitor errors.
For the current PHP2Shell advisories, see our PHP security update guide. For changed URLs, follow Google’s site move guidance. Use our redesign preparation checklist or discuss your existing site with our Kota team if you need help deciding what to keep.