Skip to content

Trust documentation · 2 of 4

Traffic validation • Topic fit • Spam screening • Ongoing review

How publisher approval actually works behind the scenes.

This page explains the evaluation logic behind publisher approval and rejection. If the standards page defines the quality bar, this methodology shows how a domain gets tested against it before it ever reaches client review.

Executive summary

The four gates most buyers want to understand first.

Traffic gate

Verifiable organic visibility

A domain does not pass on DA or DR swagger alone.

Relevance gate

Topical and audience fit

The same domain can fit one campaign and fail another.

Risk gate

Spam-footprint exclusion

Serious PBN, link-farm, and penalty signals trigger rejection fast.

QA gate

Approval is never permanent

Qualified sites are still monitored and can be removed later.

Use this page for

Approval-logic due diligence

Read this when you want to know how approval or rejection decisions are made.

Read first

Sections 1, 2, and 3

Those sections explain the fastest trust questions: traffic, fit, and spam-risk filtering.

Best next page

SLA or refund policy

Once approval logic is clear, most buyers confirm commitments and remedies.

1) Organic visibility validation

The first job is determining whether a domain has real search trust rather than metric cosmetics. Traffic is not the only signal, but it is the fastest lie detector in the room.

  • Independent tool validation: approval does not rely on screenshots or publisher self-reporting.
  • Trend review: stable or improving visibility matters more than a flattering snapshot.
  • Traffic value context: the commercial shape of the keyword footprint matters, not just raw visit estimates.

2) Topical-fit review

A placement should feel native to the site. That means reviewing the publisher’s existing topics, audience overlap, ranking footprint, and whether the proposed angle belongs on the domain.

  • Existing editorial themes should support the client topic directly or credibly indirectly.
  • The audience should plausibly care about the subject.
  • A topic that feels bolted on fails, even if the metrics are otherwise attractive.

3) Spam and network-risk screening

We actively look for disqualifying patterns instead of merely preferring cleaner sites. That includes:

  • PBN signals: ownership clustering, recycled templates, circular linking, or synthetic publishing behavior
  • Link-farm signals: excessive outbound commercial links, monetization-first publishing, irrelevant article sprawl
  • Penalty signals: manual actions, severe algorithmic loss, toxic backlink profiles, or unexplained collapses
  • Deceptive behavior: cloaking, sneaky redirects, doorway structures, or manipulative UX patterns

One serious failure is enough. This is not a weighted average where a pile of pretty metrics erases obvious risk.

4) Editorial plausibility

Beyond metrics and risk screening, the domain should also pass a plausibility test: would a reasonable reader believe the final article belongs there?

  • Recent-content coherence: the site should already publish within the relevant thematic neighborhood.
  • Commercial believability: the angle should not read like a forced placement wearing an editorial mustache.
  • Page-level intent: the final destination should make sense relative to the publisher article.

5) Ongoing monitoring

Approval is not permanent. Once a site is part of active inventory, it remains subject to later review. Material deterioration can move it out of rotation and may trigger replacement handling if it affects a live placement within the coverage window.

6) What fails automatically

Examples of immediate or near-immediate rejection include:

  • Passing only on DA/DR without real search visibility
  • Self-reported evidence without external verification
  • Clear network manipulation or penalty risk
  • Topical mismatch severe enough that the final placement would look artificial
  • Past approval on a site that has since declined materially

This page explains how sites get approved. The next document in the diligence sequence is the Service Level Agreement, which explains what happens after approval translates into delivery.