This factor reports whether RankGear finds an @type of RadioEpisode in a page’s raw source: 1 when the string is present, 0 when it is absent. It is a pattern match against source text, not a validation of the JSON-LD graph, so a matching string can register even when it sits outside a well-formed block.
| Factor ID | RG-SCJ-220 |
|---|---|
| Family | Structured Data – JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
This factor reports whether RankGear finds an @type value of RadioEpisode in the raw source. RadioEpisode is the schema.org type for a single episode of a radio series, so its presence signals that a page describes broadcast audio content with structured metadata rather than leaving that context implicit.
How RankGear measures it
RankGear searches the raw HTML for "@type": "RadioEpisode", allowing flexible whitespace around the value and optionally allowing a schema: prefix. Matching is case-insensitive, so capitalization differences do not change the result. Any match returns 1; no match returns 0.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "RadioEpisode",
"name": "Episode 12 — Field Recordings",
"episodeNumber": 12,
"partOfSeries": { "@type": "RadioSeries", "name": "Signal Drift" }
}
</script>| Value | Meaning |
|---|---|
| 1 | A RadioEpisode @type string was found in the raw source (with or without a schema: prefix, any capitalization). |
| 0 | No such string was found. |
How to optimize it
Use RadioEpisode only for a genuine radio episode, and describe it accurately: series, episode number, contributors, dates, duration, recording, and access details. Ensure every property reflects content users can verify on the page. Because the check confirms presence of the type string rather than the quality of the graph, treat a 1 as evidence the markup exists, not as proof it is complete or correct.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so it confirms the string is present, not that the surrounding structured data is well-formed.
- A matching string that sits 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 factor tracks how presence of the type relates to position within a measured result set; it is a prioritization signal, not a cause of ranking, and does not guarantee a position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.