Contact Page Schema

Generate ContactPage JSON-LD with phone, email, mailing address and ContactPoint. Free schema markup tool, no sign-up needed.

About the tool

What is the SBMM Contact Page Schema Generator?

The SBMM Contact Page Schema Generator is a free online tool that builds ContactPage JSON-LD for your Contact Us page. Add your phone number, email address, mailing address, contact-point department and language, plus the Organization the page represents; get back a clean schema.org-compliant ContactPage block ready to paste into the head tag of your contact page.

ContactPage schema is the on-page signal that confirms how customers, journalists, and partners can reach your business. Google reads it when grading site Trust under the E E A T framework, when populating contact details in the Knowledge Panel, and when matching your business to "contact" intent queries. Pages without ContactPage schema get Trust-graded down even when the rest of the site is strong.

In 2026 ContactPage schema is also a meaningful AI search signal. ChatGPT, Claude, Gemini, and Perplexity all read ContactPage to populate their answers when users ask how to reach a business. A complete ContactPage with multiple ContactPoint nodes (customer service, technical support, sales, press, billing) is one of the cheapest E E A T and AI search wins on a brand site.

Step by step

How to use this tool in 3 steps

  1. Step 01

    Enter your contact details

    Type the page name (usually "Contact" or "Contact Us"), the canonical URL of the contact page, the Organization the page represents, the mailing address, and at least one phone number plus email address.

  2. Step 02

    Add ContactPoint departments

    Add one ContactPoint per support channel: customer service, technical support, sales, press, billing, and any other named department. Each ContactPoint carries its own contactType, telephone, email, availableLanguage, and optional hoursAvailable.

  3. Step 03

    Install on the contact page head

    Copy the generated JSON-LD and paste it inside a script type application ld json tag in the head of your contact page. Google reads the schema on the next crawl and starts surfacing the contact details in Knowledge Panel and AI search answers.

Why this tool

Why use this tool

  • Full ContactPage JSON-LD

    Output uses the schema.org ContactPage type with name, URL, description, mainEntity linking to the Organization, mailing address as PostalAddress, and a contactPoint array of typed ContactPoint nodes for each department.

  • Multi-department ContactPoint array

    Add as many ContactPoint nodes as your business runs: customer service, technical support, sales, press, billing, recruitment, partnerships. Each carries its own contactType, telephone, email, and the languages it supports.

  • availableLanguage per ContactPoint

    Each ContactPoint declares the languages it supports so Google can match international users to the right department. Critical for businesses serving multiple regions where different language ContactPoints reach different team members.

  • hoursAvailable specification

    Optional hoursAvailable on each ContactPoint declares when that channel is staffed. Useful for businesses with limited support hours so customers do not call outside business hours and bounce in frustration.

  • E E A T Trust signal

    ContactPage schema with verified phone, email, and address is one of the strongest E E A T Trust signals at the site level. Google's Quality Rater guidelines explicitly check for visible, verifiable contact details on every commercial site.

  • Free, no sign-up, no cap

    Generate ContactPage schema for every contact page across multi-brand portfolios. SBMM Pro adds bulk multi-site generation, automated language-detection per ContactPoint, and direct WordPress / Webflow plugin injection.

FAQ

Frequently asked questions

What is ContactPage schema?

ContactPage schema is a structured-data block in JSON-LD format that identifies a page as the canonical Contact Us page of an organisation and declares the phone, email, address, and per-department ContactPoint details to search engines. Google uses it for E E A T Trust grading, Knowledge Panel population, and AI search matching.

Why do I need ContactPage schema?

It is the on-page signal that confirms how customers can reach your business. Google grades site Trust on whether verifiable contact details are present, accessible, and structured. A site without a clean ContactPage block scores lower on Trust under the E E A T framework, regardless of how strong the rest of the content is.

Where do I install ContactPage schema?

On the dedicated Contact Us page (usually /contact or /contact-us), inside a script type application ld json tag in the head. The page should be visibly linked from the site navigation; pages buried in the footer or hidden behind multiple clicks carry less Trust weight than prominently-linked Contact pages. Pair it with the matching AboutPage schema on the About URL and a homepage Organization schema.

What is the difference between ContactPage and ContactPoint?

ContactPage is the page type — it identifies the URL as the Contact Us page. ContactPoint is a child schema that describes one specific way to reach the business (one phone number, one email, one department). A ContactPage usually contains multiple ContactPoint nodes for different departments.

How many ContactPoint nodes should I declare?

At least one (the primary customer service channel). Add more for each named department the business runs: technical support, sales, press, billing, recruitment, partnerships. Each ContactPoint carries its own contactType, telephone, email, and availableLanguage.

Should I include a physical address?

If the business has a verifiable physical address (head office, warehouse, registered business address), yes. It strengthens the Trust signal and helps Google attach the Knowledge Panel correctly. Online-only businesses without a public office can omit the address or use a registered business address.

What goes in availableLanguage?

availableLanguage is an array of language codes (en, es, fr, de) or names (English, Spanish, French) the ContactPoint can serve customers in. Critical for international businesses where different ContactPoints reach team members who speak different languages. Match this honestly to who actually answers the line.

Does ContactPage schema trigger a rich result?

Not a dedicated SERP rich result, but it strengthens Knowledge Panel population (Google surfaces the contact details in the right-side Panel), AI search matching (ChatGPT and Perplexity surface the phone or email when users ask how to reach the business), and E E A T grading across the whole site.