Multilingual
Multilingual SEO content without the translation theatre.
A second language is a second set of questions people type, not a copy of your English pages with the nouns changed. Xt4b runs each language as its own editorial line — its own queries, its own calendar, its own dates — and publishes all of them to the blog you own.
116 languagesA plan and calendar per lineOne blog, your domain
Translation, localisation, or content written per market?
Three different jobs with three different price tags, and the difference decides whether a new language earns anything.
The short version
- Translation converts text you already have. It is the right job for a pricing page, a legal document or a brand page — pages that exist for a reason other than a search query.
- Localisation adapts a page to a market: currency, examples, regulations, the words a market actually uses. It still starts from a page written for somewhere else.
- Writing per market starts from the query instead: what people type in that language, and what the results for it currently answer. That is what Xt4b does, per language, on your own domain.
- A language is billed as its own line: 20€ per website, per language, per month, with nothing charged per article.
Multilingual SEO content means a search-driven page exists in the language of the person searching, aimed at the words they use. A translated English page usually fails that test for a boring reason: the query it targets was chosen by someone writing in English, so the page answers a question that market phrases differently — or never asks at all.
That is why each line here gets its own plan. Queries come from that market’s own results, existing pages are checked for coverage first, and the article is written in the language rather than converted into it.
The version of this written for teams running several markets- Translate when the page has to exist in every language regardless of demand: pricing, terms, contact, the homepage.
- Write per market when the page has to be found by a search: a how-to, a comparison, a cost breakdown, a category guide.
- Never auto-translate a search page and leave the English keyword in place — the page will rank for nothing and read as machine output.
- Localise the parts a reader notices immediately: currency, legal reference, examples, and the name of the thing being bought.
What makes a page findable in its own language?
The technical half is small and mostly free. It is also the half that decides whether a search engine treats the page as belonging to that language at all.
- Declare the language
- Each article carries the language it is written in, and so does the structured data around it. Without that declaration a search engine is guessing from vocabulary alone.
- Write the metadata in that language
- A translated body under an English meta title and description is a page that reads as two half-pages. Title, description, headings and FAQ are produced per line here.
- Canonical to itself
- Each post points its canonical at its own URL on your domain — not at the English version, which would tell a search engine to ignore it.
- One sitemap, every language
- One blog per site means one sitemap listing the posts of every language it publishes, so nothing depends on a per-market sitemap being remembered.
- Links inside the language
- Internal links come from your real pages and prefer the post's own language. Links into another language's section are dropped when there are enough same-language targets.
- hreflang, only when there are alternates
- hreflang points search engines at other language versions of the SAME page. These lines are separate pages rather than translations of one, so there is no alternate set to declare — and inventing one would be wrong.
What “its own line” means.
Every language on a site behaves like a site of its own for the parts that matter — and like one site everywhere a reader can see it.
- Its own plan
- A language is a separate editorial line: its own target queries, its own topics, its own gap analysis against the pages that language already has.
- Its own calendar
- Dates are assigned per line, so a market you publish twice a week is not forced onto the cadence of the one you publish daily.
- Its own research
- Research runs against the results for that language's market, not a translated English query. The wording a buyer types is the wording the post is built around.
- Written in the language
- The article is written in the language you publish in — headings, meta title, description, FAQ. It is not an English draft with the nouns swapped.
- Its own line on the bill
- 20€ per website, per language, per month, and nothing per article. Three markets is three lines; switching one off leaves the others running.
- All of it on 116 languages
- From the usual European markets to Portuguese, Polish, Turkish, Japanese, Hindi and Arabic — the full list is in the product, and a new line is added in seconds.
Adding a market, step by step.
Six steps from a new language to a market you can judge on numbers rather than on a feeling.
- 01
Add the language to the site
It becomes an editorial line with its own plan and calendar. Nothing else about the site changes: same domain, same brand, same blog.
- 02
Read the plan for that market
Queries the language's pages already answer are marked covered; the gaps are dated. This is the first place a bad assumption gets caught.
- 03
Pick the cadence
Choose the days this line publishes on. A market you are testing can run weekly while your main one runs daily, on the same account.
- 04
Posts are written in that language
Each one follows its own brief: the query, the intent, the outline, the metadata — in the language, with sources and internal links checked the same way.
- 05
Everything publishes to one blog
One hosted blog per site, with each article declaring its own language, its own canonical URL and its own structured data. One sitemap, one robots file, one favicon.
- 06
Report, then decide
Search Console is read-only per site. A market that earns its line gets more days; one that does not gets switched off without touching the rest.
- ENEnglish2 posts a weekplanned / live12 / 7
- DEGerman1 post a weekplanned / live5 / 3
- FRFrench1 post a weekplanned / live4 / 1
Same blog, same design — each language gets its own plan and its own dates.
A line shows its language, its cadence and how much of it is planned versus live. That is the whole management view: you are looking at four or five numbers per market, not a translation spreadsheet.
Because the plan is per line, a market where you already rank is not fed the same topics again — the covered queries are marked and the calendar fills with the ones that are actually open.
And because each post is written in its own language against its own brief, the blog never reads like a machine translation of a sibling post. Same brand, same design, its own argument.
Translated pages versus a market that was planned.
The failure mode of multilingual content is not bad grammar. It is fluent pages aimed at queries nobody in that market types.
Translate the English set
- The query the page targets was chosen for English speakers
- Headings read as translations: correct, and slightly foreign
- Internal links point into the English section because that is what exists
- Every market publishes on the same cadence, whatever it earns
- Nothing tells you which language produced which result
Plan each market
- Queries come from that market's own results, so the page answers what is typed there
- The article is written in the language, headings and metadata included
- Links come from the language's own pages first, and are dropped rather than forced
- Cadence is set per line, so a test market can run weekly
- The calendar shows the language of every post; Search Console reports the site it belongs to
What stays your call.
A pipeline can carry six languages without drifting. The decisions it cannot make are editorial ones.
A line goes wrong when the plan and the writing disagree: an outline approved in one language, written against queries taken from another. That is the mistake a plan makes cheap to catch — you are discarding an entry, not an article.
- The tone a language carries — a market that expects formality, or your brand's own register
- Whether a market keeps the parent brand's examples and prices, or gets its own
- Which topics are off-limits in a market you know better than we do
- The terminology your brand insists on, per language, and the words it refuses
- Every date, discard and unpublish across all of the lines
How it fits a site that already exists.
Nobody starts here with an empty domain, so the honest question is what happens to the pages you already have.
- Existing pages are read, not replaced
- The plan is built from the site as it is — its sitemap, its headings, its language. Queries an existing page already answers are marked covered, so you are not paying for a second version of a page that works.
- The blog is additive
- Posts publish to a blog on your own domain. If you would rather they land in an existing CMS, the finished posts are available through a read API as markdown or rendered HTML.
- Their language, their metadata
- Each article carries its own language, its own meta title and description, its own canonical URL and its own structured data — the pieces a search engine needs to treat it as a page in that language.
- One domain to maintain
- No subdomain-per-market sprawl: one blog, one certificate, one robots file, one favicon, and readers landing where your brand already lives.
One thing to plan for
Writing in a language is not the same as knowing a market. The articles are researched and written per line, but your judgement about tone and about what a market will not tolerate is the part that keeps a multilingual programme credible. Treat the first month of a new line as a review-heavy test, not as unattended output.
More on content
- SEO content API
Every post as JSON — the article, its metadata, its status and URL.
- Hosted blog
A blog on your own domain behind one DNS record, maintained for you.
- For multilingual markets
Which market to open next, and what it costs.
- llms.txt
The summary file for language models, and what ours contains.
Questions about running several markets.
Including the one about hreflang, which is a design choice rather than a gap.
Is this translation, or content written per language?
Written per language. A translated page answers a query nobody typed: the plan for each line is built from that market's own results, so the article is written in the language and aimed at what people actually search for there. Translating an existing post makes sense for a landing page; it rarely makes sense for a search-driven article.
Do all languages publish to one blog?
Yes — one blog per site, hosted on your own domain, with each article declaring its own language, its own canonical URL and its own structured data. One sitemap, one robots file, one favicon, one place for a reader to land, whichever language they arrived in.
Does it create hreflang alternates between languages?
No, and that is deliberate. Each post declares the language it is written in — the article's lang attribute, the Open Graph locale and the structured data all say so — but the languages here are separate editorial lines rather than translations of one page, so there is no alternate set to link. If you need hreflang between versions of the same page, that is a different job from running several markets.
How many languages can one site carry?
116 are selectable, and there is no separate ceiling on how many a site uses. What limits a site in practice is your budget and your attention: each line is its own plan and calendar, so adding a market is adding work to review, not just a setting to flip.
How do internal links work across languages?
Links come from your real sitemap and prefer pages in the same language as the post. Links to another language's pages rank last and are dropped when there are enough same-language targets, so a Dutch article is not held together by links into the English section.
Which languages are supported?
116 are selectable, covering the European markets and well beyond them — including German, Dutch, Spanish, French, Italian, Portuguese, Polish, Turkish, Japanese, Hindi and Arabic. The full list is in the product, and the language you add decides the market the research runs against.
Can I run the same topic in two languages?
Yes, and it is usually the right thing to do — but each line gets its own brief. The query, the outline and the internal links are worked out per language from that market's own results, so a German version of a Dutch article is a sibling rather than a copy.
Does Search Console report per language?
No — it is per site, read-only, which is how the property is set up in Google. A site running four lines reports one set of clicks and impressions for the domain, and the calendar is where you see which language produced which post.
Does each language need its own keyword research?
Yes, and that is the whole difference between a market and a translation. Research runs against the results for that language's market, so the wording a buyer types is the wording the post is built around — a translated English keyword is usually a phrase nobody in that market searches for. The plan is priced per language precisely because the research is done per language.
Does it guarantee that a market will rank?
No. You get a plan aimed at queries that market does not answer yet, publishing on your own domain, and the search data to judge it honestly. Ranking, traffic and revenue are not guaranteed in any language.
Start with one market
Add a language, watch four weeks of it.
Pick a market you can judge, set its cadence, and let the calendar fill in that language. If it earns its line, add the next one.
20€ per site, per languageOne blog on your domain3 days free, no card