When should vegan hotels ship a festive FAQPage so Gemini cites December stays?
Quick answer
Ship a crawlable festive FAQ on the stay or package URL once December nights are a named SKU the kitchen can staff. Use question headings, self-contained answers, and matching FAQPage JSON-LD. Gemini leans Google Search, so GBP hours plus this HTML matter more than a PDF in the inbox. Do not brief a FAQ rich-result win or a citation percentage. Kill eco festive stay in the answers. Year-round Place ID lives in vegan hotel AI citations. Package SKUs live in peak-date hotel packages. FAQ HTML patterns live in FAQ pages for AI citations.
Vs other Intelligence guides
| Guide | Job |
|---|---|
| FAQ pages for AI citations | Generic question HTML + FAQPage. This page is December stay questions on a hotel URL. |
| Vegan hotel AI citations | Place ID, NAP, LodgingBusiness, honest veganMeals, year-round city log. Not a festive FAQ. |
| Peak-date hotel packages | Named stay SKU vs OTA dump. Put those facts in the FAQ. Do not recook the SKU as schema. |
| Hotel party hire | Function-room F&B SKU. Not a stay FAQ. |
| Breakfast vegan scope | Mixed buffet vs vegan breakfast. FAQ answers must copy that fence. |
| Festive Event page AEO | Restaurant Event URL. Hotels answer stays, not diner set menus. |
| EmpCo hospitality copy | Full guest-copy crawl. This page is festive FAQ only. |
| This guide | When vegan hotels should ship a festive FAQPage so Gemini cites December stays |
Composite operator guidance. Not legal advice on EmpCo, deposits, or Google rich results. Google does not guarantee FAQ features. Do not treat a worksheet prompt count as a typical citation lift.
Four kits. The festive FAQ is only one.
| Kit | Object | This week |
|---|---|---|
| Place ID + veganMeals | The property, year-round | Hotel AI citations. Do not paste Christmas into LodgingBusiness hours and call it a FAQ. |
| Peak stay SKU | Nights, kitchen inclusion, OTA fence | Holiday packages. The FAQ copies those facts. |
| Party hire | Function room plus F&B | Party hire. Keep it off the stay FAQ. |
| Festive FAQPage | Guest questions on the stay or package URL | This fence. |
Staff line: "December stays are a named package plus a FAQ Gemini can quote. Hire is a different SKU. Place ID is the hotel." If you cannot name the nights that fire, do not ship festive answers.
Proof ladder (festive FAQ)
| What is true this week | You may publish | You freeze |
|---|---|---|
| Named December stay SKU. Kitchen can staff breakfast or dinner as printed. Hours signed. Direct book path live. | Question headings on that URL, answers that copy the SKU, matching FAQPage JSON-LD. | Eco festive stay. Climate-friendly Christmas hotel. Invented last rooms. A FAQ snippet win in the owner brief. |
| You only have year-round stay copy. No peak SKU. | Nothing as a festive FAQ. Keep Place ID honest. | Invented Christmas dinner Q&A so Gemini has "something to cite". |
| Breakfast is mixed | Named vegan stations, not vegan Christmas breakfast. Buffet scope. | "Vegan breakfast over Christmas" while dairy is on the buffet. |
| Invitation-only buyout | Honest HTML for guests who have the URL. Do not brief a public Gemini listing of a closed house. | FAQ that says book now to the general public. |
FAQ HTML + FAQPage field kit
Visible question headings. Answer in the DOM, not a click-only fetch. Each FAQPage Question.name matches the heading. Google restricted FAQ rich results. Ship schema so Gemini and ChatGPT can parse. Do not brief a snippet carousel.
| Guest question to put as a heading | Answer with | Do not |
|---|---|---|
| Is [name] a vegan hotel over Christmas? | Kitchen scope that matches veganMeals and the stay page | Fully vegan hotel on a mixed kitchen |
| Do you serve vegan Christmas dinner / NYE dinner? | Named sitting that fires, or no | A moodboard roast. Eco feast |
| Is breakfast vegan on Christmas Day? | Buffet fence. Named stations if mixed | Vegan breakfast as a synonym for one pastry |
| Are you open 24 to 26 December / 31 December? | GBP special hours and house rules | Open if the listing says closed |
| How do I book the December stay? | Direct package URL. Same BAR fence as the SKU kit | A cheaper secret web rate. Last rooms with empty PMS |
Keep party-hire questions on the hire URL. Keep year-round "vegan hotel in [city]" in the Place ID kit. Accordion is fine if the full answer is in the HTML.
Print vs banned
| Surface | Allow | Kill |
|---|---|---|
| Stay / package FAQ | Named nights, kitchen fact, hours, book path, allergen path | Eco festive stay. Climate Christmas hotel. "Gemini recommends us". Invented occupancy |
| FAQPage JSON-LD | Exact visible Q&A | Extra climate answers that are not on the page |
| GBP | Special hours. Link the package URL | Treating a Post as the FAQ. Dining GBP analog is hours/Posts, not this hotel FAQ |
| OTA blurb | Same kitchen scope as the FAQ | A greener Christmas line than the stay page. Hospitality copy |
EmpCo from 27 September 2026 still applies to FAQ answers. Score leftover adjectives in the green claims calculator. Do not publish a citation rate.
10-prompt festive stay log (run this week)
Private window. Paste into Gemini first, then ChatGPT and Google. Log named Y/N, source cited (your FAQ URL vs OTA vs blog), kitchen fact, dates, book URL.
| # | Prompt | Pass |
|---|---|---|
| 1 | Vegan hotel Christmas [city] | Right city. Kitchen label matches. |
| 2 | Vegan NYE hotel [city] | Stay URL, not the party-hire PDF. |
| 3 | Is [name] a vegan hotel? | Matches veganMeals and the FAQ. |
| 4 | Does [name] serve vegan Christmas dinner? | Only if that sitting fires. |
| 5 | [name] vegan breakfast Christmas Day | Buffet fence, not a dairy breakfast called vegan. |
| 6 | Is [name] open over Christmas? | Hours match GBP. |
| 7 | Book [name] Christmas stay | Direct package path. |
| 8 | [name] festive package | Named SKU. No eco festive paraphrase. |
| 9 | Vegan hotel near [landmark] in December | Place matches. |
| 10 | [name] vs [nearest vegan hotel] Christmas | No invented dinner or wrong hours. |
Fix the source that week. They cite the OTA: patch the OTA. They invent eco festive stay: your FAQ still has the adjective. They cite party hire: split the URLs. Do not invent a citation percentage.
FAQ freeze (labeled example)
Replace every cell from PMS, the package LP, and live HTML. Do not copy the example as a city citation benchmark.
| Field | Worked example | Your cell |
|---|---|---|
| Crawlable festive FAQ URL | 1 festive FAQ URL example | [faq_url] |
| Guest questions live on that URL | 8 guest questions example | [questions] |
| Eco festive / climate-stay / sustainable Christmas answers | 3 leftover climate-stay answers example. Kill them. | [climate_lines] |
| Named December stay SKU that fires | Named dinner stay example, or NONE | [package_sku] |
Those cells are worksheet labels, not a citation quota. If [package_sku] is NONE, festive FAQ is blank.
Go / no-go
| Call | When |
|---|---|
| No-go | Eco festive stay in answers, vegan breakfast on a mixed buffet, no nights that fire, FAQPage that disagrees with HTML, invented citation %, FAQ snippet promised to the owner, hire mashed into the stay FAQ |
| Go on a September FAQ | Named SKU, crawlable HTML, FAQPage matches visible Q&A, climate lines stripped, GBP hours match, 10-prompt log run once on Gemini |
| Partial go | HTML hours and kitchen facts live. Schema waits until Q&A is frozen. Strip climate lines today. |
Score leftover climate-stay answers, PDF-only FAQs, and named-in-answer vs fact errors. Search Console FAQ impressions are not a Gemini win.
Gemini quotes the stay FAQ, not the hire PDF
Name the nights. Put guest questions on HTML. Match FAQPage to the page. Leave eco festive stay out. Do not brief a snippet.
Template fields and 7-day run
| Field | Fill with | Do not invent |
|---|---|---|
[package_sku] | Named December stay that fires, or NONE | A moodboard gala |
[nights] | Dates the PMS will hold | Every night in December |
[kitchen_fact] | veganMeals truth plus buffet fence | Fully vegan hotel on mixed stations |
[faq_url] | Stay or package HTML, or NONE | A PDF in the sales inbox |
[book_url] | Direct engine URL | A secret cheaper web rate |
[markets] | US / EU / UK / both | One eco festive FAQ for every domain |
Brief: "SKU: [package_sku]. Nights: [nights]. Kitchen: [kitchen_fact]. FAQ URL: [faq_url]. Book: [book_url]. Markets: [markets]. If SKU or FAQ URL is NONE, festive FAQPage is blank. Kill eco festive stay. Do not brief a snippet or a citation %."
- Day 1: Export Christmas, NYE, eco festive, and climate-stay lines on stay pages, OTAs, GBP, and hire PDFs.
- Day 2: Confirm [package_sku] is staffed. Fill [nights] from PMS. If NONE, do not invent a gala FAQ.
- Day 3: Freeze banned answers. Breakfast fence: buffet scope. File in the substantiation folder.
- Day 4: Publish [faq_url] with question headings. Add FAQPage that copies the HTML. Structure: FAQ pages.
- Day 5: Match GBP special hours. Place ID still follows hotel AI citations. Hire stays on its URL: party hire.
- Day 6: OTA blurb copies kitchen scope, not a greener Christmas. Package fence: holiday packages.
- Day 7: Run the 10-prompt log in Gemini. Score leftover climate-stay answers in the green claims calculator. Readiness: AEO readiness.
Frequently asked questions
When should vegan hotels ship a festive FAQPage so Gemini cites December stays?
Ship a crawlable festive FAQ on the stay or package URL once December nights are a named SKU the kitchen can staff. Use question headings, self-contained answers, and matching FAQPage JSON-LD. Run a 10-prompt log in Gemini. Do not brief a FAQ rich-result win or a citation percentage. Kill eco festive stay in the answers.
Is this the same as generic FAQ pages or hotel AI citations?
No. Generic FAQ pages are the HTML pattern. Hotel AI citations are Place ID, NAP, and veganMeals for vegan hotel in [city]. This page is December stay questions on a hotel URL so Gemini can cite hours, breakfast scope, and the package.
Does FAQPage put us in Google FAQ rich results or in Gemini?
Neither is a contract. Google restricted FAQ rich results. Gemini synthesizes Search, GBP, OTAs, and your HTML. Ship markup so machines can parse. Log named-in-answer. Do not invent a citation lift.
Can we put party hire and the stay package on one festive FAQ?
No. Hire is a function-room SKU. Stays are rooms. Two URLs so Gemini does not mash a gala into a Christmas night room.
What do we measure if not citation %?
HTML FAQ URLs, leftover climate-stay answers, whether hours match GBP, and named-in-answer vs fact errors on the 10-prompt log. Search Console FAQ impressions are not a Gemini win.