By SocialCRM · Sources checked September 7, 2026
Updated September 7, 2026: this article replaces earlier guidance that overstated what llms.txt could do. Creating a text file does not establish that ChatGPT, Google, or another service has read it or changed an answer.
What Google has clarified
Google’s June 15, 2026 documentation update says llms.txt is unnecessary for Google Search and has no positive or negative effect on visibility or rankings. Google allows that the file may be useful for other systems that choose to use it. That is a compatibility purpose, not evidence of ranking value.
For Google AI search features, invest in accessible public pages, useful information, and accurate business facts. Do not replace those pages with a machine-oriented export.
When an optional export has a purpose
Keep an export when a named application or integration consumes it and you can explain what that application does with the data. Maintain source links, review dates, and approved facts. Treat generation, publication, retrieval, and observed answer changes as different events.
If no consumer of the file is known, give the work a lower priority than inaccurate hours, missing service information, failed booking forms, or blocked public pages. Do not award a search-readiness score simply because the file exists.
What a repair shop should publish first
Do not assume that a repeated answer will change immediately. Access permits retrieval; it does not guarantee retrieval, inclusion, recommendation, or a booking.
- Publish current address, hours, phone number, and contact options on the location page.
- Describe actual services and accepted vehicles on service pages.
- Link certifications and warranty statements to supporting evidence and applicable conditions.
- Check Googlebot and OAI-SearchBot access through both robots rules and hosting controls.
- Save specific answer errors, correct the authoritative source, and repeat the same check.
What to ask your software provider
Ask which public page was improved, which source supports each fact, and whether publication was verified. If the provider reports an AI answer change, ask for the dated prompt, system, answer, and cited sources. A generated file alone should not be reported as a visibility improvement.
Keep useful customer questions on the website. Google retired FAQ rich results in May 2026, so FAQ markup should not be presented as a route to that Google feature.
Sources and further reading
Platform guidance is linked below. The workflows and study design are SocialCRM recommendations, not ranking guarantees.
Put the guidance to work
Start with a recorded check of what AI says about your shop. Compare the answer with verified facts before deciding what to change.
Start your AI Shop Checkup