이메일에서 스키마를 어떻게 사용할지 기대됩니다. 오늘 자체 통합 테스트를 시작할 수 있습니다. x@gmail.com에서 x@gmail.com으로 보내는 모든 스키마는 Google 제품에 표시됩니다. 지금 바로 사용해 보세요.
마크업된 이메일을 사용자에게 전송할 준비가 되면 Google에 등록해야 합니다. 다음 절차를 따르세요.
아래에 나열된 모든 가이드라인과 요구사항을 충족하는지 확인하세요.
마크업/스키마를 포함하여 프로덕션 서버 (또는 유사한 DKIM/SPF/From:/Return-Path: 헤더가 있는 서버)에서 실제 이메일을 schema.whitelisting+sample@gmail.com으로 보냅니다. 이는 등록 가이드라인에 나열된 모든 가이드라인과 요구사항을 준수하는지 확인하기 위해 필요합니다.
테스트/빈 이메일을 보내거나 스키마가 포함되지 않은 이메일을 보내거나 검토를 위해 이메일을 보내지 않으면 애플리케이션이 자동으로 삭제됩니다.
이메일을 보내기 전에 마크업이 올바른지 확인하세요. 자세한 내용은 스키마 테스트를 참고하세요. 특히 이메일이 이메일 마크업 테스터를 통과하고 오류가 없는지 확인하고 가능한 한 많은 데이터를 포함해야 합니다.
Gmail은 이메일을 전달할 때 모든 마크업을 삭제합니다. 이메일을 전달하지 말고 직접 보내세요.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["필요한 정보가 없음","missingTheInformationINeed","thumb-down"],["너무 복잡함/단계 수가 너무 많음","tooComplicatedTooManySteps","thumb-down"],["오래됨","outOfDate","thumb-down"],["번역 문제","translationIssue","thumb-down"],["샘플/코드 문제","samplesCodeIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-08-29(UTC)"],[],[],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."]]
