To protect your website from hackers, keep the software current, give every account a unique password and multifactor authentication, limit who can log in, and keep a backup you have actually restored. If a site is hacked anyway, the sequence Google's hacked-site guides lay out is to confirm it, contain it, clean it, restore it and ask Google to review it. This guide is for owners of local service businesses in the Twin Cities East Metro, the St. Croix Valley and western Wisconsin.
It draws on CISA, FTC, NIST, Google and WordPress guidance and on the text of the Minnesota and Wisconsin breach notice statutes. The WordPress advice is general guidance, since McKinney Creative Ventures does not sell WordPress plans. For who should hold the logins, see web management services.
Protect your website from hackers: a checklist
Google's web.dev guide to how spammers hack sites names six routes: compromised passwords, missed security updates, insecure themes and plugins, social engineering, security policy holes and data leaks. The checklist maps to those routes, and its last column names the source.
Scroll to see all columns
| Item | What to do | Source |
|---|---|---|
| Updates | Update the CMS, plugins and themes, and remove the ones you no longer use | web.dev, WordPress handbook, CISA |
| Passwords | Use a long, unique password for every account | NIST SP 800-63B-4, FTC |
| Multifactor authentication | Turn it on for the host, registrar, CMS admin and email | CISA, FTC |
| Access | Limit administrative access to people who need it, and remove it when their work ends | web.dev, FTC |
| HTTPS | Serve the site over HTTPS, including login pages | web.dev, FTC |
| Backups | Save backups in the cloud or on an external drive, and test a restore | CISA, FTC, WordPress handbook |
| Monitoring | Verify the site in Search Console and read its Security issues report | Google Search Console Help |
Renewals are covered in SSL certificate management. HTTPS belongs on this list because web.dev counts not enabling it, and letting people sign in over HTTP, as a security policy hole.
Passwords and multifactor authentication
NIST's SP 800-63B-4, published in July 2025, covers the authentication of people using government information systems, so it is a reference point for your site and not a rule for it. Its password section says a verifier must require at least 15 characters when the password is the only factor, and may allow a shorter password of at least eight characters when it is only one part of multifactor authentication. It says verifiers must not impose composition rules such as mixing character types or require periodic changes, though they must force a change if there is evidence of compromise. The FTC's small business cybersecurity page calls a strong password at least 12 characters and says never to reuse one. In our reading, a long, unique password from a password manager meets both, with no forced rotation.
CISA's guidance for small businesses, updated in April 2024, says any form of multifactor authentication is better than none, including text message and authenticator codes. It names FIDO authentication as the only widely available phishing resistant option, and it tells IT staff to enable multifactor authentication for every system administrator account. For a website, that means the CMS admin, the hosting account, the domain registrar and the email address that resets all of them.
Keep software, plugins and access under control
The web.dev guide says attackers actively look for old software with known vulnerabilities and calls outdated or unpatched themes and plugins a major source of them. It advises removing themes and plugins that are no longer maintained, being careful with free copies from untrusted sites and deleting a retired plugin's files from the server as well as disabling it. CISA calls patching one of the most cost-effective security practices and points to its Known Exploited Vulnerabilities Catalog for what to prioritize.
For WordPress, the handbook's hardening page says automatic updates have been available since version 3.7. It also says the dashboard file editor is often the first tool an attacker will use after logging in, and shows a setting that turns the editor off, while noting that the setting will not stop an attacker from uploading malicious files. The page treats security as risk reduction, since a perfectly secure system may be impractical or impossible to find.
Access needs the same attention. The web.dev guide lists administrative access for users who do not need it as a security policy hole, and the FTC's vendor guidance says to limit a vendor's access to databases with sensitive information to a need-to-know basis, and only for the time the vendor needs to do the job. Remove former staff, freelancers and agencies from the CMS, host and registrar when the work ends.
If your website is hacked: a recovery plan
This sequence follows Google's hacked-site guides on web.dev and the FTC's breach guide. The web.dev cleanup guide lists shell access to your servers and an understanding of code as prerequisites, and its hacked-sites overview covers fixing the site yourself or hiring a professional.
1. Confirm it
Open the Security issues report in Search Console, which covers hacked content, malware and unwanted software, and social engineering. Google says affected pages can appear with a warning label in search results or an interstitial warning in the browser. If you cannot see the problem, web.dev says the hacked content may be cloaked, so visitors see a clean page while search engines see spam. A site: search on your domain and the URL Inspection tool can reveal it.
2. Contain it
Take the site offline, for example by stopping the web server or by pointing DNS at a static page on a different server that returns a 503 status. The quarantine guide says a 503 response should come from outside the compromised server, and that a 4xx or 5xx response from the compromised site is not enough to protect visitors. It adds that a robots.txt disallow only blocks crawlers, and it says to delete accounts the hacker created and change every password, including FTP, database, administrator and CMS logins. The FTC's breach guide says to document the investigation and not destroy evidence.
3. Call the right people
Call the host first. The web.dev guide says the host can check that its other customers were not affected and may help recover the site. In our reading, call the domain registrar too if the DNS records or contact email were altered. The FTC guide suggests consulting legal counsel when personal information may be involved.
4. Clean and restore
The cleanup guide's server step begins by checking that your backup was created before the hack. With a clean, current backup, it says to restore it, install available software updates, consider removing software the site no longer uses, correct the vulnerability and change every password one more time. The steps are longer for an outdated backup or none, and in our reading that is the point to hand the work to a professional. CISA adds that a scheduled backup is not enough, because restores need regular testing, and some organizations hit by ransomware found restoring took longer than expected.
5. Ask Google to review it
Before you ask, web.dev's review guide says to confirm that you have verified ownership in Search Console, cleaned the site, corrected the vulnerability and brought it back online. Then open the Security issues report, select Request a review and describe what you did. Search Console Help says most reconsideration reviews can take several days or weeks and that you should not resubmit before a decision. The review guide says a review for a site hacked with spam can take up to several weeks, malware reviews a few days and phishing reviews about a day.
6. Report it
The FBI runs the Internet Crime Complaint Center, which describes itself as the central hub for reporting cyber-enabled crime. It asks for a report even when you are unsure it qualifies.
Minnesota and Wisconsin breach notice laws
This section is general information and not legal advice, so ask your attorney how the statutes apply to you. Minnesota's notice duty runs to Minnesota residents. Wisconsin's runs to each person whose information was acquired when the entity's principal place of business is in Wisconsin or it maintains or licenses the information in Wisconsin, and to Wisconsin residents when the entity is based elsewhere.
Minn. Stat. 325E.61 covers a person or business that conducts business in Minnesota and owns or licenses data that includes personal information. It requires disclosure of a breach of the security of the system to any Minnesota resident whose unencrypted personal information was, or is reasonably believed to have been, acquired by an unauthorized person. Disclosure must come in the most expedient time possible and without unreasonable delay, subject to law enforcement needs and to the steps needed to find the scope and restore the system. The text sets no number of days for notifying residents, although a business that notifies more than 500 people at one time must also tell the nationwide consumer reporting agencies within 48 hours, and the attorney general enforces it. Personal information means a first name or initial and last name combined with a Social Security number, a driver's license or Minnesota identification card number, or an account or card number with the code or password that permits access.
Wis. Stat. 134.98 applies to an "entity," defined as a person other than an individual that conducts business in Wisconsin and maintains personal information in the ordinary course of business, among other cases. It requires reasonable efforts to notify each person whose personal information was acquired without authorization, within a reasonable time not to exceed 45 days after the entity learns of the acquisition. Its list of personal information includes a Social Security number, a driver's license or state identification number, a financial account number or a code that permits access to one, a DNA profile and unique biometric data. Notice is not required if the acquisition does not create a material risk of identity theft or fraud, and certain regulated entities are exempt.
In our reading, a contact form that collects a name, phone number, email address and message does not collect any of the listed data elements. A form, portal or file upload that takes a driver's license number, a card or account number or a Social Security number could. A Woodbury business with customers in Hudson should ask an attorney which statute applies to which customer.
Who to call before you need to
CISA's guidance describes a written incident response plan with roles and an address book for use if the network is down. For a website, our version is a one-page sheet kept off the site: the host's support contact, the registrar login, who administers the CMS, your attorney and who restores backups.
If a rebuild off WordPress is on your list, contact us about our website service.