Output mode
Paste your Contact page URL. We'll read meta tags + tel: / mailto: links and pre-populate the form.
Page information
Organization contact info
Required: Page title is required · Page URL is required
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "ContactPage"
}
</script>How to use
01
Choose Recommended or Strict mode
Recommended outputs ContactPage plus a publisher Organization carrying a contactPoint array. Strict outputs the ContactPage type alone. Start with Recommended unless your Organization markup already lives elsewhere on the site.
02
Auto-fill and check the basics
Paste your contact URL and click Auto-fill from URL. Besides the title, description, image, and dates, the tool digs through the page's tel: and mailto: links to capture a phone number and email address.
03
Set the contact point and copy
Pick a Contact type such as Customer Support, Sales, or Billing, set the Available language, confirm the phone and email, then hit Copy script and paste the block into your contact page's head.
Why Contact Page Schema
- Two modes: Recommended (ContactPage + Organization + contactPoint) or Strict (ContactPage only).
- Auto-fill from URL, pulls title, description, image, dates, and phone/email from your tel:/mailto: links.
- Eligible for knowledge-panel contact info in search results.
Common questions
What's the difference between Recommended and Strict mode for ContactPage output?
Recommended nests a publisher Organization with a contactPoint array inside the ContactPage, so one block declares the page and the people behind it. Strict emits only the ContactPage properties. Use Strict when your site already publishes Organization JSON-LD elsewhere and you'd rather not declare the entity twice.
How does the contact page schema generator find my phone number?
During auto-fill it scans the fetched page for the first tel: link and the first mailto: link, then strips the prefixes and any query string. If your page only shows the number as plain text with no clickable link, the field stays empty and you type it in yourself.
Which contactType values does the ContactPage tool offer?
The dropdown covers Customer Support, Sales, Technical Support, Media, Billing, and General Inquiry. The contactType property is free text as far as schema.org is concerned, but sticking to plain, recognizable labels like these keeps the markup easy for machines to classify.
Does ContactPage markup help local SEO?
Indirectly. It reinforces consistent name, phone, and URL data, which supports the citation consistency local algorithms reward. A business with a physical storefront should still publish LocalBusiness markup with an address and opening hours; ContactPage describes the page, not the premises.
Can a ContactPage declare more than one language?
The Available language field takes a single value like English. If you support several languages, generate the block, then edit the copied JSON and turn availableLanguage into an array such as ["English", "German"]. The structure stays valid either way.
Is it a problem if my contact page has no phone number?
No. When both the phone and email fields are empty, the tool skips the contactPoint block entirely instead of emitting a hollow one. Email-only support is common for SaaS teams, and a ContactPoint carrying just an email still validates fine.
Why put the schema on the contact page rather than the homepage?
Because the markup describes one specific URL. A ContactPage type on your homepage is a mislabel, and mislabeled types get ignored. Keep the block on the /contact URL it names, and let your homepage carry Organization or WebSite markup instead.