Verification method

A label is only useful when you can inspect the proof.

Our publish gate combines first-party evidence, Discord guild identity, dated health checks, and a clear removal path.

01

Discover the game

Release feeds, trend signals, Search Console, and permitted public sitemaps can create a candidate. A candidate is not a listing.

02

Find first-party proof

We look for the invite on a website controlled by the game or publisher. Third-party directories cannot prove an official claim.

03

Match the guild

The invite must resolve to the expected stable guild ID. A changed destination stops publication and triggers review.

04

Recheck and record

Each page shows a dated snapshot. Failed checks are quarantined or delisted instead of being silently presented as current.

Source policy

What automation can and cannot do.

Allowed

  • Use first-party game and publisher pages
  • Monitor sitemaps permitted by robots and terms
  • Normalize game entities and Discord invite codes
  • Check already collected invites and expected guild IDs
  • Publish zero pages when proof is incomplete

Not allowed

  • Copy invites or descriptions from competing directories
  • Scrape Discord messages, members, or private data
  • Call owner-claimed communities official without brand proof
  • Create one page for every keyword variation
  • Hide a stale snapshot behind a real-time claim
See a problem?

Report unsafe, impersonating, or outdated listings with a supporting source.

Report a listing