Skip to content
Lodging Enginefor Hotels
Structured Data 2 min read

Should hotels use FAQPage schema?

Short answer

For most hotels, FAQPage schema is now optional and low priority. Google stopped showing FAQ rich results in Search in 2026 and removed the documentation for the feature, so the markup no longer produces an enhanced result there. Valid FAQPage markup that matches visible questions and answers isn't harmful, and other systems may still read it, but it won't change how your hotel appears in Google. Put the effort into writing clear, visible answers to real guest questions instead — that's what helps guests, search engines, and answer engines.

By Lodging Engine Editorial Team· Reviewed by Eric Zwanenburg· Last reviewed

What changed

  • Before 2023, many sites used FAQPage markup to show expandable questions in search results.
  • From 2023, Google limited FAQ rich results to a small set of authoritative government and health sites.
  • In 2026, Google announced FAQ rich results are no longer shown in Search and removed the feature's documentation.

Should you remove existing markup?

Not necessarily. If it's valid and matches the visible questions and answers, it can stay. Remove it if:

  • It describes questions that aren't visible on the page.
  • It's duplicated across many pages with identical content.
  • It's out of date with your current policies.

Google's general structured data guidelines still apply: don't mark up content that isn't visible to readers.

Google states there's no special schema needed to appear in its AI features, including AI Overviews and AI Mode. What helps is the visible content itself: clear questions and direct answers that are crawlable and accurate. See does structured data help in AI search?.

What to do instead

  • Write FAQs from real guest questions, answered with specific facts.
  • Place answers on the relevant pages (parking on the location page, pets on the policies page).
  • Keep answers consistent with booking terms and listings.

See writing FAQs that answer engines can use.

Common mistakes

  • Adding FAQPage markup to every page with generic questions.
  • Marking up questions hidden in collapsed widgets that aren't rendered for crawlers.
  • Leaving outdated answers in markup after policies change.

Checklist

  • Existing FAQPage markup reviewed for accuracy and visibility
  • Outdated or duplicated FAQ markup removed
  • FAQs based on real guest questions
  • Answers placed on relevant pages in plain text

Sources

  1. Google Search Central documentation updates (FAQ rich result removed; llms.txt clarification) — Google Search Central
  2. AI features and your website — Google Search Central
  3. General structured data guidelines — Google Search Central

Related questions

How should hotels write FAQs that answer engines can use?Read answer How do I keep hotel structured data in sync with my website?Read answer Should I use JSON-LD or microdata for my hotel?Read answer How should a hotel group structure schema across multiple properties?Read answer