Glossary
What is a changelog?
A changelog is a dated, public list of changes to a product: new features, improvements and fixes. For users it shows the product is alive; for marketing it's a steady source of small announcements, relaunch material and fresh content that search engines and directories can pick up.
What to include
- Date and version (if you use versions).
- What changed, in user terms: "You can now export to CSV".
- Why it matters or who asked for it.
- A screenshot or short clip for bigger changes.
- Links to docs.
The Keep a Changelog convention groups entries as Added, Changed, Deprecated, Removed, Fixed and Security.
Marketing uses
- Monthly update emails built from changelog entries.
- Social posts for notable features.
- Directory listing updates with new screenshots and features.
- Material for a relaunch or launch week once enough has changed.
Example
A startup publishes a changelog entry every week. After three months, the list of 12 shipped features becomes its relaunch on Product Hunt, and evaluators comparing tools mention the visible pace of updates.
Where to host it
A /changelog page on your site, linked from the footer and the product, works well. Some teams also post updates in-app or through a dedicated changelog tool. Keep entries public and dated so evaluators and AI systems can see how actively the product improves.
FAQ
How often should a changelog be updated?
Whenever you ship something users notice; weekly or monthly is common.
Should bug fixes be in the changelog?
Notable ones, yes, in plain language.
Does a changelog help SEO?
Modestly, by adding fresh, linked content; its bigger value is for users.
Should a changelog include dates?
Yes; dates are what show activity.