Has JSON-LD Language

Abstract illustration of a globe-and-speech-bubble language marker carrying a JSON-LD structured-data tag beside a plain marker, in RankGear indigo and coral.

Has JSON-LD Language reports whether the raw source HTML contains a JSON-LD @type declaration set to Language. It returns 1 when that string pattern is found and 0 when it is not — a source-text match, not confirmation that the markup sits inside a valid JSON-LD graph.

Factor IDRG-SCJ-130
FamilyStructured data — JSON-LD
MeasurementBoolean (0 / 1)
Measured zoneRaw rendered HTML

What it measures

Has JSON-LD Language reports whether RankGear finds an @type value of Language in the raw source. A value of 1 means the recognized type pattern was present; a value of 0 means it was not. The factor detects a string pattern only. It does not validate the surrounding JSON-LD, confirm that the value describes a genuine language entity, or check that its properties are accurate.

Back to Top

How RankGear measures it

RankGear searches the raw HTML for "@type": "Language", allowing flexible whitespace around the separator and optionally accepting the schema: prefix. Matching is case-insensitive, so capitalization differences in the key or value do not affect the result. Because the detector pattern-matches source text rather than parsing a JSON-LD graph, a matching string that appears outside valid structured data can still produce 1.

Back to Top

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Language",
  "name": "Spanish",
  "alternateName": "Español"
}
</script>
ValueMeaning
1An @type of Language (or the schema:-prefixed form) was found in the raw source, in any capitalization.
0No Language type declaration was found in the raw source.
Back to Top

How to optimize it

Use the Language type only for a genuine language entity, with an accurate name, an alternate name, and a language code where one is available. Ensure every property reflects content that users can verify on the page. Read this factor as an observation of what the source contains, not as a target to add where a language entity is not actually being described — a match that lives outside valid JSON-LD still reports 1, so presence alone is not the goal.

Back to Top

Important considerations

  • The detector pattern-matches source text instead of validating a JSON-LD graph.
  • A matching string that appears outside valid JSON-LD can produce a 1.
  • Capitalization differences do not affect detection.
  • Validate the complete structured data independently to confirm it parses and represents a real language entity.
  • 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.
Back to Top

Related factors

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

Back to Top