SoftwareApplication schema for SaaS products

Google's software app documentation and Schema.org define these.

For several plans, use an AggregateOffer with lowPrice, highPrice, priceCurrency, and offerCount, or a list of Offer items, one per plan, with name and price. For a free plan, an Offer with price 0 is valid. Keep prices identical to the visible pricing page and update both together. Do not include prices that are only shown after sign-up.

Software app rich results usually require ratings, and this is where markup is most often abused. Include aggregateRating only if genuine user ratings for the product are displayed on the same page. Ratings copied from review platforms without showing those reviews, or invented ratings, violate Google's guidelines and risk a manual action. If you do not have on-page ratings, omit the property; the markup is still useful for understanding.

Declare the main product once with a stable @id, such as https://www.example.com/#software, and reference it from other blocks, for example Organization makesOffer or WebPage about. On serionflow.com, the SoftwareApplication entity, including its offer, is declared once in the shared document head alongside Organization and WebSite. Pages for individual features do not redeclare it with different values.

If you offer several distinct apps, such as a web app and a mobile app, give each its own entity and @id, on its own page where possible. Validate in the Rich Results Test and the Schema.org validator. Our free schema builder and validator can generate SoftwareApplication JSON-LD and check existing markup on a live page. SerionFlow is the wrong tool for marking up your own product pages; add that markup in your site template.