On August 28, 2026, Google confirmed that starting August 30, 2026, manual actions issued under its site reputation abuse policy will no longer affect search results shown to users inside the European Economic Area. Barry Schwartz at Search Engine Roundtable called it correctly: this is the first time Google has applied different spam-policy outcomes based on where the searcher is sitting rather than what the site did.
Within hours, the read circulating in growth-marketing circles was that Google blinked and parasite SEO is viable again — at least in Europe. That read is wrong in a way that will cost money, and Michigan companies with European customers are unusually exposed to the mistake.
What exactly did Google change on August 30, 2026?
Google changed the reach of a penalty, not the penalty itself. Manual actions for site reputation abuse are still issued, still appear in Search Console, and still suppress the affected section of a site for every searcher outside the EEA. Inside the EEA — the 27 EU member states plus Iceland, Norway and Liechtenstein — the demotion simply does not apply.
Google’s policy language is specific about what replaces it. For EEA users, affected pages “may be categorized as separate from the main domain but won’t be subject to the impact of manual action,” which “will allow the different parts of the site to rank independently of each other, on their own merits.” Google’s stated example is casino content ranking against other casino content.
The company was blunt about why. A Google spokesperson told Search Engine Roundtable that while it stands by the policy and remains “concerned about efforts to weaken our spam policies,” it agreed to change its enforcement approach for European users to address European Commission concerns raised under the Digital Markets Act. Google did not choose this. It settled.
Does this mean parasite SEO is safe again in Europe?
No. Two things survive the change intact, and either one is enough to sink a rented-authority strategy.
First, the manual action still lands. Google confirmed site owners “will continue to be notified within Search Console when a manual action is applied,” and that notice still governs every market outside the EEA. Second — the part the celebratory takes skipped — Google preserved algorithmic separation for EEA users. The affected section “may be separated in our systems so that, over time, it ranks independently from the rest of the site.”
Read that as an engineer would. The economic premise of parasite placement is that a subfolder inherits the host domain’s earned authority. Algorithmic separation cancels that inheritance. In the EEA you are not exempt from consequences; you move from a cliff to a slope, judged as if the page lived on a brand-new domain with no history.
How does algorithmic separation actually differ from a manual action?
A manual action is a suppression applied to a section of a site. Algorithmic separation is a reclassification: Google stops treating the section as part of the parent domain for ranking purposes. Different mechanisms, different timing curves, similar destination.
That distinction lets you predict cases nobody has written about yet. Take a hypothetical: a Grand Rapids equipment distributor licenses a “/deals/” subfolder on an established trade publication and fills it with vendor-written comparison pages. Outside the EEA, the day a manual action issues, that subfolder’s rankings collapse in one step. Inside the EEA, nothing visible happens on day one — then over successive crawl-and-evaluation cycles the subfolder drifts down as the borrowed signal stops flowing. The traffic chart looks like a leak instead of a break.
That is the trap. A leak gets rationalized as seasonality for a quarter; a break gets investigated on Monday. The carve-out does not make the tactic safer — it makes the failure harder to diagnose, which is worse for a small team without a dedicated analyst.
Why does searcher location matter more than server location for Michigan companies?
Because the split is drawn around the person typing the query, not the company publishing the page. A manufacturer in Auburn Hills does not get EEA treatment for being American; it gets EEA treatment only for the slice of its audience physically searching from Europe.
That asymmetry bites hardest in metro Detroit’s supplier base. Tier 1 and Tier 2 firms around Plymouth, Northville and Auburn Hills sell into European OEM programs and often maintain EU-facing content sections or partner microsites. If any of that content sits on a third party’s domain for the ranking benefit, the new rule protects the smaller half of the audience and leaves the larger half — North American buyers, distributors and specifiers — fully exposed. Long B2B research cycles mean you will not see that damage for two or three quarters. Map your actual EEA revenue share before acting, which is the kind of question we work through with clients at ROSH Media.
The mirror-image risk sits with hosts. Michigan’s local news domains, university sites around Ann Arbor and East Lansing, and health-system properties are exactly the high-authority publishers approached to rent out a subfolder. For them, sponsorship revenue keeps arriving from EEA impressions while non-EEA rankings absorb the manual action. The revenue and the cost land in different columns, which is how bad partnerships get renewed.
Will a separated subfolder still get cited in AI Overviews and AI Mode?
Google has not said, and anyone claiming certainty here is guessing. Treat what follows as reasoning, not confirmed policy.
Generative surfaces select sources from ranked results. If algorithmic separation strips a subfolder of inherited domain authority, the reasonable expectation is that its citation rate falls alongside its rankings — slowly in the EEA, sharply elsewhere once a manual action issues. The strategic conclusion holds either way: authority you rent is authority you cannot defend in an answer engine, because the citation accrues to a domain you do not control. Building citable material on your own domain is the only version that compounds, a theme we return to in our work on AI search visibility.
How should a small Michigan team audit third-party content this week?
Seven steps, executable by a three-person marketing team in a few working days. No enterprise tooling required.
- Open Search Console and check Security & Manual Actions → Manual actions for every property you own. A site reputation notice names the specific affected section, which tells you the scope immediately.
- Inventory every subfolder and subdomain on your domain that someone outside your organization writes, edits or sells. Coupon pages, sponsored guides, partner directories, syndicated vendor content, and dormant microsites all count.
- For each one, answer a single question in writing: would this page exist on its own domain and still earn traffic? If the honest answer is no, you are renting reputation, whether or not you called it that.
- Segment organic traffic by country in Search Console or GA4 and calculate your true EEA share. Most Michigan B2B and service businesses will find it in the single digits, which reframes the risk calculation.
- Apply editorial control where the content is worth keeping — a named editor, a real review step, and bylines matching people at your company. First-party oversight is the line Google’s policy draws.
- Where content fails step three, remove it or move it to its own domain deliberately, rather than waiting for Google’s systems to separate it on an unannounced timeline.
- If you believe an action was issued in error, file a reconsideration request. Google confirmed that eligible sites can now also bring disputes to mediation following that request — a route that did not exist before and costs nothing to pursue.
What dates belong on the calendar?
- August 28, 2026 — Google updates its site reputation policy documentation and publishes the EEA enforcement change.
- August 30, 2026 — The change takes effect. Manual actions stop affecting EEA searchers from this date forward.
- Early September 2026 — First clean weekly comparison. Segment organic sessions by EEA versus non-EEA and store a baseline before Q4 seasonality distorts it.
- Late September through October 2026 — The window where algorithmic separation would plausibly surface in EEA traffic. Watch subfolder-level trends, not sitewide totals.
- Q4 2026 — Holiday and year-end demand peaks. Any rented-authority page still live carries its largest revenue exposure exactly when a non-EEA demotion hurts most.
Frequently asked questions
Does my Michigan business need to do anything if it has no European traffic?
Not because of the EEA carve-out itself — that changes nothing for a purely North American audience. But the announcement is a reasonable prompt to audit third-party content on your domain, since manual actions still apply in full to your entire market. The policy you are exposed to did not soften at all.
Will Google still send a Search Console notice for EEA-only sites?
Yes. Google stated that site owners “will continue to be notified within Search Console when a manual action is applied,” regardless of region. The notice is issued, the reconsideration process remains open, and eligible sites can escalate to mediation. Only the ranking impact for EEA searchers is withheld.
Is sponsored or partner content automatically site reputation abuse?
No. Google’s policy targets third-party content published on a host domain primarily to exploit that host’s ranking signals, with little first-party editorial oversight. Sponsored content with genuine editorial review, clear labeling and real accountability is not the target. The test is oversight and intent, not the presence of a commercial relationship.
How long has this policy been in force?
Google introduced the site reputation abuse policy alongside the March 2024 core update and began enforcing it in Europe in January 2025. The August 30, 2026 change is the first regional carve-out in its history, and it followed European Commission proceedings rather than any shift in Google’s own assessment of the tactic.
The judgment call
Schwartz worried publicly that this decision will encourage more abuse. He may be right about volume, but the likelier harm is quieter: vendors will sell Michigan companies “EEA-safe” placements on borrowed domains, and those companies will accept a documented penalty across their largest market for relief in one holding a fraction of their revenue. Google conceded regional enforcement while keeping the mechanism that makes the tactic unprofitable anyway. Anyone treating August 30 as permission has misread which half of the policy moved.
Comments are closed