schema.org/ContactPointNo rich result
ContactPoint schema
A way to reach an organisation, typed by the kind of contact it handles.
Where to use it
Nested inside Organization.
A complete example
Valid as written, with every required property and the recommended ones that carry real information.
contact-point.json
{
"@context": "https://schema.org",
"@type": "ContactPoint",
"contactType": "customer support",
"email": "hello@example.com",
"telephone": "+1-555-0100",
"areaServed": "Worldwide",
"availableLanguage": "en"
}Properties
| Property | Status |
|---|---|
contactType | Required |
email | Recommended |
telephone | Recommended |
areaServed | Recommended |
availableLanguage | Recommended |
The three mistakes this type attracts
- 01contactType outside the documented list.
- 02A telephone number without an international prefix.
- 03Listing a contact method that is not monitored.
Related types
Where this appears in the playbook
- Structured data: what each type is for and which ones earned their place.
- The schema graph: composing types into one graph with stable identifiers.
- One JSON-LD script per page, holding one @graph
- Stable @id anchors that cross-reference rather than duplicate
- Optional fields are omitted, never emitted as empty strings
Questions
What is the ContactPoint schema type for?
A way to reach an organisation, typed by the kind of contact it handles. Use it on: nested inside Organization.
Which ContactPoint properties are required?
ContactPoint requires one property: contactType. It also recommends 4: email, telephone, areaServed, availableLanguage.
Does ContactPoint produce a rich result?
ContactPoint does not produce a Google rich result. It is still worth shipping, because its value is entity resolution and answer extraction rather than search result presentation.
What is the most common ContactPoint mistake?
The most common ContactPoint mistake is: contactType outside the documented list.