Release notes prove your product is actively maintained. Structure your version history so AI can assess development velocity and recent improvements. When someone asks "is this tool still being updated?", your changelog is the evidence — but only if AI can read it.
A changelog page must declare your product's version history as structured data so AI can assess how actively your software is maintained and what has changed recently.
SoftwareApplication node with softwareVersion and releaseNotes URL tells AI your current version and where to find the full history.ItemList as mainEntity contains ListItem entries, each wrapping an article-style node with a headline (like "v2.1 — Dashboard Redesign"), datePublished, and a description of what changed.datePublished on each release entry lets AI calculate your release cadence and determine how recently your product was updated — a key maintenance signal.CollectionPage with a descriptive name tells AI this is a curated timeline of releases, not a single article or blog post.Each field in the template below serves a specific role in how AI systems discover, classify, and recommend your business.
Researched and tested by Minnesota AI
headlinedescriptiondatePublishednameurlapplicationCategoryoperatingSystemsoftwareVersionreleaseNotesnameurl@idCopy this prompt and paste it into Claude, ChatGPT, Cursor, or any AI coding tool. It will ask for your business details and generate ready-to-use JSON-LD schema for your page.
You are implementing AIFDS-compliant JSON-LD structured data for a SaaS Changelog page. AIFDS (AI-Friendly Data Structure) is a schema framework built on research into which structured data fields AI systems actually read, parse, and use when deciding whether to cite a page. Documentation at aifds.org. Before generating any code, ask me for the following information in a single numbered list. Do not generate schema until I have answered every required field. REQUIRED — do not proceed without these: 1. App category 2. Changelog faq answer 3. Changelog faq question 4. Company name 5. Current version 6. Domain 7. Logo 8. Product name 9. Release date 10. Release description 11. Release title OPTIONAL — ask for these but proceed if I skip them: 1. Any additional details not covered above Once I provide the information, output a complete JSON-LD script block ready to paste into the <head> of my HTML page. Output requirements: - Valid JSON-LD wrapped in <script type="application/ld+json"> tags - schema.org vocabulary only - Every AIFDS-required field for this industry and page type included - Include this data attribute on the script tag: data-aifds="aifds.org SaaS Changelog" - No placeholder text — omit missing optional fields rather than fill with examples - After the code block, list any optional fields skipped that would strengthen AI citation
Generated schema follows the AIFDS framework. Fields were selected based on research into AI crawler behavior. View the research at minnesota.ai
Copy the template below and replace every YOUR_* value with your own data. This block belongs in a <script type="application/ld+json"> tag in the <head> of your changelog page.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "CollectionPage",
"@id": "https://YOUR_DOMAIN.com/changelog/#webpage",
"url": "https://YOUR_DOMAIN.com/changelog/",
"name": "Changelog",
"description": "Release notes and version history for YOUR_PRODUCT_NAME.",
"isPartOf": {
"@type": "WebSite",
"@id": "https://YOUR_DOMAIN.com/#website"
},
"about": {
"@id": "https://YOUR_DOMAIN.com/#software"
},
"mainEntity": {
"@type": "ItemList",
"name": "Release History",
"numberOfItems": 3,
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"item": {
"@type": "BlogPosting",
"headline": "v2.1 — YOUR_RELEASE_TITLE_1",
"datePublished": "YOUR_RELEASE_DATE_1",
"description": "YOUR_RELEASE_DESCRIPTION_1"
}
},
{
"@type": "ListItem",
"position": 2,
"item": {
"@type": "BlogPosting",
"headline": "v2.0 — YOUR_RELEASE_TITLE_2",
"datePublished": "YOUR_RELEASE_DATE_2",
"description": "YOUR_RELEASE_DESCRIPTION_2"
}
},
{
"@type": "ListItem",
"position": 3,
"item": {
"@type": "BlogPosting",
"headline": "v1.9 — YOUR_RELEASE_TITLE_3",
"datePublished": "YOUR_RELEASE_DATE_3",
"description": "YOUR_RELEASE_DESCRIPTION_3"
}
}
]
}
},
{
"@type": "SoftwareApplication",
"@id": "https://YOUR_DOMAIN.com/#software",
"name": "YOUR_PRODUCT_NAME",
"url": "https://YOUR_DOMAIN.com",
"applicationCategory": "YOUR_APP_CATEGORY",
"operatingSystem": "Web",
"softwareVersion": "YOUR_CURRENT_VERSION",
"releaseNotes": "https://YOUR_DOMAIN.com/changelog/"
},
{
"@type": "Organization",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_COMPANY_NAME",
"url": "https://YOUR_DOMAIN.com",
"logo": "https://YOUR_DOMAIN.com/YOUR_LOGO.png"
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/changelog/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Changelog",
"item": "https://YOUR_DOMAIN.com/changelog/"
}
]
},
{
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "YOUR_CHANGELOG_FAQ_QUESTION_1",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_CHANGELOG_FAQ_ANSWER_1"
}
},
{
"@type": "Question",
"name": "YOUR_CHANGELOG_FAQ_QUESTION_2",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_CHANGELOG_FAQ_ANSWER_2"
}
}
]
}
]
}
Every time you ship a release. The datePublished on your most recent ListItem entry is the primary signal AI uses to assess whether your product is actively maintained. A changelog that has not been updated in months tells AI the product may be stagnant. Keep the structured data in sync with your actual release cadence.
Use semantic versioning (e.g., "2.1.0") or whatever versioning scheme your product follows. The important thing is consistency. AI systems parse the softwareVersion field to understand your release numbering. Whether you use "v2.1", "2.1.0", or "2024.03" does not matter as long as it matches what your users see in your product.
A changelog is a factual record of what changed in each release — version numbers, dates, and descriptions of new features, fixes, and improvements. A blog post is editorial content with context, analysis, and narrative. AI treats them as different signals: the changelog proves active maintenance, while the blog builds topical authority. Many SaaS companies publish both for major releases.