Google splits site reputation enforcement inside and outside the EEA

Google published a post titled "Update to the Site Reputation Policy" on the Google Search Central blog on Friday 28 August 2026, and from 30 August a manual action issued under that policy stops producing the same outcome for every searcher. For people searching outside the European Economic Area, the effect is what it has always been: the manual action directly affects search results for the affected portion of the site, and the rest of the site is left alone. For people searching inside the EEA, the impact of the manual action does not apply, and the affected section may instead be separated in Google's systems so that, over time, it ranks independently from the rest of the site.

The change is narrower than the headline suggests. Google did not rewrite what counts as site reputation abuse, did not retire the policy, and did not add exceptions to the behaviour it targets. What changed is where and how a manual action bites. The post, signed by the Google Search Quality team, describes the move as adjusting the enforcement approach within the EEA and clarifying the criteria Google considers when applying the policy, following discussion with the European Commission. Everything else in the announcement follows from that one distinction. The full text sits on the Google Search Central blog.

What the site reputation policy was built to stop

Google says it introduced the site reputation policy in 2024 to stop a practice where third-party content is published on a trusted website purely to exploit that site's good reputation and rank higher in Search. In Google's framing the harm is twofold: it degrades search quality, and it creates a bad experience for the people doing the searching. The mechanism the policy attacks is borrowing. A domain earns trust over years through its own work, and a section of that domain is then handed to someone else whose content would never have ranked on its own merits. The host lends the reputation, the tenant takes the rankings, and the searcher gets a result that was never really vouched for.

That description matters for reading the 28 August post correctly, because the remedy Google now describes for the EEA attacks the same mechanism from a different angle. Nothing in the post says the borrowing has become acceptable. Google states plainly that it remains concerned that an overbroad application of the DMA could prevent it from addressing real threats to the integrity of its search results, and that it believes the new approach still lets it fight attempts to manipulate results. The concern is on the record inside the announcement itself.

One manual action, two different outcomes, from 30 August

Google set 30 August as the date the split takes effect. From that day, a manual action applied under the site reputation policy has a different effect for those searching in the EEA than for those searching outside it. Outside the EEA, the manual action directly affects search results for the portion of the site affected, and Google repeats that, as before, the rest of the site is not affected. Inside the EEA, the impact of the manual action does not apply, and the affected section of the site may be separated in Google's systems so that it ranks independently from the rest of the site over time.

Read the conditional wording. Google wrote that the section "may" be separated and that independent ranking happens "over time". Neither phrase promises an immediate, uniform or guaranteed outcome, and the post gives no schedule for it. Treat the separation as something Google has told site owners it can do, not as a switch that flips on 30 August for every affected section.

One more line in the post deserves attention because it produces a genuinely odd situation. Google notes that because many pages are viewed by people globally, any given page might carry a manual action while that change only affects search results shown to users outside the EEA. The manual action attaches to the page. The visible consequence depends on where the searcher is. A single URL can therefore be demoted for one audience and untouched for another at the same moment.

What "ranks independently from the rest of the site" actually means

Start with what a demotion is. A manual action that directly affects results for a portion of a site is a penalty applied on top of whatever that section would otherwise have earned. The section keeps whatever benefit it draws from sitting on a trusted domain, and Google then pushes it down. Remove the penalty and the section returns to where the domain's standing had put it.

Separation is a different operation. If a section ranks independently from the rest of the site, it is no longer being carried by the domain around it. Google has not published any detail about how that separation is implemented, so nobody outside Google can describe the machinery. What the phrase does tell you is the intended end state: the affected section stands on its own, and the reputation of the parent domain stops flowing into it.

The practical difference is easy to miss and worth spelling out. A demotion is subtractive and reversible in an obvious way. Separation is structural. It does not add a negative; it removes an inherited positive. That is why calling it the softer option is a guess rather than a conclusion, and Google did not characterise it as lighter, heavier or equivalent.

Why separation is a different remedy rather than a lighter one

Reason it through from the policy's own logic. The abuse Google described in 2024 is the exploitation of a host site's reputation by content that could not have earned those rankings alone. If a section is separated so that it ranks independently, the borrowed reputation is exactly what is taken away. The remedy is aimed at the thing the policy says was wrong, rather than at the pages as a class.

That framing has an uncomfortable consequence for anyone running a large third-party section. If the section's own content, its own links and its own demand were genuinely strong, standing alone should hurt less. If the section only ever ranked because of the domain it sat on, standing alone could look worse than a demotion, because a demotion is capped by whatever penalty Google applies while an absence of inherited authority is not capped by anything. None of that outcome analysis appears in Google's post. It is reasoning from the mechanism Google described, and it should be labelled as reasoning when you repeat it to a client.

There is a diagnostic buried in this for publishers who want an honest answer about their own sections. If you cannot say what a third-party area of your site would rank for without your domain behind it, you do not know how exposed you are. A content audit that separates a section's own earned signals from its inherited ones is the only way to find out, and it is the same exercise that makes a serious technical and content SEO audit useful rather than decorative.

Thailand is outside the EEA, so the unchanged regime applies

A business registered and operating in Thailand is not in the European Economic Area, which is a European grouping. For a Thai site, the enforcement effect Google described for users outside the EEA is the one that applies, and that effect is explicitly unchanged: a manual action directly affects search results for the affected portion of the site, and the rest of the site is not affected.

There is a nuance worth holding on to, though. Google's wording is about where people are searching, not about where a site is registered or hosted. The post speaks of users outside the EEA and users inside it. A Thai hotel, exporter, hospital or law firm that draws European readers has an audience on both sides of that line, and the same page could behave differently for the two groups. Google gave no guidance on how to observe this, and Search Console's country dimension reports impressions and clicks rather than the treatment applied, so this is a structural fact to understand rather than a metric to chase.

For most Thai advertisers the operational takeaway is dull, which is usually a good sign. The policy that governs your third-party sections is the same policy it was on 27 August, the consequence of breaking it is the same consequence, and the work that keeps you clear of it is the same work: publishing content your own site can stand behind. If your organic programme in Thailand leans on partner pages, sponsored sections or syndicated deals, the exposure sits there, and it is worth building that into how you plan SEO in Thailand rather than treating it as a legal footnote.

Notification and appeal have not changed

Google states that site owners will continue to be notified within Search Console when a manual action is applied. If you believe an action was taken in error, you can still submit a reconsideration request. Eligible sites will, following the reconsideration request, also have the opportunity to bring disputes to mediation. Google did not define which sites are eligible for mediation, did not describe how mediation works, and did not give a timeframe.

Practically, this means the first place to look is unchanged. The manual actions report in Search Console remains the only authoritative signal that a site reputation manual action exists. Ranking movement is not that signal. A section can fall for a dozen ordinary reasons, and reading a manual action into a traffic dip is how teams spend a quarter fixing the wrong problem.

What the announcement does not say

Being precise about the gaps protects you from repeating claims Google never made.

• It names no affected sites and gives no examples of enforcement.
• It gives no detail on how the separation of an affected section is implemented in Google's systems.
• It does not change the substance of the site reputation policy outside the EEA, or state that the definition of the abuse has moved.
• It does not say whether the separation approach is also used outside the EEA.
• It gives no numbers: no count of manual actions, no share of sites affected, no measured ranking impact.
• It does not describe which criteria were clarified, beyond stating that Google is clarifying the criteria it considers.

Why Google published a blog post about this at all

The timing lines up with something Google's John Mueller said the same week. Search Engine Roundtable reported on 28 August 2026 that Mueller, answering a question about why Google names updates publicly, said such announcements are primarily transparency for site owners, and that when there is something actionable for site owners to do, Google publishes it in its policies, help centre, documentation and blog independently, usually well in advance of changes in its systems.

By that standard, the site reputation post is the actionable kind. It carries a policy change, a documented effect and a start date two days out. Search Engine Roundtable also noted that Google does not announce every update, and that most updates never get a name at all. So the existence of this post is itself information: Google decided site owners needed to be able to act on it, or at least to understand it before 30 August.

The change side by side

The table below compares what Google says happens after a site reputation manual action is applied from 30 August 2026, split by where the searcher is. Every cell is drawn from the announcement.

What this means for Thai marketers

The honest answer for most Thai teams is that nothing you were supposed to do has changed, and that is the point worth making to a nervous client. The enforcement regime that applies to searchers in Thailand is the one Google left untouched. The value in the 28 August post for a Thai advertiser is not a new rule, it is a reminder of which parts of a site carry policy risk.

Go and list them. Guest-post sections, partner subfolders, coupon and discount-code areas, white-labelled directories, syndicated press-release archives, any subdomain or subdirectory where an outside party controls what gets published. For each one, write down who signs off on the content, whether it would rank on its own signals, and what your site gets from hosting it. That inventory takes an afternoon and it is the difference between knowing your exposure and hoping.

Then look at the incentive underneath. Sections like these usually exist because someone needed rankings faster than the site could earn them. The durable version of that goal is unglamorous: a publishing programme that builds topical depth your own domain owns, supported by content marketing you actually control, and authority earned through link building rather than rented from a landlord. Neither of those is a policy workaround. They are simply the version of the work that no enforcement update can take away from you.

One caution on communication. If you brief a client on this, do not tell them Google has relaxed the site reputation policy, because it has not, and do not tell them Thai sites are affected by the EEA change, because the change is defined by where the searcher is and Thailand is not in that territory. The safe sentence is that Google changed how a manual action behaves for EEA searchers from 30 August, that everything else stands, and that the appeal route is unchanged.

Frequently asked questions

Did Google change what counts as site reputation abuse?

No. The 28 August post changes the enforcement effect of a manual action for searchers in the EEA and says Google is clarifying the criteria it considers, but it does not restate or narrow the definition of the abuse itself, which Google introduced in 2024 to stop third-party content being published on a trusted site purely to exploit that site's reputation.

Does a website based in Thailand get the EEA treatment?

Not for searchers in Thailand. Google's wording turns on where people are searching, so a Thai site's Thai audience falls under the unchanged behaviour where a manual action directly affects results for the affected portion of the site, while readers searching from inside the EEA fall under the new handling.

When does the change take effect?

Google said the split begins on 30 August, two days after the post was published on 28 August 2026. Google gave no end date, no phased schedule and no timeline for how quickly an affected section would come to rank independently in the EEA.

Can a site still appeal a site reputation manual action?

Yes. Google says site owners continue to be notified in Search Console, that a reconsideration request can still be submitted if you believe the action was taken in error, and that eligible sites can bring disputes to mediation after a reconsideration request, though Google did not define eligibility or describe the mediation process.

Did Google publish a list of affected sites or any numbers?

No. The post contains no examples, no list of affected sites, no count of manual actions and no measurement of ranking impact, so any figure attached to this story did not come from Google's announcement.

Where to take this next

If your site hosts content someone else writes, the useful next step is not a policy debate, it is an inventory and an honest look at what each section would rank for standing alone. If you want a second pair of eyes on which parts of your site carry that risk and what to do about them, our team in Bangkok is happy to take a look.