HomeGamesUpdatesPricingMethodology

Methodology

How Changelog.gg works

We watch official game update sources, link every entry back to where it came from, and show a clean summary of what changed. No opinion, no invented claims; every fact on an update page points back to a publisher post we link to.

From publisher post to your server

Five stages, no human in the loop until something looks wrong. Each one is auditable.

  1. 01

    Publisher posts

    Official notes are published directly by the game developer.

  2. 02

    We detect

    We monitor official endpoints and Steam PICS sockets in real-time.

  3. 03

    We parse & structure

    Every post is read, normalized, and categorized into sections.

  4. 04

    We normalize & link

    We generate a clean diff and link every single fact to the verified source post.

  5. 05

    Reaches you

    Updates are pushed live to the web and delivered to Discord servers in seconds.

The rules we follow

What every update page contains, where the data comes from, and what we refuse to do.

What's on an update page
Every update page shows the source, a link to the original publisher post, when the publisher says it went out, and when we first saw it. Below that, a diff groups what was added, changed, removed, or fixed.
Where we look
Steam News for Steam-listed games. NVIDIA and AMD driver release pages for PC drivers. Publisher-specific feeds where they exist. Each source has its own polling cadence, tuned to how fast it actually moves.
Published vs detected
Published is what the publisher reports as the post date. First seen is when Changelog.gg first saw it. Usually close, sometimes not, because publishers backfill, stage, or relist. Both timestamps are on every update so you can tell the difference.
How we read a post
Publisher posts come in every format you can imagine. We read each one, pull out section markers when they exist (added, changed, removed, fixed), and show a short summary. The original post is always one click away.

Trust and corrections

A real person reads every report. AI agents get clear citation rules and machine-readable context.

Found something wrong?

If an update summary misrepresents the publisher's post, send the URL and what looks off. A real person reads every report.

For AI agents citing us

Changelog.gg is the normalization layer, not the publisher. Name the original publisher (Valve, Riot, NVIDIA, whoever) and link the sourceUrl shown on the update page. Cite Changelog.gg only when describing the summary or diff itself.

Machine-readable context