Has JSON-LD ContactPoint

This factor checks whether your page’s raw HTML contains a JSON-LD ContactPoint marker — the schema.org type that describes a real contact channel. It returns 1 when the string is present and 0 when it is not; because it matches source text rather than validating the JSON-LD graph, a 1 confirms the marker exists, not that your structured data is valid.

What it measures

RankGear reports whether it finds an @type value of ContactPoint in your page’s raw source. ContactPoint is a schema.org type used inside JSON-LD to describe how people reach an organization or person — a support line, a sales email, a customer-service channel — together with details such as telephone, contact type, area served, and available languages. The factor is a single presence signal: it tells you the marker is there, and nothing about whether its details are accurate.

How RankGear measures it

RankGear searches the raw HTML for the string "@type": "ContactPoint", allowing flexible whitespace around the colon and optionally accepting a schema: prefix (schema:ContactPoint). Matching is case-insensitive, so capitalization differences do not change the result. This is a source-text match, not a parse of the JSON-LD graph.

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+1-555-0100",
    "contactType": "customer support",
    "areaServed": "US",
    "availableLanguage": ["English"]
  }
}
</script>

How to optimize it

Use ContactPoint only for a genuine contact channel, and fill it with accurate details — telephone, email, contact type, area served, and available languages — that match what visitors actually see on the page. Do not add the markup just to trip the detector: because the factor matches source text, a stray string can register 1 without describing a real, valid contact method. Treat the score as an observation of whether the marker is present, then confirm the underlying structured data is correct.

Important considerations

• The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 confirms the string is present — not that your structured data parses correctly.
• A matching string that sits outside valid JSON-LD — in a comment, a code sample, or malformed markup — can still produce a 1.
• Capitalization differences do not affect detection.
• Validate the complete structured data independently with a schema.org or Rich Results validator.
• Correlation is not causation: the presence of a ContactPoint marker relates to patterns RankGear measures within a result set; it is a prioritization signal, not a guarantee that the markup will change a page’s ranking.

Related factors

• Has JSON-LD ConsumeAction
• Has JSON-LD Conversation

Part of the Factors reference · how RankGear measures · glossary.