Has JSON-LD Legislation is a binary signal (1 or 0) that reports whether RankGear finds an @type of Legislation in a page’s raw HTML. It confirms the type string is present — it does not parse or validate the JSON-LD graph, so a bare match anywhere in the source still counts.
| Factor ID | RG-SCJ-132 |
|---|---|
| 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 Legislation in the raw source. Legislation is the schema.org type for a legal instrument — a law, statute, regulation, act, or similar enactment issued by a responsible body. The factor answers one yes/no question: is that type declared anywhere in the page’s markup?
How RankGear measures it
RankGear searches the raw HTML for "@type": "Legislation", allowing flexible whitespace around the colon and an optional schema: prefix on the type value. Matching is case-insensitive: it returns 1 on any match and 0 otherwise. It is a string search over the raw source, not a parse of the structured-data graph.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Legislation"
}
</script>The whitespace around the colon may vary, the value may be prefixed ("@type": "schema:Legislation"), and case is ignored — any of these variants returns 1.
| Value | Meaning |
|---|---|
| 1 | A Legislation type string was found in the raw HTML. |
| 0 | No matching Legislation type string was found. |
How to optimize it
Use Legislation only for a genuine legal instrument, and give it accurate jurisdiction, identifier, dates, status, responsible body, text, and official references. Ensure every property reflects content that users can verify on the page. Treat the 1/0 as an observation of markup presence rather than a target to force: a bare type string satisfies this detector, but it adds nothing unless the page truly describes a legal instrument and the surrounding properties are correct.
Important considerations
- The detector pattern-matches source text; it does not validate the JSON-LD graph.
- A matching string outside valid JSON-LD can still produce 1.
- Capitalization differences do not affect detection.
- Validate the complete structured data independently.
- This is a prioritization signal that relates to position within a measured result set — presence of the type correlates with, but does not cause or guarantee, any ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.