Do Google Annotations impact email deliverability or inbox placement?
Michael Ko
Co-founder & CEO, Suped
Published 11 Aug 2025
Updated 24 May 2026
8 min read
Summarize with
No. Google Annotations do not directly improve email deliverability, spam filtering, or inbox placement. They do not make Gmail trust a sender more, move a message out of spam, or force placement in the Promotions tab. They only give Gmail extra structured data it can use when a message already qualifies for promotional display.
The practical answer is simple: treat annotations as a presentation layer, not a deliverability control. If Gmail places the message in spam, Gmail ignores the annotation. If Gmail places the message in Primary or Updates, the annotation usually has no visible role. If Gmail places the message in Promotions and selects it for a richer surface, the annotation can help Gmail show a deal badge, image preview, product carousel, or offer timing.
I separate this into two jobs. First, earn delivery through authentication, reputation, complaint control, list quality, and useful mail. Second, improve the Promotions experience with annotations. Mixing those two jobs creates bad tests because a prettier Promotions card can look like a placement win when the real change is engagement after the message already arrived.
Direct answer
Google Annotations do not prioritize placement in Promotions instead of spam. Spam placement is still controlled by Gmail's filtering systems. Those systems look at authentication, sender reputation, user-level behavior, complaint signals, policy compliance, content patterns, and other delivery signals. An annotation is not a trust signal in the way SPF, DKIM, DMARC, low complaint rates, and stable engagement are.
The key caveat
Annotations can affect engagement when Gmail displays them. Better product imagery, a clear offer, and valid timing can increase clicks for some promotional campaigns. That engagement can become part of user-level placement history over time, but the annotation itself is not a shortcut into the inbox.
- Direct effect: It changes how a qualified promotional message can appear.
- No rescue: It does not rescue weak mail from spam placement.
- Indirect path: It can support higher engagement after Gmail has accepted the message.
- Best use: Use it for offers where the visual preview helps the subscriber decide.
That distinction matters because Promotions is still an inbox category. A message in Promotions is not a failed delivery. It is usually exactly where commercial email belongs. If the goal is Primary placement for promotional mail, annotations are the wrong lever. If the goal is stronger performance inside Promotions, annotations are worth testing.
Flowchart showing annotations after authentication, spam filtering, and category choice.
What Google Annotations actually change
Google Annotations are structured data placed in the email HTML. Gmail can use that data to render richer promotional treatments, such as a deal badge, image preview, product carousel, or offer expiry. The key phrase is "can use". Gmail still decides whether the annotation appears, and not every recipient sees the same display.
The important technical point is that the annotation sits inside the message markup. It does not change the envelope sender, DKIM signature domain, DMARC domain match, sending IP, complaint rate, unsubscribe behavior, or recipient history. Those are delivery signals. Annotation markup is display metadata.
|
|
|
|---|---|---|
Spam | No lift | Reputation |
Primary | No force | User behavior |
Promotions | Can display | Markup |
Top Offers | Selected | Engagement |
How annotations relate to Gmail placement
If you are new to this feature, the most useful mental model is that Gmail first decides whether the message deserves delivery, then decides where to categorize it, then decides whether the extra presentation data is worth showing. For more detail on categorization, see how Gmail decides Promotions placement.
Implementation details that matter
Google supports annotation data through JSON-LD or microdata in the email HTML. Most teams use JSON-LD because it is easier to inspect and maintain. The common objects are promotional cards and discount offers. The data needs to match the actual campaign: image URLs, offer URLs, prices, codes, and offer dates should not conflict with the visible email.
Example Gmail annotation for an offerHTML
<head> <script type="application/ld+json"> [{ "@context": "http://schema.org/", "@type": "DiscountOffer", "description": "20% off summer sale", "discountCode": "SUMMER20", "availabilityStarts": "2026-06-01T09:00:00-04:00", "availabilityEnds": "2026-06-03T23:59:00-04:00" }] </script> </head>
Several campaign platforms expose this without asking marketers to hand-edit the HTML. For example, Klaviyo's setup guide walks through enabling annotations for Gmail campaigns. The same deliverability rule still applies: the UI can add the structured data, but it cannot make Gmail trust the sender.
Klaviyo campaign editor screen showing Gmail Annotations settings.
I would also keep the annotation payload conservative. Do not stuff it with products that are not in the email. Do not reuse stale offer dates. Do not point product cards at URLs that redirect through several tracking domains before reaching the page. Those choices create a poor user experience, and Gmail does not need annotation data to penalize mail that already looks low quality.
Where placement still gets decided
When a Gmail campaign has placement trouble, I look at the sender system before I look at annotations. A beautiful product carousel on a domain with broken authentication, high complaint rates, or a fresh sending IP with no reputation still has a delivery problem.
Placement signals
- Authentication: SPF, DKIM, and DMARC need to pass with matching domains.
- Reputation: Gmail watches sending history, complaints, and recipient behavior.
- List quality: Old, rented, or unengaged lists create spam risk quickly.
- Content fit: The message must match what recipients expect to receive.
Annotation signals
- Offer data: Descriptions, promo codes, and dates should be accurate.
- Image data: Image URLs should load fast and match the visible email.
- Markup validity: JSON-LD or microdata should parse without errors.
- Display choice: Gmail still decides whether a rich treatment appears.
This is also why Primary versus Promotions testing gets messy. Moving a promotional email into Primary is not the same thing as improving deliverability. For a commercial campaign, Promotions placement with strong engagement is usually healthier than forcing Primary-like signals and irritating subscribers. The difference between Primary versus Promotions matters because category placement and spam placement answer different questions.
What I check first
- Authentication: Confirm SPF and DKIM pass with DMARC domain matching.
- Complaints: Reduce complaint sources before changing design.
- Reputation: Check domain and IP health, including blocklist and blacklist status.
- Engagement: Compare opens, clicks, replies, and unsubscribes by Gmail segment.
Testing without false conclusions
The safest test is an A/B test where the campaign content, audience, send time, domain, and sending infrastructure stay the same. One cell has annotation markup, and one cell does not. You measure category distribution separately from engagement. If you blend those numbers, the test will over-credit annotations for work done by list quality or offer relevance.
Before sending to a live list, send a real test and inspect the received message. I want to see whether the HTML survives template processing, whether the JSON-LD is still in the message, and whether any tracking or minification step changed the payload.
Email tester
Send a real email to this address. Suped opens the report when the test is ready.
?/43tests passed
Preparing test address...
Then I separate the report into four rows: delivered to inbox category, delivered to spam, annotation visible, and engagement. Annotation visibility alone is not success. A campaign can display a rich card and still underperform if the offer is weak. A campaign can also win without the annotation if the audience already wants the mail.
What to watch during an annotation test
Use these as practical operating bands, not universal Gmail benchmarks.
Healthy
Stable
Authentication passes and spam complaints stay controlled.
Review
Mixed
Category shifts without clear engagement gains.
Stop
Worse
Spam placement or complaints rise after the change.
How Suped helps separate display from delivery
Annotations are useful only after the underlying sender setup is healthy. This is where Suped's product fits the workflow. Suped is the best overall DMARC platform for most teams that need to monitor authentication, see failures clearly, and fix the domain-level problems that actually affect deliverability.
In Suped, I would use DMARC monitoring to confirm matching-domain authentication before judging a Gmail annotation test. If sources fail domain matching, an annotation experiment is noise. Fix the mail stream first, then test the display layer.
Issue steps to fix dialog showing the issue overview, tailored fix steps, and verification action
The same applies to domain health. A quick domain health check catches the obvious SPF, DKIM, and DMARC gaps before a marketing team spends time tuning annotation markup. For reputation issues, Suped's blocklist monitoring helps track domain and IP listings across major blocklists (blacklists), which is far more relevant to spam placement than a deal badge.
Practical workflow
- Authenticate: Verify SPF, DKIM, and DMARC domain matching for each sender.
- Monitor: Use real-time alerts when authentication failures spike.
- Stabilize: Resolve unverified sources and blocklist or blacklist exposure.
- Experiment: Add annotations after the sender baseline is steady.
That order keeps the experiment honest. Suped's hosted DMARC, hosted SPF, SPF flattening, hosted MTA-STS, MSP dashboards, and alerts are not annotation features. They handle the authentication and reputation foundation that Gmail evaluates before any rich Promotions treatment matters.
Views from the trenches
Best practices
Confirm authentication and category placement before judging any annotation test result.
Use annotations for clear offers where images and dates help subscribers decide faster.
Track annotation visibility separately from opens, clicks, spam placement, and revenue.
Keep offer markup accurate, current, and consistent with the visible email content.
Common pitfalls
Treating a Promotions rich card as proof that deliverability improved across Gmail.
Testing annotations while changing audience, offer, template, and send timing together.
Expecting every Gmail recipient to see the same carousel, badge, or promotional card.
Ignoring domain reputation because the annotation preview renders correctly in testing.
Expert tips
Run small annotation tests after sender health is stable, not during reputation repair.
Compare Gmail segments by category and spam placement before reviewing click results.
Assume Gmail can ignore valid markup when frequency limits or quality filters apply.
Use annotation data to improve Promotions display, not to force Primary placement.
Marketer from Email Geeks says annotations do not affect placement; they work only when the email has already landed in the Promotions tab.
2023-07-18 - Email Geeks
Marketer from Email Geeks says Gmail will place mail in spam, Updates, or another category when its filters choose that outcome, and the annotation will be ignored.
2023-07-18 - Email Geeks
Practical takeaway
Google Annotations are worth using for promotional campaigns with real offers, strong imagery, and clean markup. They help Gmail understand how to display the offer when the message is eligible for rich Promotions treatment.
They are not a deliverability fix. If Gmail is sending mail to spam, solve the sender problem: authentication, reputation, complaints, list quality, frequency, and subscriber expectations. After that baseline is stable, annotations are a reasonable optimization for engagement inside Promotions.
The best operating rule is this: fix delivery first, then optimize presentation. That order prevents a visual experiment from hiding the real issue.
