For restaurants & cafés
Be found for the question that ends in a table.
A guest chooses with five questions open: whether there is something for the vegetarian in the group, where to park, whether a table for eight is possible on a Friday, what the neighbourhood is like at night. A menu page cannot hold any of that. Xt4b writes the pages that can, on the venue’s own domain, in every language guests arrive speaking.
The menu stays yoursOne line per languageNo per-article quotes
What someone searches on the way there.
Not another page describing the restaurant. The questions put to a search engine while deciding where to eat tonight, asked by people who have not chosen yet.
- The menu question
- Vegetarian options, gluten, nuts, the thing a guest needs to know before choosing the restaurant — answered in prose, because the menu is a list and a list cannot explain.
- The logistics of the visit
- Parking, prams, dogs, group tables, walk-ins versus bookings, what a Tuesday evening is actually like. The questions asked on the phone all day.
- The occasion
- Birthdays, private hire, a table for twelve, a quiet corner for a work lunch — the reasons a booking is made elsewhere when the venue does not explain itself.
- The neighbourhood
- Why here rather than three streets away: the market, the tram, what else is nearby, what the area looks like at eight in the evening.
- Season, menu changes and closures
- What is on in summer, when the terrace opens, the holiday the kitchen takes — content that keeps a venue findable in its quiet weeks.
- Links into the pages that take the booking
- Every post links to your menu, your booking page and your contact details, taken from your own sitemap — so the blog feeds the pages that already work.
Between services, on a schedule.
Five steps, and only one of them needs the kitchen. The rest happens between services, without anyone remembering to write.
- 01
Scan the venue's site
Free and without an account: the homepage, the menu page and the sitemap, plus the questions the site does not answer yet.
- 02
Connect the domain
One DNS record and the blog answers on a hostname inside a domain the venue owns. Nothing is installed and your reservation system is untouched.
- 03
The kitchen sees it first
With approval on, a post waits for the kitchen to read it before it publishes — what is on the menu this season, which tables fit a group. That is the only part that needs a person.
- 04
Posts publish on their dates
A post on each publishing day the venue picked, per language, with images, metadata and links back to the menu and the booking page.
- 05
See which queries appear
Connect Search Console read-only and see the clicks and impressions the venue's own domain earns for the questions guests ask before they arrive.
What stays at the venue.
A post cannot know that the fryer is separate, that the terrace closes at ten, or that the tasting menu needs a week’s notice. Those are the venue’s facts, and they belong on the pages the venue already maintains.
What it can do is keep answering the questions around them — in each language the guests arrive in — and point the reader at the menu and the booking page rather than competing with them.
- The menu, the prices and the wine list
- Allergen facts and everything the kitchen states about them
- Opening hours, holiday closures and the reservation policy
- Photographs of the food and the room
- The answer the front-of-house gives at nine on a Friday
A page nobody updates, or a blog that answers the season.
Both start the same way. Only one of them is still findable in February.
The site nobody revisits
- A menu PDF and an About page from the opening year
- Opening hours correct everywhere except the website
- The questions answered by email, one guest at a time
- The English page, for a summer that speaks four languages
- No idea which search brought anyone through the door
A blog around the venue
- A post on each publishing day the venue picked
- Queries taken from what guests type before they book
- One editorial line per language, each with its own plan
- Seasonal posts that keep working out of season
- Clicks and impressions per query, from Search Console
The limits worth knowing
It cannot improve the food, the room or the service, and it cannot make a Friday night look busier than it is. Reviews, photographs and word of mouth still decide whether a venue fills — a blog earns the consideration, not the visit.
And the honest caveat, on the page rather than in the small print: rankings, traffic and booking numbers are not guaranteed. What you get is a growing set of pages on a domain you own, publishing on a schedule, in each language you chose to serve.
One line per language, not a quote per article.
20€ per website, per language, per month. The scan comes first and costs nothing, so the questions your site is missing are visible before you decide anything.
That is the whole invoice: no per-article rate, no minimum number of posts and no separate charge for images or for hosting the blog. A second language for a summer season is one more line, and the German posts are written against German searches rather than translated from the English ones.
The blog sits on a domain the venue owns, so what it builds is an asset rather than a listing — and it keeps answering in the quiet months, when nobody is marketing anything at all.
- The plan: the questions, the outlines and the dates
- Drafting, with the kitchen's review before anything publishes
- Cover and in-article images, in the venue's colour
- Hosting the blog on the venue's own domain
- The plumbing: canonical URLs, sitemap, structured data
- Search Console numbers for the venue's domain
More on content
- For local businesses
Answer the question before they call.
- For ecommerce
The blog around the catalogue — product pages stay yours.
- For hotels & travel
Answer the guest in the language they searched in.
- 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 venues ask.
Including whether the menu gets rewritten, how allergens are handled, and whether it works for a summer of tourists.
Does it write our menu or our prices?
No. Menus, prices and wine lists are yours, and a pipeline should not restate them: they change on your schedule, not on a publishing calendar. The blog answers the questions around the menu — dietary options, group dining, the season — and links to the page that carries the definitive list.
What about allergens?
The venue's own pages stay authoritative, and the review step is where a claim about a dish is confirmed by the kitchen. A post can explain how the kitchen handles a request, but nothing is generated about a specific dish's ingredients without someone at the venue saying so.
We get tourists. Does it work in more than one language?
That is exactly the case it is built for: each language is a separate line, planned from the searches in that market rather than translated from the first. A venue whose guests arrive in three languages can run one, two or three lines, each with its own calendar, at 20€ per website, per language, per month.
Can it use our own food photography?
No — the images in a post are generated in the venue's accent colour, so nothing here pretends to be a photograph of your room. Real photographs remain the venue's own argument, on the pages where they belong, and the blog links to them rather than imitating them.
Will it update our Google Business profile?
No. Nothing here touches Google Business, review platforms or the reservation system: the posts are new pages on a domain you own, and the profile stays yours to manage. What Search Console reporting does show is which queries the domain itself is earning impressions for.
How long does it take to see anything?
The first plan is ready once the scan has run, so you can read the questions your site is missing the same day. Publishing then follows the dates in that plan — and searches, impressions and bookings are not guaranteed: they arrive on the search engines' schedule, not on ours.
What does it cost?
20€ per website, per language, per month, with the plan, the writing, the images and hosting the blog included. There are no per-article quotes, and the scan is free and needs no account.
Start with the venue
Answer the guest before they choose somewhere else.
Connect the venue's domain and read the plan: the questions the site is missing, the outlines behind them, and dates you can move before anything is written.
One line per language20€ / site / language / month3 days free, no card