This factor reports whether RankGear finds a MusicPlaylist @type declaration in a page’s raw HTML. It returns a simple present-or-absent signal (1 or 0) — and because it matches source text rather than parsing a JSON-LD graph, a match confirms the string is on the page, not that the structured data is valid.
| Factor ID | RG-SCJ-167 |
|---|---|
| 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 MusicPlaylist in the page’s raw source. It is a binary observation: the markup is either detectable in the HTML or it is not.
How RankGear measures it
RankGear searches the raw HTML for "@type": "MusicPlaylist", tolerating flexible whitespace around the colon and optionally allowing a schema: prefix. Matching is case-insensitive, so capitalization differences do not change the result. This is a text pattern match against the source — it does not parse or validate the surrounding JSON-LD graph.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "MusicPlaylist",
"name": "Late Night Focus",
"numTracks": 12,
"track": [ /* MusicRecording items */ ]
}
</script>| Value | Meaning |
|---|---|
| 1 | A MusicPlaylist @type string was found in the raw HTML. |
| 0 | No matching MusicPlaylist string was present in the source. |
How to optimize it
Use MusicPlaylist only for a genuine playlist, with an accurate creator, track list, track count, and access 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 chase — adding the string to a page that is not really a playlist misrepresents the content and offers no benefit.
Important considerations
- The detector pattern-matches source text rather than validating a JSON-LD graph, so a 1 confirms presence of the string, not correctness of the schema.
- A matching string that sits outside valid JSON-LD — in a comment, an example, or a script that never renders — can still produce a 1.
- Capitalization differences do not affect detection, since matching is case-insensitive.
- Validate the complete structured data independently with a schema validator; this factor does not do that for you.
- Correlation is not causation: this signal relates to position within a measured result set and is a prioritization signal, not proof that the markup makes a page rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.