This factor returns 1 when RankGear finds an @type value of ElectronicsStore anywhere in a page’s raw HTML, and 0 when it does not. Because it pattern-matches source text rather than parsing a JSON-LD graph, a match confirms only that the string is present — not that the structured data is valid.
| Factor ID | RG-SCJ-080 |
|---|---|
| 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 ElectronicsStore in the raw source. It is a presence check for one specific schema.org type — the type that describes an electronics retailer — and nothing more. It says a page declares itself an electronics store in machine-readable markup; it does not judge whether that declaration is accurate or complete.
How RankGear measures it
RankGear searches the raw HTML for a "@type": "ElectronicsStore" key/value pair, allowing flexible whitespace around the colon and an optional schema: prefix on the type. Matching is case-insensitive, so ElectronicsStore, electronicsstore, and similar variants all resolve to a 1. The check runs against source text, not against a parsed structured-data graph.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "ElectronicsStore",
"name": "Example Electronics"
}
</script>The matched substring is "@type": "ElectronicsStore" (optionally "@type": "schema:ElectronicsStore"), with the surrounding whitespace and casing free to vary.
| Value | Meaning |
|---|---|
| 1 | The ElectronicsStore type string was found somewhere in the raw HTML. |
| 0 | No matching ElectronicsStore type string was found. |
How to optimize it
Use ElectronicsStore only for a genuine electronics retailer, with accurate products, offers, location, hours, and contact information, and with properties that match the visible content of the page. Treat this factor as an observation of what your markup declares rather than a target to force: adding the string to a page that is not really an electronics store, or that lacks the supporting data, misrepresents the page without improving it. If your business fits the type, place it inside valid, complete JSON-LD; if it does not, a 0 here is the correct and expected result.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 confirms presence of the string, not correctness of the markup.
- A matching string that sits outside valid JSON-LD — in a comment, a code sample, or malformed markup — can still produce a 1.
- Capitalization differences do not affect detection; case is ignored.
- Always validate the complete structured data independently before relying on it.
- Presence correlates with, and never guarantees, any ranking outcome. RankGear reports this as a prioritization signal observed within a measured result set, not as a cause of position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.