收集内容的元数据
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
Google 会使用元数据属性来调整 Feed 中的内容与 Google 数据库中的内容;您为内容提供的元数据越多,Google 就越能更好地匹配内容。
文档中有些属性并未列为必需属性,因为我们了解,根据内容的来源和来源,您可能会遗漏一些内容。不过,在我们进行评估时,以下字段可能成为必填字段,以帮助您的 Feed 实现发布质量。我们强烈建议您在 Feed 中添加这些房源,以免发布流程出现延迟。
为什么强烈推荐这些属性?
Google 会使用元数据属性来调整 Feed 中的内容与 Google 数据库中的内容。成功匹配意味着您的影视内容可以显示在 Google 搜索结果中。如果您的 Feed 有太多失败的匹配,Google 不会批准该 Feed。
您提供的元数据的完整性和准确性都会提高成功匹配的可能性。标题、说明、releaseDate、演职人员、标识符、EIDR 值等属性对于对账特别有用。虽然其中某些属性未按要求载明,但 Google 仍可能会要求您为未成功对账的实体提供部分或全部属性。
执行以下操作:
- 确定内容的必需属性和强烈建议属性。
- 在一个位置收集和整理元数据信息。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
[null,null,[],[[["\u003cp\u003eGoogle uses metadata to match your content with its database for better visibility in search results.\u003c/p\u003e\n"],["\u003cp\u003eProviding complete and accurate metadata, including title, description, release date, cast, and identifiers, is crucial for a successful match and feed approval.\u003c/p\u003e\n"],["\u003cp\u003eHighly recommended metadata properties, while not initially required, may become necessary for launch and should be included to avoid delays.\u003c/p\u003e\n"],["\u003cp\u003eTo prepare your feed, identify the required and recommended properties and consolidate all metadata information.\u003c/p\u003e\n"]]],["Google prioritizes matching your content's metadata with its database to ensure content visibility. Providing complete and accurate metadata, especially for title, description, releaseDate, cast, identifiers, and EIDR values, is highly recommended, though not always required. This improves the likelihood of successful matching. If too many matches fail, Google won't approve the feed. To prepare, users should identify and collect required and highly recommended metadata properties.\n"],null,["# Collect the metadata of your content\n\nGoogle uses the metadata properties to reconcile the content in your feed with the content in Google's databases; the more metadata you provide for your content, the better Google can match the content.\n\nHighly recommended metadata\n---------------------------\n\nThere are properties in the documentation that are not listed as required because we understand that you might be missing this information for some content depending on how and where it is sourced. However, as we run evaluations, these fields might become required to help your feed achieve launch quality. Including these properties in the feed is highly recommended to avoid delays in the launch process.\n\n### Why are these properties highly recommended?\n\nGoogle uses the metadata properties to reconcile the content in your feed with the content in Google's databases. A successful match means your title can appear in Google results. Google will not approve your feed if it has too many unsuccessful matches.\n\nThe likelihood of a successful match improves both with the completeness and accuracy of the metadata you provide. Properties such as title, description, releaseDate, cast, identifiers, EIDR values are particularly valuable for reconciliation. Though some of these properties are not documented as required, Google may still require you to supply some or all of these for the entities that are not successfully reconciled.\n\nCollect the metadata\n--------------------\n\nDo the following:\n\n1. Identify the required and highly recommended properties of your content.\n2. Gather and organize the metadata information in one place."]]