Structured contact information

What is measured

The scanner parses the homepage JSON-LD for schema.org contact data: an Organization carrying contactPoint (a ContactPoint with contactType and email or telephone), or email/telephone on the organization itself. It passes when at least one reachable channel is declared with a contactType that says what it is for; it partially passes when the organization node exists but has no contact details, or when the details appear only as plain text on the page.

Reproduce it yourself

You do not have to take our word for any of this. Run the same measurement against your own domain:

              DOMAIN=https://your-domain.example
curl -sS "$DOMAIN/" | tr -d '\n' | grep -oE '"contactPoint":|"(contactType|email|telephone)":"[^"]*"' | sort -u
            

The fix

This is the artifact to ship. It is the complete change, not a description of one.

              {
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Inc.",
  "url": "https://your-domain.example",
  "contactPoint": [
    {
      "@type": "ContactPoint",
      "contactType": "technical support",
      "email": "agents@your-domain.example",
      "telephone": "+1-555-0100",
      "availableLanguage": ["en", "de"],
      "areaServed": "US"
    },
    {
      "@type": "ContactPoint",
      "contactType": "billing support",
      "email": "billing@your-domain.example"
    }
  ]
}
            

Standards referenced

• schema.org/Organization

Related checks