{
  "kind": "answer",
  "studySlug": "llmstxt-effect",
  "slug": "does-llms-txt-help-you-even-if-it-does-not-raise-citations",
  "title": "Does llms.txt help you even if it does not raise citations?",
  "description": "Possibly operationally, but not according to this citation benchmark. The study only asks whether llms.txt correlates with more citations, and the answer there is still no measurable lift.",
  "lastUpdated": "2026-03-14",
  "lastTested": "2026-03-14",
  "sourceStudyUrl": "/trakkr-research/llmstxt-effect",
  "sourceStudyTitle": "The llms.txt Effect",
  "claimIds": [
    "llmstxt-effect:p-value",
    "llmstxt-effect:adoption"
  ],
  "relatedSlugs": [
    "answer:should-you-prioritize-llms-txt-over-answer-infrastructure",
    "answer:why-is-llms-txt-getting-so-much-attention-if-the-effect-is-null",
    "fact:top-five-thousand-domain-adoption-is-still-only-sixteen-percent",
    "tracker:llmstxt-adoption-by-tier-tracker"
  ],
  "methodologySummary": "Built from HTTP scans of 37,894 AI-cited domains, linked to 337,362 citations and 882 citation snapshots in the Trakkr corpus.",
  "limitations": [
    "This is an observational study. It measures correlation with citation outcomes, not a controlled experiment.",
    "Adoption is uneven by sector, so raw averages can hide category concentration in SaaS and developer tooling.",
    "A null citation effect does not mean llms.txt has zero operational value for every workflow. It means the study did not find a measurable citation lift."
  ],
  "keywords": [
    "llms.txt",
    "llms txt effect",
    "AI citations",
    "does llms.txt work",
    "llms.txt operational value",
    "llms.txt strategy"
  ],
  "schemaHints": {
    "pageType": "Article",
    "includeDataset": true
  },
  "question": "Does llms.txt help you even if it does not raise citations?",
  "directAnswer": "Yes, operationally, but not according to this citation benchmark. The study only asks whether llms.txt correlates with more citations, and the answer there is still no measurable lift.",
  "answerSummary": "Teams can still use it for housekeeping or explicit guidance, but they should not confuse that with evidence of citation growth.",
  "keyFacts": [
    {
      "label": "Mann-Whitney p-value",
      "value": "0.85",
      "detail": "No statistically significant citation effect detected.",
      "claimId": "llmstxt-effect:p-value"
    },
    {
      "label": "Adoption rate",
      "value": "13.3%",
      "detail": "Domains with llms.txt in the study.",
      "claimId": "llmstxt-effect:adoption"
    }
  ],
  "evidenceTable": [
    {
      "label": "Mann-Whitney p-value",
      "value": "0.85",
      "note": "No statistically significant citation effect detected."
    },
    {
      "label": "Adoption rate",
      "value": "13.3%",
      "note": "Domains with llms.txt in the study."
    }
  ],
  "whyItMatters": "This distinction turns a study finding into an operating rule teams can use when they decide what to publish, refresh, or measure next, preventing misallocation of technical SEO resources.",
  "whatToDo": [
    "Treat llms.txt as an optional housekeeping file, not a primary citation-growth lever.",
    "Prioritize answer quality, source coverage, and page structure before spending disproportionate effort on llms.txt.",
    "Measure discovery and crawl behavior directly instead of assuming it improved citation performance if you do publish llms.txt."
  ],
  "faqs": [
    {
      "question": "What was the adoption rate of llms.txt in the study?",
      "answer": "The adoption rate was 13.3 percent among the domains analyzed."
    },
    {
      "question": "Did the study find any statistically significant citation effect?",
      "answer": "No, the study reported a Mann-Whitney p-value of 0.85, indicating no statistically significant citation effect was detected."
    }
  ]
}