Has JSON-LD Play Action

Abstract illustration of a play button inside a JSON-LD code bracket linked to a schema node, in RankGear indigo and coral.

Has JSON-LD Play Action is a binary (0 / 1) signal that reports whether RankGear finds an @type of PlayAction in the page’s raw rendered HTML. It is a presence check on source text, not a validation of your structured-data graph — a matching string can register as 1 even when it sits outside valid JSON-LD.

Factor IDRG-SCJ-206
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 PlayAction in the raw source of the rendered page. PlayAction is the schema.org action used to describe a genuine action through which a user can play media or a game. The factor returns a single yes/no: the markup token is present, or it is not.

Back to Top

How RankGear measures it

RankGear searches the raw HTML for the string "@type": "PlayAction", allowing flexible whitespace around the colon and an optional schema: prefix on the type. Matching is case-insensitive, so capitalization differences do not affect the result. If the pattern is found the factor is 1; otherwise it is 0.

Back to Top

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "PlayAction",
  "object": { "@type": "VideoObject", "name": "Product demo" },
  "target": "https://example.com/watch",
  "result": { "@type": "VideoObject", "name": "Product demo" }
}
</script>
ValueMeaning
1A PlayAction @type token (optionally schema:PlayAction) was found in the raw HTML.
0No matching PlayAction token was present in the source.
Back to Top

How to optimize it

Use PlayAction only for a genuine action through which a user can play media or a game, with accurate object, target, and result details. Ensure every property reflects content users can actually verify on the page. Treat this factor as an observation of what your markup contains, not a target to hit for its own sake — adding the token to a page with no playable media misrepresents the page and does not earn a ranking.

Back to Top

Important considerations

  • The detector pattern-matches source text rather than validating a JSON-LD graph, so it confirms presence of a token, not correctness of your structured data.
  • A matching string that sits outside valid JSON-LD — for example in a comment, a code sample, or malformed markup — can still produce a 1.
  • Capitalization differences do not affect detection; the match is case-insensitive and tolerates an optional schema: prefix and flexible whitespace.
  • Validate the complete structured data independently before relying on it.
  • This is a prioritization signal that relates to position within a measured result set — it is a correlation, not a guarantee that the markup makes a page rank.
Back to Top

Related factors

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

Back to Top