Has JSON-LD MusicAlbum reports whether RankGear finds an @type of MusicAlbum in a page’s raw HTML source, returned as 1 (present) or 0 (absent). It is a case-sensitive text match on the source string, not a validation of the JSON-LD graph, so a 1 only confirms the string is present — not that the markup is valid or accurate.
| Factor ID | RG-SCJ-164 |
|---|---|
| Family | Structured Data – JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
This factor reports whether the page declares an @type value of MusicAlbum in its raw HTML. MusicAlbum is the schema.org type used to describe a released music album — its artist, tracks, release date, format, label, identifiers, and offers. The check returns a single binary value: 1 when the type string is found in source, 0 when it is not.
How RankGear measures it
RankGear searches the raw HTML for the @type declaration set to MusicAlbum, allowing flexible whitespace around the colon and optionally a leading schema: prefix on the type value. Matching is case-sensitive, so the source must use the exact capitalization MusicAlbum. Because it pattern-matches the source text rather than parsing a JSON-LD graph, any matching string in the HTML — even outside a valid script block — can produce a 1.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "MusicAlbum",
"name": "Album Title",
"byArtist": { "@type": "MusicGroup", "name": "Artist Name" },
"numTracks": 10
}
</script>| Value | Meaning |
|---|---|
| 1 | The string "@type": "MusicAlbum" (with flexible whitespace, optional schema: prefix) was found in the raw source. |
| 0 | No matching MusicAlbum type string was found in the raw source. |
How to optimize it
Use MusicAlbum only for a genuine music album, and only where the markup reflects content users can verify on the page. Populate accurate artist, tracks, release date, format, label, identifiers, and offers. Because the detector matches source text and does not validate the graph, treat a 1 as an observation that the type is declared — not proof the structured data is correct. Validate the complete JSON-LD independently before relying on it.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph.
- A matching string outside valid JSON-LD can still produce a 1.
- Matching is case-sensitive: the source must use the exact capitalization
MusicAlbum. - Validate the complete structured data independently — presence of the string is not a guarantee of valid markup.
- This is a prioritization signal that relates to position within a measured result set; it does not by itself cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.