为 Search Console 中的结构化数据问题添加上下文
2022 年 3 月 28 日(星期一)
为了帮助您更高效地发现结构化数据中的问题,从明天开始,Search Console 将为其错误报告添加更多上下文。
例如,如果某个网站没有在 Review snippet
标记中提供作者的姓名,Search Console 目前会报告名为 Missing field "name" 的错误。从今天开始,该错误将被命名为 Missing field "name" (in "author")。小括号内提供更详细的上下文有助于您更轻松地发现结构化数据中的问题。
这项变更会影响所有 Search Console 富媒体搜索结果状态报告、Search Console 网址检查工具和富媒体搜索结果测试,即使您未更改结构化数据标记也是如此:
- 所有涉及嵌套属性的待解决问题都将自动关闭(例如,以上示例中的
Missing field "name"
问题)。
- 您将看到新的待解决问题,这些问题附有缺失内容的更多上下文(例如,问题会显示为
Missing field "name" (in "author")
)。
为避免 Search Console 用户收到过多电子邮件,我们在创建这些新问题时不会发送通知。
请注意,如果您在此变更之前曾请求 Search Console 验证修复效果,则需要重新验证新问题。
总的来说,此变更只是问题名称的变化,不会影响 Search Console 检测错误的方式,所有将被关闭的问题都将替换为新问题,并在问题名称中附上更多上下文。
如果您有任何问题或疑虑,欢迎通过 Google 搜索中心社区或 Twitter 联系我们。
发布者:Moshe Samet(Search Console 产品经理)和 Ryan Levering(Google 搜索工程团队)
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
[null,null,[],[[["Search Console is enhancing its structured data error reporting with more context, aiding in easier identification of issues."],["This update provides detailed error descriptions, including the specific property where the missing field resides, like \"Missing field 'name' (in 'author')\"."],["Existing open issues related to nested properties will be automatically closed and replaced by new, more informative issues."],["This change is purely for error name clarity, it does not affect Search Console's error detection or functionality, and requires revalidation for previously validated fixes."],["Users can reach out for support on Google Search Central Community or Twitter."]]],["Search Console is enhancing error reporting for structured data starting March 29, 2022. Error messages will include more context, such as \"Missing field 'name' (in 'author')\". This impacts all Search Console status reports, the URL inspection tool, and the Rich Results Test. Existing issues related to nested properties will close and new, more detailed issues will open without notification. The core functionality of error detection remains unchanged, only the error description changes. If you had requested validation before, you'll need to request it again for the new issue.\n"]]