# What we did for the AI crawlers

> Every page on this site has a markdown twin, a JSON-LD graph and a seat in llms.txt. Some of it is proven, some of it is a cheap bet — here is which is which.

Search engines index documents; answer engines lift claims. The difference changes what you publish: a definitional paragraph that stands alone, a list of steps, an honest FAQ — and machine-readable twins of all of it so a crawler that prefers plain text does not have to parse a canvas. This is a description of the actual setup on this site, including the parts we are not sure work yet.

## Proven: the structured-data graph

JSON-LD restating what every page says — articles with authors and dates, a defined-term set for the glossary, FAQ and HowTo where the page genuinely is one, LocalBusiness identity tying the studio to a place. Honest markup earns rich results and entity reconciliation; markup that says more than the page earns neither.

## Probably useful: markdown twins

Every route answers .md — same content, plain markdown — for the growing set of tools that read text better than DOM. Cheap because it is generated from the same content files, which is also what keeps it honest: there is no second source to drift.

## A bet: llms.txt

A curated index of the site's best content in the format models prefer — adopted early by docs-heavy sites, unproven in actual crawler behavior. It costs one file and the same effort produced the twins and the schema, which definitely get read; the bet is cheap enough to place.

## What to take away

- Structured data restates the page — never argues with it.
- Markdown twins are generated from the same source, so they cannot drift.
- llms.txt is a cheap bet, not a proven channel.
- Write claims that stand alone — answer engines lift sentences, not pages.

## Tags

AEO, AI SEO, llms.txt, Structured data

## We build this for clients

https://dfieldsolutions.com/en/services/web-performance

## More from the lab

- https://dfieldsolutions.com/en/lab/ai-search-visibility-checklist.md — The AI-search visibility checklist we run on this site
- https://dfieldsolutions.com/en/lab/structured-data-aeo.md — Structured data an answer engine can use
- https://dfieldsolutions.com/en/lab/eaa-accessibility-deadline.md — The EU accessibility deadline passed — what still applies
- https://dfieldsolutions.com/en/lab/web-vitals-playbook.md — Core Web Vitals on a real Next.js site

---

Source: https://dfieldsolutions.com/en/lab/llms-txt-ai-crawlers
DField Solutions — Dunakeszi, Hungary — dezso@dfieldsolutions.com
Booking: see https://dfieldsolutions.com/en/contact