Inherited a website? What to check in the first hour
You’ve taken over a site and don’t know what’s in it. This is the order I’d work through, to find out what you have before anyone changes anything.
1. Find out who controls what
Most inherited-website problems are access problems. Make a list of the four things that matter: the domain registration (who it’s registered with and whose email is on it), the DNS (where the domain’s records are managed), the hosting account, and the website’s own admin login.
They’re often held by different people or companies, such as a former agency, a previous employee or a freelancer. If your business doesn’t control the domain, fixing that comes before anything else.
2. Take a backup before you touch anything
Even if you’re only looking, make a full backup of the files and the database. Ask the host whether backups already exist and how far back they go, and download one if you can.
If you don’t know whether a restore would work, treat the backup as unproven until someone has tested it on a copy.
3. Work out what it’s built with
Log in and check what you’re dealing with: WordPress or something else, which theme, and which plugins. In WordPress, Tools → Site Health → Info lists the WordPress version, PHP version, theme and plugins in one place.
Note anything custom: a theme built specially for the site, a plugin you can’t find in the public directory, or code added in the theme’s files. These are the parts only the original developer understood.
4. Check what’s out of date, and update carefully
Look at which plugins, themes, WordPress itself and PHP are behind. Old software is the most common route to a hacked site, so it does need attention.
But don’t press “update all” on a site you don’t understand. Updates can break forms, checkout or a custom theme. Update on a copy first where you can, or at least with a backup and a quiet moment to test.
5. Review the users and security basics
Check the list of users with admin access and remove people who shouldn’t have it, such as past staff and former suppliers. Make sure everyone left has a strong, unique password.
Look for an obvious security plugin, working backups and an SSL certificate that isn’t about to expire. If you see warnings you don’t understand, write them down rather than guessing.
6. Test everything that earns or costs money
Submit the contact forms and check the email arrives. If it’s a shop, place a test order. Check that analytics and tracking are installed and recording, and that the site loads at a reasonable speed on a phone.
These are the things that fail without anyone noticing, and they’re the first things a previous developer’s departure tends to break.
7. Check email and anything connected
Find out whether your business email runs on the same domain and where it’s hosted, because moving or changing the website’s hosting can break it.
Also look for connections to other systems, such as a CRM, a mailing list or a payment provider. Each is a dependency that needs to keep working through any change.
8. Write down what you found
Keep a short document listing logins and who holds them, what the site is built with, what’s out of date, what’s broken and what’s fragile. It turns a worrying unknown into a list you can prioritise.
If this feels like more than you want to take on, a short review that ends with a written list like this is a sensible first job to hand to a developer.
Inherited a website you don’t understand?
Tell me what you know about the site and include its address. I’ll reply with any questions and tell you what I think it needs.