使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
1.6 政策检查
简介/业务影响
商家不仅需要满足非付费商品详情和付费广告的帐号要求,还需要满足 Merchant Center 网站要求。详细了解 Merchant Center 网站要求。
鉴于这些网站要求,我们希望在新手入门流程中增加一个步骤,让商家了解这些要求,并能够根据需要予以解决。
用户体验指南
在此示例中,系统会自动检测五项 Google 网店要求的状态,并将其显示在界面中。理想情况下,商店开设平台可帮助商家在上游满足所有网站要求。否则,商店开设平台需要为商家提供在新手入门过程中直接满足所有要求的权限。

我们还提供相应选项,让商家可以在初始配置过程中跳过此步骤,稍后再完成。然后,我们会指导商家在完成新手入门流程后满足网店要求。
我们强烈建议使用内容相关广告或重叠式网页来减少重定向。商家在 Google 插件页面和商店开设平台页面之间导航时很容易迷失方向,而这会提高用户流失率。
技术指南
向商家展示以下 Merchant Center 网站要求,以便他们确认其网站符合要求:
- 确保网站未受密码保护,且可供客户访问
- 添加退款和服务条款
- 添加商店联系方式
- 设置安全结账功能并完成结账
- 确认您的商店网址以 https:// 开头
推荐的实现方式
自动检测:我们建议您构建自动检测功能,以自动检测 Google 网店的 5 项要求的状态,并将其显示在界面上。
更轻松地更新未满足的要求:如果需要进行更改以满足网站要求,这些步骤应与平台中的功能相关联,以便商家更新这些信息,以确保这些信息包含在其网站上。
最低实现
如果您无法构建自动检测系统或方便商家轻松进行修改的自动化系统,我们建议您显示 5 项网站要求,并强制商家手动点击复选框,以便他们了解这些要求。
请注意,这种方法可能会导致很多帐号因不符合我们的网站要求而被暂停。这可能会导致商家轻易放弃,不再尝试解决问题以继续进行初始配置。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-25。
[null,null,["最后更新时间 (UTC):2025-07-25。"],[[["\u003cp\u003eMerchants must adhere to Merchant Center website requirements in addition to account requirements for Free Listing and Paid Ads.\u003c/p\u003e\n"],["\u003cp\u003eStorebuilders should ideally auto-detect and help merchants meet website requirements during onboarding or provide clear guidance for post-onboarding completion.\u003c/p\u003e\n"],["\u003cp\u003eContextual or overlay pages are recommended to minimize redirects and improve user experience.\u003c/p\u003e\n"],["\u003cp\u003eThe five key website requirements involve site accessibility, refund/terms of service, contact information, secure checkout, and HTTPS URL.\u003c/p\u003e\n"],["\u003cp\u003eAutomated detection and easy update functionality are ideal, but at minimum, merchants should manually acknowledge the requirements to raise awareness.\u003c/p\u003e\n"]]],["Merchants must meet Google Merchant Center website requirements for Free Listings and Paid Ads. The system should auto-detect and display the status of five requirements: site accessibility, refund/terms of service policies, contact method, secure/complete checkout, and a secure URL. Merchants should be guided to resolve unmet requirements, either within the initial setup process or later. If auto-detection isn't possible, display the requirements and force manual confirmation. Using minimal implementation increases risks for merchants.\n"],null,["1.6 Policy Check\n----------------\n\n### Introduction/Business Impact\n\n*** ** * ** ***\n\nMerchants not only need to meet the account requirements for Free Listing and Paid Ads, they need to meet the Merchant Center website requirements. Learn more about the [Merchant Center Website Requirements](https://support.google.com/merchants/answer/6363310#website-requirements).\n\nBecause of these website requirements, we want to have a step in the onboarding process where merchants are aware of these requirements and be able to fix them if needed.\n\n### UX Guidance\n\n*** ** * ** ***\n\nThis is an example where a system auto-detects the status of the five Google online store requirements and surfaces it on UIs. Ideally, the storebuilder will help the merchants complete all the website requirements upstream. Otherwise, the storebuilder will provide the merchants with direct access to complete all the requirements during onboarding.\n\nWe also provide the option for merchants to skip this step during onboarding and complete it later. Then we guide merchants to complete the online store requirements post-onboarding.\n\nWe highly recommend using contextual or overlay pages to reduce redirects. Merchants can easily get lost while navigating between Google plug-in and store builder pages, which increases the churn rate.\n\n### Tech Guidance\n\n*** ** * ** ***\n\nPresent the following Merchant Center website requirements to the merchant so they can confirm their website meets the requirements:\n\n- Ensure the site is not password protected and accessible to customers\n- Add a Refund and Terms of service\n- Add a store contact method\n- Set up secure checkout and complete checkout\n- Confirm your store URL begins with https://\n\n#### Recommended implementation\n\n**Auto detection:** We recommend building an automated which auto-detects the status of the 5 Google online store requirements and surfaces it on UIs.\n\n**Ease of making updates to requirements which are not met:** if there changes need to be made to meet the website requirements, These steps should link to functionality in the platform where merchants can update this information to make sure it is included on their website.\n\n#### Minimal implementation\n\nIf you can't build an automated system which auto-detects or make it simple for merchants to make edits, then we recommend showing the 5 website requirements and forcing the merchant to manually click on checkboxes so they are aware of these requirements.\n\nKeep in mind, this implementation method could cause a lot of account suspensions for not meeting our website requirements. This could cause merchants to easily give up and no longer try to fix the issue to continue onboarding."]]