This article was AI-generated as part of an experimental historical-content project. The date reflects the period being analyzed rather than the date the article was originally written.
Google uses the phrase “site reputation” in a narrow, technical sense. Before looking at what changed this weekend, it is worth separating that sense from the way communications people use the word, because the two meet more often than either side admits.
What the policy covers
Google introduced its site reputation policy in 2024. The Search Central post announcing Friday’s change describes the target as “a practice where third-party content is published on a trusted website just to exploit that site’s good reputation to rank higher in Search.” The industry calls it parasite SEO. A familiar example is a coupon, casino or product-review section run by an outside party on a well-known news or university domain, ranking because the host ranks.
In Google’s usage, “reputation” means ranking signals a domain has earned from its own content. It is not public opinion. But borrowed authority is not always promotional. A page about a named executive hosted on a high-authority domain will usually rank far better for that name than the same page on an unknown blog. For anyone whose name search is their first impression, rules about borrowed authority are rules about who can reach page one.
What changed on August 30
Following discussion with the European Commission, Google said that from August 30, manual actions under the policy have different effects depending on where the searcher is. Outside the European Economic Area, a manual action still affects results for the portion of the site involved, as before. Inside the EEA, “the impact of the manual action won’t apply.” Instead, the affected section “may be separated in our systems so that, over time, it ranks independently from the rest of the site.” Site owners are still notified in Search Console and can still file reconsideration requests.
Search Engine Roundtable noted that this appears to be the first time Google has applied different outcomes under a spam policy based on the searcher’s location.
Google is not a neutral narrator here. Its post says it remains concerned that “an overbroad application of the DMA” could prevent it from addressing real threats to its results. Whether European results get noticeably worse is a prediction, and Google has an interest in making it. I would not assume an outcome either way yet.
The mechanism that remains
The part worth understanding is the separation. Ordinarily, a new section on a strong domain benefits from the domain’s standing. As Search Engine Roundtable explains it, separation is the algorithmic route: Google’s systems treat part of a site as if it were its own site, so the host’s overall reputation stops carrying it, and the section is ranked on its own merits. That process is gradual. A manual action is direct.
In practice, a borrowed-authority page that would be demoted for a searcher in New York may keep its ranking for a searcher in Paris or Frankfurt until separation catches up, if it does.
What this means for monitoring
Country versions of Google have always differed, mostly because of language and local news. This adds a policy difference. A company or executive with European stakeholders should check name and brand searches from inside the EEA explicitly, rather than inferring them from U.S. results. Pay particular attention to results hosted on large third-party domains, in sections that look unrelated to the host’s core content.
Companies that host outside content themselves, such as sponsored sections, partner marketplaces or affiliate pages, should expect less uniform treatment across regions, and should review those sections against the policy regardless of where they operate.
Back in 2023 I argued that when generative answers went global, local reputation became a retrieval problem. The same is now true of the classic results page in a new way. What ranks for your name depends on where the searcher is standing, and in Europe that now includes how a spam rule is enforced.