Has JSON-LD Conversation

Abstract illustration of two conversation speech bubbles inside JSON-LD brackets with a presence checkmark, in RankGear indigo and coral.

Has JSON-LD Conversation is a binary signal (1 or 0) that reports whether RankGear finds an @type of Conversation in a page’s raw HTML. It confirms the type string is present — it does not parse or validate the JSON-LD graph, so a bare match anywhere in the source still counts.

Factor IDRG-SCJ-059
FamilyStructured Data – JSON-LD
MeasurementBinary presence (0 / 1)
Measured zoneRaw rendered HTML

What it measures

This factor reports whether RankGear finds an @type value of Conversation in the raw source. Conversation is the schema.org type for a conversation creative work — an exchange of messages between participants. The factor answers one yes/no question: is that type declared anywhere in the page’s markup?

Back to Top

How RankGear measures it

RankGear searches the raw HTML for "@type": "Conversation", allowing flexible whitespace around the colon and an optional schema: prefix on the type value. The match is case-insensitive and returns 1 on any match, 0 otherwise. It is a string search over the raw source, not a parse of the structured-data graph.

Back to Top

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Conversation"
}
</script>

The whitespace around the colon may vary, the value may be prefixed ("@type": "schema:Conversation"), and case is ignored — any of these variants returns 1.

ValueMeaning
1A Conversation type string was found in the raw HTML.
0No matching Conversation type string was found.
Back to Top

How to optimize it

Use Conversation only for a genuine conversation creative work, with accurate participants, dates, and content relationships, and with properties that match the visible content. Treat the 1/0 as an observation of markup presence rather than a target to force: a bare type string satisfies this detector, but it adds nothing unless the page truly represents a conversation and the surrounding properties reflect what visitors can see.

Back to Top

Important considerations

  • The detector pattern-matches the source text; it does not parse or validate the JSON-LD graph.
  • A matching string outside a valid JSON-LD block can still produce 1.
  • Capitalization differences do not affect this detector.
  • Validate the complete structured data independently rather than relying on this presence signal alone.
  • This is a prioritization signal that relates to position within a measured result set — presence of the type correlates with, but does not cause or guarantee, any ranking.
Back to Top

Related factors

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

Back to Top