For hotels & travel
Answer the guest in the language they searched in.
Guests decide before they arrive: which area, which season, whether the transfer is included, what a family room actually is. Xt4b writes those posts on your own domain — one editorial line per market, each planned from that market’s own searches. Room pages and rates stay yours.
Posts on your own domainOne line per marketNo per-article quotes
What the posts answer.
Not another page about the property. The questions a guest puts to a search engine in the week they are choosing where to stay.
- The choice between two listings
- Which area, how far from the airport, is breakfast included, is it walkable at night — the comparison a guest makes with three tabs open before they commit.
- The season and the timing
- When to come, what a shoulder month is actually like, what is open and what is closed — content that keeps earning impressions all year rather than only during the campaign.
- The trip you host, not just the room
- Transfers, parking, accessibility, family rooms, late arrival. The details that do not fit on a rate page because a rate page has to stay short.
- A URL you own, not one you rent
- Every post lives on your own domain with your sitemap, canonical URL and per-post structured data, so the demand it builds belongs to the property rather than to a platform.
- One line per market, planned separately
- A guest searching in German is not served by an English page with a translation bolted on. Each language is planned from that market's own searches, with its own dates.
- Links into the pages that take the booking
- Posts link to the room, rate and contact pages you already publish — taken from your sitemap, so the blog strengthens those pages instead of competing with them.
The steady version of a hotel blog.
Five steps, and only one of them is yours to repeat. The rest happens on the calendar, in the background, in season and out of it.
- 01
Scan the property site
The free scan reads your homepage, your headings and your sitemap, and shows what your site already answers plus the questions it misses.
- 02
Connect the domain
One DNS record and the blog answers on a domain you own, usually a subdomain. Nothing is installed on the site you have and nothing is written into the booking engine.
- 03
Check the plan against the property
Discard entries for a season you close, a service you do not offer, or a market you do not want. That review is the only part of this that needs a person.
- 04
Posts publish on their dates
Written to the plan entry it belongs to, checked before it publishes, then live with images, metadata and internal links to the pages they discuss.
- 05
See which queries appear
Connect Search Console read-only and each site reports the clicks, impressions and average position its posts earn, per query.
What stays at the property.
A post cannot know that room 4 is the quiet one, that the pool closes in October, or that the rate on the site is not the rate the front desk will honour. Those stay on the pages that sell the stay.
What it can do is keep answering the questions the property raises — in three languages if that is what it sells into — and point the guest at the page that takes the booking.
- Room types, rates, availability and the offers themselves
- Photography of the property, taken on the property
- The booking engine, the cancellation policy and the extras
- What you are willing to promise a guest in writing
- The answer the front desk gives at eleven at night
Six posts in the first month, or one every publishing day.
Both start the same way. Only one of them is still answering guests in a second language next season.
The blog nobody keeps up
- Six posts in the first month, then nothing until the season starts
- One page saying the hotel is ideally located, which nobody searches for
- Rate and room pages written once and never revisited
- The English posts, translated, on the assumption that is enough
- Impressions nobody reads, because analytics were never connected
A blog that answers guests
- One post per publishing day, on the dates it was planned for
- Queries taken from what guests type before they shortlist a property
- One editorial line per market, each with its own plan and calendar
- A generated cover and in-article image for every post
- Clicks, impressions and average position per site, from Search Console
What a blog does not fix
Reviews, photographs, the rate, the weather and the booking engine still decide whether a guest books. A blog earns the visit — it does not improve the checkout, and it cannot make a property with poor photographs look better than it is.
And rankings, traffic and bookings are not guaranteed — no honest supplier can promise them, and our terms say so. What you get is a growing set of pages on your own domain, publishing on a schedule, in each market you chose to serve.
Costed per language, not per post.
20€ per website, per language, per month. The scan comes first and costs nothing — you see the queries your site is missing before you decide anything.
That is the whole invoice: no per-article rate, no minimum number of posts, no separate charge for images, metadata or hosting the blog. One market is one line, and the German posts are written against German searches rather than translated from the English ones.
The blog sits on a domain you already own, so the archive is an asset of the property rather than a channel you rent — and it keeps publishing quietly through the months when nobody is marketing anything.
- The plan: queries, intents, outlines and dates
- Writing, with the review pass before publishing
- Cover and in-article images, in your brand colour
- Hosting the blog on your own domain
- Canonical URLs, sitemap and structured data
- Search Console reporting, per site
More on content
- For local businesses
Answer the question before they call.
- For ecommerce
The blog around the catalogue — product pages stay yours.
- For restaurants
The question that ends in a table — menus and prices stay yours.
- For dentists & clinics
Answer the treatment and cost questions, with clinical review.
- For law firms
Clients search the situation, not the practice area.
- For publishers
Archive depth under the news: the long tail a desk cannot reach.
- For WordPress sites
A blog for WordPress without a plugin or a theme edit.
Questions hotels ask.
Including whether the website gets translated, and whether a listing on a booking site already covers this.
Does it translate my website into other languages?
No. Nothing touches the pages you already publish: the posts are new pages on a blog on your own domain, planned separately for each language from that market's own searches. Your site keeps serving exactly what it serves today, and the blog links back into it.
We already get bookings from a booking platform. What does this add?
A listing shows your property next to its competitors, on a page you do not own. A blog on your own domain is the part of the search that is yours: a guest arriving at a URL with your name on it, with your sitemap, canonical URL and structured data, rather than a page that platforms and rivals share.
How many languages should a hotel run?
As many as it sells into. Each language is a separate line at 20€ per website, per language, per month, with its own plan, its own target searches and its own calendar — and each is planned from what that market searches for rather than translated from the English posts. A market that stops paying its way can be switched off without touching the others.
Can the posts be about the destination rather than the hotel?
Yes. The plan targets the searches your domain does not answer yet, so an entry can be about the area, the season, the route from the airport or the trip around a stay. You see every entry, with its intent and date, before a word is written, and discarding one costs nothing.
Will it publish into our booking engine?
No. The blog is served from your own domain behind one DNS record; nothing is installed and nothing is written into the booking engine, the channel manager or the property management system. If you would rather serve the posts yourself, the read-only API returns each one as markdown or as rendered HTML.
What does it cost for a hotel with two source markets?
Two lines: 20€ per website, per language, per month. There are no per-article quotes, no minimum number of posts and no charge for the scan, which needs no account and shows you the queries your site is missing plus the first entries of the plan.
Will it fill rooms?
No ranking, traffic or booking volume is guaranteed, and any supplier who promises one is guessing. What the blog does is give your own domain more pages answering what guests actually ask — the area, the season, the transfer — publishing on a schedule, with reporting that shows which queries the site is beginning to earn impressions for.
Start with your website
Answer the guest before the shortlist.
Connect your domain and read the plan: the queries your site is missing, the first entries, and dates you can move before anything is written.
One line per market20€ / site / language / month3 days free, no card