Every agency I talk to right now is getting pressure from clients asking "what are you doing about AI search?" And most of the advice floating around involves rewriting page content, restructuring headers, adding FAQ schemas — stuff that genuinely can hurt your Google rankings if you do it wrong or do too much of it at once.
There's a lower-risk option that almost nobody is talking about seriously yet: the llms.txt file.
It's a plain text file you drop in the root of a site. AI crawlers — and increasingly, LLM-based search agents — are trained to look for it. It doesn't touch your existing page content. It doesn't mess with your crawl budget or your indexed pages. It just gives AI a clean, structured place to understand what the business actually is.
Most people treat it like a sitemap or a robots.txt clone. That's not what it's for.
The content that matters most to AI isn't your menu or your service list. It's verifiable, corroborating information — the stuff that lets an AI say "yes, this entity is real and I can confirm it from multiple directions."
Think about what AI is actually trying to do when someone asks "best Italian restaurant near me" or "who's a good plumber in [city]." It's not just matching keywords. It's trying to be confident in its recommendation. That confidence comes from cross-referencing.
Things that act like AI honey in this file:
The pattern here is: any claim in the file that has a live, off-site URL pointing to an independent source is exponentially more useful than a claim with no link.
When AI crawls that file and can follow three or four links that all confirm the same entity from different sources, it has what it needs to make a confident local recommendation.
Local AI recommendations are essentially an entity verification problem.
For a national brand, there's so much data floating around that AI can triangulate easily. For a local dentist or florist or HVAC shop, the signal is thin. If your llms.txt is the place where all those corroborating threads get pulled together and linked out — business license, a local press mention, an industry directory listing, a community award — you're doing the AI's job for it.
That's not manipulation. That's just good entity hygiene applied somewhere new.
Here's the thing: some of this information exists on your site in scattered form, some of it doesn't exist on your site at all (because why would you put your business license number on your About page?), and some of it is stuff you'd never surface publicly in normal content — but it's actually fine to put in llms.txt because the file is publicly accessible.
Just don't put anything genuinely sensitive. Treat it like a well-organized business credential sheet that a journalist or a new vendor might find useful. If you wouldn't hand it to someone at a networking event, don't put it in the file.
The instinct a lot of SEOs have right now is "I need to rewrite content for AI." Sometimes that's right. But often the better move is to give AI a dedicated, low-risk path to confirm what you're already claiming on your main pages.
llms.txt is that path. The corroboration is the honey. The file is just the jar.
Curious if anyone else has started including external verification links in theirs — most examples I've seen are still just dumping a site description and a list of URLs.