This factor reports whether RankGear finds an @type value of OfficeEquipmentStore in a page’s raw source. It is a simple present-or-absent signal (1 or 0), and because it pattern-matches text rather than parsing the JSON-LD graph, a 1 means the string was found — not that the structured data is valid.
| Factor ID | RG-SCJ-184 |
|---|---|
| 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 OfficeEquipmentStore in the raw source of the page. It answers one narrow question: does the page declare the OfficeEquipmentStore schema type anywhere in its markup? The result is binary — present (1) or absent (0).
How RankGear measures it
RankGear searches the raw HTML for "@type": "OfficeEquipmentStore", allowing flexible whitespace around the colon and optionally permitting a schema: prefix on the type value. Matching is case-insensitive, so capitalization differences do not affect detection.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "OfficeEquipmentStore",
"name": "...",
"address": { "@type": "PostalAddress", "...": "..." }
}
</script>| Value | Meaning |
|---|---|
| 1 | An @type of OfficeEquipmentStore was matched in the raw source (optionally with a schema: prefix). |
| 0 | No matching OfficeEquipmentStore type string was found in the raw source. |
How to optimize it
Use OfficeEquipmentStore only for a genuine office-equipment retailer, and only when the marked-up details are accurate: products, offers, services, location, hours, and contact information. Every property should reflect content a user can verify on the page. Treat this factor as an observation of what your markup declares, not a target to chase — adding the type to a page that is not an office-equipment store misrepresents the entity and does not help.
Important considerations
- The detector pattern-matches source text; it does not validate a JSON-LD graph, so a 1 is not proof the structured data is well-formed.
- A matching string that appears outside valid JSON-LD — in a comment, an example, or unrelated text — can still produce a 1.
- Capitalization differences do not affect detection, since matching is case-insensitive.
- Validate the complete structured data independently with a schema validator; this factor is not a correctness check.
- Presence of this type correlates with, and does not cause, ranking position; it is one prioritization signal within a measured result set, never a guarantee of ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.