This factor returns 1 when RankGear finds an @type of MusicRelease in a page’s raw HTML source, and 0 when it does not. It is a text match on the source, not a validation of the JSON-LD graph, so a matching string can appear outside valid structured data — read it as a presence signal, not proof of a correct schema.
| Factor ID | RG-SCJ-169 |
|---|---|
| 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 MusicRelease in the page’s raw source. MusicRelease is the schema.org type that describes a specific release of a musical work — a single, EP, or album issued in a given format, region, and catalogue. The factor answers one narrow question: is that type declared anywhere in the markup, yes or no.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "MusicRelease", allowing flexible whitespace around the colon and optionally accepting a schema: prefix on the type. Matching is case-insensitive, so capitalization differences do not affect the result. A match sets the factor to 1; no match sets it to 0.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "MusicRelease",
"name": "Album Title",
"catalogNumber": "CAT-001",
"musicReleaseFormat": "https://schema.org/VinylFormat",
"recordLabel": { "@type": "Organization", "name": "Label" }
}
</script>| Value | Meaning |
|---|---|
| 1 | A MusicRelease type was found in the raw source (with or without a schema: prefix, any capitalization). |
| 0 | No MusicRelease type string was found in the source. |
How to optimize it
Use MusicRelease only for a genuine music release, and populate it with an accurate catalogue number, format, label, date, region, and recording relationships. Ensure every property reflects content users can actually verify on the page. Because the detector only checks for presence, treat this as an observation that the type is declared — not a target to chase. Adding the type to a page that is not truly a music release inflates the signal without adding real structured data.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a value of 1 confirms the string is present, not that the structured data is well-formed.
- A matching string that sits outside valid JSON-LD — in a comment, a code sample, or unrelated markup — can still produce 1.
- Capitalization differences do not affect detection; the match is case-insensitive.
- Validate the complete structured data independently with a schema validator before relying on it.
- This is a prioritization signal that relates to position within a measured result set. It does not, on its own, cause a page to rank or guarantee any position — correlation is not causation.
Related factors
Part of the Factors reference · how RankGear measures · glossary.