Overview
Changelog is the history of your listing: what changed, in which market, and when. It records changes made outside Spek too, because it is built from what the store actually holds.
Reading a row
Each row shows the field, the market, and the value before and after. Long text is summarised rather than dumped, with the full version one click away.
Rows the agent authored carry a marker, so you can tell a proposal you applied from an edit you typed. Keyword changes are grouped and show how much of the 100-character field is in use.
Common questions
My next update is missing. Where is it?
A version appears here once you submit it for review. While it is still being prepared (Prepare for Submission), it stays hidden — the changelog is the story of releases, not of drafts.
Confirm the app and version you are checking, then compare the provider state with the available history. A saved Editor draft and a recorded release serve different purposes. If the store was updated outside Spek, the relevant information also needs to be read before it can appear here.
Someone changed the listing in App Store Connect. Will it show up here?
Yes. The changelog is derived from the store's own values, so an edit made anywhere appears once Spek next reads it.
Can I roll a change back from here?
No. The changelog is a record, not a control. Edit the value in the editor and publish again.
How should I use listing history during an ASO review?
Find the field and market you are investigating, then read the before and after values together with the recorded timing. This helps establish what changed before you examine later ranking observations. Keep the distinction between chronology and causation: a ranking movement after a listing edit does not prove that the edit alone caused it. Use Changelog to make the review specific and reproducible for your team, while using the relevant analytics sources for the outcomes you actually want to measure.
Why is Changelog different from the Editor draft?
The Editor holds work that can still be revised before publishing, while Changelog records the store changes and release information described on this page. A draft you saved a moment ago therefore need not appear as a historical release. Check the current app and provider version when an expected entry is missing. If the change was made outside Spek, it also needs to be read from the store before it can appear in the available history.
Can history help coordinate several reviewers?
Yes. Use a specific field, market and before-and-after value when explaining what the team changed. This gives colleagues a shared reference instead of relying on memory or an old screenshot of the whole listing. If you are planning a correction, use the historical text as reference and prepare the actual edit in the Editor. Changelog does not grant access or perform a rollback, and a historical entry should not be treated as approval to publish the same wording again.
What should I check before restoring earlier wording?
Confirm that the earlier text still describes the current app and remains appropriate for the selected locale. Product capabilities, brand language and store requirements may have changed since the historical entry. Compare it with the current draft and provider values, then prepare the desired correction through the normal Editor and publishing workflow. Returning to an older sentence is a new listing decision with current consequences, rather than a way to bypass review because the text was accepted in the past.