This factor reports whether RankGear finds a JSON-LD @type of WholesaleStore in the raw page source. It is a binary presence check (1 = found, 0 = not found), and because it pattern-matches source text rather than parsing a JSON-LD graph, a matching string outside valid structured data can still register as 1.
| Factor ID | RG-SCJ-268 |
|---|---|
| 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 WholesaleStore in the raw source. It answers a single yes/no question: does the page declare the WholesaleStore schema type anywhere in its markup? It does not score how complete or accurate that schema is — only whether the type string is present.
How RankGear measures it
RankGear searches the raw HTML for "@type": "WholesaleStore", allowing flexible whitespace around the colon and optionally permitting a schema: prefix. Matching is case-insensitive, so capitalization differences do not affect detection. When the pattern is found the factor returns 1; otherwise it returns 0.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WholesaleStore",
"name": "Example Wholesale Supply"
}
</script>| Value | Meaning |
|---|---|
| 1 | A WholesaleStore @type string was found in the raw source (with or without a schema: prefix, any capitalization). |
| 0 | No matching WholesaleStore type string was found. |
How to optimize it
Use WholesaleStore only for a genuine wholesale retailer, and only when the page content backs it up — accurate products, eligibility, offers, service area, location, hours, and contact details. Every property in the schema should reflect content a user can verify on the page. Treat this factor as an observation about what your markup declares, not a target to chase: adding the type string to a page that is not actually a wholesale store misrepresents the page and will not help it. Because detection is presence-only, a returned 1 confirms the type is declared, not that the structured data is valid or complete.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 confirms the string is present, not that the schema is well-formed.
- A matching string outside valid JSON-LD — for example inside a comment, a code sample, or escaped text — can still produce a 1.
- Capitalization differences do not affect detection; matching is case-insensitive.
- Validate the complete structured data independently (for example with a schema validator) to confirm it parses and is eligible for rich results.
- This is a prioritization signal that relates to position within a measured result set. Presence of the type correlates with, but does not cause or guarantee, any ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.