Has JSON-LD State

Has JSON-LD State reports whether the page’s raw HTML contains an @type value of State for JSON-LD structured data: it returns 1 when RankGear finds the pattern and 0 when it does not. It is a text-match presence check — a 1 confirms the string is there, not that a valid State entity exists in a well-formed JSON-LD graph.

What it measures

Has JSON-LD State reports whether RankGear finds an @type value of State in the raw source. A value of 1 means the expected string appears somewhere in the HTML; a value of 0 means it does not. State is the Schema.org type for a state or regional administrative area. The factor measures the presence of that type declaration as text only — it does not parse the JSON-LD, confirm the surrounding markup is valid, or verify that the entity is used correctly.

How RankGear measures it

RankGear searches the raw HTML for the @type declaration State, allowing flexible whitespace around the value and optionally accepting a schema: prefix. Matching is case-insensitive, so capitalization differences in the type value do not affect the result. Finding at least one match returns 1; otherwise the value is 0. Because the check pattern-matches source text rather than validating a JSON-LD graph, a matching string that sits outside valid JSON-LD can still produce a 1.

What RankGear looks for

<script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@type": "State",
    "name": "..."
  }
</script>

(also matches: "@type": "schema:State", any capitalization, flexible spacing)

How to optimize it

Use State only for a genuine state or regional administrative area, and describe it accurately: an official name, correct identifiers, the places it contains, and authoritative references where they apply. Ensure every property reflects content users can verify on the page. Treat this factor as an observation of presence, not a target to chase — add the State type because it correctly describes the entity, not to satisfy a detector.

Important considerations

• The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 confirms a string, not a correct entity.
• A matching string that sits outside valid JSON-LD can still produce a 1.
• Capitalization differences in the type value do not affect detection.
• Validate the complete structured data independently — syntax, required properties, and Schema.org conformance are all outside this check.
• Presence relates to how pages are prioritized within a measured result set; it does not guarantee a ranking, a rich result, or indexing.

Related factors

• Has JSON-LD SportsTeam
• Has JSON-LD Store

Part of the Factors reference · how RankGear measures · glossary.