XooCode(){

EmailMessage

EmailMessage is a Message subtype specifically for email. It adds no properties of its own. The @type value is what differentiates it from generic Message: Gmail and other email clients read EmailMessage specifically to trigger email-specific rendering and rich snippets in the inbox.

For a complete property walkthrough, see the Message example. Replace "@type": "Message" with "@type": "EmailMessage". The most useful properties for emails are sender, toRecipient, ccRecipient, dateSent, messageAttachment, and about (linking to the order, reservation, or event the email is about).

Full example of schema.org/EmailMessage json-ld markup

The markup is verified as valid with Rich Results Test from Google.

Highlight legend:Required by GoogleRecommendedOptional
schema.org/EmailMessage
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "EmailMessage",
  "name": "Order Confirmation: XOO-2026-4821",
  "sender": {
    "@type": "Organization",
    "name": "Xoo Code Shop Dunmore",
    "email": "orders@xoocode.com"
  },
  "toRecipient": {
    "@type": "Person",
    "name": "Erik Dahl",
    "email": "erik@example.com"
  },
  "dateSent": "2026-07-15T09:22:00-04:00",
  "about": {
    "@type": "Order",
    "orderNumber": "XOO-2026-4821"
  }
}
</script>

Minimal valid version

The smallest markup that still produces a valid EmailMessage entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

schema.org/EmailMessage (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "EmailMessage",
  "sender": { "@type": "Organization", "name": "Xoo Code Shop Dunmore" },
  "toRecipient": { "@type": "Person", "name": "Erik Dahl" },
  "dateSent": "2026-07-15T09:22:00-04:00"
}
</script>

Google rich results this unlocks

Markup matching this example makes your page eligible for the following Google Search rich results. The primary target drives the required / recommended property classification in the advanced code block above.

Common EmailMessage mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

  1. 01

    Using Message instead of EmailMessage in email markup

    Wrong
    "@type": "Message" inside an HTML email
    Right
    "@type": "EmailMessage"

    Gmail's email markup features specifically read EmailMessage. Generic Message does not trigger email-specific rendering. For emails, always use the more specific EmailMessage subtype.

Schema properties in this example

EmailMessageMessageCreativeWorknamesenderOrganizationemailtoRecipientPersondateSentaboutOrderorderNumber

About the example data

An order confirmation email from Xoo Code Shop Dunmore to a customer who purchased a XooTee. The about property references the Order entity.

Comments

Loading comments...

Leave a comment