Site reputation abuse policy in the EEA from 30 August 2026

#What changes on 30 August and for whom

Start with the searcher, not the server. A London reader and a New York reader can open the same URL and see different outcomes after a site reputation policy manual action, because Google keys the remedy to searcher location.

Google’s Search Central Blog (28 August 2026) states the split in plain terms:

Beginning August 30, manual actions applied under our site reputation policy will have a different effect for those searching in the EEA than outside of it.

Outside the EEA:

For users outside the EEA, a manual action regarding our site reputation policy will directly affect search results for the portion of the site affected. As before, the rest of the site won’t be affected.

Inside the EEA:

For users inside the EEA, the impact of the manual action won’t 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.

That last sentence is the part most commercial briefings flatten into “no more penalty in Europe.” The penalty path is off for EEA results. Separation is still on the table. Separation is not a free pass to inherit the host domain’s ranking signals forever.

Google also places the change in a regulatory frame:

Following discussion with the European Commission, we are adjusting our enforcement approach within the European Economic Area (EEA) and clarifying the criteria we consider when applying the policy. While we remain concerned that an overbroad application of the DMA could prevent us from addressing real threats to the integrity of our search results, we believe this approach enables us to combat attempts to manipulate search results for our users.

Read that as Google’s own wording, not as a court summary. The company says it discussed the approach with the Commission, adjusted EEA enforcement, and still objects to what it calls an overbroad DMA reading. Treat the quote as a quote.

Who feels this in practice?

• Searchers in the EEA (EU member states plus Iceland, Norway, and Liechtenstein) see results where a site reputation manual action does not demote the affected section the way it can outside the EEA.
• Searchers outside the EEA continue to see the older pattern: the manual action can still affect the portion of the site under review.
• Site owners still get Search Console notifications when a manual action is applied. Reconsideration remains available. Eligible sites can bring disputes to mediation after reconsideration, per Google’s blog.

Google is explicit that global pages can carry a non-EEA effect without rewriting EEA rankings:

Because many pages are viewed by people 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.

Spam Policies documentation adds a useful FAQ answer in Google’s words:

No. Manual actions involving the site reputation policy outside the EEA only affect results shown to users outside the EEA, and not those shown to users within the EEA. The fact that part of a site is subject to a manual action under this policy outside the EEA isn’t used as a signal for ranking that content within the EEA.

For WordPress operators, the practical map is: one URL, two search markets, and one Search Console property that may still show a manual action while EEA traffic behaves differently from traffic in the United States or the United Kingdom. The UK left the EU, so UK searchers are outside the EEA. That single fact matters for English-language media deals sold as “European coverage.” A UK portal audience is not an EEA audience for this policy. An Irish, Dutch, or Polish searcher is.

#What site reputation abuse is

Google introduced the site reputation policy in 2024. The core definition in current Spam Policies language is:

The site reputation policy applies where third-party content is published on a host site mainly because of that host’s already-established ranking signals, which it has earned primarily from its first-party content. The goal of this tactic is for the content to rank better than it could otherwise on its own.

And the clarifying line that keeps honest publishing legal:

Having third-party content alone isn’t inconsistent with the site reputation policy; it’s only inconsistent if the third-party content is published on a host site mainly because of that host site’s already-established ranking signals.

Industry shorthand calls the abusive pattern “parasite SEO”: rent a path on a trusted host, publish commercial pages that would struggle on a new domain, and try to ride the host’s ranking signals. Google’s policy language does not need that nickname. It focuses on motive and integration - third-party pages parked mainly to borrow established signals.

Google’s documented examples of content inconsistent with the policy include:

• An educational site hosting a page about sponsored reviews of payday loans written by a third party that distributes the same page to other sites across the web
• A medical site hosting a low-quality, third-party advertising page about “best casinos” that is not integrated with the site, placed there to rank better due to the established site’s ranking signals

Examples Google lists as not inconsistent include wire services, syndicated news between news publications, forums and comment sections, editorial columns, advertorials meant to reach readers rather than manipulate rankings, and properly treated affiliate links or ad units.

For a UK / English-market category that matches how these deals are sold in practice, think comparison and lead-gen blocks on established consumer or finance portals: “best broadband deals,” “best credit cards,” “best VPN,” “best casino” roundups, or payday / short-term credit reviews syndicated across multiple hosts. The commercial buyer is often a comparison network or affiliate desk. The host is a newspaper brand, lifestyle magazine, or vertical review site with years of first-party journalism. The rented surface is usually a subdirectory (example.com/compare/...) or a dedicated WordPress install under that path, sometimes a multisite subsite mapped to a folder, sometimes a reverse-proxied app that only looks like part of the CMS.

None of those setups are automatic violations. Google’s review factors ask whether the host exercises real control and whether the section is integrated: design and UX consistency, quality parity with the main domain, clear authorship and editorial responsibility, and whether identical or near-identical copy appears on many other sites. A coupons section curated with publisher branding and navigation can be fine. An orphan affiliate article with no author, no menu path, and duplicated marketplace copy is the pattern Google describes as likely to draw action for results outside the EEA.

On WordPress, that distinction often shows up as operational reality rather than policy theory. A subdirectory install that shares the parent theme, header, footer, and editorial workflow looks closer to “integrated.” A black-box partner CMS dropped under /partners/ with different fonts, no byline standards, and feed-duplicated product pages looks closer to the risky pattern - even if the URL sits on the same hostname.

#Penalty vs section separation

The same policy label can produce two different search outcomes after 30 August. Use this comparison when you brief stakeholders.

Google’s Spam Policies text for EEA results:

Within the EEA: When pages appear in Search results shown to users within the EEA, the relevant pages may be categorized as separate from the main domain but won’t be subject to the impact of manual action. This will allow the different parts of the site to rank independently of each other, on their own merits.

And on what “categorized as separate” means:

This categorization tells our systems that the presumption that we generally apply globally — which is that individual pages (including new pages) match the overall quality of other pages on the domain — no longer applies.

Google also says separation is not an instant cliff:

This doesn’t mean that the separate portion of the site immediately loses the ranking signals of the main site. Moreover, over time, our ranking systems learn to rank these parts of a site independently.

For previously penalized EEA results, Google states it will lift those earlier manual actions for EEA searchers, and that previous action is not used as a ranking signal going forward. Separation “isn’t automatic.”

Two operational takeaways sit in that table.

1. “No penalty for EEA searchers” is accurate only if you mean no manual-action demotion on EEA results. It is incomplete if you imply the rented section keeps host-domain presumption forever.
2. A UK searcher is outside the EEA. A French searcher is inside. English-language copy on a .co.uk host does not convert UK SERPs into EEA treatment.

#Why “parasite SEO returns” is the wrong conclusion

The viral market take goes like this: Europe forced Google to stop punishing parasite SEO, so rented subdirectories are safe again for European rankings. That story sells because it is simple. It is also wrong on the mechanism Google described.

What stopped applying for EEA search results is the demotion effect of the site reputation manual action. What remains available is section separation: Google may treat the affected part as distinct from the main domain so it can, over time, rank on its own merits. Google’s casino example in the Spam Policies text is blunt about the intent of that independence:

This ensures that content is ranked in a consistent way against other content of the same nature (for example, casino content ranks against other casino content), so that users get the best possible results for their query.

If your commercial pages only won because they sat under a newspaper domain, independence is the opposite of a win. The buyer paid for adjacency to host authority. Separation is Google saying that adjacency may stop carrying the usual presumption that new pages match the overall quality of the domain.

So the correct European reading is:

• Demotion for this policy is off for EEA results.
• Borrowing host reputation as the main reason for placement is still the behaviour the policy targets.
• The EEA remedy can cut the inheritance path instead of applying a classic manual-action hit.
• Outside the EEA - including the United Kingdom - the manual-action path continues.

Calling that “parasite SEO returns” confuses the absence of one remedy with the absence of enforcement. It also ignores Google’s published concern about DMA overbreadth while still describing an enforcement approach that separates sections rather than blessing them.

For agencies and in-house SEO teams, the wrong conclusion creates bad procurement. Media plans get reopened as “safe again in Europe.” Finance teams assume traffic floors return. Legal teams hear “penalty removed” and stop reading at the headline. The accurate brief is narrower: EEA searchers will not see the old demotion for this policy; EEA searchers may see pages that no longer ride the host the way they did under domain-wide quality presumption.

#What it means for buyers of sponsored articles

If you buy placements on UK and English-language portals - newspaper comparison hubs, magazine “partner” folders, review networks that sell subdirectory packages - re-price the asset you think you purchased.

What you usually buy in those deals is a bundle: URL on a trusted host, design that looks native enough for users, and an SEO assumption that host-domain signals help the pages compete. After 30 August, that SEO assumption must be split by market.

For searchers outside the EEA (UK included):

• A site reputation manual action can still directly affect the sponsored portion in results.
• Buying a path on a strong host does not protect you if Google’s review finds the section inconsistent with the policy.
• Syndicated “best of” templates that appear on many hosts remain a documented risk pattern.

For searchers inside the EEA:

• You may avoid the demotion effect of that manual action.
• You may still face separation, where the section ranks more like its own property over time.
• If your pages cannot compete without host inheritance, EEA visibility can still erode - just through a quieter mechanism than a classic penalty banner story.

Buyer checklist for English-market deals:

1. Ask whether the placement is a true editorial collaboration (named author, host edit standards, unique reporting) or a duplicated feed page with host branding painted on.
2. Require disclosure and bylines that match how the host’s first-party articles work.
3. Map traffic by country in analytics before you celebrate “Europe is fine.” UK traffic is not EEA traffic for this policy.
4. Treat subdirectory rent as a brand and UX channel first, SEO inheritance second - especially for EEA audiences.
5. Put Search Console access and manual-action alerting in the contract. If the host gets a notification and you do not, you learn late.

WordPress-specific buyer note: when the host offers a “WordPress subdirectory install” as the product, ask who controls themes, plugins, robots rules, canonical tags, and noindex. Google’s FAQ says there is no obligation to noindex content that has a non-EEA manual action, and failure to do so is not treated as evasion for EEA ranking. That does not mean you should hide problems. It means technical workarounds are the wrong centre of the strategy. Editorial integration and unique value are the centre.

Do not invent ROI figures. Measure your own baselines. The only honest forecast is directional: authority you paid to borrow may stop flowing for EEA searchers if separation lands; outside the EEA the demotion path still exists.

#What it means for publishers who rent subdirectories

Publishers who monetise trusted domains by renting /deals/, /compare/, /partners/, or similar paths sit on the other side of the same table.

Outside the EEA, a site reputation manual action can still suppress the rented portion while leaving the rest of the site alone. That is the older commercial risk: one partner vertical can burn search visibility for that slice without taking down the homepage, but it can still wreck the revenue line tied to that slice.

Inside the EEA, demotion for this policy goes away for those searchers, which removes one headline risk for European audiences. Separation introduces a different risk: Google may stop presuming that partner pages match the quality of the newsroom. Over time, partner pages compete more like peers in their category. If the partner content is thin relative to dedicated comparison sites, traffic can fall without a dramatic “manual action killed us” narrative for EEA markets.

Publisher actions that match Google’s stated review factors:

• Keep graphic design, typography, and UX features consistent with the host domain when a partner section is meant to be part of the publication.
• Apply the same quality bar you apply to first-party features. If the newsroom would reject the piece, do not publish it under the brand for ranking reasons.
• State authorship and editorial responsibility clearly. Ambiguous ghost pages are a documented risk pattern.
• Avoid identical or near-identical syndication across many hosts when the only differentiator is the hostname.
• Make the section reachable from real navigation, not only from paid search landing paths.
• Keep a contact path for problems that matches publisher standards.

On WordPress multisite or subdirectory installs, operational hygiene matters. Shared user roles, editorial workflow, and theme continuity support an “integrated” story. A partner who gets administrator on a subsite and ships raw affiliate templates every week supports the opposite story. Logging, staging, and content review queues are not SEO tricks - they are how you prove host control if you ever need a reconsideration narrative.

Also plan for asymmetric SERPs. Your US and UK dashboards may show a manual-action impact while EEA countries look stable, or EEA countries may soften gradually after separation while non-EEA results show a sharper drop. Do not average those markets into one “Google traffic” chart and call the strategy healthy.

Revenue teams should update rate cards and partner SLAs around disclosure, uniqueness, and takedown speed - not around the false claim that European enforcement disappeared.

#How to measure after 30 August

Measurement is where this policy change becomes concrete. Google still notifies owners in Search Console when a manual action is applied. That notification is not obsolete for EEA sites. It may describe an action whose demotion effect is limited to non-EEA results, while EEA results follow the separation path instead.

Set up measurement in layers.

1. Search Console property design

• Keep the host domain property verified.
• Add the rented subdirectory as its own URL-prefix property in Search Console when you can (https://www.example.com/compare/). A separate property makes Performance, Indexing, and Manual actions views less noisy.
• If the partner runs on a WordPress subdirectory or multisite path, give the partner (or your agency) restricted access to that prefix property so alerts are not trapped in a shared inbox nobody reads.

2. Manual actions and messages

• Watch the Manual actions report and the Search Console message center after 30 August, especially on hosts that sell partner folders.
• When an action appears, do not assume EEA traffic must crash the same day. Read the policy name, the portion listed, and then check country-split performance.

3. Country and region cuts

• In Search Console Performance, compare queries and pages with country filters that separate EEA markets from non-EEA markets (include United Kingdom as non-EEA).
• In analytics, mirror the same cut with country dimensions on landing pages under the partner path.
• Look for divergence: non-EEA impressions/clicks drop while EEA holds, or EEA softens over weeks without a matching non-EEA cliff.

4. Section independence signals

Google does not publish a public “section separated” badge with a timestamp. You infer risk from behaviour:

• Partner URLs lose relative strength versus host-category peers while first-party sections stay stable.
• New pages under the partner path take longer to gain impressions than historically similar launches on the same host.
• Internal links from strong first-party articles stop “saving” weak partner templates the way teams expect.

5. Reconsideration and mediation readiness

• Document editorial control before you need it: who edits, who approves, how disclosure works, how unique the copy is.
• Know how to file a reconsideration request from Search Console.
• For eligible sites, note Google’s statement that mediation can follow reconsideration.

6. WordPress ops checks tied to measurement

• Confirm canonicals, XML sitemaps, and robots rules for the subdirectory are intentional - not leftover from a partner launch checklist.
• Confirm the partner path is included or excluded from sitemaps on purpose.
• Log plugin and theme changes on rented paths; sudden template swaps often coincide with quality regressions you will later see in Search Console.

Do not wait for a perfect official dashboard labelled “section separation.” Build the country-split and subdirectory property views now so you have a before/after baseline around 30 August.

#What we do not know yet

Several operational details remain unsettled in public documentation, and honest planning has to name them.

How long is “over time”? Google says a separated section ranks independently from the rest of the site over time, and that separation does not mean an immediate loss of main-site ranking signals. There is no public SLA for how many days or crawls that learning takes. Teams that need a calendar date for finance forecasts will not get one from the blog post.

What exactly is a “section”? Google talks about a portion or section of a site - subdirectory patterns are the industry’s mental model, but Google has not published a public checklist that maps “section” to folder depth, subdomain, CMS boundary, or WordPress multisite blog ID. Human review language focuses on integration and control, not on a single URL regex.

When is separation applied? For pages previously under manual action in EEA results, Google says those actions will be lifted for EEA searchers, and that those pages may later be categorized as separate - “but this isn’t automatic.” New cases may notify in Search Console while EEA ranking effects arrive through systems learning rather than a single visible demotion event.

How mediation works in practice. Eligible sites can bring disputes to mediation after reconsideration. Public criteria for eligibility and timelines beyond “short timeframe” language for EEA reconsideration answers are thin. Treat mediation as a path that exists, not as a process you can project-manage from a vendor playbook yet.

How reporting will look in Search Console. Owners will still see manual-action notices. It is less clear how clearly the UI will explain “affects non-EEA results only” versus any separation state for EEA results. Until the product copy is obvious, rely on country-split performance, not on assuming the banner text tells the whole geographic story.

How mixed audiences behave on one URL. Many English-language commercial pages attract UK, US, Irish, and wider EU traffic together. One URL can be demoted for some searchers and separated-for-independence for others. Attribution models that ignore country will misread the policy change as random volatility.

What WordPress site owners should do with that uncertainty is narrower than the rumour cycle. Keep first-party quality high. Treat rented or partner paths as products that must stand without borrowed presumption - especially for EEA searchers. Instrument Search Console with host and subdirectory properties, and split reporting by EEA vs non-EEA countries (remembering the UK sits outside the EEA). Do not restart thin syndicated comparison farms because a headline said penalties vanished in Europe. The demotion lever is geographically limited; the policy goal Google states - stopping third-party pages that exist mainly to exploit a host’s reputation - is not.

If you run WordPress sites with partner subdirectories, multisite folders, or sponsored comparison blocks and need a concrete audit of Search Console setup, country-split baselines, and integration risk before or after 30 August, contact wppoland.com. Bring the host URL, the rented path, and a country breakdown of organic landings. That is enough to start measuring the change Google described - without waiting for the market’s false conclusion to finish circulating.