Thursday, September 3, 2026
Always Evolving SEO
Google Updates

Google Splits Site Reputation Enforcement: EEA Searchers Won't See the Manual Action

By Paul Lovell · September 3, 2026 · 5 min read

Google updated its site reputation policy on August 28, 2026, changing how the policy is enforced for people searching inside the European Economic Area. The change took effect on August 30.

The headline reading is that the EEA gets a softer deal. The mechanism Google describes suggests something closer to the opposite.

What changed

The site reputation policy itself is unchanged — it still targets the practice of publishing third-party content on a trusted site purely to exploit that site's reputation for ranking. What changed is what a manual action does, and it now depends on where the searcher is:

Outside the EEA. A manual action under the policy directly affects search results for the affected portion of the site. The rest of the site is unaffected. This is the behaviour that already existed.

Inside the EEA. The impact of the manual action does not apply. Instead, in Google's words, the affected section "may be separated in our systems so that, over time, it ranks independently from the rest of the site."

Google says the adjustment follows discussion with the European Commission, and that it is also "clarifying the criteria we consider when applying the policy" — though the post does not spell out what those clarified criteria are. That is worth flagging rather than glossing: the criteria change is announced, not explained.

The line worth reading twice

Separating a section so that it ranks independently is not an exemption. It is a description of removing exactly the thing parasite SEO exists to borrow.

The entire premise of site reputation abuse is that a subfolder or subdomain inherits the host domain's accumulated authority — that trustednewspaper.com/casino-reviews ranks on the strength of the newspaper, not the reviews. If Google separates that section in its systems so it ranks on its own merits, the borrowed authority is gone. The section is not penalised; it is simply made to stand on its own.

For a site whose third-party section was genuinely parasitic, those two outcomes may not feel very different. For a site whose section was decent but got caught by an overbroad application of the policy, the EEA treatment is arguably fairer: it removes the unearned advantage without suppressing the content.

Google is explicit that it still has reservations about the wider context, saying it remains concerned that "an overbroad application of the DMA could prevent us from addressing real threats to the integrity of our search results."

The reporting problem this creates

Here is the practical consequence most site owners will hit before they hit anything else.

Google notes that because many pages are viewed globally, "it's possible that any given page might have a manual action taken on it, but that change will only affect search results shown to users outside the EEA."

So the manual action and its visible effect have come apart:

  • You will still be notified in Search Console when a manual action is applied. That has not changed.
  • But if you are sitting in the EEA checking your own rankings, you may see no impact at all — while the same page is demoted for everyone outside it.
  • A single Search Console notification now describes two different realities depending on the searcher's location.

If you manage a site with a significant third-party or partner content section and traffic on both sides of that boundary, segment your Search Console performance data by country before concluding anything about whether an action has bitten. A blended line will average the two behaviours together and tell you very little.

What to do

  1. Check Search Console's Manual Actions report first, not your rankings. The notification is now the only reliable signal that an action exists — the ranking impact is location-dependent and may be invisible to you.
  2. Segment performance data by country. EEA versus non-EEA is the split that matters now. If you only look at totals, a manual action affecting the majority of your non-EEA traffic can hide behind flat EEA numbers.
  3. If you believe an action was applied in error, the escalation path has grown. You can submit a reconsideration request as before. Eligible sites can then also bring disputes to mediation under the Google Search Mediation Scheme. That second route is new in this announcement and easy to miss.
  4. Don't read the EEA treatment as permission. Ranking independently of the host domain is the outcome parasite SEO is designed to avoid. If your third-party section could not survive without the main domain's authority behind it, the EEA approach removes precisely that support.

What this doesn't change

The policy's scope, the definition of site reputation abuse, and the notification process are all unchanged. This is an enforcement-mechanism change in one region, not a rewrite of the rules. Sites outside the EEA should expect the policy to behave exactly as it did before August 30.

Google's June 2026 spam update explicitly did not target the site reputation abuse policy, so if you are trying to date a movement in your own data, these are two separate threads — don't merge them.

Sources

More in Google Updates