This factor reports whether RankGear finds a JSON-LD @type of MensClothingStore in a page’s raw HTML. It returns 1 when the string is present and 0 when it is not. It is a text match on the source, not a validation of your structured-data graph, so a match only tells you the type label appears — not that the markup is correct.
| Factor ID | RG-SCJ-145 |
|---|---|
| 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 MensClothingStore in the raw source of the page. It is a presence check: the type label is either found (1) or it is not (0). The MensClothingStore type is the schema.org business category used to describe a retailer selling men’s clothing, so its presence signals that a page is attempting to identify itself as that kind of local business through structured data.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "MensClothingStore", allowing flexible whitespace around the tokens and optionally accepting a schema: prefix on the type. Matching is case-insensitive, so differences in capitalization do not change the result. Because the check runs against source text, it does not parse or validate a JSON-LD graph — it only confirms that a matching pattern exists somewhere in the markup.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "MensClothingStore"
}
</script>| Value | Meaning |
|---|---|
| 1 | A "@type": "MensClothingStore" string was found in the raw HTML (whitespace-tolerant, case-insensitive, schema: prefix allowed). |
| 0 | No matching type string was found in the source. |
How to optimize it
Use MensClothingStore only for a genuine men’s clothing retailer, and make every property reflect content a user can verify on the page — accurate products, offers, location, hours, and contact information. Treat this factor as an observation of whether that markup is present, not as a target to game: because it pattern-matches source text, adding the string without a valid, accurate structured-data graph produces a technically-present result that misrepresents the page and can undermine trust in your markup.
Important considerations
- The detector pattern-matches source text instead of validating a full JSON-LD graph, so a 1 confirms the type label is present, not that the structured data is well-formed or complete.
- A matching string that sits outside valid JSON-LD — for example in a comment, an example block, or escaped 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 testing tool before relying on it.
- This is a prioritization signal that relates to position within a measured result set. Presence of this type correlates with, and does not by itself cause or guarantee, any ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.