A family member searches for your facility's visiting hours and finds a page selling something unrelated, or a warning from the browser that the site is unsafe. The administrator gets a call from a worried daughter. The marketing person calls the web designer who built the site four years ago, and the designer no longer answers the phone.
Facility websites are usually built once and then forgotten. The login sits in someone's email, the plugins are never updated, and the person who knows the password has left the company. That is how sites end up defaced, redirected or quietly stuffed with spam pages.
Start with a short list of everyone who can log in to the site's controls. That includes the website itself (the admin area), the hosting account, the domain registration account and any page builder or email form service connected to it. In many facilities these are three or four separate accounts, and each may be owned by a different person.
The questions to answer:
Who owns the domain name registration, and is it under a company email address?
Who pays for the hosting, and whose email receives its notices?
Which user accounts exist in the site's admin area, and which of them belong to people who no longer work with you?
Are any logins shared between people?
If the domain is registered in the name of the original web designer, fix that first. The domain is the address of your facility on the internet, and whoever controls it controls your website and often your email.
Every former contractor, intern or employee who once had access should be removed or disabled. Do not simply change the password on a shared login and call it done. Give each person their own account with only the permissions they need. Most sites have roles, for example someone who can edit news posts but cannot install software or change settings.
When you part ways with a web developer, put the offboarding on a checklist:
Ask for a list of all accounts and services tied to the site.
Transfer ownership of the domain and hosting to the company account.
Remove the developer's user, or change them to a low access role for a defined period if they are still doing work.
Change every shared password and any keys they may have stored in the site.
Confirm you can log in and see backups before they leave.
Administrator accounts should use long unique passwords stored in a password manager, plus two-step sign-in wherever the site or host offers it. Avoid generic user names like "admin" where possible, and never share one login among several staff. Limit how many people hold full administrator rights. Often only one or two are necessary.
Many defaced sites were broken into through outdated software rather than clever hacking. A site built on a common content management platform depends on its core software, themes and plugins being kept current. Put someone in charge of that. The rhythm could be monthly, with a quick check of what needs updating, followed by a test that the site still works.
Other habits that help:
Delete plugins and themes you do not use, not merely deactivate them
Keep automatic backups stored away from the web server, and test restoring one
Use an encrypted connection (the padlock) on the whole site
Turn on alerts for new administrator accounts and for changes to important files, if your host or a security plugin supports them
Check contact forms, because spam abuse of forms can get your email domain blocked
Ask your host how they protect against known attacks and what support they offer when something goes wrong
If the site is defaced or redirected, take it offline or put up a simple maintenance page if you can. Contact your host and your web provider. Change passwords from a device you trust, starting with the hosting and domain accounts, and review user accounts for anything you do not recognize. Restore from a clean backup if available. Tell your administrator, and ask whether the site collected any personal information through forms, since that may need a closer look with your compliance contact.
Write down the domain registrar, hosting provider, site platform, who holds each account and when you last reviewed them. Put it in a place your administrator and business office can reach. Review it twice a year and whenever someone leaves.
UnityCare IT can help you find out who really controls your domain, hosting and site logins, move ownership to the company, and set up two-step sign-in and backups. We can also handle regular update and monitoring tasks, or work alongside your current web designer so it is clear who does what.
Monitored, backed-up hosting and website updates handled for you.
Call or text: 405-285-3845
New customers: start@unitycareit.com
Existing customers: support@unitycareit.com
Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas
Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support