This factor reports whether RankGear finds a "@type": "MobileApplication" value in the page’s raw source. It returns 1 when the string is present and 0 when it is not. Because it pattern-matches source text rather than parsing a JSON-LD graph, a match does not by itself prove valid, well-formed structured data.
| Factor ID | RG-SCJ-151 |
|---|---|
| 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 MobileApplication in the raw source of the page. It is a simple presence signal: the schema type is either detected in the source text or it is not.
How RankGear measures it
RankGear searches the raw HTML for "@type": "MobileApplication", allowing flexible whitespace around the tokens and optionally permitting a schema: prefix. Matching is case-insensitive, so capitalization differences in the type name do not change the result.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "MobileApplication",
"name": "Example App",
"operatingSystem": "iOS, Android",
"applicationCategory": "BusinessApplication"
}
</script>| Value | Meaning |
|---|---|
| 1 | The MobileApplication type string was found in the raw source (with or without a schema: prefix, any capitalization). |
| 0 | No MobileApplication type string was found in the raw source. |
How to optimize it
Use MobileApplication only for a genuine mobile application, and populate it with accurate operating system, category, version, offers, ratings, download URL, and requirements. Ensure every property reflects content a user can verify on the page. Treat this factor as an observation of whether the markup is present, not as a target to game — adding the type to a page that is not about a real app adds no value and risks misrepresenting the page.
Important considerations
- The detector pattern-matches source text; it does not validate a complete JSON-LD graph.
- A matching string that sits outside valid JSON-LD can still produce a 1.
- Capitalization differences do not affect detection.
- Validate the complete structured data independently with a dedicated schema validator.
- Presence of this markup correlates with, and does not cause, ranking. RankGear reports it as a prioritization signal within a measured result set, never as a guarantee of position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.