This factor reports whether RankGear finds a MobilePhoneStore @type declaration in a page’s raw HTML — a 1 if the schema string is present, a 0 if it isn’t. It is a text match on source, not a validation of the JSON-LD graph, so use it as an observation of what markup exists rather than proof that the structured data is correct.
| Factor ID | RG-SCJ-152 |
|---|---|
| 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 MobilePhoneStore in the page’s raw source. MobilePhoneStore is a Schema.org business type used to describe a retailer that sells mobile phones. The factor answers a single yes/no question: does the page declare itself as a MobilePhoneStore in JSON-LD? It returns 1 when the type string is present and 0 when it is absent.
How RankGear measures it
RankGear searches the raw HTML for the @type assignment to MobilePhoneStore, allowing flexible whitespace around the value and optionally accepting the schema: prefix. Matching is case-insensitive, so capitalization differences do not change the result. Because the check works on source text, it looks for the pattern anywhere in the HTML rather than parsing and traversing a JSON-LD graph.
What RankGear looks for
"@type": "MobilePhoneStore"| Value | Meaning |
|---|---|
| 1 | A MobilePhoneStore @type string was found in the raw HTML. |
| 0 | No MobilePhoneStore @type string was found. |
How to optimize it
Use MobilePhoneStore only for a genuine mobile-phone retailer, and only when the page can back it up with accurate products, offers, services, location, hours, and contact information. Every property in the markup should reflect content a user can verify on the page itself. Treat this factor as an observation of whether the type is declared, not as a target to hit for its own sake — adding the string without a real store behind it does not help, and the correct schema type for your business is the one that describes it truthfully.
Important considerations
- The detector pattern-matches source text instead of validating a complete JSON-LD graph, so a 1 confirms the string is present, not that the structured data is well-formed.
- A matching string that sits outside valid JSON-LD — in a comment, a code sample, or plain 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 before relying on it.
- Correlation is not causation: this factor tracks the presence of a markup pattern within a measured result set and is a prioritization signal, not a guarantee of ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.