This factor reports whether RankGear finds an @type value of Optician in the page’s raw HTML source. It returns 1 when the string is present and 0 when it is not — but it pattern-matches text, so it does not confirm the markup forms a valid JSON-LD graph.
| Factor ID | RG-SCJ-188 |
|---|---|
| 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 for Optician in the raw source. It is a presence check for the Optician schema type — a subtype used to describe an optician business — not an assessment of how complete or accurate that markup is.
How RankGear measures it
RankGear searches the raw HTML for the "@type": "Optician" string, allowing flexible whitespace around the colon and optionally allowing a schema: prefix. Matching is case-insensitive, so differences in capitalization do not change the result. Any match sets the factor to 1; no match sets it to 0.
What RankGear looks for
"@type": "Optician"
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Optician",
"name": "..."
}
</script>| Value | Meaning |
|---|---|
| 1 | An @type of Optician was found in the raw HTML source. |
| 0 | No Optician type string was found in the raw HTML source. |
How to optimize it
Use the Optician type only for a genuine optician business, and only when the page’s structured data reflects services, products, credentials, location, hours, and contact details that a visitor can verify in the visible content. Every property should describe something real on the page rather than exist to trigger the string match. Treat this factor as an observation that the type is present, not a target to force — a bare string with no supporting, accurate graph adds no value.
Important considerations
- The detector pattern-matches the source text; it does not validate a complete JSON-LD graph.
- A matching string that sits outside valid JSON-LD can still produce a 1.
- Capitalization differences do not affect detection, since matching is case-insensitive.
- Validate the full structured data independently — a passing check here is not proof of correct markup.
- This is a correlation-based prioritization signal within a measured result set; presence of the type does not by itself cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.