Check which requirements apply to your sending
Google distinguishes general senders from those sending more than 5,000 messages per day to personal Gmail accounts. Its guidance includes authentication, valid forward and reverse DNS, TLS and keeping reported spam rates below 0.3%. Bulk senders face additional SPF, DKIM, DMARC and alignment requirements. Verify the current rules directly.
Assign owners rather than collecting green ticks
A requirement is easier to maintain when someone owns the evidence and the response to a failure.
| Workstream | Owner to nominate | Evidence to retain |
|---|---|---|
| Authentication and DNS | Domain administrator | Approved configuration and a recent header sample. |
| Unsubscribe behavior | Marketing operations | A documented test of the actual campaign flow. |
| Complaint monitoring | Deliverability owner | Observation date and escalation decision. |
| Sending changes | ESP administrator | Change record and rollback plan. |
Test unsubscribe behavior in the actual message
Google requires one-click unsubscribe for relevant bulk marketing and subscribed messages, alongside a visible unsubscribe link. RFC 8058 defines the header-based one-click mechanism; a body link alone is not the same mechanism. Ask your sending platform how it implements the headers and test the recipient experience.
Repeat the review when the route changes
Adding a new automation, tracking domain or sending service can alter the configuration you previously checked. Keep an owner-approved change log and review representative messages after changes. A third-party diagnostic tool is supporting evidence, not certification of compliance by Google.
A question worth asking
Does passing a tool’s test mean Google has approved my sender?
No. Follow Google’s official requirements and monitor actual sending behavior. A diagnostic result is not a certification or a guarantee of acceptance.
Sources and scope
Checked: Public documentation linked below and the decision framework described on this page.
Not independently tested: Product accuracy, paid account workflows, support or delivery outcomes.
Reader should verify: Current terms and suitability for the actual sending setup. Never change production DNS from a generic example.
Last checked: September 2026.
Continue your investigation
Choose the next guide for the question that remains unanswered:
- SPF, DKIM and DMARC: a practical sender map
- Pre-send email checklist: a repeatable test protocol
- Email spam testing: turn warnings into a checklist
Partner link. Conditions can change; testing does not guarantee delivery.