Google has added an llms.txt check to Chrome Lighthouse, the website auditing tool used by developers and search specialists. That sounds like another urgent AI visibility task, but the detail is more measured than the headline suggests.
The new Lighthouse audit sits under Chrome’s experimental agentic browsing checks. It looks for whether a site has an llms.txt file, a proposed text file that gives AI agents a machine-readable summary of the website and its important links. Chrome’s documentation says the file is optional, and a normal 404 is treated as not applicable rather than a failure.
At the same time, Google’s Search Central guidance is clear that businesses do not need new machine-readable AI files, AI text files or special schema to appear in Google’s AI Overviews or AI Mode. For Bath and South West businesses, that distinction matters. This is not a reason to buy an expensive “AI SEO file” package overnight. It is a reason to understand what different Google teams are actually talking about.
What has changed in Lighthouse
Lighthouse is a diagnostic tool. It can flag performance, accessibility, technical SEO and best-practice issues so developers can see where a page might be improved. The new llms.txt audit is part of a newer set of agentic browsing checks, not the classic SEO checklist most businesses are used to seeing.
In practice, the audit checks what happens when Lighthouse tries to fetch /llms.txt from the root of a website. If the file is missing and the server returns a standard not-found response, the audit is treated as optional. If the request causes a server error, Lighthouse may flag that because the site is not handling the request cleanly.
That means the first practical job is not to panic about rankings. It is to make sure your website behaves sensibly when unfamiliar automated tools request common files. A clean 404 is very different from a server error or a security loop.
Why this is not the same as Google Search visibility
Google’s Search guidance for AI features still points businesses back to the fundamentals: pages need to be indexable, eligible to appear in Search with snippets, technically accessible, useful, and supported by normal SEO best practice. Google explicitly says there are no additional technical requirements for appearing as a supporting link in AI Overviews or AI Mode.
So an llms.txt file should not be treated as a magic AI ranking signal. It may become useful for some AI agents, developer tools, documentation sites or future browsing experiences. But that is a different claim from saying it will make a Bath retailer, Somerset consultant or Bristol service business suddenly more visible in Google Search.
This is where the AI search market is becoming muddy. Some vendors take an emerging technical convention and sell it as an urgent visibility fix. Sometimes the thing being sold may have a legitimate use. The problem is the leap from “this may help an agent understand a site structure” to “this will improve your Google AI search performance”. Those are not the same thing.
What local businesses should check first
If your website already has technical issues, thin service pages, poor internal linking, missing product information, vague location coverage or inconsistent business details, those are still likely to matter more than adding a new text file.
For a local organisation, a sensible order of work would look like this:
- Check that important pages are crawlable and indexable. If Google cannot access the page properly, AI features are not the first problem.
- Make service and product pages clearer. Explain who each offer is for, what is included, where you work, and what someone should do next.
- Keep business information consistent. Website pages, Google Business Profile, Merchant Center, directories and social profiles should not contradict each other.
- Use internal links properly. Help people and search systems move from broad pages to the detail they need, especially around core services and local areas.
- Fix obvious technical errors. Server errors, blocked assets, slow pages and broken templates are more concrete risks than a missing optional file.
Those basics overlap with good SEO for Bath businesses and practical AI search optimisation. They also make the website better for human visitors, which is still the point rather than a quaint legacy concern.
When an llms.txt file may be worth considering
An llms.txt file may be worth testing if you have a large documentation site, a complex catalogue, a substantial knowledge base, or a clear reason to help AI agents discover key pages quickly. It can also be a tidy way to summarise a site for experimentation, provided it is maintained and does not drift out of date.
For many small and medium-sized local businesses, though, it should sit behind more useful work. A well-written service page, clear location information, accurate product data, visible contact details and a technically sound site will usually do more good.
If you do add one, keep it simple. Link to genuinely important pages. Avoid marketing fluff. Do not put private or misleading information in it. Remember that it is another public file on the website, not a hidden instruction manual for trusted machines.
The practical takeaway
The Lighthouse change is a useful signal about where web tooling is heading. AI agents, browsers and search systems are all becoming more interested in structured, easy-to-understand websites. But it is not a licence to ignore the old work that still makes websites useful.
For Bath and South West businesses, the calm response is to separate experiments from essentials. If your website already explains your services clearly, supports local search properly, links useful pages together and avoids technical errors, then testing llms.txt may be a reasonable extra. If those foundations are weak, fix them first.
The businesses that do best in AI-shaped search are unlikely to be the ones that chase every new acronym. They will be the ones whose websites are easy to crawl, easy to understand and genuinely helpful when a real customer arrives with a real question.
