Most apps add this markup and never get the rich result

Adding SoftwareApplication structured data feels like a box ticked. Then nothing happens, because two properties most people omit are the ones Google actually requires.

Run the free check

For a SoftwareApplication rich result, Google's documentation requires the name property, an offers property containing a price where zero indicates a free app, and either an aggregateRating or a review. It recommends applicationCategory and operatingSystem. Markup missing the price or the rating is valid structured data that will not produce a rich result, which is why most apps see no effect from adding it.

What structured data is doing

Structured data is a block of machine-readable description added to your page, saying explicitly what the page is about in a vocabulary that search engines already understand.

Your page might say, in prose, that your tool is free and works in a browser. A human reads that easily. Structured data states the same facts in a form that requires no interpretation, which removes the guessing.

It serves two purposes now. It can qualify a page for a richer presentation in search results, and it gives any machine reading your page an unambiguous description of what the product is, which matters increasingly as more of your traffic arrives through systems that read rather than browse.

The requirements people miss

This is the section worth the whole page, because it explains why so much effort here produces nothing.

Google's documentation for software app structured data lists the required properties: the name of the app, an offers property indicating price where zero is used for a free app, and either an aggregateRating or a review. Recommended alongside those are applicationCategory, describing the type of app, and operatingSystem.

So markup that names your app and describes it accurately, but omits the price and the rating, is perfectly valid and will not produce a rich result. Nothing reports an error. It simply does not appear, and the developer concludes structured data does not work.

There is also a restriction worth knowing: Google states it does not show a rich result for software apps typed only as VideoGame, so a game needs to be combined with another type such as WebApplication to qualify.

The rating problem, and what not to do

The rating requirement creates an obvious temptation for a new product with no users, and it must be said plainly: do not invent one.

Fabricated ratings are a structured data policy violation, and all structured data has to follow Google's guidelines or a site risks a manual action. A manual action against a two-month-old domain is a far worse outcome than not having a rich result.

It is also the wrong trade on its own terms. A rich result showing a five star rating from four reviews you wrote yourself is a claim about your product that a real user will eventually test and find false.

The honest path is to collect real reviews, then add the markup once you genuinely have them. In the meantime, add the accurate structured data you do qualify for and accept that the rich result comes later.

What to add when you cannot qualify yet

A rich result is not the only reason to add structured data, and for a new product it is not the main one.

Add an Organization block naming your product, its URL, its logo, and any profiles you control elsewhere. This is the description of you as an entity, and it is what a machine reads when trying to establish that you exist and what you are.

Add FAQPage markup on pages that genuinely contain a list of questions and answers, matching what is visible on the page.

Add BreadcrumbList on nested pages so the hierarchy of your site is explicit rather than inferred.

And add SoftwareApplication with accurate values even without the rating, because the description it provides is useful to anything reading your page even when no rich result follows.

The rule that keeps you out of trouble

One principle covers nearly every mistake in this area: the structured data must describe what is actually on the page, visible to a person reading it.

FAQ markup listing questions that do not appear on the page is a violation. A rating that no visitor can see is a violation. A description of features the page does not mention is at best useless and at worst treated as an attempt to mislead.

The test is straightforward. Read your markup, then read your page. If somebody could not verify each claim in the markup by reading the page, remove that claim.

This also happens to be the approach that works best for machine readers generally, since a page whose visible content and machine-readable description agree is an easier page to trust.

Checking it

Two checks, both quick, and worth doing after every deployment that touches the markup.

First, confirm it parses. A structured data block with a syntax error is not partially working, it is ignored entirely, and this is easy to do while editing by hand.

Second, confirm the required properties for whatever result you are aiming at are all present, which given the section above means checking specifically for the price and the rating rather than assuming.

Then check a deep page rather than only the homepage. Markup is commonly added to the entry point and forgotten everywhere else, which is the same pattern that catches people with titles and with rendering.

Part of a larger guide

This page is one part of The fixes. The other parts:

Questions people ask

What does SoftwareApplication schema require?
Google's documentation requires the app name, an offers property indicating price where zero means free, and either an aggregateRating or a review. It recommends applicationCategory and operatingSystem. Markup missing the price or the rating is valid but will not produce a rich result.
Why did adding structured data do nothing for my app?
Almost always because the required price or rating property is missing. Nothing reports an error, the markup is valid, and the rich result simply never appears, which leads developers to conclude structured data does not work.
Can I add a rating if I have no users yet?
No. Fabricated ratings violate Google's structured data policies and risk a manual action, which is a far worse outcome for a young domain than not having a rich result. Collect real reviews first, then add the markup once you genuinely have them.
What structured data should I add before I qualify for a rich result?
An Organization block naming your product, URL, logo and the profiles you control, FAQPage markup where a page genuinely contains questions and answers, BreadcrumbList on nested pages, and an accurate SoftwareApplication block. These describe you to machine readers regardless of whether a rich result follows.
Does my markup have to match what is on the page?
Yes, and this single rule prevents nearly every mistake in this area. FAQ markup listing questions not on the page is a violation, as is a rating no visitor can see. If somebody could not verify a claim by reading the page, remove it from the markup.
Do video games get a rich result?
Not from the VideoGame type alone. Google states it does not show a rich result for software apps that only have the VideoGame type, so it must be combined with another type such as WebApplication or MobileApplication to qualify.

Check what structured data you have now

The free Get Found Check reads the structured data on your pages, reports what parses, and tells you which required properties are missing.

Run the free check Have Licheo do it for you