Has JSON-LD SoftwareApplication reports whether a page’s raw HTML contains an @type of SoftwareApplication: it returns 1 when RankGear finds that string and 0 when it does not. It is a text-pattern presence check — a 1 confirms the string is there, not that it sits inside a valid JSON-LD graph.
| Factor ID | RG-SCJ-242 |
|---|---|
| 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 SoftwareApplication in the raw source. A value of 1 means the string was located; a value of 0 means it was not. It measures the presence of that type marker only — it does not confirm the surrounding JSON-LD is well formed, that the properties are accurate, or that the page qualifies for any software-related rich result.
How RankGear measures it
RankGear searches the raw HTML for "@type": "SoftwareApplication", allowing flexible whitespace around the colon and optionally permitting a schema: prefix on the type. The match is case-insensitive, so capitalization differences do not change the result. Finding at least one qualifying occurrence returns 1; otherwise the value is 0. Because the check pattern-matches source text rather than parsing a JSON-LD graph, a matching string that sits outside valid structured data can still produce a 1.
What RankGear looks for
<script type="application/ld+json">
{ "@context": "https://schema.org",
"@type": "SoftwareApplication",
"name": "...", "applicationCategory": "...",
"operatingSystem": "...", "offers": { ... } }
</script>| Value | Meaning |
|---|---|
| 1 | The string "@type": "SoftwareApplication" (with flexible whitespace, optional schema: prefix, any capitalization) was found in the raw HTML. |
| 0 | No qualifying SoftwareApplication type marker was found in the raw HTML. |
How to optimize it
Use SoftwareApplication only for a genuine software application, and give it an accurate category, operating system, version, requirements, offers, ratings, and download URL. Make sure every property reflects content users can verify on the page. Treat the factor as an observation of presence, not a target to chase for its own sake — because the detector matches source text, inserting the string without a real, valid graph behind it adds no meaning and risks structured data that fails independent validation. Validate the complete JSON-LD separately to confirm it is well formed and eligible.
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 markup is valid.
- A matching string that sits outside valid JSON-LD can still produce a 1.
- Capitalization differences do not affect detection; matching is case-insensitive.
- Validate the complete structured data independently — this factor tracks a signal that relates to how pages are prioritized within a measured result set, not a guarantee of ranking or rich-result eligibility.
Related factors
Part of the Factors reference · how RankGear measures · glossary.