Catalog/SoftwareApplication schema incomplete (name/offers-or-rating/recommended)
SEO issue

SoftwareApplication schema incomplete: add name, offers or rating

SoftwareApplication schema is missing name, offers.price, or a rating/review — required for Google's app rich result. VideoGame types must be co-typed with SoftwareApplication. Find incomplete app markup free.

62
audited sites affected

What it means

This page has SoftwareApplication, MobileApplication, WebApplication, or VideoGame JSON-LD but is missing a field Google needs for the app rich result: name, or at least one of offers / aggregateRating / review. Recommended fields applicationCategory and operatingSystem route the listing to relevant queries. Reported as a notice — an advisory nudge, not a blocker.

Why it matters

Google's app rich result shows the app name, price, star rating, and platform directly in search. name is the displayed title. Google needs at least one of offers (with a numeric price — free apps must set 0 explicitly, and priceCurrency is required when price is non-zero), aggregateRating (with ratingValue and ratingCount), or review; with none of the three, the rich result is suppressed. A common, catchable mistake is the VideoGame co-type rule: a standalone "@type": "VideoGame" is not eligible — it must be co-typed as ["VideoGame", "SoftwareApplication"].

How to fix it

  1. Confirm name is present and matches the app name shown on the page.
  2. Add an offers object with a numeric price (set 0 for free apps) and priceCurrency for any non-zero price, OR an aggregateRating/review.
  3. For a rating, use aggregateRating with ratingValue and ratingCount.
  4. For a VideoGame, add "SoftwareApplication" to the @type array.
  5. Add applicationCategory (e.g. FinanceApplication) and operatingSystem to widen placement.
  6. Validate with Google's Rich Results Test.

When it's not a problem

An app that has genuinely never been reviewed will lack rating data — the rich result simply won't appear until a rating or review exists; this reflects the real eligibility state, not a false alarm. If a free app already sets offers.price to 0 and the rule still fires, confirm price sits inside an Offer node (not at the top level), which static analysis can misread. It does not overlap with schema.invalid.

How common is it?

62 audited sites in our corpus currently show this issue. The breakdowns below show which platforms, gatekeepers, verticals and countries are most exposed.

Breakdowns

CMS

View breakdown →

Category

View breakdown →

Related
Catalog Article schema missing recommended properties (Top Stories / image carousel) BreadcrumbList present but structurally incomplete Deep page has no BreadcrumbList structured data Comma decimal in schema ratingValue/price (invalid number) Deprecated data-vocabulary.org markup (no rich-result eligibility) Dataset schema incomplete (name/description; Dataset Search only) Deprecated schema type with no Google rich result Event schema missing required properties (name/startDate/location) FAQPage structured data (rich result removed May 2026) Schema describes content not visible on the page Rich-result schema missing required properties JobPosting schema missing required properties LocalBusiness schema missing required properties (name/address) JSON-LD block missing @context or @type No structured data detected Product schema missing required or recommended properties QAPage schema incomplete (mainEntity Question with an answer) Recipe schema missing required properties (name/image) Review schema missing required properties (author/itemReviewed/reviewRating) Category CMS Structured-data date has already passed (stale event/job/offer) VideoObject schema missing required properties (name/thumbnailUrl/uploadDate)

Audit your own site — free

157 checks, internal PageRank, render-diff. No signup, results in ~30s.

Scan your site →