This factor reports whether RankGear finds a JSON-LD @type of LegislationObject in a page’s raw source (1 = present, 0 = absent). It is a text match on the raw HTML, not a validated structured-data graph, so a match confirms the string is on the page — not that the markup is correct.
| Factor ID | RG-SCJ-133 |
|---|---|
| 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 LegislationObject in the page’s raw source. LegislationObject is the schema.org type for an object that forms part of, or is associated with, a piece of legislation — a bill, a statute, an act, or a related legal document. The result is binary: the page either carries the markup RankGear recognizes, or it does not.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "LegislationObject", allowing flexible whitespace around the tokens and optionally a schema: prefix on the type. Matching is case-insensitive. Because this operates on source text rather than a parsed JSON-LD graph, any occurrence of the pattern anywhere in the HTML returns 1.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "LegislationObject",
"legislationIdentifier": "...",
"legislationType": "..."
}
</script>| Value | Meaning |
|---|---|
| 1 | The LegislationObject type string was found in the raw HTML. |
| 0 | No matching type string was found. |
How to optimize it
Use LegislationObject only for a genuine object that forms part of, or is associated with, legislation, with accurate legal identifiers and relationships. Every property should reflect content a user can verify on the page. Treat the 1/0 result as an observation of whether the markup is present, not a target to chase: adding the type string to a page that has no legislative content misrepresents the page and adds nothing of value.
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 structured data is valid or complete.
- A matching string that sits outside valid JSON-LD (for example in a comment, code sample, or unrelated script) can still produce a 1.
- Capitalization differences do not affect detection; matching is case-insensitive.
- Validate the complete structured data independently with a schema validator — this factor does not.
- Presence of this markup correlates with pages in a measured result set; it is a prioritization signal, not a cause of ranking, and does not guarantee any position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.