Blog

How to create a public changelog page for your product

A public changelog page is a web page on your own site that lists what changed in each release, newest first, so customers can see your progress without asking support or reading a repository. It is the changelog for people who use your product rather than people who contribute to it.

This guide explains why a product needs one, what to put on it, how to keep it current without extra work, and the mistakes that make these pages go stale.

Why publish a changelog page

  • Customers can check what is new. A page with a stable address is easy to link from emails, support replies and the app itself.
  • It answers a common support question. "Did you fix that yet?" becomes a link instead of a conversation.
  • It shows the product is maintained. Someone evaluating your product can see recent, dated releases at a glance.
  • It can be found by search. A page with real release content gives search engines something specific to index.

What to put on the page

Keep each entry short and written for a customer, not for the team that built it:

  1. A version or a date as the heading, so readers can place each entry in time.
  2. A one-line summary of the headline change, in plain language.
  3. A short list of the other changes, grouped as new, improved and fixed.
  4. A clear note for anything that changes how existing users work, placed first.
  5. Optionally, a link to a more technical version for developers.
feat: add pdf export (#142)Changelog · developers## 1.2.0 - 2026-10-12### Added- Report PDF exporter (#142)Complete, dated, terseRelease notes · usersAcme App 1.2You can now save any reportas a PDF from the toolbar.Curated, friendly, explains
One change, two audiences, two voices.

The figure shows the idea behind the last point: one change can be written for developers as a dated list item and for customers as a sentence about what they can now do. The comparison of changelog and release notes shows both voices side by side.

Where the page can live

  • On your own domain, for example under a path such as /changelog or on a subdomain. This is the best choice for brand and for search, because the content sits next to your product.
  • On a hosted page from a changelog tool, which saves you from building and styling the page. Check that it can use your own domain and brand colors if you want it to look like part of your site.
  • In the repository, as a CHANGELOG.md that you link to. This suits developer tools but is harder for non-technical customers to read.

How to keep it current

Pages like this usually die because updating them is a separate chore from shipping. The fix is to make the update part of the release:

  • Add a changelog line when you merge, not weeks later.
  • Write the customer-facing text at release time, from the list of changes, and edit it once.
  • Make publishing one step, so it is not skipped on a busy release day.

The guide on how to write a changelog covers the writing habits, and the GitHub release notes automation setup shows how to get a first draft automatically.

Mistakes to avoid

  • Pasting commit messages. Customers do not read "refactor report service".
  • Skipping dates. Without a date, readers cannot tell whether the page is current.
  • Hiding breaking changes in the middle of a long list.
  • Letting the page go quiet for months. If you slow down, say so rather than leaving it to look abandoned.

ReleaseTale publishes a hosted changelog page from the commits of a release: it drafts the customer version and the developer version, you edit them, and you publish. See the changelog examples to compare the two voices on a sample release.

Frequently asked questions

What is a public changelog page?

A public changelog page is a page on your site that lists what changed in each release, newest first, so customers can follow your progress without reading a repository.

What should a public changelog page include?

A version or date for each entry, a one-line summary of the headline change, a short list of other changes grouped as new, improved and fixed, and a clear note for anything that changes how existing users work.

Where should I host a public changelog page?

Ideally on your own domain, for example under a /changelog path or on a subdomain. A hosted page from a changelog tool saves you building it, as long as it can use your domain and brand.

How do I keep a changelog page up to date?

Make the update part of the release: add a line when you merge, write the customer text at release time from the list of changes, and publish in one step.

Related articles