註冊 Google
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
我們很期待看到您在電子郵件中運用結構化資料。您今天就能開始測試自己的整合。所有傳送給自己的結構化資料 (從 x@gmail.com 傳送至 x@gmail.com) 都會顯示在 Google 產品中。快來試試看吧！
準備好向使用者推出標記的電子郵件時，您需要向 Google 註冊。請按照下列流程操作：
- 請確認你符合下列所有規範和規定。
- 從正式伺服器 (或具有類似 DKIM/SPF/From:/Return-Path: 標頭的伺服器) 傳送包含標記 / 結構定義的實際電子郵件至 schema.whitelisting+sample@gmail.com。我們需要這封郵件，才能確認您遵守註冊指南中列出的所有規範和規定。
- 如果傳送測試/空白電子郵件、不含結構化資料的電子郵件，或是未傳送電子郵件以供審查，系統會自動捨棄這些郵件。
- 傳送電子郵件前，請確認標記正確無誤。詳情請參閱「測試結構定義」。請特別確認電子郵件通過電子郵件標記測試工具的測試，且沒有任何錯誤，並盡可能提供最多資料。
- 轉寄電子郵件時，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:電子郵件的頂層網域相符。
- 如要快速檢查 SPF 或 DKIM 設定是否正確，請參閱電子郵件驗證說明文章。
- 電子郵件必須來自靜態電子郵件地址，例如 foo@bar.com
- 電子郵件必須遵守「避免寄給 Gmail 使用者的郵件遭到封鎖或歸類為垃圾郵件」指南
- 網域持續傳送大量郵件 (至少每天傳送數百封郵件到 Gmail) 至少幾週。
- 使用者提出的垃圾郵件申訴比率極低。
動作 / 結構定義指南
- 請使用最高保真度的可用動作。舉例來說，如果應用程式內動作 (一鍵操作、回覆活動邀請、撰寫評論) 可達成互動，就必須使用這些動作。如需更複雜的互動，可以使用「前往動作」。
- 如果預期互動率較高，請將動作用於交易郵件。不適用於宣傳大量郵件。
- 前往動作：
- 必須深層連結至可執行動作的特定頁面。
- 按鈕標籤必須反映要採取的明確動作，且必須與使用者前往的頁面相符
- 動作標籤不得包含標點符號或全大寫字母。必須簡短明瞭。
- 如果應用程式內動作適用於您的用途，就必須使用應用程式內動作，而非「前往」動作 (例如「驗證電子郵件地址」或「請檢查」應使用應用程式內動作)。
- 目前我們只會核准互動率高的特定高價值用途的「前往」動作 (例如航班登機、貨運追蹤連結)。
- 處理動作要求的服務失敗率低且回應速度快。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-08-29 (世界標準時間)。
[null,null,["上次更新時間：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."]]
