01
Look for business and content mismatch
The website may still describe old services, audiences, locations or team structures. If staff routinely apologise for the website or send separate documents to explain the real offer, the content architecture may no longer support the business.
A new visual style alone will not solve missing ownership or evidence. Identify which pages, facts and customer questions have changed and whether the current system can accommodate them.
- Important services are hidden or inaccurate
- Navigation reflects an old organisation
- Content updates depend on one unavailable person
02
Example: decide between repair and rebuild
A slow homepage caused by oversized images may need focused optimisation, not a rebuild. By contrast, an unsupported theme with inaccessible navigation, overlapping plugins and no safe update path may make repeated repairs uneconomical.
Create an issue inventory and estimate the cost, risk and lifespan of repair. Compare that with a staged replacement that preserves useful content, search equity and proven customer journeys.
- Repair when the cause is isolated and supportable
- Redesign when structure and journey no longer fit
- Rebuild when the platform blocks safe improvement
03
Run an actionable website review
Test priority tasks on mobile and desktop, review accessibility, forms, search visibility, performance, software support, account ownership and analytics. Ask customers and staff where the process becomes confusing or manual.
Prioritise critical fixes even if a rebuild is planned. Security warnings, broken forms and inaccurate contact information should not wait for a future launch.
- Record evidence for each problem
- Separate urgent remediation from strategic work
- Identify content and integrations worth preserving
- Set measurable acceptance criteria
04
Common mistakes when replacing a website
Starting design before auditing content, URLs and analytics can remove useful pages and break inbound links. Recreating every old page also carries obsolete structure into the new site.
Avoid treating launch as the finish. Redirects, monitoring, form tests, search coverage, content ownership and maintenance need post-launch attention.
- Do not delete URLs without redirect decisions
- Do not migrate inaccurate content automatically
- Do not claim improvements without a measured baseline
Practical next steps
Checklist
- 01Audit business accuracy and priority journeys
- 02Test mobile, accessibility, forms and performance
- 03Review platform support and account ownership
- 04Compare repair, redesign and rebuild options
- 05Inventory content, URLs, data and integrations
- 06Plan redirects, launch checks and maintenance
Common questions
Questions and answers
How old is too old for a website?
Age alone is not decisive. Current business fit, usability, supportability, security and maintenance matter more.
Can an existing website be improved instead?
Often, yes. Focused content, accessibility, performance or journey work may provide better value when the platform remains supportable.
Will a new website automatically improve rankings?
No. A migration can help or harm visibility depending on content, redirects, technical implementation and ongoing search work.
Should the old website stay live during development?
Usually until the replacement is ready, while urgent risks are addressed. Plan deployment, content freeze and rollback deliberately.
Need a considered recommendation?
Discuss the website, not just the symptom.
AHANIX reviews each requirement manually. Technical recommendations may depend on access to the website, hosting or DNS configuration.
Continue learning