Turn your changelog into pages that rank
· 1 min read
The short answer: give each meaningful change its own page with a descriptive title, a short explanation and a date, then link those pages from a changelog index. One long page buries your best content. Many focused pages let each change be found on its own.
The problem with one long changelog
A typical changelog is one page with dozens of entries. Search engines see one page about many things, so it's hard to rank for any of them. When someone searches "does [product] export to CSV", the entry that answers it is lost halfway down.
Give important changes their own page
Not every bug fix needs a page. New features, integrations and big improvements do. For each one:
- write a title the way a customer would search for it
- explain who it helps in two or three sentences
- add the date and the product name
- link to the docs or the feature itself
Keep an index
Your changelog page becomes a list of short entries, each linking to its full page. Readers get an overview, and every update still has a page of its own.
Label the changes
Labels like new feature, fix, improvement and integration help readers scan, and they let you build filtered views later, such as every integration you've shipped.
Make sure they're crawlable
Add every update page to your sitemap and avoid loading entries only through JavaScript after a click. If a crawler can't see it, it can't rank.
How commiToday handles it
On commiToday, every update is its own page with a label, a date and the project behind it, and the live feed works as an index across all of them. It's the changelog structure above, without building it yourself.
The takeaway
Your changelog is a list of answers to questions people search for. Give each answer a page.
