GEO Citability: Your data needs JSON-LD for AI to cite you

Citability is the metric that defines whether an LLM will cite your content or ignore it. Without JSON-LD, your post is plain text: AI engines extract entities and relationships, they don’t read prose like humans. Without structured data, you don’t exist in AI responses.

Which JSON-LD block makes your content citable?#

Inject a TechArticle block with the entities your content mentions:

geo-citability.jsonld

{
  "@context": "https://schema.org",
  "@type": "TechArticle",
  "name": "GEO Citability: Data for the AI Index",
  "description": "How to structure data so that LLMs cite you.",
  "keywords": ["GEO", "Citability", "AI Index"],
  "about": {
    "@type": "Thing",
    "name": "Graph Entity Optimization"
  }
}

This schema tells the LLM exactly what your post is about and which entities it mentions. Without this, the model has to guess from the plain text.

Why do LLMs prefer JSON-LD over plain text?#

LLMs build knowledge graphs from structured data, not from prose. A direct BLUF (40-60 words) answers the question, but JSON-LD is the semantic contract that enables citation. The difference is the same as between an HTML without alt and one with descriptive alt: for humans it looks the same, for AI it’s an abyss.

If your H2 is not a direct question, the LLM doesn’t know what it’s answering. Convert your headings into Query-Response.

Which JSON-LD block makes your content citable?#

Why do LLMs prefer JSON-LD over plain text?#

References#