Site reputation abuse: what Google's policy covers and how to stay clear of it

What site reputation abuse is

The tactic is simple. A strong domain, such as a newspaper, a university or a well-known magazine, has earned trust with years of its own journalism or teaching. Someone else then places a page on that domain about a topic with lucrative search demand: payday loans, casinos, coupons, CBD, VPNs. The page ranks because of the host, not because of anything on the page. The host is paid or shares revenue; the third party gets traffic it could never win on its own site. The industry calls this parasite SEO because the page lives off the host.

Google introduced the policy as site reputation abuse in March 2024. On today's spam policies page the section is headed Site reputation policy, and content is described as "inconsistent" with it rather than as abuse. The idea is the same.

Everything hinges on the term third-party content. Google defines it broadly: “Third-party content is content that's created by an entity that's separate from the established host site. Examples of separate entities include users of that site, freelancers, white-label services, and content created by people not employed directly by the host site.”

That list includes your own freelancers and your forum users, which is why the next sentence in the policy matters so much: third-party content on its own is not a problem. What matters is why it is there.

For the wider picture of how spam policies sit next to Google's ranking systems and core updates, see the lesson “Ranking systems, core updates and spam policies”. This lesson goes deep on one policy.

What Google officially says

Read together, these three sentences explain the whole policy. A new page on a strong domain starts with the benefit of the doubt: Google assumes it is as good as the rest of the site. The policy exists for the cases where that assumption is being exploited.

One related point from the March 2024 announcement is worth keeping in mind when you read SEO tools: “some third-party services provide "reputation" or "authority" scores for sites. These don't correspond to any of Google's own signals nor come from Google.” A high third-party authority score is not what the policy protects, and a host does not need one to be at risk.

What counts and what does not

Google gives two short lists. Both are examples, not complete rules: the first is introduced with “include, but aren't limited to”, and the second ends with “These examples are non-exhaustive. There will be other instances where we don't take action.”

Notice what the lists do not say. Coupons, affiliate content and freelancers are not banned topics. Coupons appear on the current page as a worked example of a section Google is not likely to act on (see below). Google's November 2024 FAQ is explicit about affiliates: “No, the policy is not about targeting affiliate content.” And about freelancers: “freelance content alone is not a violation of the site reputation abuse policy.”

The common thread on the "inconsistent" side is a page that has nothing to do with the host, is not part of the publication in any visible way, and often exists in the same form on other domains.

First-party involvement: does oversight make it OK?

This is where the policy has moved most, so it helps to read the wording in order.

March 2024. The first definition turned on oversight: “Site reputation abuse is when third-party pages are published with little or no first-party oversight or involvement, where the purpose is to manipulate Search rankings by taking advantage of the first-party site's ranking signals.” Many hosts responded by adding a light editorial review to partner sections and calling them supervised.

November 2024. Google closed that door. After reviewing white-label services, licensing agreements and partial ownership deals, it wrote that “no amount of first-party involvement alters the fundamental third-party nature of the content or the unfair, exploitative nature of attempting to take advantage of the host's sites ranking signals.” The new wording made it a violation “regardless of whether there is first-party involvement or oversight of the content.” Google also warned that “we don't simply take a site's claims about how the content was produced at face value”.

August 2026. The current page no longer uses the "regardless of first-party involvement" sentence. Instead it explains what a human reviewer looks for: whether content “is created with sufficient input, editorial oversight, or contribution from the host site to be considered fully integrated with the main site.”

How do the two fit? Not as a reversal. In 2024 Google rejected oversight as a label: a sign-off by an editor did not turn a partner's casino section into the publication's content. The 2026 wording asks whether the content really is part of the publication, judged by evidence a reviewer can see. A thin layer of review on top of rented content still fails that test; genuine joint editorial work can pass it. In practice: do not rely on a contract clause saying you supervise the partner. Rely on what the page shows.

The four factors and Google's worked examples

The current policy lists the objective factors reviewers use to judge how much control the host has over the content:

1. Presentation. “are the graphic design, formatting, typography and UX features of the content consistent with the host domain?”
2. Quality. Are there quality problems on these pages that the main domain does not have?
3. Authorship. The “stated or implied authorship”: is someone explicitly responsible, and is there evidence that contradicts the stated author?
4. Duplication. “Does the content appear on multiple other sites in identical or near-identical form”?

Google then walks through three cases. They are the best guide to where the line is.

The coupon example shows that a separate CMS, a commercial partner and non-unique codes do not decide the case on their own. The CBD example shows what does: no author, no integration, no disclosure and copied content, all at once.

How Google enforces it: manual actions, the EEA and algorithms

Across all spam policies Google says: “We detect policy-violating practices both through automated systems and, as needed, human review that can result in a manual action.” For this policy the documented path is human review. If a portion of a site looks out of line, “a site will be subject to human review”, and what happens next depends on where the searcher is.

The EEA change followed talks with the European Commission. The August 2026 post says: “Following discussion with the European Commission, we are adjusting our enforcement approach within the European Economic Area (EEA) and clarifying the criteria we consider when applying the policy.” Inside the EEA, Google says the separation will allow “the different parts of the site to rank independently of each other, on their own merits.” The page gives an example: casino content ranks against other casino content.

Being categorised as separate is not an instant drop. Google says: “This doesn't mean that the separate portion of the site immediately loses the ranking signals of the main site.” Over time its systems learn to rank the parts independently. And: “The fact that this categorization has been applied isn't used as a ranking signal.” The two regions are also kept apart: a manual action outside the EEA “isn't used as a signal for ranking that content within the EEA.”

You are told either way. The policy says Google will notify you in the Manual actions report and the Search Console message center. The Manual Actions help page opens the entry with “Google has detected that a portion of your site is inconsistent with our spam policy on site reputation.” It also warns: “if your site is repeatedly inconsistent with our site reputation policy, that may lead to further manual actions and/or affect your site's overall ranking.”

Algorithms that treat sections as separate sites

Separately from the policy, Google described in November 2024 “systems and methods designed to understand if a section of a site is independent or starkly different from the main content of the site.” “By treating these areas as if they are standalone sites, it better ensures a level playing field”. This can cut traffic to a coupon or review section with no manual action at all, and Google is clear it is not a penalty: “This doesn't mean that these sub-sections have somehow been demoted or are in violation of our spam policies.” If a partner section lost traffic and the Manual actions report is empty, this is the likely explanation, and the fix is to make the section good enough to rank on its own.

A short history of the policy

Two details matter for older advice you will find online. The March 2024 post said affected content “needs to be blocked from Google Search to avoid violating our spam policies”; inside the EEA there is now no such obligation. And the January 2025 update was editorial: Google called it a change to make the wording clearer, with “no substantive change to the policy itself.”

If you host third-party content: what to do

If you run a publication with partner sections, do not wait for a message in Search Console. List every section that a partner writes, feeds or operates, for example news.example.com/deals/ or example.com/partners/casino-reviews/, and run each through the decision tree above. Search a distinctive sentence from each page in quotation marks to see whether it exists on other domains.

For content that does not pass, Google's Manual Actions help lists four options:

• “Move the inconsistent content to a new domain. If you link from the old site to the new site, use the nofollow attribute in those links.” Do not redirect: “Avoid redirecting URLs from the old site to the new site”.
• “Use noindex to exclude the inconsistent content from Search indexing. To make sure your noindex rule is effective, don't block that content with your robots.txt file.”
• Redo the inconsistent content as first-party content, written and edited by your own team.
• “Remove the inconsistent content from your site.”

And two moves that do not help. “Moving to a subdomain/subdirectory may be viewed as an attempt to circumvent our spam policy, which could lead to broader actions against your site in Google Search.” Moving to another established site, such as a sister brand, “may introduce a site reputation issue to the established site”. A brand-new domain with no reputation is the clean option.

A noindex on its own does not close the case. From the November 2024 FAQ: “No. You still need to reply to the manual action in Search Console and explain that the content has been noindexed.” The same applies if you move content: submit a reconsideration request.

<!-- On every page of the partner section, e.g. https://example.com/partners/casino-reviews/ -->
<meta name="robots" content="noindex">

# robots.txt: do NOT add this, or Google never sees the noindex
Disallow: /partners/casino-reviews/

Buying placements on big sites: the SEO risk

From the other side, parasite SEO is a tactic you buy: a "best X" page on a strong domain, a sponsored review, a section run by a vendor on a magazine's subfolder. It can rank fast, which is exactly why Google wrote the policy. The risks for the buyer:

• You do not control the asset. When the host gets a manual action or simply decides to noindex the section, your rankings and traffic go with it, and there is nothing you can do on your own site to win them back.
• Outside the EEA, the page can be demoted by a manual action. Inside the EEA it is separated and has to rank on its own merits, which for a page that ranked only because of the host is often a long way down.
• It is often link spam too. If the paid page links to your site with links that pass ranking credit, it fits Google's link spam example of “Advertorials or native advertising where payment is received for articles that include links that pass ranking credit”.

Paid content is not banned. A sponsored article written for a publication's readers, promoted to them and marked as such, is the native advertising case Google accepts. Paid links are fine “as long as they are qualified with a rel="nofollow" or rel="sponsored" attribute value”. The question to ask before you pay is simple: would this placement be worth the money if it never ranked in Google? If the only value is the host's ranking power, it is the risky kind.

The durable alternative is to build the pages on your own domain and earn coverage on other sites by being worth writing about. The lesson “Digital PR and brand mentions” covers how to do that without paying for placements.

How it relates to link spam and scaled content abuse

Google launched three new policies on the same day in March 2024: “expired domain abuse, scaled content abuse, and site reputation abuse.” They target different things, and one page can break more than one.

• Site reputation is about where content is published: third-party pages riding on a host's signals.
• Link spam is about links “primarily for the purpose of manipulating search rankings”, including paid links that pass ranking credit. A parasite page that links to the buyer with a followed link can be both.
• Scaled content abuse is “when many pages are generated for the primary purpose of manipulating search rankings and not helping users.” A white-label partner that pushes hundreds of near-identical coupon or review pages onto many hosts can fall under both policies. See the lesson “AI-assisted content without scaled content abuse”.
• Expired domain abuse is the cousin of this policy: borrowing a past owner's reputation instead of a current host's.

Fixing one does not clear the others. Adding rel="sponsored" to the links on a casino section deals with link spam, but the section can still be inconsistent with the site reputation policy.

Common mistakes

• ✕"Our editor reviews it, so it is first-party"A sign-off is not integration. Reviewers look at presentation, quality, authorship and duplication.
• ✕noindex and walk awayThe manual action stays until you answer it with a reconsideration request.
• ✕robots.txt instead of noindexA blocked page is never crawled, so Google cannot see the noindex.
• ✕301 to the new domainGoogle says redirects may bring the problem back. Link with nofollow instead.
• ✕Moving to a subdomain or a sister brandSame domain may look like circumvention; another established site inherits the issue.
• ✕Reading a traffic drop as a penaltySystems that treat a section as a standalone site are not a manual action. Check the report first.
• ✕Applying old advice in the EEAInside the EEA a manual action has no impact on results and there is no obligation to noindex.
• ✕Trusting third-party authority scoresGoogle says they do not correspond to any of its signals.

FAQ

Sources

• Google Search Central — Spam policies for Google web search (Site reputation policy)
• Google Search Central Blog — What web creators should know about our March 2024 core update and new spam policies
• Google Search Central Blog — Updating our site reputation abuse policy
• Google Search Central Blog — Update to the Site Reputation Policy
• Google Search Console Help — Manual actions report

Quotes checked against the official pages on 30 October 2026.