If Google shows pages on your domain that you never created (often in Japanese, or selling medicines, gambling or knock-off goods), your site has very likely been hacked. Confirm it in Search Console, change your passwords, get the site properly cleaned and the security hole fixed, then ask Google to review it. If customer details may have been exposed, check whether Singapore's breach-notification rules apply. It's fixable, but a half-clean usually means it comes back.
Signs your site may have been hacked
Any one of these is worth investigating today:
- Searching
site:yourdomain.comin Google shows pages you don't recognise, often with foreign-language or spammy titles. - Google shows "This site may be hacked" under your listing, or Chrome shows a red warning page.
- Search Console emails you about security issues, or the Security issues report shows problems.
- New owners or users you didn't add appear in Search Console.
- Your sitemap contains URLs you've never seen, or there's a sitemap you didn't submit.
- Visitors from Google are redirected to another site, but the page looks normal when you type the address in yourself.
That last one catches people out. Hacks often show spam only to Google or to visitors arriving from search. Google's guide to fixing the Japanese keyword hack (checked 7 November 2026) warns: "Hackers will try to trick you into thinking the page is gone or fixed when it's still hacked."
Confirm it in ten minutes
- Search
site:yourdomain.comand scroll through several pages of results. - Open Search Console → Security & manual actions → Security issues. The Security issues report shows hacked content, malware and social engineering (phishing) that Google has found. A green tick means nothing is listed.
- Check Settings → Users and permissions. Remove anyone you don't recognise only after you've noted who they are (screenshot it).
- Check Sitemaps. Note any sitemap you didn't submit.
- Use URL Inspection on a suspicious URL to see what Google actually fetched, since that may differ from what you see in your browser.
If you don't have Search Console set up, ask whoever built or hosts your site to check with you.
The first hour: contain it, don't panic-delete
- Back up first. Copy the site files and database before anyone deletes anything. You'll want them to find out what happened.
- Change every password: website admin, hosting, FTP/SFTP, database, domain registrar and the email accounts linked to them. Turn on two-factor sign-in wherever it's offered.
- Tell your host and your web developer. Many hosts have a security process and can help identify the infected files.
- Don't just delete the spam pages you can see. If the hole is still open, they'll be back, sometimes within hours. Google's guide cites research that a fifth of hacked sites are re-hacked within a day.
Cleaning up: what has to happen
This part is usually technical, and it's reasonable to get help. Whoever does it should, at a minimum:
- Remove unknown Search Console owners and any verification files or rules the attacker added.
- Replace tampered system files (for example, reinstalling the CMS core, themes and plugins from clean copies) and check server files such as
.htaccess. - Search for injected code, especially recently changed or unusual files.
- Clean or remove spammy sitemaps.
- Fix the way in. Common causes are outdated plugins or themes, weak or reused passwords, and abandoned admin accounts. Cleaning without fixing the cause is the most common reason hacks return.
- Make sure the spam URLs now return "not found" (a 404 or 410), not a redirect to your homepage.
Google's hacked-site guidance walks a developer through each of these.
Asking Google to review your site
Only once the whole site is clean. The Security issues report notes that fixing only some pages won't earn a partial return.
- In the Security issues report, select Request review.
- Explain what happened, what you fixed, and how you checked it.
- Wait. Don't resubmit while a review is pending; Google says that can slow things down.
Google's request-a-review guide (checked 7 November 2026) gives typical timings: hacked-with-spam reviews "can require up to several weeks", malware reviews "a few days", and phishing about a day. Once Google confirms the site is clean, warnings are removed within about 72 hours.
Spam pages can linger in search results for a while after the review. Because they now return "not found", they should drop out as Google recrawls them. (Our guide to whether your page is indexed explains how to check individual URLs.)
If customer information may have been exposed
Many small-business sites collect personal data through enquiry forms, bookings or accounts. If the attacker could have accessed it, Singapore's PDPA may require more than a clean-up.
According to the PDPC's guide on managing and notifying data breaches (checked 7 November 2026):
- You must take "reasonable and expeditious steps" to assess whether a breach is notifiable, within 30 calendar days of having credible grounds to believe it happened.
- A breach is notifiable if it's likely to cause significant harm to the people affected, or involves the personal data of 500 or more individuals.
- If it is notifiable, you must tell the PDPC "as soon as practicable, but in any case, no later than three (3) calendar days" after deciding so, and, where required, the affected individuals.
Breaches are reported through the PDPC's data breach e-service. We're not lawyers; if you're unsure whether your situation is notifiable, get advice quickly, as the clock matters.
Reporting the incident
Singapore's computer emergency response team, SingCERT, takes reports on incidents based in Singapore through its Cyber Aid tool, and can help identify the issue and suggest how to resolve it. Its page also notes that cybercrime is a criminal offence and suggests lodging a police report if you believe your business was a victim.
Making it less likely to happen again
- Keep your CMS, theme and plugins updated, and remove ones you don't use.
- Use unique passwords and two-factor sign-in for every account that can change the site.
- Remove old admin users, such as former staff or past freelancers.
- Keep regular backups stored somewhere other than your web server.
- Check the Security issues report and a
site:search once a month. It takes two minutes.
What's in your control, and what isn't
In your control: how quickly you spot it, how thoroughly the site is cleaned, whether the way in is closed, and whether you meet any notification duties.
Not in your control: how long Google's review takes, how quickly spam URLs drop out of results, and how long any traffic dip lasts. Nobody can guarantee rankings return exactly as before.