How can a contact point declare languages and contact options?

Definition: Schema.org defines ContactPoint as a contact point, with a Customer Complaints department as an example. Its availableLanguage, contactOption and contactType properties describe language availability, service options and the purpose of the contact point.

Key facts

• Schema.org's ContactPoint definition describes a contact point and lists availableLanguage, contactOption and contactType among its properties.
• availableLanguage accepts Language or Text values and recommends language codes from the IETF BCP 47 standard.
• contactOption accepts ContactPointOption and covers options such as a toll-free number or support for hearing-impaired callers, according to Schema.org's property definition.
• contactType accepts Text and specifies the kind of contact point, such as sales or public relations, in Schema.org's definition.
• Schema.org's fuller ContactPoint example describes multiple contact numbers, including toll-free and hearing-impaired numbers, with several contact categories.

What does availableLanguage describe?

availableLanguage records a language someone may use with or at the item, service or place. Schema.org lists Language and Text as its expected value types, and its ContactPoint table includes the property on ContactPoint.

The property page recommends language codes from the IETF BCP 47 standard. The ContactPoint example uses text values in an array for a technical support point:

"availableLanguage" : ["English","French"]

The example therefore gives a concrete way to represent more than one language on one contact point. A site can use a Language value when it needs the structured type listed by Schema.org.

How do contactOption and contactType differ?

contactOption describes an option available on a point. Schema.org gives a toll-free number and support for hearing-impaired callers as examples, and its expected type is ContactPointOption. In the fuller example, one point has "contactOption" : "TollFree", while another has "contactOption" : ["HearingImpairedSupported","TollFree"].

contactType describes the point's purpose. Schema.org expects a Text value and explains that a person or organization can have different points for different purposes, including sales and public relations. The example uses values such as "technical support" and "bill payment".

What can the JSON-LD look like?

Schema.org's example places several ContactPoint objects in an organization's contactPoint property. One of those objects combines a telephone number, a purpose, a toll-free option, an area served and two available languages:

{ "@type" : "ContactPoint",
  "telephone" : "+1-877-453-1304",
  "contactType" : "technical support",
  "contactOption" : "TollFree",
  "areaServed" : ["US","CA"],
  "availableLanguage" : ["English","French"]
}

This pattern keeps separate contact points available for separate purposes. The same example includes a customer service point with HearingImpairedSupported and TollFree, and a bill payment point with TollFree.

What should a site check?

The property names should match Schema.org's spelling and casing. availableLanguage can use the documented Language or Text value types, contactOption uses ContactPointOption, and contactType uses Text. The language property page points to BCP 47 for language codes, while the ContactPoint example uses English and French as text values.

Related terms

• Structured data
• JSON-LD
• Organization structured data

FAQ

Can you use a language name for availableLanguage?

Yes. Schema.org lists Text as an expected type alongside Language, and its ContactPoint example uses English and French as text values.

Should you use the same contactType for every contact point?

Use a text value that identifies the point's purpose. Schema.org's example separates customer service, technical support and bill payment points.

How can you represent more than one contact option?

The Schema.org example uses an array containing HearingImpairedSupported and TollFree for one ContactPoint.

Sources

1. Schema.org, "ContactPoint", 16 September 2026
2. Schema.org, "availableLanguage", 16 September 2026
3. Schema.org, "contactOption", 16 September 2026
4. Schema.org, "contactType", 16 September 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer