Site Reputation Abuse 2026: Policy and Audit

Administrator in Search Engine Optimization Sep 25 / 3 weeks ago

On August 28, 2026, Google published a short blog post that split one spam policy in two. From August 30, a manual action for site reputation abuse still hits a coupon or casino section in results shown to a reader in New York or London. For a reader in Paris or Berlin, the same action now changes nothing. The policy did not go away. It gained a border.

That border matters to anyone who runs a publisher site, sells space on one, or advises someone who does. Google's spam documentation now calls the rule the "site reputation policy". It uses the older name only once on the whole page. Searchers still type the older name, so this guide uses both. Below you get the full history with dates taken from the source pages, the four factors a human reviewer weighs, and the three examples Google published. You also get two more examples I made up to test the logic, and a checklist you can run on any section of your site this week. No tool required, just a browser and Search Console.

What is site reputation abuse, and why does Google now call it the site reputation policy?

Site reputation abuse is the practice of placing third-party content on an established site so that it ranks on the host's earned signals rather than its own. Google's spam policies page now titles the rule the site reputation policy. It defines the rule around motive: the content sits on the host mainly because of the host's ranking signals. The name changed. The behavior it targets did not.

The current wording on the Google spam policies page reads: "The site reputation policy applies where third-party content is published on a host site mainly because of that host's already-established ranking signals, which it has earned primarily from its first-party content." Third-party content means work created by a separate entity. Google names users, freelancers and white-label services as examples.

The same page says: "Having third-party content alone isn't inconsistent with the site reputation policy". Two things must be true at once. Someone else made the content, and it sits on your domain to borrow your rank. Remove either half and the rule does not apply. Practitioners call the tactic parasite SEO. That older label still describes the mechanics well.

How did the site reputation abuse policy change between 2024 and 2026?

Google announced the policy on March 5, 2024. It enforced the policy from May 5, 2024. On November 19, 2024 it removed the first-party oversight exemption. The European Commission opened proceedings on November 13, 2025. On August 28, 2026 Google announced that from August 30 manual actions would not affect results shown inside the EEA. Six dates, one steady direction, then a regional turn.

1. March 5, 2024. The Search Central Blog announced three new spam policies alongside the March 2024 core update. The first wording targeted third-party pages published "with little or no first-party oversight or involvement". The post said "this new policy will take effect starting May 5, 2024".
2. May 2024. Search Engine Roundtable reported on May 7, 2024 that enforcement had begun the night before. Barry Schwartz listed coupon sections at CNN, USA Today and the LA Times among the first hit. He also noted that Forbes had removed its coupon directory ahead of time.
3. November 19, 2024. Google rewrote the definition: "Site reputation abuse is the practice of publishing third-party pages on a site in an attempt to abuse search rankings by taking advantage of the host site's ranking signals." The post added that "no amount of first-party involvement alters the fundamental third-party nature of the content". The oversight loophole closed that day. FAQs followed on December 6, 2024, and an editorial pass on January 21, 2025.
4. January 2025. Search Engine Roundtable reported on January 23, 2025 that manual actions had reached coupon sections in Italy, Spain and France. Germany was added in an update to the same report.
5. November 13, 2025. The European Commission formally launched proceedings under the Digital Markets Act. It cited "indications that Google, based on its 'site reputation abuse policy', is demoting news media and other publishers' websites and content in Google search results when those websites include content from commercial partners".
6. August 28, 2026. Google announced the EEA split, effective August 30. The rest of this guide lives in that world.

What exactly changed on August 30, 2026 for searchers in the EEA?

For users outside the EEA, a manual action still directly affects results for the section involved. The rest of the site is untouched. For users inside the EEA, the action has no ranking impact. Instead, Google may categorize the section as separate from the main domain so it ranks on its own merits over time. The notice in Search Console arrives either way.

The August 28, 2026 blog post opens with "Following discussion with the European Commission". It states that "Beginning August 30" manual actions "will have a different effect for those searching in the EEA than outside of it". The EEA means the 27 EU member states plus Iceland, Liechtenstein and Norway.

The table below takes each outcome from the current policy section and the August 28, 2026 post and sorts it by user location. Cells use Google's own wording wherever they quote anything.

Pages with a global audience get both rows at once. The blog post says so directly: "Because many pages are viewed by people globally, it's possible that any given page might have a manual action taken on it, but that change will only affect search results shown to users outside the EEA."

Does the EEA carve-out make parasite pages safe in Europe?

No. I think anyone selling that idea is reading the headline and not the FAQ. Inside the EEA the section escapes the manual action. Google may still categorize it as separate and rank such sections "on their own merits". The whole tactic depends on borrowed signals. Once the section ranks alone, the borrowed lift can evaporate without any penalty ever being applied.

Google's FAQ explains what categorization does. It tells the ranking systems that the usual presumption, that every page matches the quality of the rest of the domain, "no longer applies". The page adds: "This doesn't mean that the separate portion of the site immediately loses the ranking signals of the main site." Over time, though, the systems "learn to rank these parts of a site independently". The carve-out changes the penalty for site reputation abuse in Europe. It does not change the economics.

Google has not softened its tone either. Search Engine Roundtable quoted a Google spokesperson on August 28, 2026: "Our European users are no less frustrated by parasite SEO and other deceptive, pay-to-play tactics that degrade search results". My advice is to treat the EEA as a place where the penalty is quieter, not absent.

What are the four factors a Google reviewer weighs?

Google names four objective factors: how the content is presented, its quality against the main domain, its stated or implied authorship, and whether it appears on multiple other sites in identical or near-identical form. The page adds that "not one of these factors is either necessary or sufficient on its own". Reviewers weigh the mix. Other evidence can enter the picture.

The stated goal of a review is to judge whether the section was "created with sufficient input, editorial oversight, or contribution from the host site to be considered fully integrated with the main site". The page says "This review applies globally". The factors are the same in Ohio and in Lyon. Only the consequence differs. Here is how I would check each one myself.

• Presentation. Open a page from the section and a page from the main site side by side. Same header, fonts, navigation and footer? If a visitor could not tell it is the same site, a reviewer will notice too.
• Quality. Look for problems the main site does not have: thin text, broken layouts, stock filler, no dates, no contact route.
• Authorship. Is there a named author or a named responsible editor? Our guide to real bylines, bios and editorial responsibility covers what a credible byline looks like.
• Duplication. Paste a distinctive sentence into Google in quotes. If it appears on ten other domains, read our explainer on cross-domain canonicals and syndicated content before you decide what to keep.

Which third-party content does the site reputation abuse policy leave alone?

Google lists six kinds of third-party content it does not treat as inconsistent: wire and press release services, syndicated news between publications, user-generated content such as forums and comments, editorial columns and opinion pieces, advertorial written to reach the publication's own readers, and affiliate links or ad units handled appropriately. The list is non-exhaustive. Motive decides, not format.

The two examples Google calls inconsistent show the other side. One is an educational site hosting a sponsored payday-loan review that the same third party distributes across the web. The other is a medical site hosting a low-quality "best casinos" page that is not integrated with the site. Both pair unrelated content with a borrowed domain.

Forum threads and comment sections sit on the safe side. Our guide to the kinds of user-generated content that build authority covers what belongs in that bucket. Affiliate work sits on the safe side when it is disclosed and treated appropriately. The November 2024 FAQ says plainly that "the policy is not about targeting affiliate content". Our guide to what Google actually bans in affiliate SEO goes deeper on the added-value test. Paid placements are safe on the same terms, disclosed and written for the host's own readers. Our post on disclosing sponsored links with the right rel attribute explains the mechanics. Keep this policy separate in your head from its March 2024 sibling. Our piece on scaling pages without tripping the scaled content abuse policy covers that one.

What do Google's three worked examples actually mean?

Google published three cases. An integrated coupons section built with a specialist partner, disclosed and curated, is unlikely to draw action. An unauthored CBD-oil affiliate article on a business publication, copied from a marketplace and reachable from no menu, is likely to draw action outside the EEA. A freelancer's authored cooking section with clear editorial responsibility is unlikely to draw action.

Read the coupon case closely. It is generous. The section runs "on a different CMS than the main site", and "some of the codes may be available elsewhere". Neither fact counts against it. What saves it is integration. That means categories specific to that publisher, disclosure of the commercial character, a named editorial team, codes referenced in newsletters and articles, and a reporting link for bad codes. The section is also reachable from the homepage. Our guide to keeping every important page within three clicks of the homepage is the practical version of that point.

The CBD case fails on all four factors at once. No author, no editor, no disclaimer, no menu link, and text "purely duplicating" a marketplace.

What would a US local-news site and a French publisher look like under the policy?

Imagine two publishers with the same partner-built coupons section. A city daily in Ohio serves mostly US readers. A manual action would hit the section for nearly its whole audience. A regional daily in Lyon serves mostly EEA readers. The same action would change almost nothing they see, though the section could still be categorized as separate and lose its borrowed rank.

For example, the Ohio paper launches a deals folder from a white-label provider. No byline, no link from the homepage, and codes that match those on forty other newspapers. Three of the four factors point the wrong way. The fix is not to delete the section. It is to give it an editor, a disclosure, and a place in the menu. Add a curated set of local offers the provider does not ship to everyone else.

For example, the Lyon paper builds the same section. Its own team writes the category pages, signs them, and cross-links them from its shopping coverage. That resembles Google's first example. I would expect no action anywhere.

How do you audit a site for site reputation abuse this week?

Run five steps in roughly half a day. Find every section a third party built, using site: and inurl: queries. Score each section against the four factors. Check whether the content exists elsewhere in the same form. Confirm disclosure, authorship and navigation. Then decide to integrate, isolate, or remove. Write down the reasoning so a reconsideration request later has evidence to cite.

1. List the sections, about 45 minutes. Search site:yourdomain.com with inurl:coupons, inurl:deals, inurl:promo, inurl:casino, inurl:loans and inurl:review. Large sites forget folders. Our guide to scoping a single site section with site: and inurl: shows the exact query patterns.
2. Ownership, about 30 minutes. For each folder, write down who produced it, under what contract, and who at your company edits it. If the answer is "nobody", you have found the risk.
3. Factor scoring, about 60 minutes. Give each section a plain yes or no on presentation, quality, authorship and duplication. Two or more failures is my threshold for action.
4. Duplication check, about 30 minutes. Quote-search three sentences per section. A section that lives on other domains in the same form needs original curation or it needs to go.
5. Decision and record, about 45 minutes. Integrate what serves readers, remove what does not, and save screenshots of the before state. Our guide to deciding whether a page earns a refresh, a merge or removal gives the position and impression thresholds for that call. Do not judge risk by a third-party score. Our explainer on why Domain Authority is a third-party estimate and not a Google signal explains why that number tells a reviewer nothing.

What happens when the manual action arrives, and what does the notice say?

Google notifies you in the Manual actions report and the Search Console message center. The help page entry is titled "Site reputation policy" and begins: "Google has detected that a portion of your site is inconsistent with our spam policy on site reputation." Fix or remove the section, then file a reconsideration request. EEA sites get a faster answer and access to alternative dispute resolution.

The same help entry now carries one more line: "The impact of the manual action doesn't apply to search results shown to users in the European Economic Area (EEA)." So the notice looks the same for a Dallas site and a Dublin site. Only the map behind it differs.

I will not restate the recovery workflow here. Our manual actions recovery guide and its advice on writing a reconsideration request already cover evidence, tone and timing. If you have never opened the report, our practitioner walkthrough of the main Search Console reports shows where it lives.

Does noindex or moving the content fix the manual action?

Noindex alone does not lift the action. Google's November 2024 FAQ says you still need to reply in Search Console and explain that the content is noindexed. Moving the section to a subdomain or subfolder on the same domain does not resolve it. It may look like circumvention. A new domain with no reputation is far less likely to be an issue.

The FAQ also warns against two habits. Do not redirect the old URLs to the new home. Google says that "may introduce the site reputation abuse issue again". If you link from the old site to the new one, use nofollow. Moving the content to another established site can simply move the problem with it. If you go the noindex route, the tag must be readable. Our guide to applying noindex on a page that stays crawlable covers the trap of blocking the crawler first.

Two more notes. Our redirect mapping and URL inventory playbook is the right process for a clean move, minus the redirects in this one case. And a fresh domain starts from zero. Our post on how long a brand-new domain takes to earn rankings quantifies that.

How do you measure whether the policy is moving your traffic?

Split Search Console by country before you conclude anything. Put EEA countries in one bucket and the United States, the United Kingdom and Switzerland in another. A section that falls in the US bucket while the EEA bucket holds fits a manual action after August 30, 2026. A fall in both buckets points somewhere else. Compare fixed matched weeks, never rolling windows.

Our post on measuring EEA versus control-country traffic with fixed calendar blocks already lays out the baseline method. It also warns that the September 8, 2026 layout changes overlap with this policy. I will not repeat it. Two supporting habits help. Our hreflang guide explains why you should split reporting by country from day one. Our decision tree for diagnosing an organic traffic drop rules out tracking and seasonality before you blame any policy.

One caution on the EEA side. Policy categorization "isn't automatic", "isn't used as a ranking signal", and comes with a Search Console notice. The separate section-independence systems from the November 2024 post come with no notice that Google describes. A slow slide in a section's EEA rankings with no notice is consistent with those systems. It is also consistent with plain competition. Hold that theory loosely.

Where does the site reputation abuse policy go from here?

My prediction is that the split holds for years. That is because it came out of a Commission proceeding rather than a product decision. Outside the EEA, expect the same manual actions as 2024 and 2025. Inside it, expect quiet categorization to do the work a penalty once did. The safest section is one that would survive on its own domain.

Return to the reader in Paris and the reader in New York. From August 30, 2026 they can see different results for the same coupon page on the same publisher once a site reputation abuse action lands. Google closed the blog post with "We are committed to our site reputation policy". The Commission's own notice said the policy "appears to directly impact a common and legitimate way for publishers to monetise their websites and content". Both statements are still true. The border between them is where you now operate.

If you do one thing today, run the first step and list your sections. Ten site: queries will tell you whether you have a section you forgot about. Then ask the only question that matters: would this content deserve its rank on a domain nobody had heard of? Which of your sections would you be nervous to answer that for?

Frequently asked questions about the site reputation policy

Is site reputation abuse the same thing as parasite SEO?

In practice, yes. Parasite SEO is the industry name for renting space on a strong domain so that weak content ranks on borrowed signals. Site reputation abuse was Google's name for the same behavior from March 2024. The spam policies page now titles the rule the site reputation policy. The Google spokesperson quoted by Search Engine Roundtable on August 28, 2026 used the phrase "parasite SEO" directly. Whatever you call it, the test is motive: does the content sit on the host mainly to borrow its rank?

Does the policy apply to affiliate content?

Not by itself. Google's November 2024 FAQ says "the policy is not about targeting affiliate content". The spam policies page lists affiliate links treated appropriately among the examples that are not inconsistent with the rule. The risk appears when a third party supplies an entire affiliate section that has no author, no disclosure, no place in the menus, and copies that exist on other domains. That is the CBD-oil example Google published. An affiliate page your own team writes, signs and discloses is a different animal.

Is the site reputation policy enforced by an algorithm or by people?

Google's page says a site "will be subject to human review" if a portion looks out of line. The consequence outside the EEA is a manual action. Both are human steps. Google also runs separate systems that treat starkly different sections of a site as standalone sites, described in the November 2024 post. Those are automated. Some commentators fold the two together and call the policy algorithmic. Google's own text keeps them apart, so I would too. Do not assume a quiet drop is a policy action.

Does the EEA carve-out cover the United Kingdom?

No. The EEA consists of the 27 EU member states plus Iceland, Liechtenstein and Norway. The United Kingdom is not a member, and neither is Switzerland. Google's policy page and August 28, 2026 blog post say nothing specific about the UK. The consequence follows from the definition alone. A manual action applies to results shown to users in London exactly as it does to users in Los Angeles. A UK publisher with a large French or German readership sees the carve-out only for that slice of its audience.

Will a manual action outside the EEA hurt my rankings inside it?

Google's FAQ answers this with one word, "No", and then explains. Manual actions under the policy outside the EEA affect only results shown outside the EEA. The fact that a section carries an action elsewhere "isn't used as a signal for ranking that content within the EEA". There is also no obligation to noindex the affected content for EEA purposes. Failing to do so is not treated as an attempt to evade the policy. The section can still be categorized as separate inside the EEA on its own account.

What happened to manual actions Google had already applied in the EEA?

The policy page says Google "will lift all previous manual actions taken under this policy for pages appearing in search results for users in the EEA". Those pages are no longer demoted for EEA users. Google adds that the earlier action "isn't used as a ranking signal" when ranking the page now. The same pages may be categorized as separate from the main domain going forward. The page stresses that this "isn't automatic". If you had an EEA-facing section under action in 2025, check its EEA rankings against a fixed pre-August baseline.

Can I keep a coupon section on a news site?

Yes, if it is built the way Google's first worked example describes. That section runs on a partner's CMS, and some codes exist elsewhere, yet Google calls action unlikely. The publisher curates the categories, discloses the commercial nature, names an editorial team, links the section from the homepage, references codes in its own articles, and offers a way to report bad codes. Enforcement in May 2024 and January 2025 hit publisher coupon sections, according to Search Engine Roundtable reports on both dates.

How long does reconsideration take?

Google publishes no exact figure. For sites in the EEA, the policy page describes a new reconsideration process. Google says it will "answer requests within a short timeframe and provide more details on the reasoning", and it points to alternative dispute resolution as well. Eligible sites can bring disputes to mediation after a reconsideration request, and the page names no region. Either way, a request that documents what you removed or integrated, with dates and screenshots, is, in my view, far more likely to succeed than one that argues the policy is unfair.

Does freelance content violate the policy?

No. The November 2024 FAQ says freelance content "alone is not a violation". The third worked example on the policy page is a freelancer's cooking section that Google calls unlikely to draw action. The freelancer even sells similar interviews to other publications. What protects the section is that the selection is specific to the host, the site brands it consistently, states editorial responsibility, and names the freelancer as author. The same freelancer dumping the same articles on five domains with no editor would fail the duplication and authorship factors.

Does Google use Domain Authority or a similar score to decide?

No. Domain Authority is a Moz metric. Google's March 2024 post said outside "reputation" or "authority" scores do not correspond to any of its own signals. The policy speaks of a host's "already-established ranking signals", which Google measures internally. A high third-party score does not make a section a bigger target. A low one does not make it safe. Reviewers look at the four factors and the motive behind the placement. Spend your audit time on presentation, quality, authorship and duplication, not on a number from a browser extension.