# How to Write an FAQ Page That AI Actually Cites ## The most quoted page on your website is the one most hotels write for the wrong reader. --- If you've been paying attention to how guests ask questions these days, you've noticed the shift. Nobody calls the front desk to ask about check-in time anymore. They type it into ChatGPT while they're standing in line for coffee. They ask Claude whether your hotel is actually dog-friendly, or whether the restaurant takes walk-ins, or how far the train station really is. The front desk is still there. The questions just stopped arriving. They're being answered — right now, every day, thousands of times — by a machine reading your website. And of all the pages on that website, the one the machine is most likely to quote is your FAQ. It's the only page written as questions and answers, which is exactly the shape an AI is looking for when it's trying to answer one. A well-written FAQ page is the cheapest piece of AI visibility infrastructure you own. Most hotel FAQs are not well written. They're written for Google — keyword-stuffed, vague, hedged, designed to rank for "pet friendly hotel hudson valley" rather than to answer "do you allow dogs?" And the machines that now answer your guests' questions don't rank pages. They read them. If your FAQ can't be read, it can't be cited. Let's talk about what the machines are actually doing. --- ### The machine reads like a thief When a guest asks an AI "what time is check-in at The Maker Hotel?", the model doesn't read your homepage, your booking engine, and your policies page in order. It retrieves the most likely pages, scans them for the block that answers the question, and lifts it. It wants a standalone answer — a self-contained chunk of text that says the thing, with the facts attached. That chunk has a name in the SEO world: a fraggle — a fragment of content that answers one question on its own. The name is silly. The idea is not. The AI will do one of three things with your answer: quote it, paraphrase it, or skip you and guess. Quote and paraphrase both require the same thing — the answer has to exist, as text, in a form that can be lifted. If your FAQ says "we offer flexible check-in times to accommodate our guests' needs," there is nothing to lift. The machine will skip you and guess. And its guess will be wrong, because it has no facts to work with. Here's the part most hotel operators miss: the AI doesn't need your permission, and it doesn't need your schema. It needs your sentences. --- ### The myth of the magic markup There's a whole industry of advice telling you the answer is structured data. Add FAQ schema. Add llms.txt. Rewrite your headings as questions. Some of it is useful — llms.txt is genuinely worth doing, and I've written about it elsewhere. But here's what the testing actually shows: when Grow & Convert ran the on-site tactics everyone sells — FAQ schema, llms.txt, question headings — through controlled tests, they found no measurable difference in AI visibility. None. The markup tells a crawler "this is a question and an answer." It does nothing to make the answer worth quoting. Schema is a signpost. It points at the page. It doesn't make the page good. The machines have read most of the written internet. They recognize which blocks of text actually answer a question. A page of thirty schema-tagged questions with two-sentence, keyword-stuffed answers gets read once and discarded. A page of twelve honest questions with real answers gets quoted for years. --- ### What actually gets cited Your FAQ is already a list. Every entry is a question, and every answer is a mini-comparison: "yes, and here's how it works" — or "no, and here's what we do instead." That matters, because the machines reward exactly that shape. SOCi's analysis of 129,000+ ChatGPT citations found that listicle and comparative content — "best rooms for couples," "our hotel vs the inn down the street" — accounts for more than a quarter of everything the model quotes. Not product pages. Not homepages. Lists and comparisons. Because a list is extractable. A comparison is an answer. The same analysis found that pages updated within the last 30 days receive 3.2x more citations than older content. Freshness is a signal. The machine, like the guest, trusts the version that was updated recently — because the guest's question is about right now, and the answer should be too. You just have to write your FAQ like the list it already is. --- ### The rules **1. Write the question the way a guest actually types it.** Not "Pet Policy Information." "Do you allow dogs?" Not "Check-In and Check-Out Procedures." "What time is check-in?" The machine matches your question against the guest's question. If they don't line up, the machine can't be sure your answer is the answer. The more conversational, the better — and there's a side benefit: the guest who lands on your page recognizes the question as theirs. **2. Lead with the answer. Put the facts in the first sentence.** The first sentence of your answer should be quotable on its own. Everything after it is context, flavor, and nuance — the stuff that makes the answer human. Bad: "At The Maker Hotel, we strive to provide a comfortable and flexible arrival experience, with our friendly front desk team available throughout the day to welcome you." Good: "Check-in is at 3pm. Arrive earlier and we'll hold your bags; arrive later and the front desk is staffed 24 hours." **3. One question per block. Keep answers between 40 and 60 words.** If you need more than sixty words, the question is probably two questions. If you need fewer than forty, you're being vague. The machine lifts whole blocks; a block that answers one question cleanly gets lifted whole. A block that answers three questions gets skipped. No "as mentioned above." No "see our policies page." The block has to work in isolation, because that's how it gets used. **4. Put numbers in everything.** Check-in is at 3pm, not "in the afternoon." The pet fee is $35 per night, not "a small fee." The train station is a seven-minute walk, not "close to transit." The machine can't quote a vibe. It can quote a number. And guests trust the number — it reads like you've actually thought about it, which you have, because you answer these questions eight times a day. **5. Write comparisons, not just answers.** The most cited format in AI search is the comparison. You can use that without turning your FAQ into a spreadsheet: "Our rooms vs the cottages," "The tasting menu vs à la carte," "Staying in the main house vs the carriage house." When a guest asks an AI "where should I stay," the machine is looking for the thing that differentiates you. Give it the differentiation in your own words. **6. Update the page monthly. Even if nothing changed.** The 3.2x citation boost for recent updates isn't a trick — it's a signal that the page is alive, and the machine prefers live sources. Set a reminder. First of the month, fifteen minutes: check rates, hours, policies, seasonal details. Update the date even if the facts didn't move. The alternative is being quoted on last year's menu. **7. Answer the question the way the front desk would.** Here's the test: if you wouldn't say it to a guest standing at your desk, don't write it in the FAQ. Would the front desk say "we offer flexible check-in times to accommodate our guests' needs"? No. They'd say "check-in's at three, but if you're early, drop your bags and grab a coffee — the bar opens at noon." Write the thing you'd actually say. The machine can't tell the difference between your FAQ and your front desk. It's quoting one of them. Make it the good one. --- ### Before and after Here's a real-world example. This is the shape most hotel FAQ answers take: **Before:** > Q: Is The Maker Hotel pet friendly? > A: We are pleased to welcome pets at The Maker Hotel! We understand that pets are part of the family, and we strive to accommodate our four-legged guests with the comfort and care they deserve. Please contact our front desk for details regarding our pet policy and any associated fees. That's 50 words and exactly zero information. The machine cannot cite it. It will guess — and the guess will be "probably, with fees" — and half the time the guess will be wrong. **After:** > Q: Do you allow dogs? > A: Yes. Dogs under 40 lbs are welcome in all rooms for a $35/night fee. We ask that they not be left alone in the room, and there's a grassy relief area behind the carriage house. Service animals stay free, no size limit. Fifty words. Facts in the first sentence. A number, a rule, a location, and the exception that gets asked about constantly. The machine lifts the whole block, and the guest gets the answer they actually needed before they even clicked. That's the whole difference. It's not harder. It's just specific. --- ### Where it falls short I don't want to oversell this, because the FAQ page has a ceiling. It won't fix a thin website. If the rest of your site is two paragraphs and a booking widget, the machines will cite your FAQ and then have nothing else to work with — the way a good answer on a bad page still loses to a good page. It won't fix bad reviews. A 3.4-star average with a 5% review response rate gets filtered out of AI recommendations entirely, no matter how clean your answers are. Your reviews are your reputation; your FAQ is just your voice. It won't outrank the fundamentals. The research is consistent: owned content that ranks in traditional search, and off-site mentions in publications and forums, drive the majority of AI visibility. The FAQ is a layer on top of that — an important layer, the most quotable page you own — but it amplifies the signal you already send. It can't manufacture one. And don't stuff it. Thirty questions is curation. A hundred and thirty is a dump. The machine, like the guest, trusts the page that's confident enough to answer twelve questions well. --- ### The practical decision **Do this now if:** - Your FAQ currently reads like the "Before" example above (be honest) - Guests email or call with the same three questions every week — those are your top three entries - You've changed something in the last year: rates, hours, policies, amenities, the restaurant **The workflow:** - Pull the last month of real questions — front desk log, emails, review responses. Write them down verbatim. Those are your questions. - Answer each one in 40-60 words, facts first, numbers everywhere - Group them: staying here, eating here, getting here - Put the page in your main navigation — the machines find it faster, and so do guests - Set the first-of-the-month reminder. Fifteen minutes. Non-negotiable The whole thing takes an afternoon. Most of the raw material is already in your head, because you answer these questions every day. You're just writing it down for a reader who's going to repeat it to a thousand guests. --- ### The bottom line The questions stopped arriving at your front desk a while ago. They're being asked in chat windows now — and they're being answered, right now, by machines reading your website. Your FAQ is the page they read first. It's the only page on your site that's already in the shape of an answer. The machines will quote something. The question is whether they quote you — the hotel you actually run, with the actual times and the actual fees and the actual dog policy — or the version of you that's been guessed at from a page written for a search engine that barely reads you anymore. Write the answers you'd give at the desk. Put them where the machines can find them. Update them when things change. The guests are already asking. You may as well be the one answering.