softwareVersion

softwareVersion · Not mentioned by Google

Appears in

• SoftwareApplication

What is it?

softwareVersion records the current version number of a software application. This is the version string users see on your product page or in their installed app, such as "12.10" or "3.0.23".

Why this matters for AEO

When a user asks "What is the latest version of Debian?", AI engines pull the softwareVersion value to give a direct answer. Without it, the engine has to scrape page content and guess which number represents the version. With it, the answer is immediate and accurate.

What the specs say

Schema.org: Text. Version of the software instance. View on schema.org

Google: Not listed in Google's structured data documentation for SoftwareApplication. View on Google

How to find your value

Use the version string displayed to your users. Check your app's settings page, release notes, or package manifest. Common formats:

• Semantic versioning — "3.0.23"
• Major.minor — "12.10"
• Year-based — "2026.1"
• Simple integer — "5"

Format and code

The value is a plain text string. No specific format is enforced by schema.org.

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Debian GNU/Linux",
  "softwareVersion": "12.10",
  "operatingSystem": "Debian",
  "applicationCategory": "Operating System",
  "downloadUrl": "https://www.debian.org/distrib"
}

Keep this value current. Outdated version numbers in structured data signal stale content to both search engines and AI systems.

Webflow implementation

Static pages

Add in Page Settings > Custom Code (Before </body> tag). Update the version string with each release.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Figma",
  "softwareVersion": "124.1",
  "applicationCategory": "DesignApplication",
  "operatingSystem": "Windows, macOS, Web",
  "offers": {
    "@type": "Offer",
    "price": 0,
    "priceCurrency": "USD"
  }
}
</script>

CMS template pages

Store the version in a plain text CMS field. Reference it in your template's JSON-LD block. Update the CMS item when you release a new version.

In Schema HQ

Your CMS version field is mapped to softwareVersion automatically. For static pages, edit the version directly in the Schema HQ editor.

Real examples

Debian GNU/Linux (from debian.org):

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Debian GNU/Linux",
  "description": "The Universal Operating System",
  "operatingSystem": "Debian",
  "softwareVersion": "12.10",
  "applicationCategory": "Operating System",
  "downloadUrl": "https://www.debian.org/distrib",
  "datePublished": "2025-03-15"
}

Cookie Creator (from darrenlester.com):

{
  "@context": "http://schema.org",
  "@type": "WebApplication",
  "name": "Cookie Creator",
  "url": "https://www.darrenscookies.com/cookie-creator",
  "applicationCategory": "Game",
  "softwareVersion": "1.0.0",
  "operatingSystem": "All"
}

Related fields

• name — The app name
• downloadUrl — Download link for this version
• fileSize — Size of this version's download
• operatingSystem — Platforms this version supports

FAQ

How often should I update softwareVersion in my markup?

Update it with every public release. Stale version numbers suggest the page content is outdated, which can reduce trust signals for both search engines and AI answer engines.

Should I include the "v" prefix?

Use whatever your users see. If your product page says "v3.0", use "v3.0". If it says "3.0", use "3.0". Match the user-facing format.