AMP Email Whitelisting: How to Get Approved by Gmail & Yahoo

You've built an interactive AMP email with dynamic content, real-time data, and in-email forms. But before your recipients can actually see the AMP version, you need to register as an approved AMP sender with Gmail and Yahoo. Here's exactly how to do it.

1 Prerequisites

Before you apply for whitelisting, you must have these in place. Gmail and Yahoo will reject applications that don't meet all requirements.

Email Authentication (Required)

• SPF (Sender Policy Framework) — Your DNS must have an SPF record authorizing your sending IP/service. This tells receiving servers "yes, this IP is allowed to send email for our domain."
• DKIM (DomainKeys Identified Mail) — Your emails must be cryptographically signed. The DKIM signature domain must match your sender address domain (e.g., if you send from noreply@min8t.com, the DKIM d= field must be min8t.com).
• DMARC — A DMARC policy must be published in your DNS. At minimum: v=DMARC1; p=none; — but p=quarantine or p=reject is recommended.

Technical Requirements

• Valid public website — Your sender domain (e.g., min8t.com) must serve a live, publicly accessible website. Google checks this.
• Mass mailing history — You need an established track record of sending bulk email. Brand-new domains won't be approved.
• Low spam complaint rate — If your emails frequently get marked as spam, your application will be denied.
• CORS-compliant XHR endpoints — Any amp-list or amp-form endpoints must return proper AMP CORS headers (MiN8T handles this automatically for data sources and data storages).

2 Gmail Registration

Gmail is the largest AMP email client. Here's the exact process:

Step 1: Test Your AMP Email

Before applying, verify your AMP email works correctly in Gmail:

1. Send a test email from MiN8T to your own Gmail account
2. In Gmail, go to Settings → General → Dynamic email → Enable
3. Go to Developer settings → add your sender address as a trusted sender
4. Delete any previous test emails from the same sender (Gmail caches aggressively)
5. Send a fresh test and verify the AMP content renders correctly

Step 2: Send a Production Email to Google

Send a real, production-quality AMP email to:

ampforemail.whitelisting@gmail.com

This must be:

• A real email you'd send to customers (not a test or placeholder)
• Sent directly from your production sending infrastructure (not forwarded)
• Include both AMP and HTML MIME parts (MiN8T's export does this automatically)
• Free of bugs — Google will test your AMP content

Step 3: Fill Out the Registration Form

Complete the official Google AMP sender registration form:

https://forms.gle/fDqLE1gh4wMB6BeQ6

Step 4: Wait for Approval

Google typically responds within 5 business days. You will NOT receive any notification until you're approved (or rejected). No confirmation email, no progress updates — just silence until the decision.

3 Yahoo Registration

Yahoo uses the same registration form as Gmail. The process is nearly identical:

1. Send a production AMP email to: ampverification@yahoo.com
2. Fill out the same registration form: https://forms.gle/fDqLE1gh4wMB6BeQ6
3. Wait for approval

The same requirements apply: SPF, DKIM, DMARC, production-quality email, established sending history.

4 Clients That Don't Require Whitelisting

These email clients support AMP without any formal registration process:

For Mail.ru, FairEmail, and AOL, your AMP emails will render immediately as long as the email contains a valid text/x-amp-html MIME part with proper structure.

5 Testing Before Applying

Always test thoroughly before submitting your application:

1. MiN8T Test Send — Use the test email feature to send a 3-part MIME email to your Gmail with dynamic email enabled
2. Gmail "Show original" — Open the email → click three dots → "Show original" → verify you see text/plain, text/x-amp-html, and text/html MIME parts
3. AMP content renders — Interactive elements (forms, carousels, dynamic lists) should work in Gmail
4. HTML fallback works — Forward the email or view in Outlook — static HTML version should display correctly
5. Data endpoints accessible — If using amp-list with data sources, verify the endpoint returns JSON with proper CORS headers from outside your network

6 Common Rejection Reasons

Google will reject your application if:

• No email sent for review — You submitted the form but forgot to email ampforemail.whitelisting@gmail.com
• Test/placeholder email — You sent a demo email with placeholder content instead of a real production email
• Email lacks AMP MIME part — The email was sent as regular HTML without the text/x-amp-html part
• Forwarded email — Gmail strips the AMP part when forwarding. Send directly from your sending infrastructure.
• DKIM domain mismatch — Your DKIM signature domain doesn't match your sender address domain
• No DMARC record — Your DNS doesn't have a DMARC policy published
• New domain with no history — You need an established bulk sending reputation first
• Broken AMP content — Google tests your AMP email; if it has validation errors or broken interactivity, you'll be rejected

7 MiN8T Pre-Whitelisting Checklist

Use this checklist before submitting your application:

• ✓
  SPF record configured — DNS TXT record authorizes your sending service
• ✓
  DKIM signing active — Emails are cryptographically signed, domain matches sender
• ✓
  DMARC policy published — At minimum v=DMARC1; p=none;
• ✓
  Sender domain has public website — https://yourdomain.com loads worldwide
• ✓
  AMP email tested in Gmail — Dynamic content renders correctly
• ✓
  HTML fallback works — Email displays correctly in non-AMP clients
• ✓
  3-part MIME structure — Email has text/plain + text/x-amp-html + text/html
• ✓
  Data endpoints CORS-compliant — amp-list/amp-form endpoints return AMP CORS headers
• ✓
  Production email sent to Google — Real email to ampforemail.whitelisting@gmail.com
• ✓
  Production email sent to Yahoo — Real email to ampverification@yahoo.com
• ✓
  Registration form submitted — Google/Yahoo form

Last updated: April 2026. AMP email support and registration processes may change — always check the official AMP spec for the latest requirements.