Hacked website Google results usually show spam titles, foreign text or a “This site may be hacked” warning under your listing. That means the hack is still active or its leftovers are still indexed. It’s stressful, but it can be cleaned up, and Google can lift the warning once you show it’s fixed.
The most likely cause is an outdated plugin, theme or weak password that let someone add spam pages to your site. The first thing to check is the Security issues report in Search Console and the list of users with access to your site. This guide covers a five-minute check, the common hack types in order, how to clean up Google’s results, and when to call an expert.
Check this first
Don’t delete anything yet. These five checks show how bad the damage is and stop you destroying evidence your developer may need.
- Search for spam pages. Type site:yourdomain.com.au into Google and scroll. Look for titles about pills, casinos, replica goods or Japanese text that you didn’t write.
- Open Security issues. In Search Console, go to Security & Manual Actions > Security issues. Note any issue and the sample web addresses listed.
- Check who has access. In Search Console, open Settings > Users and permissions. Remove any owner you don’t recognise. Do the same for your website’s admin users.
- Visit from a phone. Open your site from a Google search on mobile data. Some hacks only redirect visitors who arrive from Google.
- Write it down. Screenshot the spam results and note the date. You’ll need this for the review request.
Still seeing spam in your hacked website Google results after these checks? Get a free consultation and we’ll find the cause.
Why hacked website Google results happen and how to fix them
Google’s Help, I think I’ve been hacked guide lists the common hack types and recovery steps. Here they are in order of how often small business sites see them.
1. Spam pages added to your site
How to tell: Google shows pages on your domain you never created, often in Japanese or full of product names. This is known as the Japanese keyword hack or the gibberish hack.
- Ask your developer or host to take a full backup of the hacked site for evidence.
- Find how the pages are being created. They are often generated by a hidden file, not saved as normal pages.
- Remove the hidden files and any spam pages so those addresses return a “not found” (404) or “gone” (410) error.
- Remove any sitemap the hacker added, the file that lists pages for Google.
2. An outdated plugin or theme let them in
How to tell: your WordPress dashboard shows plugins or themes needing updates, or plugins you don’t recognise. Patchstack found 96% of new WordPress vulnerabilities in 2024 were in plugins.
- Update WordPress, every plugin and your theme.
- Delete plugins and themes you don’t use. Deactivated plugins can still be attacked.
- Replace any plugin that’s no longer maintained.
3. Hidden redirects to spam sites
How to tell: visitors from Google land on a different site, but you see your normal site when you type the address in. This is called cloaking, showing Google or searchers something different from what you see.
- Ask your developer to check the .htaccess file and the top of your theme files for redirect code.
- In Search Console, use URL Inspection and click View tested page to see what Google sees.
4. Stolen passwords or a rogue user
How to tell: unknown admin users on your site, or an unknown owner in Search Console.
- Change passwords for WordPress, hosting, FTP and your database.
- Turn on two-step login for every admin account.
- Remove unknown users from your site and from Search Console.
Warning: don’t change your domain’s DNS settings, move hosts or restore old backups without help. A wrong step can bring the hack back or take your email offline. Get help first if you’re unsure.
5. Malware on the site
How to tell: browsers show a red warning page, or Security issues lists malware. This needs a professional clean, not just a plugin scan.
- Ask your host for a malware scan and clean.
- Once clean, follow Google’s Security issues report steps and click Request Review, explaining what you fixed.
Once the site is clean, keep it that way. Turn on automatic updates for minor WordPress releases, check for plugin updates weekly, and keep at least one recent backup stored away from your hosting account. Ask your host whether they run a firewall and regular malware scans. These steps cost little and close the doors most hackers use.
Australian businesses can also report a cyber attack through ReportCyber on the Australian Signals Directorate’s cyber.gov.au website.
Hacked website causes at a glance
Use this table to match what you see with the likely cause and fix.
| Cause | Sign | Fix | Time to show |
|---|---|---|---|
| Spam pages added | Foreign or product titles in results | Remove files, return 404 or 410 | Weeks as Google recrawls |
| Outdated plugin or theme | Pending updates, unknown plugins | Update, delete unused, replace | Immediate protection |
| Hidden redirects | Google visitors sent elsewhere | Remove redirect code | Days to weeks |
| Stolen passwords | Unknown users or owners | Reset passwords, two-step login | Immediate protection |
| Malware | Browser warnings, security issue | Professional clean, request review | Several days to a few weeks |
Statistics: 7,966 new vulnerabilities were found in the WordPress ecosystem in 2024, 96% of them in plugins. Source: Patchstack, State of WordPress Security in 2025. The average self-reported cost of cybercrime for an Australian small business was $56,600 in 2024 to 2025. Source: ASD Annual Cyber Threat Report 2024 to 2025 factsheet.
How to check the fix worked
Start with Search Console. In Security issues, the review result arrives by email, and Google says most reviews take several days to a few weeks. Then open Indexing > Pages and watch the spam addresses move to Not found (404). Those website errors are a good sign here, because they show the spam pages are gone.
Also check the Indexing > Sitemaps report. If a sitemap you didn’t add is listed, select it and remove it so Google stops being pointed at spam addresses. Then resubmit your real sitemap.
If spam pages are still showing after the clean, use Indexing > Removals > New request to hide the worst ones for about six months while Google recrawls. Keep searching site:yourdomain.com.au weekly. Picture a South Yarra beauty salon whose results showed replica handbag pages. After the clean and a review request, the warning lifted and the spam titles faded from results over the following weeks.
Want to see what a clean recovery looks like for other Melbourne businesses? See our results.
When to get help
Get expert help if spam pages come back after you clean them, if Google’s review is rejected, if you see malware warnings, or if there’s a manual action for spam. Those signs usually mean a back door is still open. If your site disappeared from Google completely, read our guide to a site that disappeared from Google overnight. Our guide to the biggest SEO mistakes Melbourne small businesses make also covers site upkeep. Technical SEO cleanups are part of our SEO services, and our process starts with a free audit.
If spam keeps reappearing in your hacked website Google results, it’s time for a second pair of eyes. Get your free consultation. No lock-in contracts.
Hacked website Google results FAQs
How long until spam disappears from Google?
Usually a few weeks after the clean, as Google recrawls each address. The Removals tool can hide the worst pages sooner. There’s no fixed timeline.
Will my rankings recover after a hack?
Often, once the site is clean and Google has rechecked it. Recovery depends on how long the hack was live and how much spam was indexed. Sites cleaned within days usually bounce back faster than sites that carried spam for months.
Should I delete my website and start again?
No. A new site on the same hosting can be hacked the same way. Find the entry point, clean it and keep your existing pages and links.
Does a hack slow down my site?
It can. Hidden spam code and malware often hurt site speed and use up server resources. More answers are on our FAQ and blog.
