Shipped llms.txt — what should I track first? (sanity-check my plan)

Milan Novák
🔧 Schema, llms.txt, technical fundamentals

Just dropped an llms.txt at the root. ~250 words, includes product description, key features, pricing summary, support contact.

My plan to measure if it works:

  1. Baseline GEO score today (before AI re-crawls)
  2. Wait 2 weeks (avg recrawl cadence I've seen)
  3. Re-scan 5 monitored queries
  4. Compare mention quality, not just rate (rate jumps with noise; quality jumps with substance)

Questions for the room:

  • Has anyone seen llms.txt move ChatGPT vs Perplexity differently? (My hypothesis: Perplexity reads it faster, ChatGPT lags.)
  • Should I add a 'use cases' section, or keep it lean?
  • Anyone using llms-full.txt? Worth the maintenance overhead?
445

5 replies

  1. Nora

    From my test (see seed-010 if you want the methodology): Perplexity reads llms.txt, ChatGPT is inconsistent, Google AI Mode seems to not read it at all. So your hypothesis is right in my data too. I'd keep it lean — 'use cases' section yes, but max 3-4 bullet points. My 300+ word llms.txt performed worse than the trimmed 170-word version in terms of how accurately Perplexity described my product.

  2. Dave A.

    The SE Ranking study from earlier this year showed basically zero citation correlation with llms.txt adoption. I'm not saying don't do it, but temper expectations. If your real bottleneck is entity recognition and external mentions, llms.txt is just a nice-to-have right now.

  3. Milan Novák

    I've been running the llms-full.txt experiment for 6 weeks. Honest answer: not worth the maintenance overhead yet. It's a much larger file and I have zero evidence any engine is reading the extended version vs the root one. Maybe in a year.

  4. Petr VlčekFounder

    Petr here — we have llms.txt on roughly 40% of monitored domains now. Honest take: the measurable lift in citation rate is small and concentrated on Perplexity. The bigger value we observe is editorial — the act of writing the file forces a clean one-page positioning statement that people then port into their hero copy and About page, and THAT moves things. So don't expect the file itself to be the win.

  5. Marcus B.

    If you want a cleaner A/B than 'before vs after deploy', stand up a second subdomain (or a noindex staging clone) without llms.txt and run the same prompt battery against both. That isolates the file from concurrent content/PR/schema work, which is usually the real confound. We ran this for 6 weeks across two product lines and saw a measurable delta only on Perplexity for the variant with the file.

Add a reply

Have a related question or experience?

Post a new question