Google can now rank one section of your site separately from the rest

The interesting part of Google's August site reputation update was not the enforcement change that made the headlines. It was the sentence describing what happens instead of a penalty: the affected section of the site may be separated in Google's systems so that, over time, it ranks independently from the rest of the site. That is a statement about architecture, and it undercuts an assumption most site structures are built on.

What Google changed on 30 August 2026

Google updated its site reputation policy, the rule introduced in 2024 against publishing third-party content on a trusted site in order to exploit that site's ranking. The update did two things: it changed enforcement inside the European Economic Area following discussion with the European Commission, and it clarified the criteria Google considers when applying the policy.

The enforcement split is where the interesting mechanism is exposed.

So an EEA site can hold a manual action for site reputation abuse that has no effect on EEA searchers at all. That sounds like a reprieve. It is not, and the reason is the phrase doing the work in that last cell: ranks independently of the rest of the site.

Why that phrase matters more than the penalty

For twenty years the operating assumption of site architecture has been that a domain accumulates a single reputation, and that everything inside the domain draws on it. That assumption is the entire basis of the standard advice to put new content in a subfolder rather than on a subdomain. The subfolder "inherits domain authority"; the subdomain "starts from scratch".

What Google described on 30 August is a system that can hold a section of a domain at arm's length from that shared reputation and let it earn its own. Both enforcement regimes now describe section-scoped treatment: outside the EEA, a manual action lands on "the portion of the site affected" and explicitly not the rest; inside the EEA, the section gets split off and ranks on its own merits. The penalty differs by region. The capability — resolve a site into sections and treat them separately — is the same in both.

This is not a claim that subfolders stopped working. For ordinary sites where every section is genuinely the same publisher doing the same job, nothing changes. It is a claim that the specific trick of using folder placement to lend reputation to content that is not really yours has a named mechanism pointed at it now, and that mechanism is architectural rather than punitive.

Google already closed the obvious escape route

The other half of the policy worth knowing, because it predates this update and people still get it wrong: first-party involvement does not fix third-party content. Google's own language is that no amount of first-party involvement alters the fundamental third-party nature of the content, and it specifically lists the arrangements it has reviewed — white label services, licensing agreements, partial ownership agreements and other complex business arrangements. Google also says it does not take a site's claims about how content was produced at face value.

That kills the three most common mitigations sold to publishers: adding an in-house editor's byline, signing a licensing agreement, and taking an equity stake in the partner. None of them change the answer. What changes the answer is whether the content is actually the site's own work serving the site's own audience.

A diagnostic: is one of your sections at risk of being separated?

Most businesses reading this are not running a parasite SEO operation. They have one or two sections that grew sideways: a partner directory, a user-generated reviews area, a coupon or deals subfolder somebody added for affiliate revenue, a white-labelled tool, a guest-post section from a 2023 link-building push, a careers microsite on the agency's CMS. Those are the sections worth checking.

Score each section of your site on these six questions. One point each.

Read the score like this:

1. 0–1: integrated. It is your content on your site. No action.
2. 2–3: drifting. Not a policy problem today, but the section is accruing independence. Decide deliberately whether to integrate it properly or move it out, rather than letting it drift further.
3. 4–5: already separate in everything but URL. Treat the shared reputation as unreliable. Plan either real editorial integration or a move to its own domain.
4. 6: this is the pattern the policy describes. The subfolder is doing the work, not the content. Expect it to be separated, and plan for it to rank on its own merits.

What to do with a section that scores high

There are three honest options and one bad one.

If you pick "move it", resist the instinct to do a clean redirect of every URL to a matching URL on the new domain and expect the rankings to follow. Redirects pass signals; they do not pass a reputation the content never earned. Budget for the new domain to perform like a new domain. The redirect mechanics are the easy part of that project; the forecast is the hard part.

What this does not change

Three clarifications, because this policy generates more misreading than most:

1. Normal guest contributions are not site reputation abuse. An expert writing one piece for your blog, edited by you, on your subject, for your readers, is editorial practice. The policy is about scale and purpose: third-party content published to exploit the host's ranking.
2. Hosting user-generated content is not automatically a problem. Reviews, comments and forum posts are expected on the sites that have them. The question is whether a UGC section has become a channel for content aimed at Google rather than at your users.
3. This is not a reason to move your blog to a subdomain. The subfolder-versus-subdomain question still resolves the same way for genuinely first-party content, for the reasons covered in URL structure best practices. What changed is that the folder is no longer a mechanism for laundering reputation onto content that is not yours.

How this fits the wider direction of travel

Section-level evaluation is consistent with everything else Google has shipped in the past two years. Experience and expertise are assessed against the content and its author rather than the domain, which is the point we made in the E-E-A-T explainer. Generative surfaces select individual passages to cite, not domains. The unit of evaluation has been shrinking from site, to page, to passage, for some time.

The practical consequence for anyone planning a build: stop treating domain authority as a pool you can draw from and start treating each section as something that has to stand up on its own. That is a harder brief, and it is also a more durable one, because a section that would rank on its own domain will rank anywhere. It is also the brief we work to on every website design and development project: information architecture decided by who owns the content and who it serves, not by which folder will inherit the most authority.

Frequently asked questions

What changed in Google's site reputation policy in August 2026?

From 30 August 2026, manual actions under the site reputation policy have different effects depending on where the searcher is. Outside the European Economic Area, a manual action affects search results for the affected portion of the site and the rest of the site is unaffected. Inside the EEA, the manual action has no impact on searchers; instead the affected section may be separated in Google's systems so that, over time, it ranks independently from the rest of the site. Google made the change following discussion with the European Commission and also clarified the criteria it considers when applying the policy.

Does a subfolder still inherit domain authority?

Not unconditionally. A subfolder is a request for shared reputation rather than a guarantee of it. Google has now described, in policy, systems that can scope treatment to a portion of a site and separate a section so it ranks on its own merits. For genuinely first-party content serving the same audience, subfolder placement still works as it always did. For content that is substantively independent of the rest of the site, the folder no longer reliably lends it the domain's standing.

Does adding an in-house editor or a licensing deal make third-party content compliant?

No. Google's position is that no amount of first-party involvement alters the fundamental third-party nature of the content, and it specifically names white label services, licensing agreements and partial ownership arrangements among the cases it has reviewed. Google also says it does not take a site's claims about how content was produced at face value. Editorial bylines, contracts and equity stakes do not change the outcome; genuine editorial ownership does.

Is hosting guest posts or user-generated content site reputation abuse?

Not by itself. A commissioned expert contribution, edited by you, on your subject, for your readers, is ordinary editorial practice. Reviews, comments and forum content are expected on the sites that carry them. The policy targets third-party content published at scale with the purpose of exploiting the host site's ranking signals, so the test is purpose and oversight, not format.

How do I tell whether one of my site's sections is at risk?

Check six things for each section: whether a third party writes it, whether it could exist unchanged on another domain, whether its topic is adjacent to your main business, whether its commercial model differs from the rest of the site, whether it shares navigation and internal linking, and whether you would defend it to a customer. Sections answering 'independent' to four or more of those are already separate in everything but URL, and the shared reputation should be treated as unreliable.

If I move a section to its own domain, will the rankings transfer?

Partly, and less than you expect. Redirects pass signals, but they cannot transfer a reputation the content never earned on its own. If a section ranked largely because of its placement on a stronger domain, moving it to a new domain will produce a real and slow-to-recover traffic drop. Forecast the new domain as a new domain rather than as a continuation.

The takeaway

The headline was a regional enforcement change. The durable fact is that Google has now described, in its own policy, resolving a domain into sections and ranking one of them on its own merits. Audit your site section by section rather than as a single entity, score the ones that grew sideways against the six independence questions, and deal with anything scoring four or more by either integrating it editorially or moving it out. The old shortcut, drop it in a subfolder and let the domain carry it, now has a named mechanism pointed at it. Build sections that would rank on their own domain, and the question stops mattering.