Business Website Hacked? Warning Signs and a Recovery Plan
How to recognise a hacked business website, what to do in the first hour, how to restore it from a clean backup, and how to clean up the damage in Google.
Baca dalam Bahasa Indonesia
Most business owners think about website security only after something happens: a customer reports a browser warning, search results show pages nobody on your team created, or the site simply will not open. At that point you do not need theory. You need a clear order of steps.
This article covers what happens after a gap has been exploited: how to recognise the signs, what to do in the first hour, how to restore the site, and how to clean up the damage in Google. For prevention, read why a secure digital foundation matters for your business website. No site can be guaranteed 100% immune, so a recovery plan matters as much as prevention.
Signs your website may have been hacked
None of these proves a hack on its own, but each deserves a quick check.
| Sign | What it may mean | Check this first |
|---|---|---|
| The browser shows a warning when the site opens | A certificate problem, or the site has been flagged for harmful content | Open it from another device and read the warning itself |
| Search results show pages or titles you did not create, often about gambling or pills | Spam pages have been injected into the site | Search for your domain name in Google and look at what appears |
| Visitors are sent to another site, especially from search results or on phones | Redirect code has been planted | Open the site on a phone by clicking through from search rather than typing the address |
| Admin accounts or changes you do not recognise | Access has been taken over | The user list in the admin panel and the login history in hosting |
| The site suddenly becomes very slow or unreachable | The server is loaded by unfamiliar activity, or the host suspended the account | Notices and emails from your hosting provider |
| Email from your domain lands in spam, or customers receive messages you never sent | The domain or server is being used to send spam | Warnings from your email and hosting providers |
The first hour
This order is designed so the damage does not grow and the evidence does not disappear.
- Record and keep evidence. Take screenshots, note the time, and keep the pages or messages you can see.
- Do not wipe straight away. Ask your host to keep a copy of the current state before anything is cleaned. That copy helps find the original gap.
- Change passwords. Start with hosting, the website admin panel, the database, and related email accounts. Do it from a device you trust to be clean.
- Limit the exposure. If you can, switch on a maintenance page so visitors do not see harmful content while recovery is under way.
- Contact your hosting provider. They can read server logs and can often help isolate the problem.
- Decide who leads. One person coordinating the steps and the communication stops people undoing each other's work.
Restoring the website properly
Deleting the files that look suspicious is rarely enough. Attackers usually leave more than one way back in.
- Choose a backup from before the incident. If you do not know when the attacker got in, start with an older copy that is still clean and inspect it.
- Restore to a separate environment first when you can, and check it before it goes live.
- Apply every update to the system, theme, and plugins before the site reopens.
- Review accounts and access. Remove admin accounts you do not recognise and revoke access that is no longer needed.
- Find the cause. If the original gap stays open, it can happen again.
- Watch the site for a few weeks to be sure no pages or redirects reappear.
If you are not sure of the cause, or you have no clean backup, it is safer to ask a professional than to restore halfway.
Cleaning up in Google and browsers
- Open the Security issues report in Google Search Console. It is explained in the Search Console Help page on the Security issues report.
- Remove the spam pages completely, and make sure those addresses no longer return harmful content.
- Once the site is clean, request a review in Search Console if a security warning was recorded.
- Check your sitemap again so it lists only pages that really belong to you.
Telling customers and others
If customer data may have been exposed, tell the people affected in plain language: what happened, what data may be involved, what you have done, and what they should do, such as changing a password. Notification duties differ by country and situation, so speak to legal counsel when personal data is involved.
The most common causes and how to prevent them
| Common cause | How to prevent it |
|---|---|
| A system, theme, or plugin that has not been updated for a long time | Schedule regular updates and remove plugins you do not use |
| Weak or reused passwords | Unique passwords, a password manager, and two-step verification |
| Access left open for a former vendor or employee | Review the account list regularly and keep one account per person |
| Neglected hosting or loose configuration | A supported PHP version, sensible file permissions, and sensitive files not reachable from the public web |
| No backup that can actually be restored | Automatic backups stored separately, and restore tests on a schedule |
Recovery plan checklist
- Your hosting provider's and developer's contact details are stored where you can find them quickly.
- You know where the latest backup is and have tried restoring it.
- Access to hosting, the domain, and the admin panel is recorded and held by the right people.
- One person leads when an incident happens.
- A short message for customers has been thought through, not written in a panic.
Frequently asked questions
Will a hacked website always lose its rankings?
Not always. The impact is felt when Google flags the site for harmful content, or spam pages get indexed. The faster the site is cleaned and a review is requested, the smaller the impact tends to be.
Can I recover the site myself?
For a simple case with a clean backup, often yes. If you are unsure where the problem came from, ask for help, because restoring without closing the gap only postpones the next incident.
How long does recovery usually take?
It depends on whether a clean backup exists, how widely the site was affected, and how quickly the cause is found. Ask for an estimate broken down by stage rather than a single number with no explanation.
Next steps
Today, write down three things: who you would call if the site had a problem, where the latest backup is stored, and who has access. If you would like us to look after it, see our security and backup and website maintenance packages.
Talk to Codwa Studio about your website's security
Reviewed by Riki Siahaan. Published: November 9, 2026.
Reviewed by Riki Siahaan Founder · Full-Stack Web Developer
Codwa Studio service
Company Profile Website
A professional website to strengthen your business credibility.
Learn moreFree Codwa tools


