Has JSON-LD City is a 0 / 1 flag for whether RankGear finds an @type value of City in a page’s raw HTML, marking a city as a named place entity in JSON-LD structured data. Important caveat: RankGear pattern-matches the text and does not parse or validate the JSON-LD graph, so a 1 only means the string was present — not that the surrounding markup is valid.
| Factor ID | RG-SCJ-049 |
|---|---|
| Family | Structured data — JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
This factor reports whether the page declares the City type in its JSON-LD structured data. The City type identifies a city as a named place — a populated geographic entity carrying a name, geographic relationships to the larger administrative areas that contain it, and external identifiers — expressed in a machine-readable form. RankGear returns 1 when it finds the declaration in the raw source and 0 when it does not.
How RankGear measures it
RankGear performs a case-insensitive search of the raw HTML for a "@type": "City" declaration, allowing flexible whitespace around the colon and permitting an optional schema: prefix on the type value. Because the match is case-insensitive, differences in capitalization do not affect detection. The check operates on raw source text rather than on a parsed JSON-LD graph, so it confirms the presence of the string pattern, not the validity of the structured data around it.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "City",
"name": "Austin"
}
</script>
# also matched: "schema:City", flexible whitespace, any capitalization| Value | Meaning |
|---|---|
| 1 | A City JSON-LD @type declaration was found in the raw HTML. |
| 0 | No matching declaration was found in the raw source. |
How to optimize it
Treat this as an observation, not a target. Use the City type only for a genuine city entity, and give it an accurate name, correct geographic relationships to the administrative areas that contain it, and reliable external identifiers. Supply properties that agree with the content visible on the page. Because the check matches text rather than validating structure, do not add or alter markup solely to move the score — declare City only where it truthfully describes the entity.
Important considerations
- RankGear pattern-matches the text rather than parsing or validating the JSON-LD graph.
- A matching string that sits outside valid JSON-LD can still produce a 1, so the flag is not proof of correct structured data.
- Capitalization differences do not affect detection; the search is case-insensitive.
- Validate the complete structured data independently with a dedicated Schema.org or search-engine testing tool.
- Structured data correlates with, and does not guarantee, ranking outcomes; it is a prioritization signal measured within a result set, not a cause of position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.