Guide

llms.txt vs schema.org Q&A markup: which one do you need?

Q: What's the difference between llms.txt and Q&A schema.org markup?

They work at two different levels. llms.txt is a single file, placed at the root of your domain, that gives AI engines a structured summary of your whole site: who you are, what you offer, where your important pages live. It operates at the site level and serves discovery and comprehension. Q&A schema.org markup is JSON-LD embedded in the code of individual pages: it exposes question-and-answer pairs in a format machines read without ambiguity. It operates at the page level and serves citability — it cuts your content into units an answer engine can lift as-is. The shorthand that sums it up: llms.txt makes you readable, Q&A markup makes you quotable word for word. One introduces your site; the other structures your answers.

Q: Which one should you add first?

If you have five minutes: llms.txt, because it is a single file to drop in and it covers the whole site at once. If you have an hour: both, because they each cover a different half of the path to citation. Answer engines work in two stages — retrieve and understand candidate pages, then select the passages to cite. llms.txt acts on the first stage: it makes your site easy to discover and understand. Q&A markup acts on the second: it makes your answers easy to select and quote as-is. Deploying only one optimizes half the funnel: readable but not quotable with llms.txt alone, structured but poorly summarized with markup alone. So the real answer is: both, generated from the same content so they stay consistent.

Q: Do the two formats overlap or conflict?

Neither — as long as you keep them consistent. They do not say the same thing: llms.txt summarizes and points to your pages, the markup structures the content of those pages. There is no possible conflict between the formats themselves — an engine can read both, and each helps it differently. The real risk is editorial: drift. An llms.txt that promises what your pages don't say, or Q&A markup whose answers contradict the visible text of the page, destroys exactly the trust you are trying to build — answer engines cross-check sources, and inconsistency is paid in non-citation. The practical rule: both files should be generated from the same real content, and regenerated together when the site changes. That is a strong argument for automating the pair rather than hand-maintaining each piece.

Updated · July 5, 2026 — Joffrey Bonifay

Two formats come up whenever AI-answer visibility is discussed: the llms.txt file and Q&A schema.org markup (JSON-LD). They are often confused, sometimes pitted against each other. In reality they do two different jobs — and they work as a pair.

What's the difference between llms.txt and Q&A schema.org markup?

They work at two different levels. llms.txt is a single file, placed at the root of your domain, that gives AI engines a structured summary of your whole site: who you are, what you offer, where your important pages live. It operates at the site level and serves discovery and comprehension.

Q&A schema.org markup is JSON-LD embedded in the code of individual pages: it exposes question-and-answer pairs in a format machines read without ambiguity. It operates at the page level and serves citability — it cuts your content into units an answer engine can lift as-is. The shorthand that sums it up: llms.txt makes you readable, Q&A markup makes you quotable word for word.

What does Q&A schema.org markup actually do?

schema.org is a structured-data vocabulary created in 2011 by Google, Microsoft, Yahoo and Yandex to describe page content in a machine-readable format. Q&A markup is one application of it: a JSON-LD block that explicitly declares “here is a question, here is its accepted answer”.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Do you deliver on weekends?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Yes — Saturday deliveries are available
               in the whole Lyon area, ordered before 6pm Friday."
    }
  }]
}
</script>

An honesty note: since 2023, Google rarely shows FAQ rich results in classic search pages for ordinary sites. But that is about SERP display widgets, not machine readability. For an AI answer engine parsing your page, the markup remains an unambiguous citation unit — a precise question, a direct answer, a clear source.

Which one should you add first?

If you have five minutes: llms.txt, because it is a single file to drop in and it covers the whole site at once. If you have an hour: both, because they each cover a different half of the path to citation.

Answer engines work in two stages — retrieve and understand candidate pages, then select the passages to cite. llms.txt acts on the first; Q&A markup on the second. Deploying only one optimizes half the funnel: readable but not quotable with llms.txt alone, structured but poorly summarized with markup alone. The real answer: both, generated from the same content so they stay consistent.

Do the two formats overlap or conflict?

Neither — as long as you keep them consistent. They do not say the same thing: llms.txt summarizes and points to your pages, the markup structures the content of those pages. There is no possible conflict between the formats themselves — an engine can read both, and each helps it differently.

The real risk is editorial: drift. An llms.txt that promises what your pages don't say, or markup whose answers contradict the visible text, destroys exactly the trust you are trying to build — answer engines cross-check sources, and inconsistency is paid in non-citation. The practical rule: generate both from the same real content, and regenerate them together when the site changes. That is a strong argument for automating the pair rather than hand-maintaining each piece.

How does Citeable generate the two together?

Citeable crawls your site's public pages — no admin access, nothing modified — then extracts the real content: your offer, your answers, your practical information. From that single crawl it generates both files: a structured llms.txt following the specification and the Q&A schema.org markup as JSON-LD, ready to drop onto your pages. Because both come out of the same analysis, they are consistent by construction.

Payment is one-time, per pack of sites, and the files are regenerable for life as your site evolves. Honest scope: nobody controls the answer engines, so this is a best-efforts obligation — making your site as readable and citable as possible, cleanly.