FREE TOOL
FAQ Schema Generator
Paste your Q&A pairs. Get ready-to-paste FAQPage JSON-LD in 60 seconds. The single highest-leverage move for getting cited by AI Overviews, ChatGPT, and Perplexity.
Your Q&A pairs
3 questionsAdd the actual questions travelers ask. Don't fluff. Google ignores FAQs that are obviously SEO-stuffed.
95 chars · 16 words
134 chars · 22 words
154 chars · 29 words
Generated JSON-LD
Paste inside the <head> of your tour page (or anywhere in the body — both are valid).
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How long is the tour?",
"acceptedAnswer": {
"@type": "Answer",
"text": "The tour is approximately 3 hours including a 15-minute break for refreshments at a local cafe."
}
},
{
"@type": "Question",
"name": "What should I bring?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Comfortable walking shoes, a water bottle, and a camera. We recommend dressing in layers as the weather can change throughout the day."
}
},
{
"@type": "Question",
"name": "Is the tour family friendly?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes — we welcome children aged 6 and up. Children under 12 receive a 25% discount with a paying adult. Strollers can be accommodated on most of the route."
}
}
]
}
</script>After pasting, validate it:
- Google Rich Results Test — confirms FAQ rich-snippet eligibility
- Schema.org validator — checks JSON-LD syntax
Why FAQ schema matters
FAQ schema is the single highest-leverage move for getting cited by AI Overviews, ChatGPT, and Perplexity. AI engines specifically look for question-and-answer structure when picking sources to quote. Pages with proper FAQPage schema get cited 3–4× more often than pages without it.
Best-practice checklist
- Use real questions from customer emails, OTA reviews, or Google “People also ask”
- Keep answers 50–300 words, with definite numbers where possible
- Add 5–8 questions per page — too few looks lazy, too many dilutes signal
- Make the FAQ visible to users, not just in JSON-LD (Google penalizes hidden-only schema)
- Refresh quarterly — questions and answers shift over time
Why FAQ schema is the easiest big win
Most tour operator pages have zero structured data. The first 5 minutes of work — adding FAQPage schema — produces meaningful results in three places:
- Google rich snippets: FAQ questions can appear directly in search results, expanding your snippet vertically and lifting CTR 15-25%.
- AI Overview citations: ChatGPT, Perplexity, and Google AI Mode look for question-answer structure when picking sources. FAQ-schema pages get cited 3-4x more.
- Voice search visibility: Voice assistants extract direct answers from FAQ schema for spoken results.
Total time investment per page: about 30 minutes (writing the FAQ + generating schema + validating). The compounding visibility return makes it the highest-ROI single SEO move available.
Related tools & deep-dives
TouristTrip Schema Generator
For tour pages, pair FAQ schema with TouristTrip + AggregateRating + Offer.
Schema Markup Guide
Full schema strategy for tour operators including TouristTrip, FAQ, AggregateRating, and Organization.
GEO Strategy: Get Cited by AI
Why FAQ schema is the most extractable format for AI search citations.
FAQ
What is FAQ schema and why does it matter?+
FAQPage schema is structured data that tells search engines and AI engines: "this page contains a list of questions with answers." Google uses it to display FAQ rich snippets directly in search results (which lift CTR 15-25%), and AI engines like ChatGPT and Perplexity specifically scan for FAQPage structure when picking sources to cite. Pages with proper FAQ schema get cited 3-4x more often by AI search.
How many FAQs should I add to a page?+
5-8 questions is the sweet spot. Fewer than 3 looks lazy and Google rarely shows the rich snippet. More than 10 dilutes the signal — Google may decide your FAQ is generic SEO stuffing rather than genuinely useful. Use real questions you actually receive from customers, not fabricated SEO bait.
Where do I get the right questions?+
Three best sources: (1) your customer support inbox — pull the most-asked questions from emails and DMs, (2) your OTA reviews on Viator and TripAdvisor — guests describe what surprised them or what they wish they had known, (3) Google's "People also ask" panel for your tour's search results — these are verified queries from actual searchers.
Should the FAQ be visible on the page?+
Yes — Google explicitly requires FAQ content to be user-visible (not just in JSON-LD). Hidden-only FAQs violate the structured data guidelines and can result in manual actions. Display the FAQ as a real section with the same questions and answers you put in the schema.
How long should each answer be?+
50-300 words is the practical range. Under 50 words is too thin for AI Overview extraction. Over 300 words means the answer probably contains multiple sub-topics that should be separate questions. Aim for 80-150 words with at least one definite number, fact, or specific detail per answer — that's what AI engines extract verbatim.
Can I use FAQ schema on every page?+
Yes, but each page needs unique, page-relevant questions. Don't copy-paste the same FAQ across 50 tour pages — Google will detect duplication and the schema becomes worthless. Use page-specific questions: tour-specific FAQs on tour pages, location-specific FAQs on destination pages, pricing-specific FAQs on pricing pages.
Want this rolled out across every page on your site?
Generating schema for one page is easy. Doing it consistently across 30–100 tour pages, validating each, and refreshing quarterly is operational work. We do this end-to-end as part of our SEO retainer.
See SEO Service →