JSON-LD agreement
JSON-LD agreeing with the file
In short: Add Organization JSON-LD to your homepage’s server-sent HTML, using the name in your llms.txt H1 and your site’s URL as url.
What it checks
Whether your JSON-LD / schema.org markup agrees with what the file says about who you are.
Why it matters
When structured data and llms.txt disagree about your name or site, an agent has to pick one. Agreement makes both more trustworthy.
When it applies
Applies when at least one page loaded (HTTP 200) and we could read its JSON-LD. Unverified when no page loaded, or when we found no identity markup and your homepage was too large to read to the end (over 256 KB) or didn’t load: removed from your score, never counted as a zero.
An audit that doesn't apply, or that we couldn't verify, is removed from your score and its weight shared among the Ecosystem Integration audits that do apply. It is never scored as a zero.
How it's scored
0.4 when your homepage or a sampled page carries identity JSON-LD (Organization or a subtype, WebSite, Person, Product, Service or an application) · + 0.4 when its name, legalName or alternateName agrees with your llms.txt H1 · + 0.2 when its url is on the same site as the file (www. and subdomains count as the same site). Names agree when either contains the other, ignoring case, punctuation, legal suffixes such as Inc or LLC, and generic words such as Docs. An H1 that is a domain (“acme.com”) agrees through that domain’s name. 0 when we read your pages and found no identity JSON-LD; markup that doesn’t parse counts as absent.
How to fix
- Add an Organization JSON-LD block to your homepage, in the HTML the server sends.
- Use the name your llms.txt H1 uses (legalName and alternateName can carry the formal and short forms), and your site’s URL as url.
- Validate the markup so it parses: a block with a syntax error counts as missing.
Example
<script type="application/ld+json">
{"@context": "https://schema.org", "@type": "Organization",
"name": "Acme", "legalName": "Acme, Inc.", "url": "https://acme.com/",
"sameAs": ["https://github.com/acme"]}
</script>Frequently asked questions
What does the JSON-LD agreement check compare?
Organization or one of its subtypes, WebSite, Person, Product, Service or an application) on your homepage and up to 3 pages linked from your llms.txt, against the file: 0.4 for having identity markup at all, 0.4 more when its name, legalName or alternateName agrees with your llms.txt H1, and 0.2 more when its url is on the same site as the file. Names agree when either contains the other, ignoring case, punctuation, legal suffixes such as Inc and generic words such as Docs. sameAs is recorded but not scored.Sources: schema.org — Organization · LLMSRank — JSON-LD agreement audit
Does missing or mismatched JSON-LD lower my LLMSRank score?
Sources: LLMSRank — How we score (rubric v2.0) · LLMSRank — JSON-LD agreement audit
What JSON-LD should I add so it agrees with my llms.txt?
Organization block on your homepage (Google recommends the homepage or an about page) with name, legalName if it differs, url, logo and sameAs links to your official profiles, using the name your llms.txt H1 gives (see Entity identity). Put it in the HTML the server sends, not only through client-side scripts, and validate it so it parses: an agent that finds two different names for you has to guess which one is right. The consistency checker lists each mismatch with the exact line to fix.Sources: Google Search Central — Organization structured data · schema.org — Organization
How often does JSON-LD agree with llms.txt, in LLMSRank’s research?
Sources: LLMSRank — How we score (rubric v2.0) · LLMSRank — JSON-LD agreement audit