Inherited a website? How to rescue it without starting over

Most websites are inherited

The developer moved on. The agency was acquired. The marketing person who set it all up left, and the notebook with the passwords went with them. Now you have a site that is slow, that occasionally shows an error, and that nobody on your team fully understands. The instinct is to tear it down and start again. Usually that is the expensive way to fix a cheap problem.

Here is the order we work in when we take over a site we did not build.

Step 1: recover ownership

Before you touch anything, make sure the business owns the pieces: the domain name, DNS, hosting, the content management system, analytics, Search Console and the Google Business Profile. Log into each. If you cannot, use the provider’s ownership-recovery process now, not later. The domain is the asset that matters most; everything else can be rebuilt around it.

Write down where each account lives and who can access it. This one document prevents the next inheritance from being as painful.

Step 2: back everything up

Take a full copy of the site files, the database if there is one, and any exports the platform allows. Do it before making a single change. If a fix goes wrong, you want a way back.

Step 3: stop the leaks

Some problems cost you money every day they persist. Fix these first, in this order:

• Forms. Submit every form yourself, from a phone, and confirm the message arrives. Silent form failure is the most common and most expensive fault we find.
• Security. If the platform or its plugins are years out of date, patch them, or isolate the site until you can. A hacked site loses trust with visitors and with Google.
• Uptime and errors. Set up basic monitoring so you learn about outages before your customers do.
• Phone numbers and hours. Check that the contact details on the site are current. An old number is a lost lead every time it is dialed.

Step 4: repair in priority order

With the bleeding stopped, work through the rest by impact:

1. Performance. Oversized images, unused scripts and cheap hosting are the usual culprits. Fixing them improves every visit and your Google rankings.
2. Search damage. Look for broken links, pages that return errors, duplicate URLs, missing titles and descriptions, and redirects that were never set up after a previous change. Search Console will show most of it.
3. Tracking. Confirm analytics is installed once, not three times, and that leads are being counted as conversions.
4. Content. Outdated services, staff who left years ago, prices from a previous decade. Update or remove.

Step 5: decide about the platform

Only now is it worth asking whether the platform should be replaced. The test is simple: does it block the fixes you need? A theme so heavy it cannot be made fast, a builder that cannot output the structured data AI search relies on, or a stack that costs more to keep alive than to replace are real reasons. “It is old” on its own is not.

If a rebuild is right, do it with every existing URL either kept or redirected, so the search visibility the old site earned survives the move.

Step 6: keep it that way

A rescued site drifts back without maintenance. Schedule updates, keep backups running, check performance and search health monthly, and have one person who answers when something breaks. That can be someone on your team or a care plan; what matters is that it is someone.