軟體應用程式 (SoftwareApplication) 結構化資料

只要在網頁內文中標記軟體應用程式資訊,就能在 Google 搜尋結果中更有效地顯示應用程式的詳細資訊。

Google 搜尋結果中的軟體應用程式複合式搜尋結果

How to add structured data

Structured data is a standardized format for providing information about a page and classifying the page content. If you're new to structured data, you can learn more about how structured data works.

Here's an overview of how to build, test, and release structured data.

  1. Add the required properties. Based on the format you're using, learn where to insert structured data on the page.
  2. Follow the guidelines.
  3. Validate your code using the Rich Results Test and fix any critical errors. Consider also fixing any non-critical issues that may be flagged in the tool, as they can help improve the quality of your structured data (however, this isn't necessary to be eligible for rich results).
  4. Deploy a few pages that include your structured data and use the URL Inspection tool to test how Google sees the page. Be sure that your page is accessible to Google and not blocked by a robots.txt file, the noindex tag, or login requirements. If the page looks okay, you can ask Google to recrawl your URLs.
  5. To keep Google informed of future changes, we recommend that you submit a sitemap. You can automate this with the Search Console Sitemap API.

範例

JSON-LD

以下是採用 JSON-LD 格式的軟體應用程式範例:


<html>
  <head>
    <title>Angry Birds</title>
    <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "SoftwareApplication",
      "name": "Angry Birds",
      "operatingSystem": "ANDROID",
      "applicationCategory": "GameApplication",
      "aggregateRating": {
        "@type": "AggregateRating",
        "ratingValue": 4.6,
        "ratingCount": 8864
      },
      "offers": {
        "@type": "Offer",
        "price": 1.00,
        "priceCurrency": "USD"
      }
    }
    </script>
  </head>
  <body>
  </body>
</html>
RDFa

以下是採用 RDFa 格式呈現的軟體應用程式範例:


<div vocab="https://schema.org/" typeof="SoftwareApplication">
  <span property="name">Angry Birds</span> -

  REQUIRES <span property="operatingSystem">ANDROID</span>
  TYPE: <span property="applicationCategory" content="GameApplication">Game</span>

  RATING:
  <div property="aggregateRating" typeof="AggregateRating">
    <span property="ratingValue">4.6</span> (
    <span property="ratingCount">8864</span> ratings )
  </div>

  <div property="offers" typeof="Offer">
    Price: $<span property="price">1.00</span>
    <meta property="priceCurrency" content="USD" />
  </div>
</div>
  
微資料

以下是採用微資料格式呈現的軟體應用程式範例:


<div itemscope itemtype="https://schema.org/SoftwareApplication">
  <span itemprop="name">Angry Birds</span> -

  REQUIRES <span itemprop="operatingSystem">ANDROID</span>
  TYPE: <span itemprop="applicationCategory" content="GameApplication">Game</span>

  RATING:
  <div itemprop="aggregateRating" itemscope itemtype="https://schema.org/AggregateRating">
    <span itemprop="ratingValue">4.6</span> (
    <span itemprop="ratingCount">8864</span> ratings )
  </div>

  <div itemprop="offers" itemscope itemtype="https://schema.org/Offer">
    Price: $<span itemprop="price">1.00</span>
    <meta itemprop="priceCurrency" content="USD" />
  </div>
</div>
  

指南規範

您的必須遵守下列規範,才能以複合式搜尋結果的形式顯示您的應用程式。

結構化資料類型定義

您的內容必須包含必要的屬性,才能以複合式搜尋結果的形式呈現。 您也可以加入建議的屬性,為內容增添更多相關資訊,提供更優質的使用者體驗。

SoftwareApplication

schema.org/SoftwareApplication 內提供 SoftwareApplication 的完整定義。

Google 支援的屬性如下:

必要屬性
name

Text

應用程式名稱。

offers.price

Offer

銷售應用程式的商情內容。對開發人員而言,offers 可以代表展示應用程式的賣場。對市集而言,offers 則是用來指出特定應用程式例項中應用程式的價格。

如果無須支付費用即可使用應用程式,請將 offers.price 設為 0。例如:

"offers": {
  "@type": "Offer",
  "price": 0
}

如果應用程式的價格大於 0,建議一併加入 offers.priceCurrency 屬性 (否則 Google 會嘗試尋找正確的幣別)。例如:

"offers": {
  "@type": "Offer",
  "price": 1.00,
  "priceCurrency": "USD"
}
rating 或 review

應用程式的評分或評論。您必須添加下列其中一個屬性:

aggregateRating

AggregateRating

應用程式的平均評分。請遵循評論摘錄規範,以及必要和建議的 AggregateRating 屬性清單。

review

Review

應用程式的單則評論。請遵循評論摘錄規範,以及必要和建議的 Review 屬性清單。

建議屬性
applicationCategory

Text

應用程式的類型 (例如 BusinessApplicationGameApplication)。這個值必須是支援的應用程式類型。

支援的應用程式類型清單

  • GameApplication
  • SocialNetworkingApplication
  • TravelApplication
  • ShoppingApplication
  • SportsApplication
  • LifestyleApplication
  • BusinessApplication
  • DesignApplication
  • DeveloperApplication
  • DriverApplication
  • EducationalApplication
  • HealthApplication
  • FinanceApplication
  • SecurityApplication
  • BrowserApplication
  • CommunicationApplication
  • DesktopEnhancementApplication
  • EntertainmentApplication
  • MultimediaApplication
  • HomeApplication
  • UtilitiesApplication
  • ReferenceApplication
operatingSystem

Text

執行應用程式時所需的作業系統 (例如 Windows 7OSX 10.6Android 1.6)

應用程式子類型的擴充屬性

此外,Google 也支援適用於行動應用程式和網頁應用程式的 MobileApplicationWebApplication

如果軟體應用程式只使用了 VideoGame 類型,Google 就不會顯示該軟體應用程式的複合式搜尋結果。為確保軟體應用程式能顯示為複合式搜尋結果,除了 VideoGame 類型之外,請一併使用其他類型。例如:

{
  "@context": "https://schema.org",
  "@type": ["VideoGame", "MobileApplication"],
  ....
}

Troubleshooting

If you're having trouble implementing or debugging structured data, here are some resources that may help you.

  • If you're using a content management system (CMS) or someone else is taking care of your site, ask them to help you. Make sure to forward any Search Console message that details the issue to them.
  • Google does not guarantee that features that consume structured data will show up in search results. For a list of common reasons why Google may not show your content in a rich result, see the General Structured Data Guidelines.
  • You might have an error in your structured data. Check the list of structured data errors and the Unparsable structured data report.
  • If you received a structured data manual action against your page, the structured data on the page will be ignored (although the page can still appear in Google Search results). To fix structured data issues, use the Manual Actions report.
  • Review the guidelines again to identify if your content isn't compliant with the guidelines. The problem can be caused by either spammy content or spammy markup usage. However, the issue may not be a syntax issue, and so the Rich Results Test won't be able to identify these issues.
  • Troubleshoot missing rich results / drop in total rich results.
  • Allow time for re-crawling and re-indexing. Remember that it may take several days after publishing a page for Google to find and crawl it. For general questions about crawling and indexing, check the Google Search crawling and indexing FAQ.
  • Post a question in the Google Search Central forum.