Has JSON-LD Listen Action

Abstract illustration of a JSON-LD ListenAction node with a play glyph and audio waveform, in RankGear indigo and coral.

Has JSON-LD Listen Action records whether RankGear finds an @type of ListenAction in a page’s raw HTML — a binary 0 / 1 signal. It is a case-insensitive text match on the source, not a validation of the JSON-LD graph, so a matching string can register a 1 even when it sits outside valid structured data.

Factor IDRG-SCJ-135
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 ListenAction in the raw source of the page. ListenAction is the schema.org action describing an interaction through which a user listens to an audio object, so its presence indicates the page declares a listen interaction in JSON-LD. The result is binary: the markup is either detected or it is not.

Back to Top

How RankGear measures it

RankGear searches the raw HTML for the token "@type": "ListenAction", allowing flexible whitespace around the colon and optionally permitting a schema: prefix on the type. Matching is case-insensitive, so capitalization differences do not change the outcome. If the pattern appears anywhere in the source, the factor returns 1; otherwise it returns 0.

Back to Top

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ListenAction",
  "target": "https://example.com/play/episode-12",
  "object": {
    "@type": "AudioObject",
    "name": "Episode 12",
    "contentUrl": "https://example.com/audio/episode-12.mp3"
  }
}
</script>
ValueMeaning
1A ListenAction type token was found in the raw HTML (with or without a schema: prefix).
0No ListenAction type token was found in the source.
Back to Top

How to optimize it

Use ListenAction only for a genuine action through which a user can listen to an audio object, with accurate target and object details. Every property should reflect content users can actually verify on the page — the correct audio object, a working target, and honest metadata. Because the detector reads source text rather than a parsed graph, treat a 1 as confirmation that the token is present, not as proof the structured data is valid; pair it with independent validation.

Back to Top

Important considerations

  • The detector pattern-matches source text instead of validating a JSON-LD graph.
  • A matching string outside valid JSON-LD can still produce a 1.
  • Capitalization differences do not affect detection.
  • Validate the complete structured data independently with a schema testing tool.
  • This is a correlation-based prioritization signal within a measured result set, not a guarantee that adding the markup will raise a page’s ranking.
Back to Top

Related factors

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

Back to Top