2026 Structured Data Blueprint

The Ultimate ContactPoint
Schema Generator

A contact point—for example, a Customer Complaints department.

Includes:additionalTypealternateNameareaServedavailableLanguagecontactOptioncontactTypedescriptiondisambiguatingDescription+15 more

Instant JSON-LD Generation

Start Generating Sign up for Bulk Tools

Magic Build

Paste your URL below and our AI will automatically fill the ContactPoint fields for you.

Configuration

Live Generator

Why use ContactPoint?

Structured data like ContactPoint markup helps search engines identify the most important details about your content instantly, improving your chances of earning rich results.

Output Panel

Awaiting input...

Want to automate this?

Connect your site to SchemaGen and our AI will automatically extract and deploy schemas for you. No manual coding required.

Launch AI Generator

What is ContactPoint Schema?

A contact point—for example, a Customer Complaints department.

Why It Matters for SEO

Google uses ContactPoint structured data to understand the content and context of your pages. When correctly implemented, this schema can unlock rich results in Google Search — enhancing your listing with additional information that dramatically improves visibility and click-through rates.

Why Add ContactPoint Structured Data?

🔍

Appear in Rich Results

Structured data helps Google show enhanced results for your pages in search — including stars, prices, FAQs, and more.

📈

Boost Click-Through Rate

Rich snippets can increase CTR by up to 30% compared to plain search results — more clicks with the same ranking.

🤖

Feed AI Search Engines

AI answer engines like Perplexity and Google SGE use structured data to verify and cite facts from your content.

How to Implement ContactPoint JSON-LD

Generate

Use the form above to fill in your details and generate valid ContactPoint JSON-LD markup in seconds.

Copy

Copy the generated JSON-LD output code with one click — it's already formatted and ready to deploy.

Deploy

Paste the code into your <head> tag, or use SchemaGen's SDK to deploy without touching code.

Want to skip steps 2 & 3? Connect SchemaGen's SDK to deploy directly from the dashboard.

Properties You Can Include

ContactPoint schema supports the following schema.org properties. Required fields are the minimum Google needs to consider your markup valid; recommended fields unlock richer search result appearances.

Property	Description	Expected Type	Status
additionalType	An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. Typically the value is a URI-identified RDF class, and in this case corresponds to the use of rdf:type in RDF. Text values can be used sparingly, for cases where useful information can be added without their being an appropriate schema to reference. In the case of text values, the class label should follow the schema.org style guide.	Text, URL	Optional
alternateName	An alias for the item.	Text	Optional
areaServed	The geographic area where a service or offered item is provided.	AdministrativeArea, GeoShape, Place, Text	Optional
availableLanguage	A language someone may use with or at the item, service or place. Please use one of the language codes from the [IETF BCP 47 standard](http://tools.ietf.org/html/bcp47). See also inLanguage.	Language, Text	Optional
contactOption	An option available on this contact point (e.g. a toll-free number or support for hearing-impaired callers).	ContactPointOption	Optional
contactType	A person or organization can have different contact points, for different purposes. For example, a sales contact point, a PR contact point and so on. This property is used to specify the kind of contact point.	Text	Optional
description	A description of the item.	Text, TextObject	Optional
disambiguatingDescription	A sub property of description. A short description of the item used to disambiguate from other, similar items. Information from other properties (in particular, name) may be necessary for the description to be useful for disambiguation.	Text	Optional
email	Email address.	Text	Optional
faxNumber	The fax number.	Text	Optional
hoursAvailable	The hours during which this service or contact is available.	OpeningHoursSpecification	Optional
identifier	The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See [background notes](/docs/datamodel.html#identifierBg) for more details.	PropertyValue, Text, URL	Optional
image	An image of the item. This can be a URL or a fully described ImageObject.	ImageObject, URL	Recommended
mainEntityOfPage	Indicates a page (or other CreativeWork) for which this thing is the main entity being described. See [background notes](/docs/datamodel.html#mainEntityBackground) for details.	CreativeWork, URL	Optional
name	The name of the item.	Text	Required
owner	A person or organization who owns this Thing.	Organization, Person	Optional
potentialAction	Indicates a potential Action, which describes an idealized action in which this thing would play an 'object' role.	Action	Optional
productSupported	The product or service this support contact point is related to (such as product support for a particular product line). This can be a specific product or product line (e.g. "iPhone") or a general category of products or services (e.g. "smartphones").	Product, Text	Optional
sameAs	URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Wikidata entry, or official website.	URL	Optional
serviceArea	The geographic area where the service is provided.	AdministrativeArea, GeoShape, Place	Optional

Example ContactPoint JSON-LD

Here's what valid ContactPoint structured data looks like with sample values filled in. Use the generator above to replace these with your own data.

Example Output

{
  "@context": "https://schema.org",
  "@type": "ContactPoint",
  "name": "Example ContactPoint",
  "image": "https://example.com/images/example.jpg",
  "url": "https://example.com/page",
  "additionalType": "Example additionalType",
  "alternateName": "Example alternateName",
  "areaServed": {
    "@type": "AdministrativeArea",
    "name": "Example AdministrativeArea",
    "image": "https://example.com/images/example.jpg",
    "url": "https://example.com/page"
  },
  "availableLanguage": {
    "@type": "Language",
    "name": "Example Language",
    "image": "https://example.com/images/example.jpg",
    "url": "https://example.com/page"
  },
  "contactOption": {
    "@type": "ContactPointOption",
    "name": "Example ContactPointOption",
    "image": "https://example.com/images/example.jpg",
    "url": "https://example.com/page"
  }
}

Validate Your ContactPoint Schema

Once deployed, validate your schema is working correctly with our free audit tool. Paste your URL and we'll check for errors, missing properties, and Google Rich Result eligibility.

Free Schema Audit Tool →

Check your ContactPoint schema for errors and Rich Result eligibility

SchemaGen

The Ultimate ContactPoint Schema Generator