Repair or Replace an Older Website
How to decide whether an established website should be repaired, redesigned, or rebuilt.
An older website may have valuable content and search visibility even if its design feels dated. List what works, what visitors cannot do, and what technology is no longer supported before deciding to rebuild.
What to check first
- Identify what still works and has value
- List the business problems that must be solved
- Consider search visibility, content, access, and maintainability
What to do next
A targeted repair may solve broken forms, mobile layout, or speed without moving every URL. If a rebuild is necessary, map existing pages, preserve useful content, and plan redirects so customers can still find the services they need.
Identify the value already on the site
An older website may have service pages, customer references, search traffic, and working integrations worth keeping. Make a list of what visitors use and what the owner can still update. A dated appearance alone does not prove the whole foundation needs replacing.
Compare the two paths honestly
A focused repair may address mobile layout, forms, accessibility, and speed. A rebuild may make sense if unsupported software or a fragile structure blocks routine work. Include content migration, redirects, account ownership, and testing in the rebuild estimate, not only the new design.
Protect continuity at launch
If a replacement is chosen, map useful old URLs, preserve relevant copy, and verify contact paths before switching traffic. Review the new site on desktop and phone, then check for missing pages and broken forms after launch.
Can I keep the existing domain?
Usually yes. The domain and website are separate assets, so plan their access and DNS before moving hosting or rebuilding.
