
A business website can look perfectly normal while its software falls behind, old user accounts remain active, or nobody is sure how to restore it after a problem. Those gaps are easy to miss when the site is doing its job and customers can still reach it. But, even if it’s not broken today, that doesn’t mean it wont break tomorrow, and so it’s best you plan for it now.
Website security is easier to manage when someone owns the routine work and knows what to do if something goes wrong. You do not need to handle every technical task yourself. You do need to know which tasks someone handles, who takes responsibility, and how to reach the right person when the site needs attention.
What We'll Cover
Start with the software
If your website runs on a content management system such as WordPress, you need to maintain its core software, theme, and plugins. Updates often fix security weaknesses as well as bugs. When software goes without updates for long periods, known weaknesses can put the site at risk.
Make a simple inventory of what the site uses and who maintains it. Check that WordPress, themes, and plugins still receive support and updates. Remove plugins and themes you no longer use, and avoid installing software from unfamiliar sources as part of sound plugin management and broader website security best practices.
Automatic updates can help with routine maintenance, but they do not remove the need for oversight. Some sites rely on custom features or integrations, so someone should check them after each update. Before major work begins, decide who will review important changes, how the team will report problems, and which backup or rollback option you can use.
Know who can get in
A website often relies on several connected accounts: the content management system, hosting provider, domain registrar, business email, analytics, and payment tools. Someone who gains access to one of these accounts may be able to disrupt the site or take control of important settings.
Review the list of people and service providers who can access each account. Give each person their own login where possible, remove accounts they no longer need, and limit administrator access to people who genuinely need it. Keep user permissions aligned with each person’s role. Turn on multi-factor authentication (MFA), especially for administrator, hosting, domain, and email accounts. Use unique passwords in a password manager, and keep recovery details current.
Also check who controls the domain registration and hosting account. The business should know which email address receives renewal notices, who can approve account changes, and how to recover access if the usual contact leaves. Store this information securely, and make sure at least two trusted people know where to find it.
Check backups before you need them
A backup helps only when you can restore it. Confirm that your provider backs up your website files and database on a schedule that fits how often the site changes. Keep a copy separate from the live website and the account you use to administer it, so one compromised account cannot automatically expose every copy.
Ask your provider what each backup includes, how long it keeps backups, and how restoration works. A brochure that promises “daily backups” does not tell you how quickly the provider can restore the site or whether the restore will recover customer orders, forms, and recent changes.
Test a restore in a safe environment or ask your provider to demonstrate the process. Record who handles restoration, how to request it, and how much downtime or data loss you might face.
Make sure someone would notice a problem
Website trouble does not always begin with a dramatic warning. Someone may change a page without permission, add a new administrator account, break a form, or redirect visitors somewhere unexpected. Customers may spot the issue before your team does.
Decide who checks the site and where alerts should go. At a minimum, know how you will learn about failed updates, unusual account activity, malware warnings, downtime, expired certificates, and missed backups. If a provider monitors the site, ask what it checks, how it sends alerts, and whether the service includes response or cleanup. Build regular website maintenance checks into the routine, including reviews of updates, alerts, and recovery processes.
Do not assume your hosting support covers every layer of website security. Your host may maintain the server, while you or your web developer manage WordPress, plugins, account access, content, or third-party tools. Write down exactly where the provider’s responsibility ends and yours begins.
Decide what to do if the site is compromised
If you suspect someone has hacked your website, avoid making a series of rushed changes without a plan. Contact the person who handles website security or your trusted IT provider. If you use a managed service, follow the emergency contact method you confirmed in advance.
Your response will depend on what happened. You may need to take the site offline temporarily, change affected passwords, remove malicious changes, and restore a clean backup. Keep notes about what you noticed and when, and save relevant alerts or messages. Do not assume that deleting an unfamiliar file or changing one password has fixed the problem.
If the incident may have exposed customer or employee information, get qualified advice promptly about how to investigate, communicate, and meet any applicable notification obligations. Requirements depend on the circumstances, so do not assume every incident calls for the same reports.
Write down the essentials
A useful website security plan can fit on one page. Store it securely, but make sure the right people can access it even if the website or a staff member’s email account becomes unavailable. Include:
- The website address, hosting provider, domain registrar, and the person responsible for each.
- Who has administrator access and where the business keeps account recovery information.
- Who handles software updates, monitoring, backups, and restoration.
- The main contact for urgent support, plus a backup contact if that person is unavailable.
- What to do if someone alters the site, the site goes offline, a security warning appears, or the incident may have exposed information.
- How the business will communicate with staff and customers if the site becomes unsafe or unavailable.
Then test the plan with a short walk-through. Ask: if the website went offline tonight, would we know whom to call? Could we access the domain and hosting accounts? Do we know whether a clean backup exists? Who would decide whether to take the site offline or notify customers? A few minutes spent answering these questions can reveal gaps before they become urgent.
A short checklist for this week
Choose a few concrete actions and assign an owner and due date:
- Confirm that the website platform, theme, and plugins still receive security updates and support.
- Review administrator accounts and enable MFA on key accounts.
- Check when your provider last backed up the site, and test the restoration process.
- Check that monitoring and renewal notices go to someone who will act on them.
- Save the support contact details and write down the first steps to take if something goes wrong.
Keep the work manageable
Website security requires ongoing maintenance. You can automate some tasks, but a person still needs to review changes, test recovery, and make decisions. Make sure you know what your provider, employees, and tools actually handle instead of relying on assumptions.
If you are unsure who manages your website updates, backups, access, or incident response, ask for a clear list of responsibilities. We can help review your website’s maintenance and security arrangements and identify practical next steps. Contact us to get started.
