What happened: Google announced on 28 August 2026 that, from 30 August, manual actions under its site reputation abuse policy are enforced differently depending on where the searcher is. Outside the European Economic Area, “a manual action regarding Google’s site reputation policy will directly affect search results for the portion of the site affected”, as before. Inside the EEA, “the impact of the manual action will not apply. The affected section of the site may be separated in our systems so that, over time, it ranks independently from the rest of the site.” Google says the change follows a European Commission investigation that required it to stop enforcing the policy within the EEA.
This guide covers site reputation abuse eea for SaaS teams: what it means, why it matters, and the practical steps to get it right.
Sources: Google Search Central blog; Search Engine Roundtable.
What site reputation abuse is
The policy, introduced in 2024 and often called “parasite SEO”, targets third-party content published on a strong host site mainly to borrow the host’s ranking signals: coupon sections on news sites, sponsored “best of” listicles on publishers, affiliate reviews on university domains. Google’s enforcement has been through manual actions that remove the offending section from results.
What is different now
| Searcher location | Before 30 August | After 30 August |
|---|---|---|
| EEA (EU countries plus Iceland, Liechtenstein, Norway) | Manual action removes the section from results | No ranking impact from the manual action. The section is separated and ranks on its own signals over time |
| UK | Manual action applies | Unchanged. The UK is not in the EEA |
| US and everywhere else | Manual action applies | Unchanged |
Barry Schwartz called it “the first time Google is applying different rules and outcomes for its spam policies based on the location of the searcher.” Note the second half of Google’s sentence: the separated section ranks independently, which means it also stops inheriting the host’s authority. A parasite page in the EEA is not penalised, but it is not boosted either. The durable route is still content with a named owner and first-hand experience, which is the ground we cover in our guide to E-E-A-T for SaaS sites.
What it means for SaaS sites
Most SaaS marketing sites are not hosts for third-party content, so the direct impact is small. Three situations are worth a look:
- You publish partner or guest content in a section of your domain (a community blog, a partner directory, a marketplace with vendor-written listings). Outside the EEA nothing changed, so keep the editorial control you already have. If a section could be read as existing mainly to rank third-party content, the risk is the same as last month.
- You buy placements on publisher sites to rank for “best X software” queries. Those placements are still subject to manual actions for US, UK and every non-EEA searcher, which is where most SaaS revenue is. Do not read this as a green light. Our link building guide covers what holds up.
- You compete against parasite pages in EEA markets. Expect some of them to come back in results for EU users over the coming months, ranking on their own signals. Watch your EEA rankings separately in your tracker; a mixed global view will hide it.
What to do
- Split rank tracking by country if you sell into the EU. Germany, France and the Netherlands will behave differently from the US and UK for affected queries.
- Audit any section of your site written by third parties against Google’s site reputation policy. Editorial oversight and a clear reason for the content to exist on your domain are what Google looks for.
- Do not change your content strategy for a regional enforcement carve-out. Google’s algorithmic systems for detecting low-value third-party content still run everywhere.
Quick recap: Site reputation abuse eea
Site reputation abuse eea usually comes down to a short, repeatable checklist. Use this whenever site reputation abuse eea comes up again:
- Diagnose site reputation abuse eea by checking the relevant report first, not assumptions.
- Confirm the current setup is actually causing site reputation abuse eea before you change anything.
- Re-check site reputation abuse eea again after the fix ships, not before.
Treat site reputation abuse eea as an ongoing signal rather than a one-time fix. For background on the platform rules behind this, see Google Search Central.
