This factor reports whether RankGear finds a MovieTheater @type declaration in a page’s raw HTML source. It returns a simple yes/no (1 or 0). Because the check is a text-pattern match rather than a full JSON-LD parse, a 1 confirms the string is present, not that the structured-data graph is valid.
| Factor ID | RG-SCJ-161 |
|---|---|
| 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 MovieTheater in the raw page source. It is a presence signal for cinema-specific structured data: the schema.org MovieTheater type used to describe a movie theater entity — its location, screens, showings, accessibility, offers, hours, and contact details. The result is binary: the declaration is either detected (1) or it is not (0).
How RankGear measures it
RankGear searches the raw HTML for the token "@type": "MovieTheater", allowing flexible whitespace around the colon and an optional schema: prefix on the type value. Matching is case-insensitive, so capitalization differences do not affect the result. The check looks at source text directly rather than parsing and validating a JSON-LD graph.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "MovieTheater",
"name": "Downtown Cinema",
"address": { "@type": "PostalAddress", "streetAddress": "..." }
}
</script>| Value | Meaning |
|---|---|
| 1 | A MovieTheater @type string was detected in the raw source. |
| 0 | No matching MovieTheater @type string was found. |
How to optimize it
Use MovieTheater only for a page that genuinely represents a real cinema, and populate it with accurate location, screens, showings, accessibility, offers, hours, and contact information. Every property should reflect content a user can verify on the page itself. Treat this factor as an observation of whether the markup is present, not a target to force: adding the type to a page that is not actually a movie theater misrepresents the entity and provides no benefit.
Important considerations
- The detector pattern-matches source text rather than validating a complete JSON-LD graph, so a 1 confirms only that the string is present.
- A matching string that appears outside valid JSON-LD — for example in a code sample or comment — can still produce a 1.
- Capitalization differences do not affect detection; matching is case-insensitive.
- Validate the complete structured data independently with a schema validator; presence alone does not confirm correctness.
- This is a correlation-based prioritization signal within a measured result set. Adding the markup does not by itself cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.