Schema inLanguage
Why it matters
The inLanguage schema field declares the content language to every parser of your JSON-LD; it should match <html lang> and the visible text.
What we check
Whether the page's schema markup includes an inLanguage property to declare the content language.
How to fix
- 1 Add "inLanguage": "en" (or appropriate ISO 639-1 code) to your Article or WebPage schema.
- 2 For regional variants, use BCP 47 format (e.g., "pt-BR").
- 3 Ensure this matches the <html lang> attribute.
Example
inLanguage on the page's main JSON-LD entity
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How to Choose a Standing Desk",
"inLanguage": "en-US",
"datePublished": "2026-10-01"
}
</script>
How to check it yourself
- View the page source and search each application/ld+json block for inLanguage, including nodes inside @graph.
- Compare the value with the <html lang> attribute. Both should carry the same IETF BCP 47 code, such as en, de or pt-BR.
- Paste the URL into the Schema Markup Validator (validator.schema.org) and confirm inLanguage sits on the page's main entity, not on an unrelated node.
FAQ
Does Google use inLanguage?
Google does not list inLanguage among the recommended properties for Article structured data, and it determines a page's language from the visible text. Treat inLanguage as a machine-readable language declaration for other consumers of your JSON-LD, not as a Google ranking factor.
Which language code format should I use?
Schema.org asks for codes from the IETF BCP 47 standard: a language subtag such as en or fr, optionally with a region or script subtag such as en-GB, pt-BR or zh-Hant.
Where does inLanguage belong on a multilingual site?
On each page's own main entity, such as its Article, WebPage or Product node, with the language of that page. A single sitewide value on a translated page contradicts the visible text.
What if inLanguage and <html lang> disagree?
No parser documents which one wins, so a mismatch makes both declarations unreliable. Fix whichever is wrong so the JSON-LD, the lang attribute and the visible text all name the same language.
Is inLanguage needed on a single-language site?
It is optional in schema.org. On a single-language site it costs one property and keeps the JSON-LD self-describing when it is read without the surrounding HTML.