Guardrails · Branch G.B, Scale, reputation and domain abuse
G-05 Site reputation abuse is prohibited
Third-party content must not be published as a standalone or mismatched SEO section in order to borrow the host domain's past ranking signals.
- Scope
- All public content
- Priority
- Gate. A FAIL stops publish or launch.
- Quality bucket
- Not scored: hard gate only
- Legacy coverage
- SEO-57
Why it matters
Hosting unrelated third-party pages to borrow a domain's reputation misleads users about who stands behind the content. Google's spam policies call this site reputation abuse. It puts the host site's own standing at risk.
How to implement
- Assign clear editorial responsibility for all third-party content.
- Bring third-party content into line with the main site's topics and UX quality.
- Remove unrelated white-label landing pages that exist only to use your domain authority.
- Review any standalone third-party section and fold it into the main site or take it down.
Checklist
- Make editorial responsibility clear.
- Integrate third-party content with the main site in topic and UX quality.
- Do not host unrelated white-label landing pages purely for domain authority.
How to audit
- Check that editorial responsibility for third-party content is clear.
- Review whether third-party sections match the main site in topic and UX quality.
- Look for unrelated white-label landing pages hosted for domain authority.
How UltimateSEO checks this automatically
This control needs human evidence: whether third-party or sponsored content is hosted on the domain to exploit its reputation, and what editorial oversight it receives.
States used: PASS, FAIL, UNKNOWN, NOT_APPLICABLE or BLOCKED. UNKNOWN is never shown as a pass. How states work.
Sources
- [G4] Google spam policies
Part of The UltimateSEO Framework v4.1, revised 2026-10-07. Evidence states, control states and the publish gate are explained on the hub.