Has JSON-LD RadioSeries

Abstract illustration of a radio broadcast tower with signal waves linking to a structured-data schema node of episode cards, in RankGear indigo and coral.

Has JSON-LD RadioSeries is a yes/no (1 / 0) signal: it reports whether RankGear finds an @type of RadioSeries anywhere in your page’s raw HTML source. It is a text pattern match, not a validation of your structured-data graph — a stray matching string can flip it to 1 even where no valid schema exists.

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

What it measures

This factor reports whether a RadioSeries schema type appears in the page’s source. RadioSeries is the schema.org type for a radio program built from episodes — a show with hosts, a network, a broadcast schedule, and listening details. A value of 1 means RankGear located the @type of RadioSeries in your raw HTML; 0 means it did not. The check speaks only to the presence of that type string, not to whether the surrounding markup is complete or correct.

Back to Top

How RankGear measures it

RankGear searches the raw HTML for the token "@type": "RadioSeries", allowing flexible whitespace around the colon and value and optionally accepting a schema: prefix. Matching is case-insensitive, so capitalization differences do not affect the result. It is a source-text search, not a parse of the JSON-LD graph.

Back to Top

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "RadioSeries",
  "name": "The Midnight Signal",
  "episode": [ /* RadioEpisode items */ ]
}
</script>
ValueMeaning
1The @type of RadioSeries (optionally with a schema: prefix) was found in the raw HTML.
0No matching RadioSeries type string was present in the source.
Back to Top

How to optimize it

Use RadioSeries only for a genuine radio series, and make sure every property reflects content users can verify on the page — accurate episodes, hosts, network, schedule, dates, and listening details. Because the detector only confirms the type string is present, treat a 1 as an observation that the markup exists rather than a target to chase. A page that is not a radio series has nothing to gain from adding the type, and forcing it invites structured-data that misrepresents the content.

Back to Top

Important considerations

  • The detector pattern-matches source text; it does not validate a complete JSON-LD graph.
  • A matching string outside valid JSON-LD — in a comment, a code example, or escaped text — can still produce a 1.
  • Capitalization differences do not affect detection.
  • Validate the complete structured data independently with a schema validator before relying on it.
  • Correlation is not causation: this signal relates to position within a measured result set and is a prioritization observation, not a lever that makes a page rank.
Back to Top

Related factors

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

Back to Top