Poisoned SEO: what SEO poisoning is and how to fix your site


SEO poisoning is when attackers push spam or malicious pages up in search results so people click them. The fastest way to rank those pages is to put them on a site Google already trusts, so most poisoned SEO starts with a hacked business site: thousands of casino, pharmacy or fake-store pages appear under your domain, Google finds them, and your real pages drop.
ℹ️
Seeing wrong rankings in DataForSEO or your rank tracker? That's Google serving fake results pages to scrapers, a different problem. See Poisoned SERPs in DataForSEO.
This guide is for founders and site owners who see strange pages in Google under their domain, a sudden drop in traffic or a warning in Search Console. It covers:
  • The 3 kinds of SEO poisoning
  • How to check if your site is poisoned
  • How to fix a hacked site, step by step
  • How long recovery takes
  • What to do about spam links pointing at you
  • What to do when fake pages rank for your brand
  • How to keep it from happening again

The 3 kinds of SEO poisoning

Kind
What happens
Where you fix it
Hacked content
Attackers add pages, links or redirects to your site to rank their own offers
Your server, then the Security Issues report in Search Console
Brand impersonation
Fake sites rank for "\[your brand\] login", "support" or "download" and phish your customers
Abuse reports to Google, the registrar and the host, plus your own pages
Spam links (negative SEO)
Someone points thousands of junk links at your site
Usually nothing; disavow only after a manual action
Google's spam policies treat hacked content as a violation even though you didn't add it: "Sites that violate our policies may rank lower in results or not appear in results at all." So a hack you didn't notice still costs you rankings.

How to check if your site is poisoned

Do these 7 checks. One hit is enough to start the cleanup.
  • Search your own domain. Run site:yoursite.com and flip through a few pages of results. Then add spam words: site:yoursite.com casino, site:yoursite.com viagra, site:yoursite.com replica. Titles in Japanese, Indonesian ("Situs Toto", "slot gacor") or Chinese on an English site are the most common sign.
  • Open the Security Issues report. In Search Console, go to Security & Manual Actions → Security issues. "Hacked: URL injection" means Google found pages an attacker created. Also open Manual actions next to it.
  • Compare indexed pages to real pages. In Indexing → Pages, the number of indexed pages should be close to the number of pages you published. A site with 300 pages and 40,000 indexed URLs has been injected.
  • Read your search queries. In Performance, sort queries by impressions. Queries for products or topics you never wrote about point to injected pages.
  • Check owners and sitemaps. In Settings → Users and permissions, look for owners you don't know. In Sitemaps, look for sitemaps you didn't submit. Attackers add both so they can push their pages into the index.
  • Look at your site the way Google does. Many hacks only show spam to search bots, so your site looks normal in the browser. Run curl -A "Googlebot" https://yoursite.com/ and compare it with what you see, or use URL Inspection → Test live URL → View tested page.
  • Click your own results from Google. Some hacks redirect only visitors who arrive from a search engine, so typing the URL directly shows nothing wrong.
ℹ️
Cloaked hacks are easy to miss. In a January 2026 case documented by Sucuri, visitors saw a normal site with "No popups. No redirects. No visible spam." Code added to one PHP file checked for Googlebot, Bingbot and Baiduspider, pulled gambling spam from a remote domain and showed it to the bots only. The owner noticed because Google's results for the site filled with "Situs Toto" pages.

How to fix a hacked site, step by step

Work through these in order. Skipping the first 3 is how sites get cleaned and hacked again the same week.

1. Back up everything first

Copy the files and export the database before you delete anything. You need the infected copy to find how the attacker got in, and a way back if a cleanup step breaks the site.

2. Lock the attacker out

  • Remove Search Console owners you don't know. Then remove their verification token: a google[random].html file in your site root, or a rewrite rule in .htaccess that answers any google*.html request. Open yoursite.com/google123abc.html: if it returns anything but a 404, the token is still there.
  • Change every password: hosting panel, SFTP and SSH, database, every CMS admin, and API keys stored in your config.
  • Delete admin users you didn't create and turn on 2-factor sign-in for the rest.

3. Find and remove the injected code

  • Replace .htaccess with a clean default. If you never wrote one and one exists, it's probably the attacker's.
  • Sort files by last modified date. Files changed on a day nobody deployed are your first suspects. Attackers often edit index.php, wp-load.php, 404.php and theme files.
  • Search the code for obfuscation: base64_decode, eval, gzinflate, str_rot13, strrev. A long unreadable string passed to one of these is almost always malicious.
  • Reinstall the CMS core, plugins and themes from official sources, and delete the ones you don't use. Reinstalling overwrites customizations, so keep those in your backup.
  • Check the database. On WordPress, look for spam in wp_posts and for unknown scripts or URLs in wp_options.
On a static or custom site, check the build pipeline too: compromised CI tokens, a changed dependency, or a writable storage bucket the site serves files from.

4. Clean your sitemaps

Remove spam URLs from your sitemaps and delete any sitemap that contains only spam. Then resubmit the clean sitemap in Search Console and in Bing Webmaster Tools.

5. Make the spam URLs return 410

Every injected URL should return 410 Gone (or 404). That tells Google the page is deleted on purpose, and it drops the URL faster. If the spam lives under a pattern like /?id= or /shop-xyz/, one server rule covers all of it.
  • Don't redirect spam URLs to your homepage. Google treats mass redirects to an unrelated page as soft 404s and keeps crawling them.
  • Don't block the spam URLs in robots.txt. Google then can't see the 410 and keeps the old pages in the index.
  • Hide the worst ones right away with Indexing → Removals in Search Console. It hides a URL for about 6 months, so use it for the pages people are actually seeing, not as the fix.
  • Ping Bing and other engines with IndexNow for the removed URLs, so they recrawl them now instead of in a few weeks.

6. Close the hole

Find how they got in, or they'll be back. The usual causes: an outdated plugin or theme, a leaked admin password, a file upload form that accepts PHP, an old staging copy on the same server. Update everything, remove what you don't use, and put a web application firewall in front of the site (Cloudflare's free plan covers most small sites).
Google's own guide on fixing the Japanese keyword hack cites a study where 20% of hacked sites were hacked again within 1 day.

7. Ask Google to review the site

When the Security Issues report lists problems, open it and select Request Review, but only once every issue is fixed on every page. Google's Security Issues help is direct about it: "Fixing the issue on just some pages will not earn you a partial return to search results."
In the request, write 3 things: what the problem was, what you did to fix it, and what the result is (for example, "the 38,000 injected URLs now return 410, verified with URL Inspection"). Google emails you when it gets the request and again when the review is done. Reviews take from a few days to a few weeks. A request sent before the site is clean slows the next review and can get the site marked as a repeat offender.

How long recovery takes

The spam leaves the index in days to weeks. Rankings take longer.
In an August 2025 case, a site with 210,000 injected fake product pages dropped from 2,000+ daily visits to about 1,100 in 2 weeks. 2 weeks after the cleanup, traffic still hadn't come back. John Mueller, Search Advocate at Google, replied that "these kinds of hacks can take a bit of time to settle back down."
To speed it up:
  • Check site:yoursite.com and the Pages report weekly until indexed pages match your real count.
  • Request indexing in URL Inspection for your 10-20 most important pages.
  • Publish or update a few real pages, so Google has fresh reasons to crawl you.

What to do about spam links pointing at you

Thousands of junk links from sites you've never heard of look scary, but Google ignores most of them. Its disavow help page says: "In most cases, Google can assess which links to trust without additional guidance."
Disavow only when both are true:
  • You have a considerable number of spammy, artificial or low-quality links pointing to your site
  • They caused a manual action, or likely will
How to do it when you need to:
  • Check Manual actions first. No "Unnatural links to your site" action means you probably don't need to do anything.
  • Write a .txt file with one domain per line, prefixed with domain: (for example, domain:spam-links.example). Up to 100,000 lines and 2 MB.
  • Upload it in the disavow tool for a URL-prefix property. It doesn't work with Domain properties. Google takes a few weeks to apply it.
Don't pay anyone to clean "toxic links" by a score from an SEO tool. Google has no "toxic" label, and disavowing good links by mistake can hurt your rankings.

What to do when fake pages rank for your brand

This kind of poisoning hurts your customers before it hurts your rankings: a fake "support" page with a scam phone number, a look-alike download page with malware, a phishing copy of your login.
  • Search your brand with buyer words: "\[brand\] login", "\[brand\] support phone number", "\[brand\] download", "\[brand\] pricing". Ask ChatGPT and Google AI Mode the same questions, since AI answers can quote fake pages too.
  • Own those results. Publish a real page for each one: a support page with your official contacts, a download page, a login link, a pricing page. When your page ranks first for "\[brand\] support", a fake page has less room.
  • Send abuse reports to the fake site's registrar and host. Find them with a WHOIS lookup. Quote your trademark and attach screenshots.
  • Buy the obvious look-alike domains before someone else does: common typos and your name with -login, -support or -app.

How to keep it from happening again

  • Turn on Search Console emails and add a second owner, so a security warning doesn't sit unread in one inbox.
  • Auto-update the CMS and plugins, and delete plugins and themes you don't use.
  • Use 2-factor sign-in for hosting, the CMS, the registrar and Search Console.
  • Give people the least access they need. A writer doesn't need admin rights.
  • Keep daily backups off the server, so a hack can't delete them.
  • Check site:yoursite.com once a month and compare indexed pages with your real count.
  • Watch for new files. A file change alert from your host or a security plugin catches injections the day they happen.
⚠️
Skip: redirecting spam URLs to the homepage, blocking them in robots.txt, asking for review before every page is clean, and paying for "toxic link" removal without a manual action.

Ship faster than
your competition

Focus on customers and sales while we handle product delivery. Hire a dedicated AI maker or a whole product team.

Launch new products
Fix your delivery
Hit fundraising milestones
[Analytics Chart]
Wireframe v0.1
User
Sarah Chen CEO, Founder
$127k
MRR
2,847
Customers
+23%
Growth
Sales Performance
Latest Deal
Customer
Enterprise plan closed
Acme Corp · $12k/mo
© 2026 Paralect, Inc 651 N Broad St, Suite 206, Middletown, 19709, Delaware, United States