Automatic listing updates

Set it up after claiming

First claim your resource through the DNS TXT or signed HTML proof in GG Atlas. Once the claim is verified, use the tailored setup panel on your resource page to copy a version of this file with your resource and game identifiers already filled in.

Publish location

Serve the file from this exact path on your canonical resource host:

Use HTTPS, public access, and an application/json content type. Do not include credentials, internal addresses, visitor data, or other non-public operational information.

JSON file

{
  "schemaVersion": 1,
  "listing": "your-resource-slug",
  "supports": [
    {
      "game": "poe2",
      "version": "0.3",
      "language": "en",
      "server": "global"
    }
  ]
}

schemaVersion

Use 1 for this format.

listing

Your resource slug from its GG Atlas URL, for example https://ggatlas.app/tools/your-resource-slug.

supports

Add one statement for each game and support scope you need to keep in sync.

game and version

Use the GG Atlas game slug and the exact game version, patch, or release label you support. Omit version only when support is not version-specific.

language and server

Optional support scope, such as en and global. Omit either field when it does not apply.

Keep it in your release flow

Update and deploy this file whenever you release support for a new game version or change a supported language or server. GG Atlas reads it separately from reachability checks and shows the resulting update as a maintainer statement, not an independent endorsement.

CDN and WAF rules

If your CDN or WAF blocks automated requests, allowGGAtlasHealth/1.0 (+https://ggatlas.app) for your normal resource URL and GGAtlasCompatibility/1.0 (+https://ggatlas.app) only for the/.well-known/ggatlas-resource.json file. Restrict any bypass to the relevant public path rather than creating a broad rule.

Website HTML claim files are also requested withGGAtlasHealth/1.0. GG Atlas monitoring uses public Fargate egress addresses that can change, so do not use a fixed IP allowlist.

GitHub repository resources

A resource whose listing source is a GitHub repository does not publish this JSON file or a .well-known path. GG Atlas instead checks GitHub's fixed repository metadata API during normal monitoring to record whether the repository exists, is archived, its default branch, and its latest push day.

This automatic repository observation is separate from ownership and game-version support. Claim a repository with the signed.github/ggatlas-claim.txt file shown in the claim flow. Repository metadata does not infer that a project supports a particular game version, and GG Atlas does not read repository source code or GitHub HTML pages.

Repository claim verification uses GitHub's API withGGAtlasClaim/1.0 (+https://ggatlas.app); no CDN or domain configuration is needed for that path.