Has JSON-LD TVEpisode

Abstract illustration of a TV screen linked to a JSON-LD episode schema node, in RankGear indigo and coral.

Has JSON-LD TVEpisode reports whether RankGear finds an @type value of TVEpisode in a page’s raw HTML. It is a 1/0 presence signal — it confirms the string is there, not that the surrounding structured data is valid.

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

What it measures

This factor reports whether RankGear finds an @type value for TVEpisode in the raw source of the page. It answers a single yes/no question: does the page declare the TVEpisode schema type anywhere in its markup?

Back to Top

How RankGear measures it

RankGear searches the raw HTML for the pattern "@type": "TVEpisode", tolerating flexible whitespace around the colon and optionally allowing a schema: prefix on the type. Matching is case-insensitive, so differences in capitalization do not affect the result. If the pattern is found 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": "TVEpisode",
  "episodeNumber": 3,
  "partOfSeason": { "@type": "TVSeason", "seasonNumber": 1 },
  "partOfSeries": { "@type": "TVSeries", "name": "..." }
}
</script>
ValueMeaning
1A @type of TVEpisode (optionally schema:TVEpisode) was found in the raw HTML.
0No matching TVEpisode type string was found in the raw HTML.
Back to Top

How to optimize it

Use TVEpisode only for a genuine television episode, and populate it with accurate series, season, episode number, cast, dates, duration, and viewing details. Ensure every property reflects content users can actually verify on the page. Treat this factor as an observation of whether the type is present, not a target to force onto pages that are not episodes — adding the markup where it does not belong misrepresents the page and returns 1 without any real benefit.

Back to Top

Important considerations

  • The detector pattern-matches the source text rather than validating a full JSON-LD graph, so a 1 confirms the string is present but says nothing about whether the structured data is well-formed.
  • A matching string that appears outside valid JSON-LD — in a comment, an example, or unrelated text — can still produce a 1.
  • Capitalization differences do not affect detection, since matching is case-insensitive.
  • Validate the complete structured data independently (for example with a schema validator) before relying on it.
  • This is a prioritization signal that relates to position within a measured result set; presence of the markup does not by itself cause a page to rank.
Back to Top

Related factors

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

Back to Top