To meet Google’s property requirements for app rich results, you must provide the app’s name (name), its price (offers.price), and at least one of aggregateRating or review. The app must also comply with the general structured data guidelines and app-specific requirements. Providing all required properties does not guarantee that a rich result will appear; recommended properties can supply additional app information.
Required properties: name, price, and a rating or review
According to the SoftwareApplication documentation, marking up the app’s name alone is not enough. Check that you have included the following:
- name: The app’s name.
- offers.price: The app’s price. This property cannot be omitted, even for free apps.
- aggregateRating or review: The app’s average rating or an individual review, respectively. At least one must be included.
Marking up ratings and reviews involves more than entering a number or some text. You must also follow the review snippet guidelines, include the required properties for AggregateRating or Review, and consult the guidance on recommended properties. The list above covers only the core app properties, not a complete review markup template.
Use 0 for free apps; a currency is recommended for paid apps
If the app can be used without payment, set offers.price to 0. If the price is greater than 0, the documentation recommends also including offers.priceCurrency. If no currency is provided, Google will try to find the correct one.
For example, for an app priced at one US dollar, you could enter 1.00 as the price and USD as the currency. This is only an example; use the app’s actual price when implementing the markup. Remember that the price is required, while a currency for paid apps is recommended, not mandatory.
Add the category and operating system, and note the restrictions on game types
The recommended property applicationCategory describes the app’s category, such as BusinessApplication or GameApplication, and its value must be a supported type. The operatingSystem property describes the operating system required to run the app.
Google also supports the MobileApplication and WebApplication subtypes. However, a software app that uses only the VideoGame type will not appear as a software app rich result. For a mobile game, you can use both VideoGame and MobileApplication where they accurately describe the app, but adding types still does not guarantee that a rich result will appear.
Validate the markup and meet content and access requirements
Supported markup formats include JSON-LD, Microdata, and RDFa, with JSON-LD recommended. After adding the required properties, validate the markup with the Rich Results Test and fix any critical errors. Fixing non-critical issues is also recommended, but is not required for eligibility.
The page must also be accessible to Google and must not be blocked by robots.txt, noindex, or a login requirement. The markup should reflect the page’s main content and should not be misleading or refer to information hidden from users. Even if the page passes the test, it must still comply with content policies and relevant guidelines, and Google does not guarantee that a rich result will appear.
App rich results: perspectives from across the web
Do structured data violations affect regular search rankings?
According to Google's general structured data guidelines, a manual action for structured data issues does not affect a page's ranking in Google web search, but it does make the page ineligible for rich results. Site owners can check the status in Search Console's Manual Actions report. The app guidelines state that a reconsideration request can be submitted after the relevant issues have been fixed.
Why might different users still see different search results when the markup is correct?
Google's search results depend on factors such as search history, location, and device type. In some cases, the system may consider other features or text results more appropriate. The Rich Results Test also cannot detect every error. Even if the test reports that the markup is correct, issues that prevent a rich result from appearing may still remain.
References
- 軟體應用程式 (SoftwareApplication) 結構定義 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: Do structured data violations affect regular search rankings?
- 結構化資料通用指南 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: Do structured data violations affect regular search rankings?; Why might different users still see different search results when the markup is correct?

