Hotelrank ResearchResearch / llms.txt StudyMarch 2026

Hotel llms.txt Adoption Study

We scanned 105,002 hotel websites for llms.txt files. Only 6.3% have one β€” and 7.3% of those misuse it as a robots.txt clone.

105K
Hotels Scanned
6.3%
Adoption Rate
12.4%
US Lead
0.3%
llms-full.txt

TL;DR

We fetched /llms.txt and /llms-full.txt from 105,002 hotel websites across 7 countries. Only 6.3% have a llms.txt file (6,590 hotels) and just 0.3% serve a llms-full.txt (265 hotels). The US leads adoption at 12.4%, while France trails at 3.8%. WordPress SEO plugins (AIOSEO, Yoast, Rank Math) drive 33.4% of all files, but 7.3% of llms.txt files misuse the format as robots.txt-style access control rules. Hotels with llms.txt score 62% higher on schema.org quality β€” suggesting it's a marker of technical SEO maturity.

Executive Summary

The llms.txt file is an emerging standard for websites to communicate their content structure to AI models. Unlike robots.txt (which tells bots what not to crawl), llms.txt tells AI models what a site is about β€” a curated index of pages with descriptions that helps LLMs understand and accurately represent a property.

Our analysis of 105,002 hotel websites reveals extremely early adoption. At 6.3%, llms.txt is where robots.txt was in the early 2000s β€” a technical signal adopted by forward-thinking properties and platforms, but unknown to the vast majority. The companion file llms-full.txt (designed for detailed content) is even rarer at 0.3%, and every hotel with llms-full.txt also has llms.txt β€” the two-file approach has not gained traction.

Most adoption is plugin-driven, not strategic. WordPress SEO plugins (AIOSEO, Yoast, Rank Math) account for 33.4% of all llms.txt files, often auto-generated with little curation. The best files β€” like rich hotel descriptions with room types, amenities, and policies β€” represent just 2.9% of the total. Meanwhile, 7.3% of files are outright misconfigurations: robots.txt-style access control rules served as llms.txt, providing zero value to AI models.

93.7%
No llms.txt file
42.9%
Follow intended format
7.3%
Misuse as access control
The key finding: llms.txt adoption is a proxy for technical SEO maturity, not an isolated decision. Hotels with llms.txt have 62% higher schema.org scores (22.4 vs 13.8) and 49% higher JSON-LD adoption (80.6% vs 54.2%). Both stem from the same investment in search optimization β€” whether driven by a web agency, CMS platform, or technically aware hotelier.

Adoption Overview

How does llms.txt adoption compare to robots.txt? (n=105,002 hotels)

6.3%
Have llms.txt
6,590 hotels
0.3%
Have llms-full.txt
265 hotels
82.2%
Have robots.txt
For comparison
0
Only llms-full.txt
Always paired with llms.txt

llms.txt vs robots.txt adoption rates

llms.txt adoption overview

MetricCount% of Reachable
Has llms.txt6,5906.3%
Has llms-full.txt2650.3%
Has either6,5906.3%
Has both2650.3%
llms-full.txt adoption is negligible. Every hotel with llms-full.txt also has llms.txt β€” there are zero hotels with only the full variant. This suggests the standard's two-file approach hasn't gained traction; hotels treat llms.txt as a single deliverable.

Who Generates These Files?

WordPress SEO plugins drive 33.4% of hotel llms.txt files. The majority (57.4%) are custom.

57.4%
Custom / Unknown
3,784 files
33.4%
WordPress Plugins
AIOSEO + Yoast + Rank Math
4.2%
Backhotelite
Spain-specific platform
2.1%
ComboCMS
Italy-specific platform

Generator breakdown of hotel llms.txt files

Generator breakdown

GeneratorCount% of llms.txt Files
Custom3,78457.4%
AIOSEO1,19718.2%
Yoast SEO67510.2%
Backhotelite2804.2%
Rank Math2383.6%
robots-style1792.7%
WordPress SEO plugins are the primary driver of identifiable adoption. AIOSEO (19.6% combined free + pro), Yoast SEO (10.2%), and Rank Math (3.6%) together account for 33.4% of all llms.txt files. These plugins added llms.txt generation as a feature in late 2025/early 2026, making adoption as simple as toggling a setting. But auto-generated files need curation β€” many are generic site indexes, not curated hotel descriptions.

Industry-specific platforms

Spain

Backhotelite (4.2%) β€” A hotel-specific CMS platform primarily used by Spanish properties. Accounts for 18.1% of Spanish llms.txt files.

Italy

ComboCMS (2.1%) β€” An Italian hotel CMS that auto-generates llms.txt. Accounts for 10.5% of Italian llms.txt files.

Misuse

robots-style (2.7%) β€” 179 files contain User-agent/Allow/Disallow directives instead of the intended llms.txt format. These provide zero value to LLMs.

What's Inside These Files?

Only 42.9% follow the intended spec. 7.3% misunderstand the format entirely.

Content type distribution of hotel llms.txt files

Content type breakdown

Content TypeCount%Description
Site Index2,82642.9%Page listings with URLs and descriptions
Other2,01330.5%Mixed or unstructured content
Sitemap Only93314.2%Just a sitemap reference, no page details
Access Control4847.3%User-agent allow/disallow rules (misuse)
Hotel Description1942.9%Detailed property info, amenities, policies
Summary911.4%Brief business summary with contact info
7.3% of llms.txt files are robots.txt clones. 484 hotels serve User-agent/Allow/Disallow rules as their llms.txt β€” a fundamental misunderstanding of the standard. These are primarily generated by Backhotelite, a Spanish hotel platform. While well-intentioned (explicitly allowing AI crawlers), this format doesn't help LLMs understand the site's content. The llms.txt spec is about describing your content, not controlling access to it.

The 2.9% doing it right: rich hotel descriptions

194 hotels serve llms.txt files with detailed property information β€” room types, cancellation policies, amenities, and contact details. These are exactly what an AI concierge needs to recommend a property.

The sweet spot for content is 11-50 pages listed (39.1% of files), covering a typical hotel site's key pages: rooms, amenities, location, dining, events, contact, and blog posts. The median file lists 15 pages.

Adoption by Country

The US leads at 12.4%. France trails at 3.8% β€” consistent with its resistance to AI integration.

llms.txt adoption rate by country

Full country-level adoption data

CountryReachable HotelsHas llms.txt% Adoptionllms-full.txt %Top Generator
USA7,44592412.4%0.2%Custom
Spain16,4111,4188.6%0.3%Custom
Netherlands2,8912378.2%0.4%Custom
United Kingdom10,5477296.9%0.3%Custom
Germany22,2681,2565.6%0.2%Custom
Italy27,3191,3094.8%0.3%Custom
The US leads at 12.4% β€” 2x the adoption rate of France. American hotels are more likely to embrace AI visibility, and the US also has the highest "custom" rate (77.1%), suggesting tech-savvy hoteliers writing their own files rather than relying on CMS defaults.

The France Paradox: Blocks Most, Adopts Least

France has the highest AI blocking rate (7.5% in our robots.txt study) AND the lowest llms.txt adoption (3.8%) among major markets. This is a consistent signal: the French hospitality industry is the most resistant to AI integration.

7.5%
France AI blocking rate
Highest of 7 countries
3.8%
France llms.txt adoption
Lowest of 7 countries
3.3x
Block-to-adopt ratio
vs US at 0.2x

For comparison, the US has the opposite pattern: lowest blocking rate (2.1%) and highest llms.txt adoption (12.4%). The divergence suggests fundamentally different attitudes toward AI in the hospitality industry β€” with France leaning toward restriction and the US toward visibility.

Spain is surprisingly strong at 8.6% β€” driven partly by Backhotelite (18.1% of Spanish llms.txt files), a hotel CMS platform that auto-generates the file. Platform decisions matter: a single CMS provider shipping llms.txt support can meaningfully move a country's adoption rate.

Adoption by Star Classification

5-star hotels adopt at 2.5x the rate of 1-star properties.

llms.txt adoption rate by star classification

Adoption rates by star classification

StarsHotelsHas llms.txt% Adoptionllms-full.txt %Avg File Size
5-star2,06222510.9%0.3%11.0 KB
4-star16,5481,4598.8%0.2%17.9 KB
3-star30,1991,8126%0.3%19.6 KB
2-star10,2225395.3%0.3%10.9 KB
1-star2,6991184.4%0.3%12.9 KB
Unclassified43,2722,4375.6%0.3%10.9 KB
Clear correlation with hotel class. 5-star hotels adopt llms.txt at 10.9% β€” 2.5x the rate of 1-star hotels (4.4%). This parallels our schema.org findings where higher-rated properties invest more in technical SEO. Interesting size pattern: 3-star hotels have the largest average file size (20 KB), driven by WordPress sites with many blog posts and pages. 5-star hotels have smaller but more focused files (11 KB), suggesting curated content rather than full site dumps.

Schema.org Correlation

Hotels with llms.txt have 62% higher schema.org scores β€” it's a proxy for technical SEO maturity.

22.4
Schema Score (with)
6,590 hotels
13.8
Schema Score (without)
98,412 hotels
80.6%
JSON-LD (with)
vs 54.2% without
+62%
Score Difference
Strong correlation

Average schema.org score: with vs without llms.txt

With llms.txt

Hotels6,590
Avg Schema Score22.4
JSON-LD Adoption80.6%

Without llms.txt

Hotels98,412
Avg Schema Score13.8
JSON-LD Adoption54.2%
llms.txt adoption is a proxy for technical SEO maturity. Hotels that care enough to implement llms.txt also tend to have better structured data. It's not that llms.txt causes better schema β€” it's that both are symptoms of a hotel (or its web agency) that takes search optimization seriously. Use llms.txt presence as a quick diagnostic: if a hotel client doesn't have one, they likely have schema.org gaps too.

File Size Distribution

Median: 3.3 KB (~15 pages). The long tail reaches 1 MB.

3.3 KB
Median Size
Typical 10-20 page listing
15 KB
Average Size
Skewed by large files
1 MB
Maximum Size
Large resort site dumps
15
Median Pages
Avg 38.8 pages

llms.txt file size distribution

File size distribution

Size RangeCount% of Files
1-100 B1712.6%
101-500 B2824.3%
501 B-1 KB82012.4%
1-5 KB2,62039.8%
5-10 KB1,20818.3%
10-50 KB1,11016.8%

Pages listed per llms.txt file

Pages ListedCount% of Files
0 pages1,39821.2%
1-5 pages3765.7%
6-10 pages99415.1%
11-20 pages1,10016.7%
21-50 pages1,47322.4%
51-100 pages73711.2%
The median of 3.3 KB represents a typical 10-20 page listing with descriptions. The long tail above 100 KB (188 files) consists of large resort/chain sites that list hundreds or thousands of pages with full descriptions. 21.2% of llms.txt files list zero pages β€” these are the access-control and minimal files that don't serve the intended purpose.

Frequently Asked Questions

Methodology

Data Collection

  • Source: HotelRank global hotel index β€” 121,425 hotels from Google Maps
  • Reachable websites: 105,002 (84.8% of total)
  • Files checked: /llms.txt and /llms-full.txt per hotel
  • 7 countries: US (7.4K), ES (16.4K), NL (2.9K), UK (10.5K), DE (22.3K), IT (27.3K), FR (17.6K)
  • Files fetched during March 2026 crawl window

Content Analysis

  • Generator detection: Heuristic identification from file header comments (AIOSEO, Yoast, Rank Math, etc.)
  • Content classification: Rule-based categorization into site-index, access-control, hotel-description, summary, sitemap-only, minimal
  • Language detection: Keyword-frequency heuristics for English, German, Spanish, Italian, French
  • Structural analysis: Section header extraction, URL counting, page listing enumeration
105,002
Hotels Scanned
84.8% of index
6,590
Valid llms.txt Found
6.3% adoption
7
Countries Covered
US, ES, NL, UK, DE, IT, FR