Video (VideoObject, Clip, BroadcastEvent) structured data

While Google tries to automatically understand details about your video, you can influence the information that's shown in video results, such as the description, thumbnail URL, upload date, and duration, by marking up your video with VideoObject. Adding video structured data to your watch pages can also make it easier for Google to find your video. Videos can appear in several different places on Google, including the main search results page, Video mode, Google Images, and Google Discover.

Video content in Google search results, the video tab, and Discover

Based on how you mark up your watch page, your videos may also be eligible for the following specific video features:

Video features

LIVE badge: Get a LIVE badge added to your video by marking your video with BroadcastEvent. The LIVE badge can be applied to any public video that is live-streamed for any length of time. Here are a few examples:

  • Sporting events
  • Awards shows
  • Influencer videos
  • Live streaming video games

Make sure you follow the LIVE badge guidelines and use the Indexing API to make sure Google crawls your page at the right time.

Video with a LIVE badge in search results

Key moments

The key moments feature is a way for users to navigate video segments like chapters in a book, which can help users engage more deeply with your content. Google Search tries to automatically detect the segments in your video and show key moments to users, without any effort on your part. Alternatively, you can tell Google about the important points of your video. We will prioritize key moments set by you, either through structured data or the YouTube description.

  • If your video is embedded on your web page or you're running a video platform, there are two ways that you can enable key moments:
    • Clip structured data: Specify the exact start and end time to each segment, and what label to display for each segment. This is supported in all languages where Google Search is available.
    • SeekToAction structured data: Tell Google where timestamps typically go in your URL structure, so that Google can automatically identify key moments and link users to those points within the video. This is supported for the following languages: English, Spanish, Portuguese, Italian, Chinese, French, Japanese, German, Turkish, Korean, Dutch, and Russian.
  • If your video is hosted on YouTube, you can specify the exact timestamps and labels in the video description on YouTube. Check out the best practices for marking timestamps in YouTube descriptions. This is supported in all languages where Google Search is available. If you want to enable Video Chapters on YouTube, follow these additional guidelines.

To opt out of the key moments feature completely (including any efforts Google may make to show key moments automatically for your video), use the nosnippet meta tag.

Video with key moments in search results

如何添加结构化数据

结构化数据是一种提供网页相关信息并对网页内容进行分类的标准化格式。如果您不熟悉结构化数据，可以详细了解结构化数据的运作方式。

下面概述了如何构建、测试和发布结构化数据。如需获得向网页添加结构化数据的分步指南，请查看结构化数据 Codelab。

  1. 添加必要属性。根据您使用的格式，了解在网页上的什么位置插入结构化数据。
  2. 遵循指南。
  3. 使用富媒体搜索结果测试验证您的代码，并修复所有严重错误。此外，您还可以考虑修正该工具中可能会标记的任何非严重问题，因为这些这样有助于提升结构化数据的质量（不过，要使内容能够显示为富媒体搜索结果，并非必须这么做）。
  4. 部署一些包含您的结构化数据的网页，然后使用网址检查工具测试 Google 看到的网页样貌。请确保您的网页可供 Google 访问，不会因 robots.txt 文件、noindex 标记或登录要求而被屏蔽。如果网页看起来没有问题，您可以请求 Google 重新抓取您的网址。
  5. 为了让 Google 随时了解日后发生的更改，我们建议您提交站点地图。Search Console Sitemap API 可以帮助您自动执行此操作。

Examples

Standard video result

Example of standard video search results

Here's an example of a single VideoObject.

JSON-LD

<html>
  <head>
    <title>Introducing the self-driving bicycle in the Netherlands</title>
    <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "VideoObject",
      "name": "Introducing the self-driving bicycle in the Netherlands",
      "description": "This spring, Google is introducing the self-driving bicycle in Amsterdam, the world's premier cycling city. The Dutch cycle more than any other nation in the world, almost 900 kilometres per year per person, amounting to over 15 billion kilometres annually. The self-driving bicycle enables safe navigation through the city for Amsterdam residents, and furthers Google's ambition to improve urban mobility with technology. Google Netherlands takes enormous pride in the fact that a Dutch team worked on this innovation that will have great impact in their home country.",
      "thumbnailUrl": [
        "https://example.com/photos/1x1/photo.jpg",
        "https://example.com/photos/4x3/photo.jpg",
        "https://example.com/photos/16x9/photo.jpg"
       ],
      "uploadDate": "2024-03-31T08:00:00+08:00",
      "duration": "PT1M54S",
      "contentUrl": "https://www.example.com/video/123/file.mp4",
      "embedUrl": "https://www.example.com/embed/123",
      "interactionStatistic": {
        "@type": "InteractionCounter",
        "interactionType": { "@type": "WatchAction" },
        "userInteractionCount": 5647018
      },
      "regionsAllowed": ["US", "NL"]
    }
    </script>
  </head>
  <body>
  </body>
</html>
Microdata

<html itemscope itemprop="VideoObject" itemtype="https://schema.org/VideoObject">
<head>
  <title itemprop="name">Introducing the self-driving bicycle in the Netherlands</title>
</head>
<body>
  <meta itemprop="uploadDate" content="2024-03-31T08:00:00+08:00" />
  <meta itemprop="duration" content="PT1M54S" />
  <p itemprop="description">This spring, Google is introducing the self-driving bicycle in Amsterdam, the world's premier cycling city. The Dutch cycle more than any other nation in the world, almost 900 kilometres per year per person, amounting to over 15 billion kilometres annually. The self-driving bicycle enables safe navigation through the city for Amsterdam residents, and furthers Google's ambition to improve urban mobility with technology. Google Netherlands takes enormous pride in the fact that a Dutch team worked on this innovation that will have great impact in their home country.</p>
  <div itemprop="interactionStatistic" itemtype="https://schema.org/InteractionCounter" itemscope>
    <meta itemprop="userInteractionCount" content="5647018" />
    <meta itemprop="interactionType" itemtype="https://schema.org/WatchAction" />
  </div>
  <link itemprop="embedUrl" href="https://www.example.com/embed/123" />
  <meta itemprop="contentUrl" content="https://www.example.com/video/123/file.mp4" />
  <meta itemprop="regionsAllowed" content="US" />
  <meta itemprop="regionsAllowed" content="NL" />
  <meta itemprop="thumbnailUrl" content="https://example.com/photos/1x1/photo.jpg" />
</body>
</html>

LIVE badge

Example of a video in search results with a LIVE badge

Here's an example of VideoObject and BroadcastEvent.

JSON-LD

<html>
  <head>
    <title>Bald Eagle at the Park - Livestream</title>
    <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "VideoObject",
      "contentURL": "https://example.com/bald-eagle-at-the-park.mp4",
      "description": "Bald eagle at the park livestream.",
      "duration": "PT37M14S",
      "embedUrl": "https://example.com/bald-eagle-at-the-park",
      "expires": "2024-10-30T14:37:14+00:00",
      "regionsAllowed": "US",
      "interactionStatistic": {
        "@type": "InteractionCounter",
        "interactionType": { "@type": "WatchAction" },
        "userInteractionCount": 4756
      },
      "name": "Bald eagle nest livestream!",
      "thumbnailUrl": "https://example.com/bald-eagle-at-the-park",
      "uploadDate": "2024-10-27T14:00:00+00:00",
      "publication": [
        {
          "@type": "BroadcastEvent",
          "isLiveBroadcast": true,
          "startDate": "2024-10-27T14:00:00+00:00",
          "endDate": "2024-10-27T14:37:14+00:00"
        },
        {
          "@type": "BroadcastEvent",
          "isLiveBroadcast": true,
          "startDate": "2024-10-27T18:00:00+00:00",
          "endDate": "2024-10-27T18:37:14+00:00"
        }
      ]
    }
    </script>
  </head>
  <body>
  </body>
</html>
Microdata

<html itemscope itemprop="VideoObject" itemtype="https://schema.org/VideoObject">
<head>
  <title itemprop="name">Bald Eagle at the Park - Livestream</title>
</head>
<body>
  <meta itemprop="uploadDate" content="2024-10-27T14:00:00+00:00" />
  <meta itemprop="duration" content="PT37M14S" />
  <p itemprop="description">Bald eagle at the park livestream.</p>
  <div itemprop="interactionStatistic" itemtype="https://schema.org/InteractionCounter" itemscope>
    <meta itemprop="userInteractionCount" content="4756" />
    <meta itemprop="interactionType" itemtype="https://schema.org/WatchAction" />
  </div>
  <link itemprop="embedUrl" href="https://example.com/bald-eagle-at-the-park" />
  <meta itemprop="expires" content="2024-10-30T14:37:14+00:00" />
  <meta itemprop="contentUrl" content="https://example.com/bald-eagle-at-the-park.mp4" />
  <meta itemprop="regionsAllowed" content="US" />
  <meta itemprop="thumbnailUrl" content="https://example.com/bald-eagle-at-the-park" />
  <div itemprop="publication" itemtype="https://schema.org/BroadcastEvent" itemscope>
    <meta itemprop="isLiveBroadcast" content="true" />
    <meta itemprop="startDate" content="2024-10-27T14:00:00+00:00" />
    <meta itemprop="endDate" content="2024-10-27T14:37:14+00:00" />
  </div>
  <div itemprop="publication" itemtype="https://schema.org/BroadcastEvent" itemscope>
    <meta itemprop="isLiveBroadcast" content="true" />
    <meta itemprop="startDate" content="2024-10-27T18:00:00+00:00" />
    <meta itemprop="endDate" content="2024-10-27T18:37:14+00:00" />
  </div>
</body>
</html>

Clip

Example of a video in search results with key moments

Here's an example of VideoObject and Clip.

JSON-LD

<html>
  <head>
    <title>Cat jumps over the fence</title>
    <script type="application/ld+json">
    {
      "@context": "https://schema.org/",
      "@type": "VideoObject",
      "name": "Cat video",
      "duration": "PT10M",
      "uploadDate": "2024-07-19T08:00:00+08:00",
      "thumbnailUrl": "https://www.example.com/cat.jpg",
      "description": "Watch this cat jump over a fence!",
      "contentUrl": "https://www.example.com/cat_video_full.mp4",
      "ineligibleRegion": "US",
      "hasPart": [{
        "@type": "Clip",
        "name": "Cat jumps",
        "startOffset": 30,
        "endOffset": 45,
        "url": "https://www.example.com/example?t=30"
      },
      {
        "@type": "Clip",
        "name": "Cat misses the fence",
        "startOffset": 111,
        "endOffset": 150,
        "url": "https://www.example.com/example?t=111"
      }]
    }
    </script>
  </head>
  <body>
  </body>
</html>
Microdata

<html itemscope itemprop="VideoObject" itemtype="https://schema.org/VideoObject">
<head>
  <title itemprop="name">Cat jumps over the fence</title>
</head>
<body>
  <meta itemprop="uploadDate" content="2024-07-19" />
  <meta itemprop="duration" content="P10M" />
  <p itemprop="description">Watch this cat jump over a fence!</p>
  <div itemprop="interactionStatistic" itemtype="https://schema.org/InteractionCounter" itemscope>
    <meta itemprop="userInteractionCount" content="5647018" />
    <meta itemprop="interactionType" itemtype="https://schema.org/WatchAction" />
  </div>
  <div itemprop="hasPart" itemtype="https://schema.org/Clip" itemscope>
    <meta itemprop="name" content="Cat jumps" />
    <meta itemprop="startOffset" content="30" />
    <meta itemprop="endOffset" content="45" />
    <meta itemprop="url" content="https://www.example.com/example?t=30" />
  </div>
  <div itemprop="hasPart" itemtype="https://schema.org/Clip" itemscope>
    <meta itemprop="name" content="Cat misses the fence" />
    <meta itemprop="startOffset" content="111" />
    <meta itemprop="endOffset" content="150" />
    <meta itemprop="url" content="https://www.example.com/example?t=111" />
  </div>
  <link itemprop="embedUrl" href="https://www.example.com/embed/123" />
  <meta itemprop="contentUrl" content="https://www.example.com/cat_video_full.mp4" />
  <meta itemprop="ineligibleRegion" content="US" />
  <meta itemprop="thumbnailUrl" content="https://www.example.com/cat.jpg" />
</body>
</html>

SeekToAction

Here's an example of a single VideoObject that includes the additional properties needed for SeekToAction markup.

JSON-LD

<html>
  <head>
    <title>John Smith (@johnsmith123) on VideoApp: My daily workout! #stayingfit</title>
    <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "VideoObject",
      "potentialAction" : {
        "@type": "SeekToAction",
        "target": "https://video.example.com/watch/videoID?t={seek_to_second_number}",
        "startOffset-input": "required name=seek_to_second_number"
      },
      "name": "My daily workout!",
      "uploadDate": "2024-07-19T08:00:00+08:00",
      "thumbnailUrl": "https://www.example.com/daily-workout.jpg",
      "description": "My daily workout!",
      "embedUrl": "https://example.com/daily-workout"
    }
    </script>
  </head>
  <body>
  </body>
</html>
Microdata

<html itemscope itemprop="VideoObject" itemtype="https://schema.org/VideoObject">
<head>
  <title itemprop="name">John Smith (@johnsmith123) on VideoApp: My daily workout! #stayingfit</title>
</head>
<body>
  <meta itemprop="uploadDate" content="2024-07-19" />
  <p itemprop="description">My daily workout!</p>
  <div itemprop="potentialAction" itemtype="https://schema.org/SeekToAction" itemscope>
    <meta itemprop="target" content="https://video.example.com/watch/videoID?t={seek_to_second_number}" />
    <meta itemprop="startOffset-input" content="required name=seek_to_second_number" />
  </div>
  <link itemprop="embedUrl" href="https://example.com/daily-workout" />
  <meta itemprop="thumbnailUrl" content="https://www.example.com/daily-workout.jpg" />
</body>
</html>

Guidelines

For your video structured data to be eligible for usage in Google Search, you must follow the Search Essentials, general structured data guidelines, and video indexing requirements.

In addition, we recommend that you check out these guidelines if they apply to your video content:

LIVE badge guidelines

If you're adding BroadcastEvent to livestream videos, follow these guidelines:

  • Don't use vulgar or potentially offensive language in the structured data.
  • To make sure Google crawls your livestream video at the right time, use the Indexing API. Call the API for the following events:
    • When the video goes live
    • When the video has stopped streaming, and the page's markup has been updated to indicate the endDate
    • Whenever a change has happened in the markup and Google needs to be notified

Best practices for marking timestamps on YouTube

If your video is hosted on YouTube, Google Search may automatically enable key moments for your video based on the video description on YouTube, and you may not have to mark specific timestamps in your YouTube description. However, you can tell us more explicitly about the important points in your video and we will prefer that information. The following diagram shows how timestamps and labels in a YouTube video description can appear in search results:

A video in search results with timestamps and labels
1. Label: The name of the clip.
2. Timestamp: When a clip starts.

Keep in mind the following guidelines when formatting timestamps and labels for YouTube descriptions:

  • Format the timestamp in the following format: [hour]:[minute]:[second]. If there's no hour, you don't need to include it.
  • Specify the label of the timestamp on the same line as the timestamp.
  • Place each timestamp on a new line in the video description.
  • Link the timestamp to the specified point in the video.
  • Make sure the label contains at least one word.
  • List the timestamps in chronological order.

If you want to enable Video Chapters on YouTube, follow these additional guidelines.

Clip and SeekToAction guidelines

If you're adding Clip or SeekToAction structured data to mark video segments, follow these guidelines:

  • The video must have the ability to deep link into some point other than the start point in the video URL. For example, https://www.example.com/example?t=30 starts 30 seconds into a video.
  • VideoObject structured data must be added to a page where users can watch the video. It's a bad user experience to point users to a page where they can't watch the video.
  • The total video duration must be a minimum of 30 seconds.
  • The video must include the required properties that are listed in the VideoObject structured data documentation.
  • For Clip structured data only: Make sure that no two clips on the same video defined on the same page share a start time.
  • For SeekToAction structured data only: Google must be able to fetch your video content files.

Structured data type definitions

This section describes the structured data types related to video features in Google Search. You must include the required VideoObject properties for your markup to be eligible for usage in Google Search. You can also include the recommended properties to add more information about your VideoObject, which could provide a better user experience. In addition to VideoObject, you can add the following data types to enable video enhancements in Google Search:

  • BroadcastEvent: Mark up livestream videos to enable a LIVE badge on your video.
  • Clip: Mark important segments in your video to help users quickly navigate to specific points in a video.
  • SeekToAction: Enable key moments by indicating how your URL structure works, so that Google can automatically identify key moments and link users to those points within the video.

VideoObject

The full definition of VideoObject is available at schema.org/VideoObject. If you don't include the required properties, Google may not be able to extract any information about the video. You can also include the recommended properties to add more information about your content, which could provide a better user experience.

Required properties
name

Text

The title of the video. Make sure to use unique text in the name property for each video on your site.
thumbnailUrl

Repeated URL

A URL pointing to the video's unique thumbnail image file. Follow the thumbnail image guidelines.
uploadDate

DateTime

The date and time the video was first published, in ISO 8601 format. We recommend that you provide timezone information; otherwise, we will default to the timezone used by Googlebot.
Recommended properties
contentUrl

URL

A URL pointing to the video file's actual content bytes, in one of the supported file types. Don't link to the page where the video lives; this must be the URL of the video file's actual content bytes itself.

"contentUrl": "https://www.example.com/video/123/file.mp4"

Make sure to follow our video best practices.
description

Text

The description of the video. Make sure to use unique text in the description property for each video on your site. HTML tags are ignored.
duration

Duration

The duration of the video in ISO 8601 format. For example, PT00H30M5S represents a duration of "thirty minutes and five seconds".
embedUrl

URL

A URL pointing to a player for the specific video. Don't link to the page where the video lives; this must be the URL of the video player itself. Usually this is the information in the src attribute of an <embed> element.

"embedUrl": "https://www.example.com/embed/123"

Make sure to follow our Video best practices.
expires DateTime

If applicable, the date and time after which the video will no longer be available, in ISO 8601 format. Don't supply this information if your video does not expire. We recommend that you provide timezone information; otherwise, we will default to the timezone used by Googlebot.
hasPart

If your video has important segments, nest the required Clip properties in your VideoObject. For example:

<script type="application/ld+json">
{
  "@context": "https://schema.org/",
  "@type": "VideoObject",
  "name": "Cat video",
  "hasPart": {
    "@type": "Clip",
    "name": "Cat jumps",
    "startOffset": 30,
    "url": "https://www.example.com/example?t=30"
  }
}
</script>
ineligibleRegion

Place

The region where the video isn't allowed, if applicable. If not specified, then Google assumes the video is allowed everywhere. Specify the countries in two- or three-letter ISO 3166-1 format. For multiple values, use multiple country codes (for example, a JSON-LD array or multiple meta tags in Microdata).
interactionStatistic

InteractionCounter

The number of times the video has been watched. For example:

"interactionStatistic":
  {
    "@type": "InteractionCounter",
    "interactionType": { "@type": "WatchAction" },
    "userInteractionCount": 12345
  }
publication

If your video is happening live and you want to be eligible for the LIVE badge, nest the BroadcastEvent properties in your VideoObject. For example:

<script type="application/ld+json">
{
  "@context": "https://schema.org/",
  "@type": "VideoObject",
  "name": "Cat video",
  "publication": {
    "@type": "BroadcastEvent",
    "name": "First scheduled broadcast",
    "isLiveBroadcast": true,
    "startDate": "2018-10-27T14:00:00+00:00",
    "endDate": "2018-10-27T14:37:14+00:00"
  }
}
</script>
regionsAllowed

Place

The regions where the video is allowed, if applicable. If not specified, then Google assumes the video is allowed everywhere. Specify the countries in two- or three-letter ISO 3166-1 format. For multiple values, use multiple country codes (for example, a JSON-LD array or multiple meta tags in Microdata).

BroadcastEvent

To be eligible for display with a LIVE badge, nest the following properties in your VideoObject. While BroadcastEvent properties aren't required, you must add the following properties if you want your video to display with a LIVE badge.

The full definition of BroadcastEvent is available at schema.org/BroadcastEvent.

Required properties
publication

BroadcastEvent

Describes when the video is to be streamed live. Can be a list or a single instance.
publication.endDate

DateTime

Time and date of when the livestream ends or is expected to end, in ISO 8601 format.

It's required to provide the endDate once the video has finished and is no longer live. If the expected endDate is unknown prior to the livestream starting, we recommend providing an approximate endDate.

If endDate is in the past or present, it indicates stream actually ended and is no longer live. If endDate is in the future, it indicates stream is scheduled to end at that time.
publication.isLiveBroadcast

Boolean

Set to true if the video is, has been, or will be streamed live.

publication.startDate

DateTime

Time and date of when the livestream starts or is expected to start, in ISO 8601 format. If startDate is in the past or present, it indicates that the stream actually started. If startDate is in the future, it indicates stream is scheduled to start at that time.

Clip

To tell Google what timestamp and label to use for the key moments feature, nest the following properties in your VideoObject. While Clip properties aren't required, you must add the following properties if you want Google to show the timestamps and labels that you specify for your video, instead of the video segments that Google may automatically show for your video.

The full definition of Clip is available at schema.org/Clip.

Required properties
name

Text

A descriptive title for the content of the clip.
startOffset

Number

The start time of the clip expressed as the number of seconds from the beginning of the work.
url

URL

A URL that points to the start time of the clip.

The clip URL must point to the same URL path as the video with additional query parameters that specify the time.

For example, the following URL means the video starts at 2:00 minutes:

"url": "https://www.example.com/example?t=120"
Recommended properties
endOffset

Number

The end time of the clip expressed as the number of seconds from the beginning of the work.

SeekToAction

To tell Google how your URL structure works (so that Google can display key moments that are automatically identified for your video), nest the following properties in your VideoObject. While SeekToAction properties aren't required, you must add the following properties if you want Google to understand how your URL structure works, so Google can link users to a point within the video.

The full definition of SeekToAction is available at schema.org/SeekToAction.

Required properties
potentialAction

SeekToAction

Indicates a potential action. Include the following nested properties

For example: 

{
  "@context": "https://schema.org",
  "@type": "VideoObject",
  "potentialAction" : {
    "@type": "SeekToAction",
    "target": "https://video.example.com/watch/videoID?t={seek_to_second_number}",
    "startOffset-input": "required name=seek_to_second_number"
  }
}
potentialAction.startOffset-input

Text

The placeholder string that Google will identify as your timestamp structure and then replace with the number of seconds to skip to. Use the following value:

"startOffset-input": "required name=seek_to_second_number"

startOffset-input is an annotated property. See the Potential Actions page for more information.

potentialAction.target

EntryPoint

The URL of the page that contains this VideoObject, including a placeholder in the URL structure that indicates where Google can insert the number of seconds to skip to in the video. This is how Google understands your URL structure and how you format your timestamps. Replace the timestamp part of the URL with the following placeholder string:

{seek_to_second_number}

For example, replace the timestamp part of the URL: 

"target": "https://video.example.com/watch/videoID?t=30"

So that the timestamp now looks like this:

"target": "https://video.example.com/watch/videoID?t={seek_to_second_number}"

Monitor rich results with Search Console

Search Console is a tool that helps you monitor how your pages perform in Google Search. You don't have to sign up for Search Console to be included in Google Search results, but it can help you understand and improve how Google sees your site. We recommend checking Search Console in the following cases:

  1. After deploying structured data for the first time
  2. After releasing new templates or updating your code
  3. Analyzing traffic periodically

After deploying structured data for the first time

After Google has indexed your pages, look for issues using the relevant Rich result status report. Ideally, there will be an increase of valid items, and no increase in invalid items. If you find issues in your structured data:

  1. Fix the invalid items.
  2. Inspect a live URL to check if the issue persists.
  3. Request validation using the status report.

After releasing new templates or updating your code

When you make significant changes to your website, monitor for increases in structured data invalid items.
  • If you see an increase in invalid items, perhaps you rolled out a new template that doesn't work, or your site interacts with the existing template in a new and bad way.
  • If you see a decrease in valid items (not matched by an increase in invalid items), perhaps you are no longer embedding structured data in your pages. Use the URL Inspection tool to learn what is causing the issue.

Analyzing traffic periodically

Analyze your Google Search traffic using the Performance Report. The data will show you how often your page appears as a rich result in Search, how often users click on it and what is the average position you appear on search results. You can also automatically pull these results with the Search Console API.

问题排查

如果您在实施或调试结构化数据时遇到问题，请查看下面列出的一些实用资源。

  • 如果您使用了内容管理系统 (CMS) 或其他人负责管理您的网站，请向其寻求帮助。请务必向其转发列明问题细节的任何 Search Console 消息。
  • Google 不能保证使用结构化数据的功能一定会显示在搜索结果中。如需查看导致 Google 无法将您的内容显示为富媒体搜索结果的各种常见原因，请参阅结构化数据常规指南。
  • 您的结构化数据可能存在错误。请参阅结构化数据错误列表。
  • 如果您的网页受到结构化数据手动操作的影响，其中的结构化数据将会被忽略（但该网页仍可能会出现在 Google 搜索结果中）。如需修正结构化数据问题，请使用“人工处置措施”报告。
  • 再次查看相关指南，确认您的内容是否未遵循指南。问题可能是因为出现垃圾内容或使用垃圾标记导致的。不过，问题可能不是语法问题，因此富媒体搜索结果测试无法识别这些问题。
  • 针对富媒体搜索结果缺失/富媒体搜索结果总数下降进行问题排查。
  • 请等待一段时间，以便 Google 重新抓取您的网页并重新将其编入索引。请注意，网页发布后，Google 可能需要几天时间才会找到和抓取该网页。有关抓取和索引编制的常见问题，请参阅 Google 搜索抓取和索引编制常见问题解答。
  • 在 Google 搜索中心论坛中发帖提问。