llms.txt
Who you are, what you sell and how to book, in plain text with no markup. It is the file a model can read whole without spending tokens parsing HTML.
Agentic property
So a machine can understand you and book you.
More and more people ask a model before searching. That model does not see your photo carousel: it sees text, structured data and routes. bookfer's engine publishes all three, and the GEO editor lets you declare what you are in your own words.
/llms.txt/availability.json/engine-capabilities.json
# Cabañas del Alerce > Six mountain cabins in Villa La Angostura, Neuquén. ## Units - Alerce · 4 pax · 1 bedroom · from USD 78 - Coihue · 6 pax · 2 bedrooms · from USD 112 ## Booking Machine-readable availability: /availability.json What the engine accepts: /engine-capabilities.json Checkout: /book?in=&out=&pax= ## Policies Check-in 15:00 · check-out 10:00 · 2-night minimum on weekends
The shift
The question no longer starts in a search box.
It used to be “cabins in Villa La Angostura” and the answer was ten blue links. Now it is “where do I stay four nights with two kids and a dog, less than thirty minutes from the centre?” and the answer is a paragraph with two or three names. Being in that paragraph depends on there being something of yours that can be read.
What classic SEO optimisesWhat the agentic layer adds
Title and description for the resultEntity description, in plain text
Cover image for the clickReal machine-readable availability
Keywords on the pageUse cases, audiences and geographic scope
Inbound linksDeclared, verifiable trust signals
A contact formA booking route an agent can follow
The four surfaces
What your engine publishes.
It turns on with a switch in the engine settings. From then on, your property has a public face for machines as well as the one it already had for people.
availability.json
Your real availability, in a format a machine can query. It is not a form to fill in: it is the data.
engine-capabilities.json
Which operations your engine accepts and with what parameters. It is the difference between an agent knowing you exist and knowing how to book you.
JSON-LD on the pages
Structured data on the published site, which is what classic search engines already read and what models read too when they visit the page.
GEO editor
You declare what you are in your own words, not a robot's.
The editor goes well beyond classic SEO. It is a record meant so a model can describe you accurately even if nobody visits your site.
- Entity type: hotel, resort, B&B, vacation rental, apartment, hostel, motel, campsite or generic lodging.
- Categories, use cases and problem domains: what your property is for, said the way people search for it.
- Audiences and geographic scope: who you serve and how far.
- Trust signals: years active, number of clients, certifications and featured clients.
- AI indexing control and priority: the layer turns off if you do not want it.
- Per page: intent (informational, commercial, transactional, comparative or support), topic, semantic context and related entities.
/llms.txt/availability.json/engine-capabilities.json
# Cabañas del Alerce > Six mountain cabins in Villa La Angostura, Neuquén. ## Units - Alerce · 4 pax · 1 bedroom · from USD 78 - Coihue · 6 pax · 2 bedrooms · from USD 112 ## Booking Machine-readable availability: /availability.json What the engine accepts: /engine-capabilities.json Checkout: /book?in=&out=&pax= ## Policies Check-in 15:00 · check-out 10:00 · 2-night minimum on weekends
Why it works here
Because the data is not copied.
The reason an availability file can be published without fear is the same reason the engine's calendar shows real remaining units: it is the same inventory the hotel's calendar uses. There is no nightly export that can drift.
- A room is loaded once and appears in the engine, on the site, in the availability JSON and in the RMS.
- A maintenance block takes real inventory out and disappears from every surface at once.
- The brand description you loaded feeds the site, LinkHub, the OTA listings and the llms.txt.
mo
tu
we
th
fr
sa
su
8$78k
9$78k
10$78k
11$78k
12$84k3 left
13$96k
14$96k
15$96k
16$96k
17$88k
18$78k
19$78k
20$84k2 left
21$112k
22$112k
23$98k
24$84k
25$78k
26$78k
27$78k1 left
28$78k
Minimum 2 nights to check in on the 14th
Practising what we preach
This site has its own llms.txt too.
It would be odd to ask that your property be readable by a machine and for the page asking it not to be.
See /llms.txtFrequently asked questions
Does this guarantee I show up when someone asks ChatGPT?
No, and anyone who tells you otherwise is lying. Nobody controls what a model recommends, just as nobody controls Google's ranking. What does depend on you is that, when an agent goes to look, it finds something it can understand — text describing what you are, availability that can be read and a clear route to book. A property whose only public data is a photo carousel on Instagram has nothing a model can cite.
What is GEO and how is it different from SEO?
Classic SEO optimises for a person to click a result: title, description, cover image. GEO — Generative Engine Optimization — optimises for a model to describe you accurately without anyone visiting your site: what type of entity you are, for which audiences, in which area, with what trust signals. They are complementary; the system's editor has both.
Can I decide that AI should not index me?
Yes. The engine's agentic layer turns on or off in the settings, and the GEO editor has AI indexing control and priority. It is your decision, not a default we impose.
Turn it on with a switch.
The agentic layer is one more section of the engine settings. If your inventory is already loaded, publishing the routes takes no time at all.
01You load inventory and brand identity.
02You turn the agentic layer on in the engine.
03You fill the GEO editor in your own words.