SEO guide
Slay the Spire 2 Update Tracker
A Slay the Spire 2 update tracker for players who want the latest patch context, changed rankings, and refreshed guide pages.
Quick answer
Update pages should route readers into patch notes, changed tier lists, and newly affected card or relic pages.

What to check first
Use this page as a practical search-intent answer first, then follow the related database links for deeper card, relic, character, boss, and patch context.
- Summarize what changed in plain English.
- Link to affected tier lists and database entries.
- Mark pages that still need retesting.
What an update page should do
An update tracker is not a duplicate of patch notes. It translates changes into site work: which card pages need new warnings, which relics moved, which boss-prep checks changed, and which tier list entries should be marked provisional.
- Add changed items to the top of affected tier lists.
- Flag stale screenshots or video notes when a patch changes UI or behavior.
- Use community notes to collect early run evidence before changing rankings.
Turn broad update news into page actions
Update videos often mix release timing, balance commentary, strategy news, and community reaction. The page should split those into actions a returning player can use: read the changed system, check the affected tier list, and watch for pages that are still waiting on run evidence.

- Use update news to refresh internal links between patch notes, roadmap, and tier lists.
- Add review-needed labels when a video raises a question without enough current proof.
- Keep old screenshots only when they are clearly labeled as historical footage.
Newsletter clips belong beside roadmap caveats
Developer-letter and newsletter coverage is helpful for readers who search updates, but it needs caveats. When the source points toward future content, the update page should explain what is known now, what is only being watched, and which guide pages will change if the official build confirms it.

- Point confirmed changes to patch notes first, then affected database pages.
- Point speculative content to roadmap and FAQ pages with a visible caveat.
- Use discussion submissions to collect timestamped evidence after the update lands.
Editorial note
This page is part of the first English-only content batch. It is written conservatively for Early Access and should be tightened whenever a major patch changes public information or run data.