Site reputation abuse penalty — diagnose third-party content risk

70-100% subfolder traffic loss in a discrete event tied to the May 7, 2024 site-reputation-abuse policy is the surgical-strike pattern: one subdirectory (frequently /coupons/, /reviews/, /best/, /casino/, /loans/, or a partner-content subfolder) collapses while the rest of the domain is untouched. If a manual action has been issued, you'll see it in Google Search Console under Security & Manual Actions with the description "Third-party content abuse," published at https://developers.google.com/search/docs/essentials/spam-policies. If it's algorithmic, there's no notification — the drop just happens, usually within 48 hours of a public Google announcement about site reputation abuse enforcement. The remaining giveaway is that the affected subfolder's URLs lose impressions across all queries simultaneously, not just commercial ones.

White-label coupon, deals, or affiliate content from a third-party provider

A common pattern: a publisher signs a deal with a coupon syndicator or affiliate network, who provides programmatic content under /coupons/ or /deals/. The publisher takes a revenue share; the partner gets reputation lift from the host domain. This is the textbook definition of site reputation abuse and is the first pattern Google hunts.

Sponsored or partner directories sitting under /best-of/, /reviews/, or /partners/

Even when the host has editorial oversight, if the content is functionally produced by or for a third party with minimal first-party review, it falls under the policy. The test Google applies is whether a reasonable user would understand the content represents the host site's editorial voice and standards.

Template-generated location pages produced by a vendor on the publisher's domain

City-by-service pages ("plumbers in {city}", "dentists in {city}") generated by a SaaS vendor and hosted on a media or directory site's primary domain are an emerging enforcement target. The vendor's template plus the publisher's authority is exactly the asymmetry the policy targets.

User-generated content sections that have evolved into commercial pages

Forums, classifieds, or community sections that started as UGC but now host structured listings, affiliate links, or merchant-supplied descriptions can trip the policy. The line is whether the content's primary value is from your community or from a commercial partner using your community as a hosting layer.

1. 1

   Check Search Console → Security & Manual Actions for the explicit "Third-party content abuse" notice. If present, you have a deadline to respond and a defined reconsideration path.

2. 2

   Segment your traffic by URL prefix and find subfolders with anomalous quality patterns: high publisher-domain authority, low-edit-effort content, and commercial intent concentrated in templates.

3. 3

   List every third-party content arrangement on the domain: coupon networks, affiliate networks, vendor-hosted location pages, syndicated press releases, sponsored editorial. If you can't list them, find the contracts.

4. 4

   Run pseolint on the affected subfolder — the spam/template-coverage, spam/template-diversity, content/missing-author, and content/eeat-signals findings will quantify how machine-generated and unsigned the content reads.

5. 5

   Verify byline accuracy and editorial oversight: does each page have a real author who actually reviewed it, or is the byline a partner brand or a generic "Editorial Team"?

6. 6

   Decide per-arrangement: end the partnership, move the content to a separate subdomain or domain owned by the partner, or invest enough first-party editorial review to credibly own the content. There is no fourth option.

7. 7

   Document the editorial process for any third-party content you keep — the documentation matters both for reconsideration requests and for surviving the next enforcement wave.

pseolint findings most strongly correlated with this pattern.

A regional newspaper hosted /coupons/ as a revenue-share partnership with a national coupon syndicator — 14,000 URLs, ~12% of total organic traffic. After a March 11, 2024 manual action for site reputation abuse, the publisher migrated the coupon content to a subdomain owned by the partner (coupons.partner.com), 301-redirected the old URLs, and applied for reconsideration on March 18, 2024. The manual action was lifted in 23 days; the rest of the site never lost traffic. Coupon revenue dropped to roughly 30% of prior levels (an estimated $42,000 monthly hit) because the subdomain didn't inherit the publisher's authority — which was the point of the enforcement.

Manual-action timelines are bounded: reconsideration requests are typically reviewed within 14 to 28 days of submission, and the action is lifted as soon as Google's reviewer agrees the underlying practice has ended. Algorithmic demotions take longer because there's no human in the loop — the demotion lifts when Google's next crawl confirms the third-party content is genuinely gone or restructured. Plan for 30 days from fix to algorithmic lift and 60 days from fix to traffic stabilization on the subfolder. If you noindex rather than restructure, the subfolder may never recover; it stops being a liability but it also stops being an asset. Revenue forecasting should assume the affected subfolder operates at 20-40% of its pre-enforcement contribution permanently — Ahrefs and Semrush historical data on the November 5, 2024 enforcement wave show median post-restructure subfolder traffic stabilizing at 35% of pre-action baselines.