This factor reports whether RankGear finds an @type value of NGO in a page’s raw source HTML. It returns a simple yes/no (1 or 0): present or absent. The important caveat is that it pattern-matches the source text rather than validating a real JSON-LD graph, so a match confirms the string exists, not that your structured data is well-formed.
| Factor ID | RG-SCJ-175 |
|---|---|
| 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 NGO in the raw source. The NGO type in Schema.org describes a nongovernmental organization, and its presence signals that a page is declaring itself as that kind of entity. The check is a binary observation: RankGear records that the declaration appears, nothing more.
How RankGear measures it
RankGear searches the raw HTML for flexible whitespace around "@type": "NGO", optionally allowing a schema: prefix. Matching is case-insensitive, so differences in capitalization do not change the result. Because the match runs against source text, the tool is confirming that the literal declaration is present in the markup, not parsing or resolving the surrounding JSON-LD structure.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "NGO",
"name": "Example Relief Foundation",
"url": "https://example.org/",
"areaServed": "Worldwide"
}
</script>| Value | Meaning |
|---|---|
| 1 | An @type of NGO (case-insensitive, optional schema: prefix) was found in the raw HTML. |
| 0 | No such declaration was found in the source. |
How to optimize it
Use NGO only for a genuine nongovernmental organization, with an accurate mission, legal identity, area served, leadership, contact details, and official links. Every property should reflect content that users can verify on the page itself. Treat this factor as an observation of what your markup declares rather than a target to chase: adding the type to a page that does not represent a real NGO invites a mismatch between your structured data and your visible content.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a returned 1 confirms the string is present, not that the structured data is valid.
- A matching string that sits outside valid JSON-LD, for example in a comment or a code sample, can still produce a 1.
- Capitalization differences do not affect detection.
- Validate the complete structured data independently with a dedicated schema validator.
- This is a prioritization signal that relates to position within a measured result set; it is correlation, not causation, and its presence does not by itself cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.