Insights

Why XML sitemaps matter to your hotel website

An XML sitemap helps Google find your pages. It does not make them rank. What to put in one, what Google ignores, and whether you need an HTML sitemap.

SEO / GEO
Harry FielderCEO & Co-Founder
20 Oct 2026 · 5 min read

In 2018 we told hotels that an XML sitemap increases their chances of appearing on Google. That was generous to the sitemap.

An XML sitemap is a file that lists the pages on your website you want search engines to crawl, and when each one last changed. It helps Google find pages. It does not make any of them rank. A hotel site of forty well-linked pages would mostly be found without one, and Google says as much.

You should still have one, built automatically and kept honest, because a bad sitemap misleads Google about your own website. The HTML sitemap page some hotels still carry in the footer does very little for search if the menu does its job.

Our hotel SEO guide covers the rest of the technical foundations.

What a sitemap actually does

A search engine finds most pages by following links. The sitemap is a second route in, a list you hand over directly. Google's sitemap overview says listing a page does not guarantee it will be crawled or indexed, and that a site of about 500 pages or fewer, with good internal links, may not need one at all.

Most hotel websites fall comfortably inside that, so the sitemap is rarely what stands between a hotel and its rankings. Its job is to remove doubt, not to add visibility.

Where it earns its keep on a hotel site

The sitemap matters most at the moments a hotel website is least stable.

  • A relaunch. New URLs and old pages redirected. The sitemap tells Google what the new site contains while the links settle.
  • Offers and events. Seasonal packages and event pages are often linked only from a homepage panel. Listing them gets them found while they still matter.
  • Hotel groups. Ten properties with rooms, restaurants and event spaces can outgrow what internal links reliably cover.
  • Language versions. A sitemap can carry the hreflang annotations that tell Google which page is for which market, one of the points in our piece on translating a hotel website.
  • Photography. Image sitemaps are still supported, and hotel galleries often load images through scripts a crawler can miss.

In our Website & Development practice we treat the sitemap as something the website produces, not a file someone uploads. When we wrote this in 2018, we built hotel sitemaps with a WordPress plugin. On the sites we build now, the CMS generates the sitemap from the pages it publishes, so it cannot fall behind them.

What Google reads, and what it ignores

The sitemap protocol has more fields than Google uses, and its guidance on building a sitemap says which.

The date it trusts, conditionally

The lastmod field records when a page last changed. Google uses it only if it is consistently and verifiably accurate, and it should mark the last significant change to the content, not a new copyright year in the footer.

Plenty of hotel sites stamp every page with today's date on every build. Then the date tells Google nothing, and you lose the one signal that helps a changed offer page get recrawled sooner.

A sitemap does not tell Google what matters.
It tells Google what you claim exists, and Google checks.

The fields it ignores

Google ignores changefreq and priority. Setting the homepage to 1.0 and the rooms to 0.8 was standard advice for years. On Google it does nothing, so there is no point arguing about the numbers.

The old ping address for sitemaps has gone too. Google retired it in 2023. Submit the sitemap in Search Console, list it in robots.txt, and Google returns to it on its own schedule.

The mistakes we find on hotel sites

Most sitemap problems are the sitemap disagreeing with the website. Each is small, and each teaches Google to trust the list less.

Listing pages you do not want indexed

A sitemap should contain only canonical URLs that return a normal page. Pages marked noindex, URLs that redirect, expired offers that now return an error, and the staging site that someone left open all turn up regularly. Each asks Google to crawl something the website then disowns.

Listing pages that are not yours

The booking engine usually sits on the provider's domain or a subdomain they control. Its date-specific URLs do not belong in your sitemap, and nor do tracking parameters or filtered views that produce endless variations of one page.

Letting it go stale

A sitemap written by hand at launch is out of date by the first new offer. If yours was built once and never touched, assume it is wrong.

Do you need an HTML sitemap?

An HTML sitemap is an ordinary page listing every section of the site, for people rather than crawlers. Google's John Mueller said in 2016 that a site with good navigation probably does not need one for search engines, and that remains the sensible view.

For a hotel, the menu should already do this job. If guests need a list of everything to find the spa, the menu is the problem, and our guide to hotel website navigation is where to start.

There is one honest reason to keep one. Accessibility guidelines ask for more than one way to reach a page, and the W3C lists providing a site map as one way to meet that.

A search box or a clear footer can do the same, and our piece on hotel web accessibility covers what else the guidelines ask of a hotel site.

Checking your own

You can check a hotel sitemap in ten minutes without a developer.

  1. Find it. Open your robots.txt (your domain followed by /robots.txt) and look for a line starting Sitemap. If there is none, try /sitemap.xml.
  2. Open the Sitemaps report in Search Console. Check it says Success and that the discovered pages roughly match the size of the site.
  3. Filter the Page indexing report by that sitemap. The gap between submitted and indexed is where the problems are.
  4. Spot-check five URLs. Each should load a live page, on https, at the address listed, with no redirect.
  5. Compare two lastmod dates. Pick a page changed last month and one untouched for a year. If the dates match, the field means nothing.

If you are planning a relaunch, save the old sitemap before the new site goes live. It is the cleanest list you will ever have of the URLs that need a redirect.


A sitemap will never win a hotel a booking. A wrong one can quietly stop Google seeing the page that would have.

Questions hotels ask

Strictly, a small, well-linked hotel site can be found without one. It is still worth having, generated automatically by the CMS, because it helps Google find new offers, event pages and language versions quickly, especially after a relaunch.

No. Google says it ignores both. It reads the lastmod date, but only when the dates are consistently accurate, so set it from the date the page content actually changed.

Submit it in the Sitemaps report in Google Search Console and add a Sitemap line to your robots.txt file. Google retired its sitemap ping address in 2023, so there is no need to resubmit every time the site changes.

Not much, if the site's navigation is clear. It can help visitors on a large site and is one recognised way to meet the accessibility requirement for more than one route to a page, but it will not lift rankings on its own.

Free 30 Minute Consultation

Is your website telling Google the truth about itself?

Our Website & Development team checks your sitemap, redirects and indexing against what the site actually publishes, and fixes the gaps before they cost you visibility.

Keep reading

More in SEO / GEO