Schema.org vs llms.txt: which AI search signal matters most?
Both matter and they do different jobs. Schema.org JSON-LD identifies your entities (Organization, Product, Person) per-page for machine parsing. llms.txt is a site-level declaration of what your site is about, what content to prioritize, and how AI engines should use it. Ship both.
The two signals serve different layers of the AI visibility stack. Treating them as alternatives leads to picking the wrong one and shipping incomplete coverage.
Side-by-side
| Dimension | Schema.org JSON-LD | llms.txt |
|---|---|---|
| Scope | Per-page entity identification | Site-level declaration |
| Format | Embedded JSON-LD in <head> | Standalone markdown file at /llms.txt |
| Primary purpose | Identify entities (Org, Product, Person, etc.) | Tell AI what site is about + use policy |
| Maturity | Established W3C spec, well-supported | Emerging 2024 spec, fast-adopting |
| Engines that consume | Google + all 4 AI engines | ChatGPT, Claude, Perplexity, Gemini |
| Update frequency | On content change | On structural change (product launches, etc.) |
When Schema.org matters more
Per-page entity identification, rich results in Google search, breadcrumb / FAQ / Article / Product snippets in SERPs. If you want Google to render rich results AND give AI engines entity grounding on each page, Schema.org is non-negotiable.
When llms.txt matters more
When AI engines need a fast, structured site-level summary. llms.txt is the file an LLM reads first to decide what your site is about. Without it, the engine reconstructs from crawled pages (slower, noisier, lower-confidence grounding).
The right framing: Schema.org is per-page entity grounding; llms.txt is whole-site narrative. They compound — a page with Organization JSON-LD AND a complete llms.txt outperforms either alone.
How to audit both
Radar runs Schema Audit (per-page JSON-LD coverage) AND llms.txt Validator (site-level file structure) in parallel. The unified report shows where each signal is weak and which to fix first.
Want to take action on this?
Related questions
Why is not ChatGPT citing my B2B SaaS?
ChatGPT cites sites it treats as authoritative for a query. Most B2B SaaS sites lack three specific signals: structured data declaring entity identity, an llms.txt file, and citations from domains ChatGPT already trusts.
WhyWhy is my company invisible in AI search results?
AI engines surface companies they trust as authoritative for a query. Invisibility usually means one of three things: AI crawlers cannot access your site, your structured data does not identify your entity, or no high-authority source on the web mentions you.
How-toHow do I add Organization schema for AI search?
Add a JSON-LD script tag with Organization schema to your root layout (head). Include name, legalName, url, logo, foundingDate, founders, sameAs links to LinkedIn/GitHub/Crunchbase, and disambiguatingDescription if a similarly-named company exists. AI engines re-crawl and update within 7-14 days.
DefinitionWhat is Generative Engine Optimization (GEO)?
Generative Engine Optimization (GEO) is the practice of structuring web content so AI search engines like ChatGPT, Claude, Perplexity, and Gemini cite it in their responses. Unlike SEO which optimizes for keyword rankings, GEO optimizes for entity recognition, structured data, and citation probability.
