email

email · Recommended

Appears in

Organization

What is it?

email is the contact email address for an organization. It provides a direct communication channel that search engines can surface in business listings and knowledge panels. For organizations that accept customer inquiries by email, this field makes that address machine-readable and attributable to the correct entity.

The value is a plain text string containing a valid email address. No formatting beyond the raw address is expected.

Why this matters for AEO

AI answer engines answering "how do I contact [company]?" or "what is [company]'s email address?" can surface email directly from structured data. Without it, an AI system must scrape or infer contact information from unstructured page content, which is less reliable.

Google's Organization structured data documentation lists email as a recommended field for the organization Knowledge Panel. When a user asks Google Assistant or Siri for a company's contact email, the structured data value is the primary source. Including email removes ambiguity about which address belongs to this specific entity versus other entities on the same domain.

What the specs say

Schema.org:email expects Text. "Email address." [Source: https://schema.org/email]

Google: Recommended for Organization. "The email address to contact your business, if applicable." [Source: https://developers.google.com/search/docs/appearance/structured-data/organization]

How to find your value

Use a monitored, public-facing email address that customers or partners can contact. Avoid:

• Personal email addresses of individual employees
• Temporary or campaign-specific addresses
• Addresses that will change if a staff member leaves

Good options: hello@company.com, info@company.com, support@company.com, or a department-specific address for the primary contact function.

Format and code

email expects a valid email address string:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Basecamp",
  "url": "https://basecamp.com",
  "email": "support@basecamp.com"
}

With multiple contact options (use ContactPoint for structured contact channels):

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Basecamp",
  "email": "support@basecamp.com",
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer support",
    "email": "support@basecamp.com",
    "availableLanguage": "English"
  }
}

Invalid, mailto: prefix not needed:

{
  "@type": "Organization",
  "email": "mailto:support@basecamp.com"
}

The email field expects a plain address string, not a mailto: URI. Use mailto: only in HTML href attributes.

Webflow implementation

Static pages

Add email to your organization JSON-LD block in Site Settings > Custom Code or Page Settings > Custom Code:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company",
  "url": "https://yoursite.com",
  "email": "hello@yourcompany.com"
}
</script>

CMS template pages

If your CMS stores contact email per record (useful for directory or multi-brand sites), bind it with an embed:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "{{wf {"path":"business-name"} }}",
  "email": "{{wf {"path":"contact-email"} }}"
}
</script>

Use a plain text CMS field for the email address.

In Schema HQ

The email field is set in the Organization schema configuration panel. Enter it once and Schema HQ adds it to the structured data block across all pages that use the Organization schema template.

Real examples

HubSpot :

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "HubSpot",
  "url": "https://hubspot.com",
  "email": "support@hubspot.com",
  "telephone": "+1-888-482-7768",
  "sameAs": [
    "https://www.linkedin.com/company/hubspot",
    "https://twitter.com/HubSpot"
  ]
}

Related fields

• telephone — primary phone contact number
• contactPoint — structured contact channel with type, hours, and language
• url — organization website
• name — organization name
• faxNumber — fax contact number

FAQ

Does Google display the email field in search results?

Google may include it in the Knowledge Panel for an organization. It is not currently used for standalone rich results, but it feeds the Knowledge Graph and surfaces in answer engine responses to "how to contact" queries.

Should I use a department email or a general address?

A general contact address (info@, hello@, contact@) is appropriate for the root Organization. If you want to expose specific department contacts, use contactPoint with contactType set to the appropriate value (customer support, sales, technical support).

Is email used for spam purposes if included in structured data?

Structured data in JSON-LD script blocks is not directly visible to casual visitors, but it is machine-readable. Use an address that you already publicly display on your contact page, since it is equally discoverable there. The structured data use adds no meaningful exposure beyond what is already on the page.