This factor reports whether RankGear finds a MusicStore @type declaration in a page’s raw HTML — a 1 when the pattern is present, a 0 when it is not. It is a text match on source, not a validation of the underlying JSON-LD graph, so a match confirms the string exists, not that the structured data is correct.
| Factor ID | RG-SCJ-170 |
|---|---|
| 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 MusicStore in the raw source of the page. MusicStore is the schema.org type used to describe a business that sells musical instruments, recordings, or related merchandise, and its presence signals that a page has declared itself as that kind of local retailer to search engines and other consumers of structured data.
How RankGear measures it
RankGear searches the raw HTML for "@type": "MusicStore", allowing flexible whitespace around the colon and an optional schema: prefix on the type value. 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": "MusicStore",
"name": "..."
}
</script>| Value | Meaning |
|---|---|
| 1 | A MusicStore @type string was found in the raw HTML. |
| 0 | No MusicStore @type string was found. |
How to optimize it
Use MusicStore only for a genuine music retailer, and only where the markup is backed by accurate inventory, offers, services, location, hours, and contact details. Every property should reflect content a user can verify on the page itself. Because this factor matches source text rather than a validated graph, treat a 1 as evidence the declaration is present, not proof it is complete or well-formed — do not add the string purely to move the value.
Important considerations
- The detector pattern-matches source text rather than validating a JSON-LD graph, so a 1 confirms the string is present, not that the structured data is valid.
- A matching string that sits outside valid JSON-LD — for example inside a comment or an example block — can still produce a 1.
- Capitalization differences do not affect detection; matching is case-insensitive.
- Validate the complete structured data independently with a dedicated schema testing tool.
- This is a prioritization signal that relates to how pages are measured within a result set; presence of the markup does not by itself cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.