Short answer
Website security starts with eight checks: HTTPS and HSTS, current software, admin accounts you recognise with two-step sign-in, a backup that has been restored and tested, protected forms, security headers and the Security issues report in Search Console. After a breach, take a copy, change passwords and return to a clean backup in the first hour.
Picture this: on a Tuesday morning a customer rings and says, “your site gave me a danger warning.” You open the site and everything looks fine. Google’s Security issues report page describes exactly this: Safe Browsing shows warnings depending on the visitor’s browsing context, so you may not be able to reproduce one. The page tells you to treat the report as the source of truth. This is an example scene, but it shows why a website security checklist is needed: seeing your site open is not the same as knowing it is safe.
This guide gives a business owner eight checks that need no coding, in order, and ends with what to do in the first hour after a breach. The routine of updates, backups and SSL dates is in how to maintain a website; we do not repeat it here and look at the security side instead.
The table below summarises the eight checks. Write a name next to each row; a check with no owner does not get done.
| Check | How to look | What good looks like |
|---|---|---|
| HTTPS | Type the address with http:// | It switches to https:// by itself |
| HSTS | See the headers in a browser tool | A Strict-Transport-Security header is present |
| Updates | Look at the software and plugin list | Every item has a version and an owner written down |
| Admin accounts | Open the user list | You know every one, two-step sign-in is on |
| Backup | Restore it to a test environment | The site opens and the form works |
| Form and spam | Try it from your own address | Messages arrive, spam does not pile up |
| Security headers | Run a scanning tool report | Gaps are written down and assigned |
| Security issues report | A green check mark |
Step 1: HTTPS and HSTS
Type your site into the address bar with http://. If the page does not move to https:// by itself, that is your first job. Tie the renewal dates of your SSL/TLS certificate to the calendar described in the maintenance guide.
HSTS is one step beyond HTTPS. MDN’s Strict-Transport-Security page says the header tells the browser the site must only be reached over HTTPS. Later http:// attempts are upgraded automatically. According to the page, the browser also does not offer visitors a way to click through an error such as an invalid certificate. The header takes max-age in seconds. For the “preload” option, max-age must be at least 31536000 seconds (1 year) and includeSubDomains must be present.
Our suggestion: start with a short max-age. If your certificate renewal slips by a day, a visitor to an HSTS site cannot get past the warning. Lengthen the period once you are sure renewal works. Ask your host or developer to add the header.
Step 2: Keep software and plugins current
Google’s page on preventing malware suggests keeping a list of all the software and plugins on your site and tracking version numbers and updates. The same page names a common pitfall: installing a forum or blog and then forgetting it. It also says you can stay exposed, even if you keep everything current, when your hosting company has not installed the latest operating system patches.
The Security issues page lists the ways hackers typically get in: a directory with open permissions, an old CMS version or a third-party plugin. Our suggestion is to always update after a backup. We describe the order in the maintenance guide. For how different systems carry this load, see what a CMS is and how to choose one.
Step 3: Tidy admin accounts and turn on two-step sign-in
Open the user list and look at every account you do not recognise. Close the accounts of people who have left. Give everyone their own account and leave no shared “admin”. These are our suggestions.
On two-step sign-in, OWASP’s multifactor authentication page says user accounts are most often compromised through weak, reused or stolen passwords. The same page calls multifactor authentication by far the best defence against most password-related attacks. It also says the weaknesses of the different methods are in many cases only relevant against targeted attacks, and that any MFA is better than no MFA. In its table, SMS and phone calls carry a “restricted” note. Our suggestion is to use an authenticator app where you can. Start with the hosting panel, the domain account and the site admin panel.
Google also recommends choosing good passwords and keeping the computer you work on up to date and clean. Do not reuse a password anywhere else.
Step 4: Restore the backup for real
Taking a backup is not security; a backup that restores is. Every three months, load the backup into a test environment and check that the site opens and the form works. The method and frequency are in the maintenance guide. Two security notes are our suggestions. Keep a copy somewhere other than the site’s own server. And write down the date of each backup, because a backup taken after an attack carries the attack with it.
Step 5: Protect forms and comments from spam
Google’s page on user-generated spam says spammers take advantage of open comment forms. According to the page, even simple deterrents can help. Its suggestions include manually approving suspicious user interactions, adding nofollow or ugc to links in untrusted content, putting repeat sources on a blocklist and using human verification. The same page says that if the site is verified in Search Console, you get email alerts about security issues.
We went into the trade-offs of each form protection in how a contact form should work. The one rule here: do not lock real visitors out while protecting the form. After adding protection, send a message from your own phone.
Step 6: Check security headers with a tool
You can see headers without writing code. A scanning tool will do it; Mozilla’s HTTP Observatory is one of them.
How to use the report is our suggestion. Copy the missing lines to your developer or host support, and write a name and a date next to each. Do not add a header from the report yourself before you know what it does. A rule set up wrongly can quietly break part of the site. After a header is added, try the home page, the form and the payment step by hand. The report is not there to chase a full score but to show the work still open.
Step 7: How Google shows security issues
Google’s Security issues report shows findings when a Google evaluation determines that your site was hacked or behaves in a way that could harm a visitor. According to the report page, affected pages can appear with a warning label in search results, or with an interstitial warning page in the browser. There are three categories: hacked content, malware and unwanted software, and social engineering.
Do not wait to look at the report. Our suggestion is to check the Security issues report and the message panel in Search Console once a week. Google’s page on preventing malware also suggests forwarding messages to your email and running a site: search regularly. If that search shows pages you do not recognise or topics you did not write, you may have been hacked.
The Security issues page has two more warnings. First, many hackers make changes that only Google can see. So open the page in the URL Inspection tool, which shows it as Google sees it; your own browser may not show the change. Second, the fix has to cover the whole site: the page says that fixing only some pages will not earn a partial return to search results.
Step 8: The first hour after a breach
If you think your site has been hacked, do these six things in order. The order is our suggestion; the first-detection date and the review request rest on Google’s Security issues page.
- Take a copy. Keep the damaged site exactly as it is. Do not delete files before you understand what changed.
- Switch to maintenance mode. Restrict public access so visitors are not harmed.
- Change the passwords. Hosting, FTP, the database and every admin account. Delete accounts you do not recognise. Do it from a clean computer.
- Find the way in. An old software version, a plugin or an open directory? The Security issues page names these three routes. Loading a clean backup before the route is closed invites the attack again.
- Load a clean backup. The report shows the date the issue was first detected. Look for a backup from before that date.
- Request the review. When every issue is fixed across the whole site, choose the “Request Review” button in the Security issues report and describe what you did. According to Google, a good request explains the issue, the steps you took and the outcome. A review can take from a few days to a few weeks. Do not resend before you get an answer.
If the problem is beyond your own knowledge, call your host’s support and get help from someone who knows the work. If personal data may have leaked, ask your legal adviser separately about your obligations under KVKK. This is our suggestion.
Common mistakes
- Deleting files blindly after an attack. Cleaning up without knowing what changed destroys the evidence and the answer.
- Restoring the backup without closing the way in. The same hole gives the same result.
- Treating a hacked backup as clean. The backup must be dated before the attack.
- Skipping the warning because you cannot see it in your browser. Google shows warnings by context; go by the report.
- Turning on two-step sign-in for one account and forgetting the rest. Hosting, domain and the admin panel all matter.
- Adding headers once and leaving it. Every new plugin or update can change the settings.
Common questions
How do I know my website has been hacked?
Look at the Security issues report and the message panel in Search Console, and run a site: search on Google. Google says that if you see pages you do not recognise or topics you did not write, you may have been hacked. A customer complaint or a browser warning is also a sign.
Is my site safe if it has an SSL certificate?
No. HTTPS encrypts data in transit. An old plugin, a weak admin password or an open directory is not closed by HTTPS. That is why updates and account checks are separate steps on the list.
Is there a risk in turning on HSTS?
Yes. A browser does not let a visitor click past a certificate error on an HSTS site. If certificate renewal slips, visitors cannot get in. So start with a short period and check that renewal works.
One thing you can do today
Type site:yoursite.com into Google and look at the results: is there a page you do not recognise? Then open the Security issues report in Search Console and look for the green check mark. Finally, turn on two-step sign-in for your hosting account. For building and maintaining your site, see our web and software service; Detmore’s maintenance and performance service covers security patches, and we write the scope in a separate proposal.
Sources
This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 15 November 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.