Should You Ever Host Someone Else's Content on Your Domain?

Does Google still punish third party content on your own domain?

As of September 2026, yes, but where you sell now changes the outcome. Google still issues manual actions under its site reputation policy. Since August 30, 2026, those actions change search results for people outside the European Economic Area and do not change rankings for people inside it.

That is a strange sentence to write. One policy, two outcomes, split by the location of the person typing the query. It is also the most consequential search policy change we have read this year, and most of the teams we talk to have not noticed it.

We build marketing sites for B2B companies, so this lands on our desk in a specific way. A growth lead asks whether the company should host a partner's content on the main domain. The honest answer used to be short. Now it needs a map.

What is the site reputation policy, in plain terms?

The site reputation policy targets third party content published on a trusted site mainly to borrow that site's ranking strength. Google's spam policies page defines it as content hosted on a site because of ranking signals the host earned from its own first party work, so the content ranks better than it could alone.

The industry nickname is parasite SEO. A well known domain rents out a folder. A third party fills that folder with reviews, coupons, or sponsored guides. The pages rank because of the domain, not because of the pages.

Google introduced the policy in 2024. The blog post announcing this year's change says so directly: "In 2024, we introduced our site reputation policy to stop 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."

It sits alongside fifteen other named spam policies on the same page, including scaled content abuse, expired domain abuse, cloaking, doorway abuse, and thin affiliation. That page was last updated on August 28, 2026.

What changed on August 30, 2026?

Enforcement split by region. Google's Search Quality team published "Update to the Site Reputation Policy" on Friday, August 28, 2026. Starting August 30, a manual action under this policy affects search results for users outside the European Economic Area only. Inside the EEA, the manual action does not apply to rankings.

Two details matter more than the headline. First, Search Console still notifies the site owner when a manual action is applied, and reconsideration requests still work. Nothing went quiet.

Second, and this is the part people skim past, Google wrote that inside the EEA "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." The penalty is lifted. The separation is not.

So a coupon subfolder in Europe is not punished. It is simply judged on its own merits, without the parent domain carrying it. For most rented subfolders, that is the same outcome by a gentler route.

Why did Google split enforcement by region?

The European Commission. Google's post says the adjustment follows discussion with the Commission, and names the Digital Markets Act as the pressure point. Google did not pretend to be happy about it, which is unusual for a policy post and worth reading closely.

The company wrote that it remains "concerned that an overbroad application of the DMA could prevent us from addressing real threats to the integrity of our search results." That is a regulator shaping search quality enforcement directly, and saying so in public.

We think this is the real story. Ranking policy used to be a product decision. In the EEA it is now partly a regulatory one, and the two do not always point the same way.

Does a manual action still hurt if you sell mostly in Europe?

Yes, in three ways. The section can still be separated and ranked on its own. Search Console still shows the action, which any buyer, investor, or agency doing diligence can see. And a page viewed globally still loses non EEA traffic, because the action follows the searcher, not the server.

Google made that last point explicitly. Because many pages are read by people all over the world, a page can carry a manual action that only changes results for users outside the EEA. Your German readers see one internet. Your American readers see another.

For a B2B software company with customers in both markets, that is a reporting problem before it is a ranking problem. Aggregate organic traffic drops and nothing in your dashboard explains why.

How do you tell a real partnership from site reputation abuse?

Ask one question: would this content rank on its own domain? If the honest answer is no, and the whole reason it sits on your site is your domain's strength, you are inside the policy. Intent is not the test. Dependency on borrowed authority is.

We use a second check with clients. Who edits it? Not who approves the invoice, who actually edits the words. If nobody on your team can name the editor, there is no editorial oversight, and oversight is the line Google keeps drawing.

This connects to how search evaluates expertise more broadly. If you have not thought about that layer, our explainer on what E E A T actually means for a B2B site covers the same ground from the content side.

What does Google say counts as acceptable third party content?

Google's own example is a news publication running freelance work. It passes because three things are true: authorship is clear, editorial oversight is real, and the content fits the rest of the site. The violating example is an education site hosting sponsored payday loan reviews that also appear on many other sites.

Read those two side by side and the pattern is obvious. Freelance writing for a newsroom is still the newsroom's content. Syndicated loan reviews on a university domain are not the university's content in any meaningful sense.

So guest contributors are fine. A partner writing one genuine case study is fine. A vendor uploading two hundred templated pages into yourdomain.com/deals is not, and no contract language changes that.

Why do we tell clients to stop chasing this in the first place?

Because the economics were always short term, and the site pays the cost. Renting a subfolder converts a durable asset, your domain's credibility, into one quarter of revenue. We have never seen a version of this trade that a marketing team was glad about two years later.

There is a quieter reason now. Answer engines changed what a click is worth. Pew Research Center tracked the browsing of 900 United States adults across 68,879 Google searches in March 2025, of which 12,593 produced an AI summary. When a summary appeared, users clicked a result in 8% of visits, against 15% when no summary appeared.

Pew also found that users clicked a link inside the AI summary itself in just 1% of those visits, and ended the session entirely 26% of the time with a summary, against 16% without. Thin rented pages were never going to survive that. They exist to catch a click that increasingly does not happen.

The pages that still earn attention are the ones with something first hand in them. That is also why we keep arguing that authority signals have shifted rather than disappeared.

How should you audit your own site for exposure?

Start with a crawl and sort by folder. Look for any directory your marketing team did not create. Common ones are /coupons, /deals, /reviews, /partners, and any path a vendor set up during a promotion that nobody turned off. Then check which of those folders rank for queries unrelated to your product.

Next, open Search Console and read the manual actions report properly, not the summary card. It names the affected section, which tells you exactly which folder Google is looking at.

Then decide per folder. Fold it into your real content with a named author and genuine editing, noindex it, or remove it and redirect. Doing nothing is a decision too, and in the EEA it now means the folder quietly floats away from your domain's strength.

If your site also publishes machine assisted content, the same audit should cover that, because a different policy applies. We wrote about where that line sits in Google's spam policies and AI written content.

What will the next version of this policy look like?

We expect the separation mechanic to matter more than the manual action. Google already says affected sections may rank independently over time. That is a system judging parts of a domain separately, and it works without any human at Google pressing a button.

If that is where this goes, the regional split stops being the interesting part. Domain strength stops flowing evenly across a site, and every folder has to earn its own standing. Teams that built one honest site will not notice. Teams that built a good site plus a rented annex will notice a lot.

Our advice has not changed because of this update, only sharpened. Publish things your own name belongs on. If you are weighing a partnership that involves hosting someone else's pages, or you have inherited a folder nobody can explain, we are happy to look at it with you. You can find us at phoenix.studio and we will tell you plainly whether it is worth keeping.