Can a changelog page tell AI what your product can do now?
It can supply material, but no official source says AI reads it specifically. We found no OpenAI, Anthropic or Perplexity documentation saying they crawl or prefer changelog pages, so that point is unverified. Only the first two rows of the table below can be checked; the last two rows are inference, so do not write them into your page as fact.
| Argument | Why | Status (2026-11-07) |
|---|---|---|
| Dates should be visible to both readers and crawlers | Google's byline date guidance: label dates with words such as Published or Last updated, and keep dates in structured data consistent with the visible ones | Checked |
| Software versions and release notes have standard properties | schema.org SoftwareApplication has softwareVersion (version of the software instance) and releaseNotes (what changed in this version, as text or a URL) | Checked |
| A changelog can answer “does it support X now?” | A dated entry is easier to verify than the sentence “the latest version supports it”. This is our inference; no official source says so | Inference |
| AI search reads changelog pages specifically | We found no statement from the three AI companies or from Google | Not verified |
So the value of a changelog page is mainly this: it is a text page, output directly by the server, dated, with one fact per entry (the body must be server-rendered; see Do AI crawlers render JavaScript? for why). When someone asks “what changed recently and can it do X now?”, you have an authoritative source that can be pointed to.
How should a changelog page be structured?
Keep a Changelog is the most cited format convention (checked 2026-11-07), and its principles can be used as they are:
| Element | How to write it | Source |
|---|---|---|
| Order | One entry per version, newest first | Keep a Changelog |
| Date | Give each entry its release date in ISO 8601 (2026-11-05), largest unit first, to avoid confusion between regional formats | Keep a Changelog |
| Categories | Group similar changes: Added, Changed, Deprecated, Removed, Fixed, Security | Keep a Changelog |
| Upcoming | An Unreleased section at the top, merged into the new version on release | Keep a Changelog |
| Linkable | Each version has its own anchor (id) so it can be cited on its own | Keep a Changelog |
| Who is affected | State who each entry affects (all plans, one platform, one region). This one is Pagent's practice, not a Keep a Changelog requirement | Pagent |
Put the result first and the detail after, one thing per entry. Below is a structure you can copy (the data is placeholder):
<h1>Changelog</h1>
<ol>
<li id="v2-4-0">
<h2>2.4.0 <time datetime="2026-11-05">2026-11-05</time></h2>
<h3>Added</h3>
<ul><li>CSV export now includes the "plan" column.</li></ul>
<h3>Fixed</h3>
<ul><li>Imports of files over 10 MB no longer time out.</li></ul>
<p>Affects: all plans.</p>
</li>
</ol>
A real example: Pagent's changelog page
Pagent's changelog page (page source read on 2026-11-07) has 3 entries, all dated 2026-10-22: “Rubric v0.1 published”, “Overall score accounts for coverage” and “Scores expire after 90 days”. Its structure is:
| Element | What Pagent does | How to read it |
|---|---|---|
| Date | Each entry uses a time tag whose datetime holds a full ISO time (for example 2026-10-22T12:00:00Z) | Machines can read the date directly |
| Title | One h2 per entry, one sentence saying what changed | The title is the takeaway |
| Description | One or two sentences stating the concrete rule (for example “scores expire after 90 days; older scores still count but are shown in grey”) | Has numbers, can be checked |
| Who is affected | Each entry has an “Affects:” line; all three currently say “All assistants” | Readers know whether they need to care |
| Version numbers and categories | None | Its version appears only once, in the footer: “Rubric v0.1” |
| Structured data | The page's JSON-LD is only the site-wide Organization and WebSite, with no changelog-specific markup | Gap |
| Subscription | No RSS or Atom; the head has a link to llms.txt | Gap |
All three entries have the same date, so the page is still new; we cannot conclude anything about how many citations a changelog page brings, and we have no data on that. Two more comparisons: mochistamp.com/changelog and gammaslide.com/changelog both returned 404 on 2026-11-07, and on 2026-11-07 kagentx added its own changelog page (/changelog/), so of our four sites Pagent and kagentx now have one.
How do you write structured data for a changelog page?
We found no Google documentation with markup specifically for changelog pages, and whether there is a rich result is unverified. What can be checked comes in two layers:
1. The page itself: dates match the visible content
Write “Last updated” and the date on the page, and put the same date in dateModified in markup such as Article; see Does showing an updated date on a page help AI citations? for the rules.
2. The product: SoftwareApplication for the latest version
Put the current version in softwareVersion and point releaseNotes at that version's anchor on the changelog page. This only applies to products that really are software; for anything else, use layer 1 only.
{ "@context": "https://schema.org", "@type": "SoftwareApplication", "name": "ExampleTool", "applicationCategory": "DeveloperApplication", "softwareVersion": "2.4.0", "releaseNotes": "https://example.com/changelog/#v2-4-0" }3. Markup must match the page
The version number and anchor URL must really exist in the page body. For the general principle see Does structured data help AI search?.
How do the changelog, update dates and lastmod divide the work?
These three answer different questions, so do not let one stand in for another:
| Where to write it | Question it answers | Details |
|---|---|---|
| Changelog page | What the product or service changed, entry by entry, on which day, and who is affected | This article |
| The “Updated” date on feature and pricing pages, plus dateModified | Whether this page's content is current | See the page dates article |
| lastmod in sitemap.xml | Which URLs changed and are worth crawling again | See the lastmod article |
How they work together: when you add a changelog entry that changes pricing or features, change the matching feature or pricing page too and update its date (for pricing pages see How should a pricing page be written so AI answers your price correctly?); the changelog page's own lastmod changes as well. For dates see Does showing an updated date on a page help AI citations?, for lastmod see How do you write a trustworthy sitemap lastmod?.
How do I do it, step by step?
1. Create a fixed URL
Use a path such as /changelog/ that is obvious at a glance, put it in the footer and the sitemap, and link to it from feature pages so it has at least two internal entry points; see Do internal links help AI search?.
2. Render the body on the server
Do not pull records from an API and render them with a script. Open the page in a browser with JavaScript off; if the records are still there, it passes.
3. Four fixed fields per entry
A date (a time tag with an ISO date), a one-sentence title, what changed (with a number or a rule), and who is affected.
4. Group similar changes, newest first
Group with labels such as Added, Changed and Fixed; do not write a whole month of changes as one big paragraph.
5. Give each version an anchor
So other pages and answers can link to one specific entry.
6. Add SoftwareApplication if you have a software version
softwareVersion and releaseNotes must match the page body.
7. From now on, write each change on the day it happens
A back-filled date makes the whole page less trustworthy; write the day the change really happened.
A Mac app's changelog should stay consistent with its pages on the Mac App Store, Homebrew, Setapp and other channels; see How do Mac apps get recommended by AI?.
FAQ
Will a changelog page raise my chance of being recommended by ChatGPT?
No evidence. We found no official documentation saying AI reads changelogs specifically and have no measured data either, so this is unverified. Its value is giving AI a dated, checkable source of facts.
Does a changelog need version numbers?
For software products, yes; Keep a Changelog's convention is one entry per version. A website or service without version numbers can use dates as titles, as Pagent does with just a date and a title.
What date format should I use?
Keep a Changelog recommends ISO 8601 (2026-11-05). Label it with words on the page and put the full time in the datetime attribute of a time tag.
Do I need an RSS or Atom feed?
We have not verified whether it helps crawlers find new entries; it helps users who subscribe. Pagent has none today, which is one of its gaps.
Should changes in the changelog also change the feature pages?
Yes. If pricing or features changed, change the matching pages and their dates too; otherwise the changelog and the feature page will say two different things.
Sources
- Keep a Changelog · Keep a Changelog 1.1.0 (checked 2026-11-07)
- Google Search Central · Add a Byline Date to Google Search Results (checked 2026-11-07)
- schema.org · SoftwareApplication(softwareVersion、releaseNotes) (checked 2026-11-07)
- Pagent · Changelog (Page source, read 2026-11-07)
- kagentx evaluations: the data on the case study pages; each example gives its date.