TL;DR: Write the guest FAQ once, in the language you think in, with a number and a date on every answer. Translate it with AI, have each language read by someone who speaks it, and publish the same text everywhere: your website, the pre-arrival email, OTA listings and Google. When a fact changes, change the source row first, then every language. That is how to write a guest FAQ in several languages without the versions drifting apart.
In August a guesthouse by a lake answers the same questions every day, in three languages: where to park, when check-in starts, why the receptionist scans an ID card, what the extra charge on the bill is. The answers live in the owner's head, in an old German page on the website, in the OTA listing and in a few email drafts. They do not quite agree. The parking fee on the German page is last year's.
How to write a guest FAQ in several languages is less a translation problem than a version problem. This article shows a simple way to keep one source and several languages in step. It is part of our boutique hotel marketing strategy guide.
Why does a small hotel need one source FAQ?
Because the same answer appears in many places: the website, the booking confirmation, the pre-arrival email, the OTA listings and your Google profile. If each place has its own text, they drift apart, and the guest who reads the wrong one arrives annoyed. One source, numbered and dated, means you change a fact once.
Guests are not the sole readers. AI assistants that answer travel questions draw on whatever text is published about you. In BrightLocal's 2026 survey of US consumers, across all local business types, 45% used ChatGPT or other generative AI for local recommendations (BrightLocal). If your German page says one parking price and your English page another, the answer a guest gets may be either.
Some facts on Google are only yours to set if the profile is verified. Amenities can be edited in the "Hotel details" section only on a claimed and verified profile (Google), so verify it before you rely on it as one of the FAQ's outlets.
Which questions belong in the guest FAQ?
The ones guests actually ask, and the ones where a wrong answer causes trouble at the desk. Collect them for a month from emails, OTA messages and the reception desk. Most small properties end up with fifteen to twenty-five questions: arrival, parking, payment, rules, local tips, and the legal steps of checking in.
The legal steps deserve careful wording, because guests often meet them for the first time at your desk. In Hungary, for example:
- Guest identity and document data must be recorded at check-in in the accommodation software and sent to the designated storage, known as VIZA; without an identity document the stay must be refused (Turisztikai törvény § 9/H, Nemzeti Jogszabálytár).
- The tourist tax, idegenforgalmi adó, is paid by guests who are not permanent residents, is collected by the host with the room fee, and guests under 18 are exempt. The text of the Act states an upper limit of 300 Ft per person per night or 4% of the room fee, indexed limits may differ, and the actual rate comes from the local council's decree (Htv. §§ 30–34, Nemzeti Jogszabálytár).
- Accommodation services may only be offered with a valid classification, an NTAK registration and accommodation software that reports to NTAK (239/2009. Korm. rendelet, Nemzeti Jogszabálytár).
Across the EU, Regulation 2024/1028 applies from 20 May 2026: in Member States that use registration, platforms must verify hosts' registration numbers and pass activity data to the authorities monthly (European Commission). A registration number in the FAQ and on every listing saves questions.
Price questions belong here too. If you advertise to US guests, the FTC fee rule requires hotels and vacation rentals to make the total price, including mandatory fees, the most prominent price (FTC, 2024). Say plainly in the FAQ whether the tourist tax is included in the price shown.
How do you keep the languages in sync?
Keep the FAQ as a table: one row per question, with a number, the source answer, one column per language, and the date the source answer last changed. When a fact changes, edit the source row, update the date, and re-translate that row only. Every outlet takes its text from the table.
| No. | Question | Source answer (HU) | DE | EN | Last changed |
|---|---|---|---|---|---|
| 01 | When is check-in? | from the source | translated | translated | date |
| 02 | Where can we park? | ||||
| 03 | Why do you scan our ID card? | ||||
| 04 | Is the tourist tax included? | ||||
| 05 | Can we bring a dog? |
The outlets, and what each takes from the table:
- The FAQ page on your website: every row, every language.
- The booking confirmation: rows 01, 02 and 04.
- The pre-arrival email: rows 01, 02, 03 and one local tip.
- OTA listings: the house rules and policies fields, copied from the matching rows.
- Google: amenities in "Hotel details", matching the FAQ.
Twice a year, before each main season, compare every outlet with the table, row by row. It takes an hour and finds the drift.
How should AI translate the FAQ, and who checks it?
Give the AI the source row, the target language and a short glossary of terms that must not change, then have a speaker of that language read the result. AI handles everyday phrasing well. Legal and local terms, such as the tourist tax or the ID rule, need a fixed wording that a person has approved once.
A brief that works: "Translate FAQ row 03 into German for guests of a small guesthouse. Keep it short and friendly. Use the glossary: idegenforgalmi adó = Kurtaxe; VIZA = the national guest-registration system, explain it in one clause. Do not add information that is not in the source." Then read it, or ask a German-speaking friend or regular guest to read the whole column once.
Keep the glossary with the table. Once the German word for the tourist tax is agreed, every row uses it. Guests notice when the same thing has three names.
A filled example: a lakeside guesthouse
The example shows the method end to end for one property in peak season: the questions collected, the source answers, the translations and the outlets. It uses a Hungarian guesthouse, because the legal rows are concrete there; the structure works the same with your country's rules in those rows.
Example (illustrative, not a real case): a guesthouse by Lake Balaton gets the same 15 questions in peak season: parking, check-in time, ID, tourist tax and others. The owner writes the source answers in Hungarian in a table, asks an AI tool to draft German and English versions, and reviews them, with a German-speaking regular guest reading the German column. Row 03 explains why the ID card is scanned at check-in: the law requires the data to be recorded and sent to the national system. Row 04 says the tourist tax is collected with the room fee and that guests under 18 do not pay it. The same rows go onto the FAQ page, into the pre-arrival email and into the OTA house rules. When the council changes the tax rate, the owner edits row 04, updates the date and re-translates that one row.
Action plan
Collect first, write second, translate third. The order matters because the source answers decide everything downstream, and a translation of a wrong answer is still wrong. The first version takes a few evenings; after that, keeping it current takes an hour before each season and a few minutes whenever a fact changes.
- Collect guest questions for a month from emails, OTA messages and the desk.
- Write the source answers in one table, numbered and dated.
- Agree a glossary for legal and local terms.
- Translate with AI, one language at a time, and have each read by a speaker.
- Publish to every outlet from the table.
- Before each season, compare the outlets with the table.
The same facts will come up in reviews; replies that point to them are in hotel review response template. Where the FAQ sits on your booking path is covered in boutique hotel website design.
If you want help writing the source FAQ and the pre-arrival messages in a voice that sounds like your house, we are building the Conversion Copywriting Pack. Get notified when it launches.
FAQ
Which language should the source FAQ be in?
The language you think and write in most precisely, usually your own. The source is where facts are decided, so it should be the version you can check without help. Translations come from it, never from each other, so a mistake in one language does not spread to the others.
Can I rely on AI translation for a guest FAQ?
For everyday phrasing it is usually good enough to publish after a read-through. For legal and local terms, such as the tourist tax or ID rules, agree a fixed wording once and add it to a glossary that the AI must use. Have each language read by someone who speaks it before the first publication.
How do I stop the FAQ on my website and OTA listings from drifting apart?
Keep one table as the source, with a number and a last-changed date on every answer, and copy from it to every outlet. When a fact changes, edit the table first, then each outlet. Before each main season, compare every outlet with the table row by row; it takes about an hour.
Should the guest FAQ explain the ID check and tourist tax?
Yes. Guests often meet these rules for the first time at your desk, and a short, calm explanation in their language prevents most arguments. Say what is recorded and why, that the tourist tax is collected with the room fee, who is exempt, and whether the price shown already includes it.
Sources
- Local Consumer Review Survey 2026 — BrightLocal, 2026.
- Manage your hotel's details — Google Business Profile Help, accessed 2026.
- 2016. évi CLVI. törvény (Turisztikai törvény) — Nemzeti Jogszabálytár (Hungarian legislation database), state as of 2026.
- 1990. évi C. törvény a helyi adókról (Htv.) — Nemzeti Jogszabálytár, state as of 2026.
- 239/2009. (X. 20.) Korm. rendelet — Nemzeti Jogszabálytár, state as of 2026.
- Common EU rules on data sharing for short-term accommodation rentals — European Commission, 2026.
- FTC announces bipartisan rule banning junk ticket and hotel fees — U.S. Federal Trade Commission, 2024.