llms.txt

llms.txt Implementation for AI Search Visibility


A plain-text file that states who a company is, what it sells and which pages matter — without the navigation, scripts and markup that surround the same facts in HTML. Both of ours are live on this domain.

/llms.txttext/plain
Available
# InTheMind AI > InTheMind AI is a Technical SEO & AI Visibility studio for B2B companies. Canonical website: https://inthemindai.com ## Company Name: InTheMind AIAlternate names: InTheMindAI, In The Mind AI, InTheMindCategory: Technical SEO and AI visibility studioCustomers: B2B companies, SaaS companies, tech companies and B2B service businessesPrimary outcome: Help companies improve visibility in AI answer engines such as ChatGPT, Perplexity, Gemini, Claude and Google AI OverviewsFounders: Ilia Onufriev and Artiom Cojocaru ## Core services * GEO audits* AI crawlability optimization* llms.txt and llms-full.txt implementation* Schema.org and JSON-LD implementation* Entity graph optimization

Public files

What we actually publish

Both files below are live on this domain. The short file is an index; the long file is the expanded profile. Open either tab to see the difference in shape rather than in wording.

/llms.txttext/plain
Available

Concise index — company, services and priority URLs in one screen.

# InTheMind AI > InTheMind AI is a Technical SEO & AI Visibility studio for B2B companies. Canonical website: https://inthemindai.com ## Company Name: InTheMind AIAlternate names: InTheMindAI, In The Mind AI, InTheMindCategory: Technical SEO and AI visibility studioCustomers: B2B companies, SaaS companies, tech companies and B2B service businessesPrimary outcome: Help companies improve visibility in AI answer engines such as ChatGPT, Perplexity, Gemini, Claude and Google AI OverviewsFounders: Ilia Onufriev and Artiom Cojocaru ## Core services * GEO audits* AI crawlability optimization* llms.txt and llms-full.txt implementation* Schema.org and JSON-LD implementation* Entity graph optimization

Excerpt from the live file — /llms.txt

What the file does

  • States the canonical domain and company name in one machine-readable place
  • Names the pages a company considers most important
  • Removes the navigation, scripts and markup that surround the same facts in HTML
  • Gives a stable URL that can be re-read whenever the site changes

What it does not guarantee

  • It is not a ranking signal and no vendor promises to read it
  • It cannot make a claim true that the website does not support
  • It does not replace robots.txt, sitemap.xml or structured data
  • A published file with stale facts is worse than no file at all

Two files

Where the short and the long file differ

They are not one document at two lengths. They answer different questions and go stale for different reasons.

Purpose
llms.txt — a short index of what matters
llms-full.txt — the expanded profile behind it
Content
Company summary, canonical domain, services, priority URLs
Founder context, service detail, public limitations and maintenance context
Maintenance
Changes when the page inventory changes
Changes when the business or the people behind it change

Lifecycle

How the file gets written and kept alive

A high-level view of the sequence. The file only stays useful for as long as it agrees with the website it describes.

  1. Review public company information

    We work from what the website, profiles and documentation already state — the file records facts, it does not invent them.

  2. Prepare the public file

    Company summary, canonical domain, services and priority URLs are written as plain text with a predictable shape.

  3. Validate accessibility and consistency

    The file has to be reachable as plain text and agree with the pages it points to, or it becomes another contradictory source.

  4. Maintain when the website changes

    New services, renamed pages and moved URLs make the file stale, so ownership of updates is agreed up front.

What you get

A file you can defend, not just publish

The deliverable is the published file plus the reasoning behind what went in and what stayed out. Anything the website cannot already support does not belong in it.

  • The published file on your canonical domain
  • A page map showing which URLs were prioritised and why
  • Notes on claims the site could not support
  • An agreed owner and trigger for updates

FAQ

Frequently asked questions

Next step

Ready to make your site citable by AI answer engines?

Tell us about your company and website. We will review the request and contact you to discuss the most relevant GEO and AI Visibility audit scope.