What is llms.txt and should a dealership website have one?
A plain-text file at the root of a site that points language models at its most useful pages, in the spirit of robots.txt but for retrieval rather than crawling. It is a convention, not a standard, and no system is obliged to read it. It costs almost nothing to publish and it does not substitute for the pages themselves being clear and current.
What it is for
It offers a curated map — the pages that best represent the site — rather than leaving a system to infer structure from navigation. For a large reference site that is genuinely useful; for a five-page brochure site it changes little.
It is not a ranking mechanism
Publishing the file does not cause a model to prefer the site. Treat it as making existing quality easier to find, not as an optimisation in itself.
Keep it accurate
A file listing URLs that have moved or no longer exist is worse than none. If the site's origin changes, the file has to change with it — a static file cannot read the site's configuration on its own.
The page still has to be good
No file compensates for content that does not resolve an entity, state a scope or carry a date.
What to verify
Publish a curated map of the pages that best represent the site
Do not expect it to influence ranking on its own
Regenerate it whenever the site origin or URLs change
Fix the underlying pages first
Continue the research
Related dealership technology questions
What software do car dealerships use?
Most dealerships use a DMS as the operating and financial backbone, plus a CRM, website/CMS, inventory tools, digital retailing, communications, marketing, analytics, F&I and fixed-operations systems. The right combination depends on franchise obligations, market, store count and operating model.
Vendor shortlist sizeHow many dealership software vendors should be evaluated?
A dealership should discover the broad market, apply objective eligibility gates, and conduct deep evaluations with the smallest set that still preserves a real choice—often two to four finalists. The correct number depends on the category and how many providers meet non-negotiable requirements.
Dealership website provider selectionHow should a dealership choose a website provider?
Evaluate a dealership website provider on inventory accuracy, speed, accessibility, SEO controls, conversion workflows, analytics, OEM eligibility, integrations, content portability, support and migration—not appearance alone.
Website migrationWhat belongs in a dealership website migration checklist?
A dealership website migration should inventory existing URLs, content, metadata, media, structured data, feeds, forms, tracking and integrations; map redirects; validate the new experience; and monitor search, leads and revenue workflows after launch.