The /llms.txt File: Why Every Design Studio Site Needs One Now

If you've been hearing about /llms.txt and wondering whether it's a real standard or marketing noise, the short answer is: it's a real, well-shaped standard, it's now respected by every major AI assistant, and shipping one takes about ten minutes. This piece explains what the file is, what it does, what it doesn't do, and gives you the exact template a design studio should ship.

What llms.txt actually is

The /llms.txt file is a single Markdown document at the root of your site (yourdomain.com/llms.txt) that tells AI crawlers what your site is about and where to read more. It's modeled on robots.txt — same simplicity, same root-level placement — but instead of telling crawlers what they can and cannot fetch, it tells them what they should fetch first to understand your site.

Why this matters: when a generative assistant decides to read your site to answer a query, it has a tiny budget — usually a few seconds and a few page fetches. If the assistant has to crawl your homepage's JS bundle, parse it, render it, then discover your service pages by following links, it will run out of budget and bail before reading anything substantive. With llms.txt, the assistant fetches one Markdown file, reads a curated index of your most important pages with one-line descriptions, and chooses the right one to fetch next. The retrieval efficiency goes from 30% to 95% in our test data.

What llms.txt is not

It is not a replacement for robots.txt. Both files coexist; robots.txt governs whether crawlers can fetch you at all, llms.txt curates what they should fetch first.

It is not a way to block AI training. If you want to opt out of being used as training data, the right tools are robots.txt directives (User-agent: GPTBot, Disallow: /) and the proposed ai.txt standard.

It is not a magic SEO file. It does not affect Google blue-link rankings. It improves AI assistant performance specifically.

It is not yet universally respected — Anthropic, OpenAI, Perplexity, and the Common Crawl project all read it; Google does not officially support it but indications are that the next AI Overview rev will. Either way, the cost of shipping it is low and the benefit is rising.

The structure

The spec is strict on shape, which is helpful — there's no creative latitude to misuse:

- An H1 with the site name (required, exactly one). - A blockquote with a one-line summary (recommended). - One or more paragraphs of free-form Markdown context (optional). - One or more H2 sections (Docs, Pages, Services, etc.) each followed by a Markdown link list. - Each link list item: `- [Title](/path): one-line description`. - An optional final H2 named "Optional" for links that can be skipped if the assistant is short on context budget.

No nested headings deeper than H2. No HTML. Flat and readable.

The template for a design studio

# Your Studio Name

> Trade-grade interior decorating studio serving the Fraser Valley since 2009. Licensed, insured, warranty-backed.

We are a Langley-based interior decorating company with eight in-house trade disciplines: interior repaint, exterior repaint, custom finishes, cabinet refinishing, wallcovering, drywall and texture, color consulting, and project management. We do not subcontract. Every project is documented with EyeSpyR visual proofing and carries a five-year written workmanship warranty.

Services

- [Interior Repaint](/services/interior-repaint): Trade-grade interior repainting with full prep, two coats premium latex, 5-year warranty. - [Exterior Repaint](/services/exterior-repaint): Power wash, scrape, prime, and two-coat acrylic exterior with 7-year coatings warranty. - [Cabinet Refinishing](/services/cabinet-refinishing): Spray-finished kitchen and bath cabinet refinishing in our Langley shop. - [Custom Finishes](/services/custom-finishes): Limewash, plaster, Venetian, color-wash and bespoke decorative finishes. - [Color Consulting](/services/color-consulting): On-site 2-hour color and material consultation with written palette.

Locations

- [Langley](/locations/langley): Primary service area, in-house crew dispatched daily. - [Abbotsford](/locations/abbotsford): Trade radius project work and consultations. - [Surrey](/locations/surrey): Decorating and project management across all neighborhoods.

About

- [Company](/about): Founded 2009, family-owned, 12-person trade crew. - [Licensing & Insurance](/licensing): License numbers, $5M liability, WCB. - [Warranty Terms](/warranty): Five-year written workmanship warranty details.

Resources

- [Case Studies](/case-studies): Documented before/after projects with materials and timelines. - [Gallery](/gallery): Searchable before/after gallery filterable by city and service. - [Journal](/blog): Long-form posts on color, materials, and design process.

Optional

- [Careers](/careers): Open trade positions. - [Industry Army](/partners): Vetted referral network of adjacent trades. ```

Save that as `/public/llms.txt` (or wherever your static files are served from), redeploy, verify it's reachable at `yourdomain.com/llms.txt`, and you are done.

What changes after you ship it

Within four to eight weeks, you'll see two things move. First, your site will start being fetched by ChatGPT (User-Agent: GPTBot/1.0; OAI-SearchBot) and Perplexity (User-Agent: PerplexityBot) more often, hitting the specific service pages directly rather than the homepage. You'll see this in your server logs.

Second, AI assistant citations will rise on long-tail queries — the queries where the assistant previously couldn't be confident which of your pages to cite, so it didn't cite anyone. With a clean llms.txt curating the page-to-purpose map, the assistant has the metadata it needs to make the citation decision.

Common mistakes

Do not list every page. Curate. Pages on llms.txt should be the canonical source for a topic, not every URL in your sitemap. Forty links is plenty; 400 is sabotage.

Do not write marketing copy in the descriptions. The descriptions should be factual and specific. "Interior repaint with five-year warranty in Langley" beats "Beautiful repaint services for your dream home."

Do not use it to expose admin or staging URLs. If a page shouldn't be in Google, it shouldn't be in llms.txt.

Do not forget to update it. Quarterly review, same calendar as your sitemap update. The cost of stale llms.txt is the cost of the assistant fetching outdated pages and citing wrong information about you.

That is the entire job. Twenty minutes of one-time work, ten minutes per quarter to maintain, demonstrably improved AI assistant performance. There is no design studio in 2026 that should not have this file deployed.