向 Google 注册
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
我们很高兴看到您计划如何在电子邮件中使用架构。您可以立即开始测试自己的集成。您发送给自己的所有架构（从 x@gmail.com 到 x@gmail.com）都将显示在 Google 产品中。快来试试吧！
当您准备好向用户发布标记后的电子邮件时，需要向 Google 注册。请按以下流程操作：
- 请确保您符合下列所有准则和要求。
- 从您的生产服务器（或具有类似 DKIM/SPF/From:/Return-Path: 标头的服务器）发送一封包含标记 / 架构的真实电子邮件到 schema.whitelisting+sample@gmail.com。我们需要此电子邮件，以便检查您是否符合注册指南中列出的所有准则和要求。
- 如果您发送的是测试电子邮件/空白电子邮件（不包含架构），或者您未发送电子邮件以供审核，您的申请将被静默舍弃。
- 在发送电子邮件之前，请确保标记正确无误。如需了解详情，请参阅测试架构。请务必确保电子邮件通过 Email 标记测试工具，并且没有错误，同时确保尽可能多地包含数据。
- Gmail 会在转发电子邮件时移除所有标记。请勿转发电子邮件，而是直接发送。
- 填写注册表单，我们会尽快回复您。
注册指南
为了确保您发送的架构能够得到处理，您必须遵循以下准则：
电子邮件发件人质量指南
- 电子邮件必须通过 DKIM 或 SPF 进行身份验证
- SPF 检查或 DKIM 签名的顶级域名 (TLD) 必须与您的
From: 电子邮件地址的 TLD 一致。
- 例如，如果您使用
From: foo@bar.com，则 DKIM 或 SPF 必须适用于 bar.com 或 sub.bar.com
- Gmail 只会检查您
Return-Path: 电子邮件的网域中的 SPF。如果您仅依赖 SPF 而不依赖 DKIM，则您的 Return-Path: 电子邮件地址必须与您的 From: 电子邮件地址的顶级网域 (TLD) 相匹配。
- 如需快速检查您的 SPF 或 DKIM 设置是否正确，请参阅我们的电子邮件身份验证帮助文章。
- 电子邮件必须来自静态电子邮件地址，例如 foo@bar.com
- 电子邮件必须遵循防止发送给 Gmail 用户的邮件遭到屏蔽或被列为垃圾邮件指南
- 您的网域持续发送大量邮件（每天至少向 Gmail 发送数百封电子邮件）的历史记录至少有几周。
- 用户提出的垃圾内容投诉非常少。
操作 / 架构指南
- 应使用最高保真度的操作。例如，如果可以通过应用内操作（一键操作、回复活动邀请、评价）实现互动，则必须使用该操作。对于更复杂的互动，可以使用“前往操作”。
- 对于预期互动率较高的事务性电子邮件，应使用操作。不应在促销批量邮件中使用。
- 常用操作：
- 必须深层链接到可执行相应操作的特定网页。
- 按钮的标签需要反映要采取的明确操作，并且必须与用户将要前往的网页相符
- 操作标签不应包含标点符号或全大写字母。必须简短明了。
- 如果应用内操作可用于您的使用情形，您必须使用应用内操作，而不能使用“前往”操作（例如，“验证电子邮件地址”或“请查看”应使用应用内操作）。
- 目前，我们仅针对具有高互动率的非常具体的高价值使用情形（例如航班值机、货运跟踪链接）批准 Go-To 行动。
- 处理操作请求的服务具有较低的失败率和快速的响应速度。
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-08-29。
[null,null,["最后更新时间 (UTC)：2025-08-29。"],[],[],null,["# Register with Google\n\nWe are excited to see how you plan to use schemas in email. You can start testing your own integration today. All schemas you send to yourself (from x@gmail.com to x@gmail.com) will be displayed in Google products. So go ahead and try it out now!\n\nWhen you are ready to launch your marked up emails to your users, you will need to register with Google. Please follow this process:\n\n- Make sure that you meet all the guidelines and requirements listed below.\n- Send a real-life email coming from your production servers (or a server with similar DKIM/SPF/From:/Return-Path: headers) including the markup / schema to [schema.whitelisting+sample@gmail.com](mailto:schema.whitelisting+sample@gmail.com). We need this in order to check that you comply with all the guidelines and requirements listed in [Registration Guidelines](#registration_guidelines).\n - If you send a test/blank email, an email that does not contain schema or if you don't send an email for review your application will be silently discarded.\n - Make sure that the markup is correct prior to sending the email. For more details see [Testing your Schema](https://developers.google.com/workspace/gmail/markup/testing-your-schema). Especially make sure the email passes the [Email markup Tester](https://www.google.com/webmasters/markup-tester/) and that there are no errors, also make sure to include as much data as possible.\n - Gmail removes all markup when forwarding an email. Do not forward the email but send it directly.\n- Fill out the [registration form](https://docs.google.com/a/google.com/forms/d/e/1FAIpQLSfT5F1VJXtBjGw2mLxY2aX557ctPTsCrJpURiKJjYeVrugHBQ/viewform?pli=1) and we will get back to you.\n\nRegistration Guidelines\n-----------------------\n\nIn order for the schema you send to be processed, the following guidelines must be met:\n\n### Email Sender Quality guidelines\n\n- Emails must be [authenticated via DKIM or SPF](https://support.google.com/mail/answer/180707)\n- The top-level domain (TLD) of the SPF check or DKIM signature must match the TLD of your `From:` email address.\n - e.g. if you use `From: foo@bar.com` the DKIM or SPF must be for `bar.com` or `sub.bar.com`\n - Gmail only checks the SPF on the domain of your `Return-Path:` email. If you only rely on SPF and not DKIM your `Return-Path:` email must match the TLD of your `From:` email.\n - To quickly check if your SPF or DKIM settings are correct have a look at our [Email Authentication help article](https://support.google.com/mail/answer/180707).\n- Emails must come from a static email address, e.g. foo@bar.com\n- Emails must follow the [Prevent mail to Gmail users from being blocked or sent to spam](https://support.google.com/mail/answer/81126) guidelines\n- Consistent history of sending a high volume of mail from your domain (order of hundred emails a day minimum to Gmail) for a few weeks at least.\n- A very very low rate of spam complaints from users.\n\n### Actions / Schema Guidelines\n\n- The highest-fidelity action available should be used. For example, if an interaction can be achieved by an In-App Action (One-Click, RSVP, Review), that must be used. For more complex interactions, Go-To Actions can be used.\n- Actions should be used for transactional mail where a high interaction rate is expected. They should not be used on promotional bulk mail.\n- Go-To Actions:\n - Must deep link into the specific page on which the action can be performed.\n - Label of button needs to reflect clear action to be taken and must be true to page the user is going to\n - Label of action should not contain punctuation or all caps. Must be short and concise.\n - If an In-App action can be used for your usecase you must use the In-App action and not the Go-To action (e.g. \"Verify Email Address\" or \"Please Review\" should use In-App actions).\n - We are currently only approving Go-To actions for very specific high-value usecase with high interaction rate (e.g. Flight Check-in, Shipment tracking links).\n- Low failure rate and fast response for services handling Action Requests."]]
