Set up llms.txt and pass Google's Agentic Browsing audit

The llms.txt editor lives under AI search → llms.txt. It builds both files — the short map and llms-full.txt with inlined content — from your real pages, and updates them when your content changes. You pin the pages that must come first, set a preferred citation line ("cite us as …") and a contact line, and watch the live token counter so the file stays within what assistants actually read.

The three rules

Google's PageSpeed "Agentic Browsing" audit checks that the file exists at the root, parses as valid Markdown with the expected sections, and contains real, resolvable links. The panel shows all three checks with their current state before you run the report — if something would fail, you see it here first, with the fix named.

What belongs in it

Not everything. The strongest llms.txt files list 10–30 pages that answer buyer questions: what you do, what it costs, how you compare, proof. The pin list is where you enforce that order. Blog archives, tag pages and legal boilerplate stay out — the generator excludes them by default.