A customer calls: "Your website redirects me to some strange page." Or Google shows "This site may be hacked" in the search results. Or the host has suspended the site because it is sending spam. At that moment what counts is not blame but sequence. Use the first hours correctly and you have the website back clean in one or two days. Start wrong and you lose data, rankings and time.
This article is the checklist we use ourselves when a Swiss SME comes to us with a hacked website: recognising symptoms, the first 60 minutes, step-by-step clean-up, Google's all-clear, the duties under the revised Swiss Data Protection Act and the prevention so it does not happen again.
Emergency? Send us your website address and a phone number. We get back to you the same working day, secure the site and tell you what to do. Report an emergency →
How to recognise that your website has been hacked
| Symptom | What is behind it |
|---|---|
| Google warning "This site may be hacked" or a red warning page in the browser | Google Safe Browsing has found malicious code or spam pages |
| Redirects to gambling, pharma or dating sites, often only on mobile or from Google search | Injected JavaScript or manipulated .htaccess |
| Foreign pages in the Google index, for example Japanese or pharmaceutical terms under your domain | SEO spam hack, thousands of generated pages |
| Email from the host about spam sending, phishing pages or high server load | The website is being abused as a spam relay or phishing host |
| New administrators or plugins nobody installed | Attacker has admin access |
| Changed homepage or political messages | Defacement, usually automated |
| Antivirus warning on visiting, customers report virus alerts | Malicious code is being served to visitors |
| Suddenly slow, high CPU load, full storage | Crypto mining or spam sending in the background |
The first 60 minutes
- Stay calm and document. Screenshots of warnings, redirects and error messages with timestamps. You need them for the host, insurance and possibly the authorities.
- Take the website offline. Maintenance mode with password protection via the hosting panel, or temporarily redirect the site to a static notice page. Protecting visitors comes before revenue.
- Change all passwords, in this order: hosting panel, SFTP, database, WordPress administrators, mail accounts of the domain. New, long, unique passwords everywhere, enable two-factor authentication wherever possible.
- Secure the backup state, do not overwrite it. Download the current infected state and the last clean backups. Otherwise automatic backups overwrite the last clean state within two days.
- Inform the host. Swiss hosts help with analysis, show logs and lift suspensions as soon as the site is clean.
- Check access. Deactivate unknown admin users, end active sessions, check password reset emails to foreign addresses.
- Check your own devices. If the admin password was stolen, an infected computer is often the source. Virus scan on all devices with access.
Clean-up in 7 steps
The rule of thumb: do not patch, rebuild. Hunting infected files one by one takes longer and almost always misses a backdoor.
- Find a clean backup state. Narrow down the time of infection using host logs and file dates. The last backup before that is the basis for database and uploads.
- Reinstall WordPress core, theme and plugins fresh. All code files come new from wordpress.org and the vendors' sites, not from the backup. Outdated plugins are updated or removed in the process.
- Scan the uploads folder. Only images and documents belong in wp-content/uploads. Any PHP file there is malicious code. The same applies to hidden files starting with a dot.
- Check the database. Table wp_options for foreign siteurl, home and injected scripts, wp_users for unknown accounts, posts and pages for inserted JavaScript or iframes.
- Renew the configuration. Check wp-config.php for foreign lines, regenerate security keys, replace .htaccess with the default version, set file permissions (folders 755, files 644, wp-config 600).
- Scan completely. Run Wordfence, Sucuri or MalCare over the cleaned installation, plus the host's scanner. Only go back online at zero findings.
- Close the gap. Without this step the website is infected again in two weeks. The most common entry points: outdated plugins and themes, weak or reused passwords, pirated "nulled" themes, open file permissions, an infected workstation.
Clearing Google and mail blocklists
- Google Search Console: request a review under "Security issues" as soon as the site is clean. The warning usually disappears within one to three days.
- Remove spam URLs: the foreign pages now return 404 or 410. The "Removals" tool in Search Console can take hundreds of URLs out of the index at once.
- Browser warnings: Google Safe Browsing updates itself after the review; Microsoft SmartScreen and antivirus vendors have their own reporting forms.
- Mail blocklists: if spam was sent, the server IP or domain is on lists such as Spamhaus. Check via mxtoolbox.com and request removal from the list operator so your normal emails arrive again. While you are at it, check that SPF, DKIM and DMARC are set correctly.
Duties in Switzerland: FADP and reporting
The revised Data Protection Act has applied since September 2023. For a hacked website this means:
- Reporting duty to the FDPIC: Under Article 24 FADP you must report a data security breach to the Federal Data Protection and Information Commissioner as soon as possible if it is likely to result in a high risk for the data subjects. That is typically the case if customer data, logins, health data or payment data may have leaked. A website with a plain contact form and no data storage usually does not fall under this; a shop or customer portal very much does.
- Informing the data subjects if necessary for their protection or if the FDPIC requires it, for example so customers change passwords.
- Documentation: what happened when, which data was affected, what was done. Even if no report is required, this belongs in the records.
- Voluntary report to the National Cyber Security Centre (NCSC/BACS): via its reporting form, helps the national situation picture and is not mandatory for SMEs.
- Criminal complaint with the cantonal police is possible and often a prerequisite for insurance claims.
Prevention: what a website needs in 2026
| Measure | Effort | Impact |
|---|---|---|
| Weekly updates for core, themes and plugins, critical ones immediately | 15 minutes per week or automated | Closes the most common entry point |
| Two-factor authentication for all administrators | 10 minutes once | Makes stolen passwords worthless |
| Daily off-server backups with 30 days of history | Set up once | Fast, clean recovery |
| Minimise plugins, only from official sources, no nulled themes | Ongoing | Smaller attack surface |
| Web application firewall (Cloudflare or Wordfence) | 1 hour | Blocks known attacks before the website |
| Login protection: limit attempts, disable XML-RPC, admin username not "admin" | 30 minutes | Stops brute force |
| File permissions and block PHP execution in uploads | 30 minutes | Prevents reloading of malicious code |
| Monitoring: availability, file changes, malware scan, blocklists | Set up once | You find out before your customers do |
| Maintenance contract with all of this in one package | Fixed monthly | Someone is responsible |
What the clean-up costs
Done yourself: one to two days if you handle WordPress, SFTP and databases confidently. As a service including analysis, rebuild, scan, hardening and Google clearance usually CHF 500 to 2,500, more for shops with lots of data. For outdated systems that have not been maintained for years, a rebuild is often cheaper than a rescue, and afterwards the site runs fast again too.
Don't want to wait until it happens? We check your website for open vulnerabilities, outdated components and missing backups and deliver an action plan with a fixed price. Request a security check →
Frequently asked questions
Is restoring the backup enough?
No. The backup contains the same vulnerability the attacker came through, and often the backdoor already. Use the backup for data, install code fresh, close the gap.
How long does the clean-up take?
For a normal SME website one to two working days including the Google review. Shops with many orders and customer data take longer because the database has to be checked more carefully.
Do I have to inform my customers?
If customer data may be affected and this creates a high risk, yes, after consulting the FDPIC or a lawyer. For a plain company website without stored personal data usually not, but document the incident.
How long does the Google warning stay?
After a successful review in Search Console usually one to three days. Spam pages in the index disappear within weeks, faster with the Removals tool.
Was the host to blame?
Rarely. In over 90 percent of the cases we see, the cause was an outdated plugin or theme or a weak password on the website itself, not the server.
Conclusion: sequence saves websites
A hacked website is unpleasant but not the end if you act in the right order: take it offline, change passwords, secure backups, rebuild instead of patching, close the gap, clear Google, check your duties. And then make sure that updates, backups and two-factor authentication no longer depend on chance.
We clean hacked websites for Swiss SMEs at a fixed price and afterwards, on request, take over updates, backups, monitoring and security checks in a maintenance package.
Is your website affected, or do you want to make sure it never is? Write to us and we will get back to you promptly. Get in touch →
Further reading
security, hacked, wordpress, malware, revdsg, fdpic, backup, website help

