Has JSON-LD Notary reports whether the raw HTML contains a JSON-LD @type value of Notary. It returns 1 when that string pattern is found and 0 when it is not — a text-level detection, not proof that a valid JSON-LD graph exists or that the page truly represents a notary service.
| Factor ID | RG-SCJ-177 |
|---|---|
| Family | Structured data — JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
Has JSON-LD Notary reports whether RankGear finds an @type value of Notary in the raw source. A value of 1 means the recognized string pattern is present; a value of 0 means it is not. This factor detects a text pattern only — it does not parse the JSON-LD, confirm that the surrounding markup is a valid graph, or verify that the page genuinely describes a notary service.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "Notary", allowing flexible whitespace around the separator and optionally accepting the schema: prefix. Matching is case-insensitive, so differences in capitalization do not affect the result. Because the check works on source text, the pattern can be matched anywhere it appears in the HTML, not only inside a well-formed JSON-LD block.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Notary",
"name": "..."
}
</script>| Value | Meaning |
|---|---|
| 1 | A @type of Notary (or the schema:-prefixed form) was found in the raw HTML, regardless of capitalization. |
| 0 | No Notary type string was found in the raw HTML. |
How to optimize it
Use the Notary type only for a real notary service, and describe it with accurate credentials, services, jurisdiction, location, availability, and contact information. Make sure every property reflects content that users can verify on the page itself. Read this factor as an observation of what markup is present, not as a target to add to pages that do not represent a notary service.
Important considerations
- The detector pattern-matches source text instead of validating a 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 to confirm it is well-formed and accurate.
- This factor relates to position within a measured result set — it is a prioritization signal, not a cause of ranking, and adding it does not by itself make a page rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.