Hotels

Does ChatGPT know your hotel?

More and more guests ask an assistant instead of searching. The assistant answers with whatever it managed to read, and most hotel websites only exist after JavaScript runs. This page explains how to check that for free, what to fix and in what order.

Book a call Tell us about your project

At night in a hotel lobby, a guest with a suitcase checks his phone at a marble desk while a receptionist works on a laptop, city lights behind the glass

Guide

What you need to know.

For example: 22 public routes prerendered as static HTML. Hotel Marien

Book a call Tell us about your project

The short answer

Ask an assistant for a hotel in your town and it answers with whatever it managed to read. If your website only exists after JavaScript runs, it read nothing, and it recommends the hotel next door.

What a visitor reads, and what an AI crawler receives

Characters of body text from one real news page, before and after. An assistant recommends what it could read, so the second number is the one that decides whether you are in the answer.

You can check that yourself, for free, at polargate.ai/tools/ai-search-radar. The scan fetches your site the way the assistants do and hands you a report you can forward to whoever built it.

What an assistant actually reads

GPTBot, OAI-SearchBot and ChatGPT-User request the raw HTML and never execute JavaScript. Vercel and MERJ confirmed that across more than 500 million GPTBot fetches. ClaudeBot and PerplexityBot behave the same way.

Most modern hotel sites are single page applications. The server sends an almost empty shell, and the browser builds the rooms, the restaurant, the spa hours and the address afterwards. A guest sees a finished page. A crawler sees the shell.

It is the pattern we keep finding when we audit a site: healthy on the inside, blind from the outside. On one corporate site we audited, crawlers were served an empty body, and the robots file excluded the AI crawlers on top of that.

Check it for free

Our AI Search Radar requests your pages with the real user agents of GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot and Googlebot, with JavaScript switched off. That is exactly the view those crawlers get.

You get a shareable report at polargate.ai/scan/yourdomain: which crawlers were allowed in, and how much real text each of them actually received. Googlebot is in the list on purpose, because comparing it with the rest shows how much of your site depends on JavaScript to exist at all.

Nothing to install, nothing to pay, no signup. If the report is boring, you are fine and you can stop reading here.

What to fix, and in what order

1. Let them in

Start with the robots file. A blanket rule that blocks GPTBot or ClaudeBot makes everything below it pointless. Blocking the answer engines does not protect your rates or your photography, it takes you out of the answer. When we harden a site, those crawlers stay allowed on purpose.

2. Put the content in the served HTML

This is the step that changes the answer, and there are two ways to do it. Pre render every route to static HTML at build time, which is how we build new sites. Or, when a rebuild is not on the table, inject the content at the edge for crawlers only: title, description, canonical, hreflang, Open Graph, JSON-LD and a real body with headings and paragraphs. Guests keep receiving the application untouched, and neither the build nor the app changes.

3. Give every page and every language its own head data

One title, one description, one canonical, hreflang between language versions, and structured data that says what the property is, where it is and how to book it. An assistant that cannot tell your English page from your Dutch one will quote neither with confidence.

4. Answer first, one question per page

Rooms, restaurant, parking, pets, check in times, distance from the airport. Each of those is a question a guest asks out loud, and each deserves a page that answers it in the first sentence. Our own build fails if a page renders without an H1 or with fewer than 120 words.

What changed on a site we worked on

On Globalia's public site, measured in 2026: a news article now gives an AI crawler 11,421 characters of readable text. The home page gives 756, and interior pages between 200 and 260, across six routes and their language versions. An archive of around 700 articles is readable. No redesign, no migration, and no change to what a person sees.

What a monitoring dashboard cannot do

There are products that track how often a brand gets mentioned by assistants and draw it on a chart. That is useful once the basics work. It is also the part that fixes nothing: a dashboard cannot edit your robots file, pre render your routes, write the edge middleware or write the page that answers the question.

We do the fix. The scan is free and the report is yours whether you hire us or not.

Where to start

Run the scan on your own domain, read the report, and send it to whoever maintains your site. If the answer that comes back is that this needs engineering, that is the conversation to have with us.

FAQ

What people ask us.

Does ChatGPT read the JavaScript on my hotel website?

No. GPTBot, OAI-SearchBot and ChatGPT-User fetch the raw HTML and never execute JavaScript, which Vercel and MERJ confirmed across more than 500 million GPTBot fetches, and ClaudeBot and PerplexityBot work the same way. So if your rooms, your restaurant menu or your address only appear once the browser has built the page, they are not there for the assistant. The test is simple: whatever is missing from the HTML your server sends is missing from the answer.

How can I check for free whether AI assistants can read my hotel?

Run our AI Search Radar at polargate.ai/tools/ai-search-radar. It requests your pages with the real user agents of GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot and Googlebot, with JavaScript switched off, so you see the same thing they see. You get a shareable report at polargate.ai/scan/yourdomain showing which crawlers were allowed in and how much real text each one received, and you can forward that link to whoever maintains your site. It costs nothing, there is nothing to install and it needs no signup.

Do I have to rebuild my website to be readable by assistants?

Not necessarily. There are two routes: pre render every page to static HTML at build time, which is how we build new sites, or leave the site as it is and inject title, description, canonical, hreflang, Open Graph, JSON-LD and a real body at the edge for crawlers only. We did exactly that on a corporate site: crawlers started receiving real content, guests kept getting the application untouched, and neither the build nor the app changed. A full rebuild is the right call when the site has other problems that justify it, not just this one.

Should I block AI crawlers to protect my content and my rates?

Understand what you are choosing. The crawlers you would block, GPTBot, OAI-SearchBot, ClaudeBot and PerplexityBot, are the same ones that answer a guest asking for a hotel in your town, so blocking them removes you from the answer rather than protecting the price. We see it often: sites whose robots file excludes the AI crawlers while the owner wonders why the assistant never mentions the property. When we harden a site for security, we keep those crawlers allowed on purpose.

Is a monitoring dashboard for AI mentions enough?

A dashboard measures, it does not fix. Tracking how often assistants mention your hotel is useful once the basics work, but it cannot edit your robots file, pre render your routes, write the edge middleware or write the page that answers the guest's question. Our scan is free precisely because the value is not in the report, it is in the work that follows it, and that work is engineering on your site. If the report says the crawlers are getting an empty page, the next step is a fix, not a chart.

For example: 16 indexable URLs, Spanish and English. Hotel Talavera

Book a call Tell us about your project

Does ChatGPT know your hotel?

What you need to know.

The short answer

What an assistant actually reads

Check it for free

What to fix, and in what order

1. Let them in

2. Put the content in the served HTML

3. Give every page and every language its own head data

4. Answer first, one question per page

What changed on a site we worked on

What a monitoring dashboard cannot do

Where to start

What people ask us.

Tell us what you want to build.