XooCode(){

ContactPointOption

ContactPointOption is a schema.org Enumeration for special capabilities on a ContactPoint. It is the value of contactOption, typically array-valued.

It has 2 members:

  • HearingImpairedSupported: the contact point supports hearing-impaired callers (TTY / TDD, relay service).
  • TollFree: the number is toll-free to the caller.

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

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

schema.org/ContactPointOption
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ContactPoint",
  "contactType": "customer support",
  "telephone": "+1-800-555-0700",
  "contactOption": [
    "https://schema.org/TollFree",
    "https://schema.org/HearingImpairedSupported"
  ],
  "availableLanguage": ["en", "es"],
  "areaServed": { "@type": "Country", "name": "United States", "identifier": "US" }
}
</script>

Why publish contactOption

HearingImpairedSupported is a meaningful accessibility signal that lets Deaf and hard-of-hearing users identify reachable customer-service numbers. TollFree is a commercial signal that cost-conscious callers and AI assistants filter on.

Minimal valid version

The smallest markup that still produces a valid ContactPointOption 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/ContactPointOption (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ContactPoint",
  "contactType": "customer support",
  "telephone": "+1-800-555-0700",
  "contactOption": "https://schema.org/TollFree"
}
</script>

Google rich results this unlocks

ContactPointOption is a structural type. It does not produce a rich result on its own.

Its value comes from combining it with a primary type whose markup earns a rich result (Article, Product, Event, and so on). ContactPointOption becomes the trunk that the primary type branches off viamainEntityorbreadcrumb. Include it on every page as the backbone of your markup.

Common ContactPointOption 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

    HearingImpairedSupported on a non-TTY line

    Wrong
    Flagging HearingImpairedSupported when the number is not actually TTY-accessible
    Right
    Only flag when the line is verifiably TTY-capable (or via relay service)

    Accessibility misrepresentation is a harm; only flag support you can deliver.

Schema properties in this example

ContactPointOptionEnumerationHearingImpairedSupportedTollFreeContactPointcontactTypetelephonecontactOptionavailableLanguageareaServedCountry

About the example data

Xoo Code's customer-support contact point on a toll-free number with TTY support.

Comments

Loading comments...

Leave a comment