This factor reports whether a page declares a Museum type in JSON-LD structured data. It returns 1 when RankGear finds an @type of Museum in the raw HTML and 0 when it does not. It is a text pattern match on source, not a validation of the underlying JSON-LD graph.
| Factor ID | RG-SCJ-163 |
|---|---|
| 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 Museum in the raw source of the page. It is a presence check: the value is 1 when the museum type declaration is found and 0 when it is absent. It tells you that the page claims to describe a museum entity in structured data, not whether that structured data is complete or accurate.
How RankGear measures it
RankGear searches the raw HTML for "@type": "Museum", allowing flexible whitespace around the colon and optionally accepting a schema: prefix on the value. Matching is case-insensitive, so capitalization differences do not change the result.
What RankGear looks for
"@type": "Museum"
"@type" : "schema:Museum"| Value | Meaning |
|---|---|
| 1 | A Museum @type declaration was matched in the raw HTML. |
| 0 | No Museum @type declaration was found in the raw HTML. |
How to optimize it
Use the Museum type only for a page that represents a real museum, with accurate collections, exhibitions, location, hours, admission, accessibility, and contact details. Ensure every property reflects content a user can verify on the page itself. Because this factor only detects the presence of the type string, treat a value of 1 as confirmation that the declaration exists, not as proof that the markup is valid or well-formed.
Important considerations
- The detector pattern-matches source text rather than validating a JSON-LD graph, so a value of 1 confirms the string is present, not that the structured data parses correctly.
- A matching string that appears outside valid JSON-LD, for example in a code sample or a comment, can still produce a 1.
- Capitalization differences do not affect detection, since 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 appear within a measured result set. It does not, on its own, cause a page to rank; correlation is not causation.
Related factors
Part of the Factors reference · how RankGear measures · glossary.