Do local businesses actually need an llms.txt file?

Not in the way a documentation site does, because most llms.txt traffic comes from coding agents following developer documentation. But an assistant answering 'is this plumber open on Sunday' or 'who does emergency callouts in this suburb' is reading ordinary web pages, and the same file that helps a coding agent find the right page helps a chat assistant find your service and location pages instead of a thin directory listing. The cost is one file; the downside is that the answer is assembled from whatever the crawler happened to fetch.

Should a multi-location business use one llms.txt or one per location?

Start with one root file that lists every location page in a named section. Add a per-location file only when a location has enough distinct content to justify it — its own services, its own team, its own service area. The spec says a file covers the URLs under its path and that agents should use the most specific file that applies, so /locations/denver/llms.txt takes precedence over the root file for everything under /locations/denver/.

Does llms.txt replace LocalBusiness schema or my Google Business Profile?

No, and treating it as a replacement is the most common mistake. Your Google Business Profile is where local pack and Maps information comes from, and LocalBusiness schema is what tells a parser your address, hours and service area in a structured form. llms.txt is a plain-language index that points a reader at the right page. Ship all three, and keep the facts identical across them.

Local SEO · September 2026

llms.txt for Local Businesses: Service Pages, NAP Data and Multi-Location Files

Most llms.txt writing assumes a documentation site with hundreds of pages. A local business has ten pages and one question to answer: which of them should an assistant read when someone asks whether you cover their street, what you charge, and when you are open. That is a much smaller file — and a much stricter one, because the facts in it have to stay true.

The Three Questions the File Has to Answer

Professional services, trades, clinics, salons, agencies: the content differs, but the questions an assistant is trying to resolve are the same three.

What do you do, exactly? The specific services someone searches for — emergency callout, root canal, monthly bookkeeping — not "tailored solutions".
Where and when? The service area, the physical address, opening hours, and whether you take bookings or walk-ins.
How does someone act? The page a person should land on to book, call, or get a quote.

Everything else — the history, the team bios, the blog — is secondary. If your file answers those three questions in its first screen, it is already doing more than most published files.

Which Pages to List, in Order

Priority	Page	What the description must contain
1	Booking / contact	How to book, phone number, response time
2	Each core service page	The service name and who it is for — one page per service, not one "Services" hub
3	Location or service-area page	Town names and postcodes covered, address, hours
4	Pricing or rates	Whether prices are published; starting rate if you show one
5	Credentials / accreditations	Licences, insurance, professional bodies
6	FAQ and reviews	The real questions customers ask before booking

Skip anything a crawler should not spend tokens on: thank-you pages, gated quote forms, tag archives, and the three near-duplicate location pages you created for the same city. Thin pages are not just useless in the file — listing them weakens the file's credibility. The triage rules in what not to include in llms.txt apply to a five-page plumber site exactly as they do to a SaaS docs hub.

Write the Summary Like a Business Card, Not a Mission Statement

The blockquote under the H1 is the part an assistant is most likely to quote or lift as standalone context. Put the factual core there: what you do, where you do it, and the one number that matters.

> Northline Plumbing is a licensed plumber in Portland, Oregon,
> covering Multnomah and Washington counties with same-day
> emergency callouts, Monday to Saturday, 7am to 7pm.
> Book at /book or call (503) 555-0142.

Compare that with "Northline Plumbing delivers quality solutions with a customer-first philosophy." Both are accurate; only one answers a question. The same discipline applies to the per-link lines, and the rewrite checklist in how to write llms.txt descriptions is written for exactly this.

Multi-Location: One Root File, Then Per-Location Files Only When Earned

A business with four branches needs one root file listing all four, one section per location, each pointing at that location's page. That is the whole requirement for most chains.

A per-location file becomes worth it when a branch has genuinely different content — different services, its own team, its own service area, its own prices. Because the spec scopes a file to the URLs under its path and tells agents to prefer the most specific file available, /locations/denver/llms.txt automatically wins for everything under /locations/denver/. That scoping rule is the same one that makes per-language files work, and it costs you nothing to use here too.

Hours, Prices and Seasonality: The Maintenance Trap

Local information changes far faster than docs. A stale llms.txt that says "open until 7pm" in December is worse than no file, because it is a confident, quotable, wrong answer. Two rules keep it manageable:

Put volatile facts in one place and link to it. A one-line summary of hours is useful; a full holiday schedule is not — point at the page that owns it and update that page.
Make the file part of an existing routine. If you already update your Google Business Profile before a holiday, the llms.txt file belongs in the same checklist.

Keep those facts identical to your LocalBusiness structured data and your Business Profile. Contradictory hours across three sources is how a business ends up described as "possibly closed".

A Complete Single-Location Example

# Northline Plumbing

> Licensed plumber in Portland, Oregon. Emergency callouts and
> residential repairs across Multnomah and Washington counties,
> Monday to Saturday, 7am to 7pm. Call (503) 555-0142.

## Book
- [Book a visit](https://northlineplumbing.com/book): Online booking form, same-day slots for emergencies.
- [Contact and hours](https://northlineplumbing.com/contact): Address, phone, opening hours, holiday closures.

## Services
- [Emergency callout](https://northlineplumbing.com/services/emergency): Burst pipes, leaks and no-water callouts, under 90 minutes in the core area.
- [Water heater repair and install](https://northlineplumbing.com/services/water-heaters): Repair, replacement and tankless installs.

## Service Area
- [Coverage and postcodes](https://northlineplumbing.com/service-area): Portland, Beaverton, Lake Oswego, Gresham.

## Optional
- [Reviews](https://northlineplumbing.com/reviews): Customer feedback from the last 24 months.

That is roughly 150 words. It fits in any context window, and an assistant can answer the three questions in the first section without opening anything.

Publishing and Verifying It

Serve it as plain Markdown at /llms.txt — not an HTML page that looks like text. On a CMS, upload it or publish it as a template; never rebuild it as part of a page layout. Then confirm what the outside world actually gets:

curl -sI https://northlineplumbing.com/llms.txt
curl -s https://northlineplumbing.com/llms.txt | head -12

Expect 200 and a text content type — a redirect to the homepage counts as missing.
Every link must resolve; a 404 in the booking line wastes the whole file.
Re-check after any site migration or URL change, when local pages are most likely to move.

Paste a sitemap into the llms.txt generator to get the structure, then cut it down to the pages above and rewrite the descriptions in plain language. Run it through the checker before you publish, and again after each service change. The file is small enough that a local business can keep it accurate — which is the only advantage that matters here.