Has JSON-LD Message

Has JSON-LD Message reports whether RankGear finds an @type of Message in a page’s raw HTML source. It is a 0/1 presence check on the source text — not a validation that the Message schema is well-formed — so a match can appear anywhere in the HTML, inside valid JSON-LD or not.

What it measures

This factor reports whether RankGear finds an @type value of Message in the raw source. Schema.org’s Message type describes a single message — an email, chat, or notice — carrying a sender, recipient, date, and body. The check returns 1 when that type declaration is present in the page’s HTML and 0 when it is absent.

How RankGear measures it

RankGear searches the raw HTML for the string "@type": "Message", allowing flexible whitespace around the colon and an optional schema: prefix on the type value. Matching is case-sensitive, so the source must use the exact capitalization Message. Any single match sets the factor to 1.

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Message",
  "sender": { "@type": "Person", "name": "..." },
  "recipient": { "@type": "Person", "name": "..." },
  "dateSent": "2026-01-01",
  "text": "..."
}
</script>

How to optimize it

Use Message only for a genuine message with an accurate sender, recipient, date, text, and context where public markup is appropriate. Ensure every property reflects content users can verify on the page. Treat this factor as an observation of whether the markup is present, not a target to chase — declaring the type where no real message exists misrepresents the page and helps no one.

Important considerations

• The detector pattern-matches source text rather than validating a JSON-LD graph, so a 1 confirms the string is present, not that the structured data is correct.
• A matching string outside valid JSON-LD — in a code sample, a comment, or an inline script — can still produce a 1.
• Matching is case-sensitive: the source must use the exact capitalization Message, so message or MESSAGE will not match.
• Validate the complete structured data independently with a schema validator; this factor does not.
• Presence of this markup correlates with, and does not cause, ranking position. It is a prioritization signal measured within a result set, never a guarantee of where a page ranks.

Related factors

• Has JSON-LD MenuSection
• Has JSON-LD Midwifery

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