LLMs.txt is not a shortcut to better Google visibility for a contractor website. On August 28, 2026, Google clarified that it does not use the file for Search, AI Overviews, or AI Mode, and that adding one will neither help nor hurt rankings. My recommendation is simple: do not pay for an llms.txt file as an SEO deliverable unless a specific system your company uses has documented that it reads the file.
That does not make the format fraudulent or useless. It means contractors need to separate a proposed web standard from a proven visibility requirement. The distinction matters when marketing budgets are already competing with website fixes, local pages, reviews, paid search, call handling, and booked-job tracking.
What is llms.txt for contractor websites?
LLMs.txt is a proposed Markdown file that gives language models and agents a curated description of a website and links to important resources. The published llms.txt specification places the file at a root or subdirectory path and organizes it with a site name, summary, explanatory text, and selected links.
For a plumbing company, for example, the file might point to pages about sewer repair, water heaters, financing, service areas, and emergency availability. That sounds reasonable. A concise directory could help a system that has deliberately been built to request and interpret it.
The problem begins when that limited purpose gets converted into a broad promise that installing the file will improve Google rankings or make a company more likely to appear in AI answers. Google now explicitly says otherwise.
Google says llms.txt does not affect Search visibility
Google recorded the clarification in its August 28, 2026 Search documentation update. The company says llms.txt files are not needed for Google Search and have no positive or negative effect on visibility or rankings.
Google’s complete guide to generative AI visibility is even more direct. Google Search does not use llms.txt, special AI text files, new machine-readable files, or special markup to determine whether a site can appear in AI Overviews or AI Mode. Google may still discover or index a text file, but that does not give the file special ranking value.
This clarification applies specifically to Google Search. It does not prove that no current or future tool will ever use the format. Google says maintaining the file is fine for another service that supports it. The practical question is whether that service exists in the contractor’s actual technology stack and has documented the benefit.
LLMs.txt, robots.txt, and sitemaps do different jobs
Contractors should not treat these files as interchangeable. Each one has a different purpose, and only the first remains a proposed convention with uneven support.
| File | Primary job | What it does not guarantee |
|---|---|---|
| llms.txt | Offers a curated Markdown guide for systems that choose to read it | Google rankings, AI Overview inclusion, or AI citations |
| robots.txt | Controls which paths compliant crawlers may access | Removal of an allowed or externally linked URL from search results |
| XML sitemap | Lists preferred URLs for search engines to discover | Crawling, indexing, ranking, or lead generation |
Google’s robots.txt documentation describes that file as a crawler-access control, mainly used to manage requests. OpenAI likewise documents OAI-SearchBot controls through robots.txt for sites that want to be eligible for ChatGPT search results. Those are documented crawler instructions. An llms.txt file is a separate content guide, not an access-control replacement.
If a contractor is unsure whether crawlers can reach important pages, I would inspect that before adding another file. A website and visibility audit should verify indexing, crawler access, page quality, local signals, tracking, and conversion paths together.
When creating an llms.txt file can be reasonable
An llms.txt file can be reasonable when a named vendor, agent, or internal workflow says it consumes the format and explains how. The file should then be treated as maintained technical documentation for that use case.
I would require four conditions before assigning the work:
- A specific system documents that it requests or reads llms.txt.
- The business can identify the task the file improves.
- The listed pages contain accurate, public, current information.
- Someone owns updates when services, markets, policies, or URLs change.
A file that points to retired offers, incorrect service areas, or thin pages can create a maintenance problem without producing a measurable business benefit. It also must never contain internal pricing rules, customer records, unpublished offers, or other information that should not be public.
What contractors should prioritize for AI and search visibility
Google’s current recommendation is to keep the website crawlable, technically clear, useful, and grounded in original expertise. For a local-service company, that means publishing accurate service and service-area information, showing real project evidence, maintaining business details, and answering the questions homeowners ask before booking.
I would prioritize these items ahead of llms.txt:
- Indexable service pages: Each important service needs a useful page that can be crawled, indexed, and understood without relying on a script or an image.
- Consistent local details: The company name, phone, address or service area, hours, and core services should agree across the website and Google Business Profile.
- First-hand proof: Real project descriptions, photographs, technician expertise, licenses, warranties, and clearly qualified claims give search systems and homeowners something specific to evaluate.
- Clear page relationships: Internal links should connect services, locations, projects, and supporting answers in a way that makes sense to a customer.
- Outcome measurement: Track visibility through qualified calls, appointments, sold jobs, and collected revenue. Our contractor AI-search scorecard explains why mentions alone are not enough.
None of these actions guarantees placement in a search result or AI answer. Google explicitly notes that meeting its requirements does not guarantee crawling, indexing, or serving. These priorities are still more defensible because they improve the public website customers use while aligning with documented search requirements.
A simple decision rule for contractor owners
Ask one question before approving an llms.txt project: Which named system will use this file, and what business process will improve if it does?
If the answer is only “Google,” “AI SEO,” or “future-proofing,” I would decline the work for now. Google has stated that the file does not affect its Search visibility. If a real vendor documents support and the implementation is inexpensive to maintain, adding the file can be a reasonable experiment, but it should be labeled as such and measured against a defined outcome.
Established trades companies have more consequential problems to solve first: pages that cannot be indexed, weak proof, inconsistent service information, low-quality leads, missed calls, and marketing systems that stop reporting at the form submission. If those pieces are fragmented, our connected implementation program for established home-service companies is the appropriate next step.
