"ContactPage" schema

ContactPage is used to identify a page with the primary purpose of providing contact information — phone numbers, addresses, contact forms, opening hours, or "get in touch" content.

Pairing it with Organization (or LocalBusiness) and ContactPoint markup turns a basic contact page into a richer entity signal.

Where to use it

Only use ContactPage on dedicated contact pages (/contact, /contact-us, /get-in-touch, etc.). It does not need to be applied to the homepage or site-wide, even if those pages include contact details in the body or components like the header or footer — it should only be included on pages where the main purpose is contact information.

Key properties

• name – page title
• url – page URL
• description – brief summary
• mainEntity – the Organization being contacted, including its contactPoint array

Example (JSON-LD)

{
  "@context": "https://schema.org",
  "@type": "ContactPage",
  "name": "Contact Us",
  "url": "https://example.com.au/contact",
  "description": "Get in touch with our team.",
  "mainEntity": {
    "@type": "Organization",
    "name": "Example Co",
    "contactPoint": [
      {
        "@type": "ContactPoint",
        "telephone": "+61-3-0000-0000",
        "contactType": "customer service",
        "areaServed": "AU",
        "availableLanguage": ["en"]
      },
      {
        "@type": "ContactPoint",
        "telephone": "+61-3-0000-0001",
        "contactType": "sales",
        "areaServed": "AU"
      }
    ]
  }
}

"ContactPage" schema value

• Helps search engines identify the canonical contact page for your business
• Reinforces NAP (name, address, phone) consistency when paired with Organization or LocalBusiness
• Supports branded search experiences
• Google does not provide a specific rich result tied to ContactPage, but the structured data improves entity clarity and is used by other search engines and AIs

Best practices

• Match phone numbers and addresses exactly with your Google Business Profile and other directory listings/citations
• Use multiple contactPoint entries to differentiate sales, support, billing, etc.
• Include availableLanguage if you serve multilingual customers

Schema

Disclaimer: All information contained herein is for informational purposes only. It is not advice or instructional.