使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
商品级别的错误和警告
简介/业务影响
商家解决其帐号问题后,商品级问题属于优先事项,因为这是促成展示和点击的内容。请务必向商家提供必要的信息,帮助他们确定商品状态,以及修正商品问题的解决路径。
用户体验指南
对于发现的商品级问题,商家应该能够在信息中心查看问题类型、严重程度和受影响的商品数量的细分数据。在概览页面上,他们可以查看有多少商品(如果有)“未获批准”:

如果商家切换到“商品”标签页,他们可以看到哪些商品受商品级问题的影响。如果他们点击“问题”列下的问题链接,系统会提示他们修正这些错误。您可以点击此处,详细了解商品级别问题的解决和申诉流程。

当商家点击列表中的特定商品时,您应显示 Merchant Support API 提供的视图,如模拟示例中所述(此视图对于商品和帐号问题是相同的)。
技术指南
如需显示包含大量未获批准或已批准的商品和商品列表的概览页面,您可以使用商品过滤 API。
如需在详细视图中显示每个商品的问题,我们建议您使用新的商家支持服务呈现商品问题方法,向您的商家显示商品信息和问题。这种方法侧重于帮助商家解决问题,它提供多种功能,例如不同的支持的语言、更新后的政策以及对未来即将推出的新功能的支持。详细了解如何在界面中实现这种新方法。
此外,我们建议您查看以下资源,了解不同商品状态在 Merchant Center 和 Content API 中的工作原理。
我们建议商家修正被拒登和收到警告的商品,因为这会影响完全适合上架销售的商品的数量。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-25。
[null,null,["最后更新时间 (UTC):2025-07-25。"],[[["\u003cp\u003eAfter account-level issues, product-level issues should be addressed to improve product visibility and performance, as they directly impact impressions and clicks.\u003c/p\u003e\n"],["\u003cp\u003eMerchants can utilize the dashboard to view a breakdown of product-level issues, including the type, severity, and number of affected products, and access a detailed view of each product's issues for troubleshooting.\u003c/p\u003e\n"],["\u003cp\u003eGoogle provides APIs and services, such as the Product Filtering API and Merchant Support Service, for developers to integrate product-level issue data and resolution paths into merchant interfaces.\u003c/p\u003e\n"],["\u003cp\u003eMerchants should prioritize fixing disapproved and warned products, as these issues can hinder product visibility and overall performance.\u003c/p\u003e\n"],["\u003cp\u003eComprehensive documentation and resources are available to guide developers and merchants in understanding product statuses, issue resolution, and API implementation, including links to specific Google support pages and developer guides.\u003c/p\u003e\n"]]],[],null,["Offer Level Errors and Warnings\n-------------------------------\n\n### Introduction/Business Impact\n\n*** ** * ** ***\n\nAfter a merchant solves their account issues, product level issues are a\npriority because this is the content which drives impression and clicks.\nIt is vital to provide merchants the necessary information they need to\nidentify the product statuses and resolution paths to fix their products.\n\n### UX Guidance\n\n*** ** * ** ***\n\nFor product level issues surfaced, Merchants should be able to see in the\ndashboard breakdown of issue type, severity, and the number of products\naffected. On the overview page, they can see how many products (if any)\nare \"not approved\":\n\nIf the merchant toggles to the \"Products\" tab, they can see which products\nare affected by the product-level issue. If they click the link to the issue\nunder the \"Issues\" column, they will be prompted to fix these errors. You can\nfind more about the resolution and appeal process for offer level issues,\n[here](/merchant/storebuilder/online/sections/3_2_2_appeal).\n\nWhen a merchant clicks on a specific product in the list, you should display\nthe view provided by Merchant Support API as described in [sample mocks](https://developers.google.com/shopping-content/guides/merchant-support#ui_mocks)\n(this view is identical for product \\& account issues).\n\n### Tech Guidance\n\n*** ** * ** ***\n\nTo display an overview page with a number of disapproved or approved products\nand product list you can use the [product filtering API](https://developers.google.com/shopping-content/guides/reports/products).\n\nTo display issues for each product in a detailed view, we recommend using the\nnew [merchant support service](https://developers.google.com/shopping-content/guides/quickstart) render product issues method to display\nproduct information and issues to your merchants. With the focus of this method\non helping merchants help themselves, it comes with a variety of features\nsuch as different supported languages, updated policies, and support for new\nupcoming features in the future. Learn more about\n[how to implement this new method into your interface](https://developers.google.com/shopping-content/guides/merchant-support).\n| **Note:** Use [Product Filtering API](https://developers.google.com/shopping-content/guides/reports/products) or [Product Status](https://developers.google.com/shopping-content/reference/rest/v2.1/productstatuses) for listing the overall issues (list of disapproved products). For detail of the issue, users should use Merchant Support API; for a list of products with issues, users should use Product Filtering API (recommended) or ProductStatuses.\n\nAlso, we suggest reviewing following resources to understand how the different\nproduct statuses work in Merchant Center and the Content API.\n\n- Learn more about [product disapprovals and warnings for Merchant Center](https://support.google.com/merchants/answer/9227009?ref_topic=7288019&sjid=10480504730388959254-EU)\n\n- Learn more about\n [Content API, product issues and severity for Merchant Center](https://developers.google.com/shopping-content/guides/how-tos/severity-mapping)\n\nWe recommend merchants to fix disapproved and warned products because this\naffects the number of products which are fully optimal to be live."]]