ContactPage & Support Channel Schema (JSON-LD)
Structured data for Contact Us pages with official customer service hotlines, support emails, office hours, and ticketing endpoints.
Displayed below main page header or above the tool container. • Zero CLS Container
Production JSON-LD Code Block
Embed this structured data block directly into your HTML <head> or framework layout template.
{
"@context": "https://schema.org",
"@type": "ContactPage",
"name": "Contact OmniSEO Tools Engineering & Support",
"url": "https://omniseotools.com/contact",
"mainEntity": {
"@type": "Organization",
"name": "OmniSEO Technologies Inc.",
"contactPoint": [
{
"@type": "ContactPoint",
"contactType": "technical support",
"email": "support@omniseotools.com",
"telephone": "+1-800-555-0199",
"availableLanguage": [
"English",
"Arabic"
],
"hoursAvailable": {
"@type": "OpeningHoursSpecification",
"dayOfWeek": [
"Monday",
"Tuesday",
"Wednesday",
"Thursday",
"Friday"
],
"opens": "09:00",
"closes": "18:00"
}
}
]
}
}Typed Properties Specification (6 Fields)
Key Schema.org properties and sub-objects required to qualify for rich snippet treatment in Google Search.
| Property | Expected Type | Status | Description & Example |
|---|---|---|---|
| name | Text | Required | Contact page title. e.g. Contact OmniSEO Tools Engineering & Support |
| url | URL | Required | Canonical contact page URL. e.g. https://omniseotools.com/contact |
| contactPoint | ContactPoint | Array<ContactPoint> | Required | Direct communication channels (phone, email, hours). e.g. [{ "@type": "ContactPoint", ... }] |
| mainEntity | Organization | Required | Parent Organization entity. e.g. { "@type": "Organization", ... } |
| Text | Recommended | Direct support email inbox. e.g. support@omniseotools.com | |
| inLanguage | Text | Recommended | Primary contact page language. e.g. en-US |
Google Search Console Pitfalls & Critical Warnings
Avoid these 3 common validation traps, parser errors, and algorithmic policy penalties when deploying ContactPage schema.
Omitting contactType Property
Supplying a telephone without contactType (e.g. 'customer support', 'sales').
Always state contactType explicitly.
Non-Standard Phone Formatting
Writing '1-800-CALL-US' instead of international standard '+1-800-555-0199'.
Use RFC 3966 / E.164 international phone number formatting.
Missing Support Hours Availability
Failing to state when live support is reachable causes off-hours user frustration.
Include hoursAvailable with OpeningHoursSpecification.
Recommended Implementation Scenarios
Related Schema Blueprints
Explore complementary structured data blueprints across the Organization & Identity cluster.
Displayed below main page header or above the tool container. • Zero CLS Container