For multilingual markets
Content for every market you sell in, not just the English one.
Search in German, Dutch or Polish and the competition is thinner than it is in English — provided a page exists in that language. Most companies own exactly one market’s worth of content, and it is the English one.
116 languages selectableOne plan, calendar and invoice per marketEach post declares its own language
A market is a line item, not a project.
Four consequences of treating language as configuration rather than as a translation task.
- 01
One language is one line
Adding a market is not a translation project. A language is a separate editorial line with its own queries, its own intent mapping and its own dates, so the German calendar and the English one never wait on each other.
- 02
Queries are chosen per market
People do not search the same words in Amsterdam as in Austin, and a translated keyword is usually nobody's query. Each market's plan is built from that market's searches, which is the part machine translation cannot do.
- 03
The article declares its language
Every post carries its language in its structured data and its canonical URL on your own domain. A system deciding whether a page answers a Dutch question has no guesswork to do.
- 04
Every market is measured, and can be stopped
Search Console is reported per site, and each language is a separate line on the invoice. A market that is not paying its way gets switched off without touching the ones that are.
Where a second market is still winnable.
A language with fewer well-structured pages in it is a language where being one of them costs less. That is the whole argument for a second market: not a market of the year, but one where the pages that already exist are thinner than what you would publish.
Which market that is depends on who already publishes in it, and that is a question your team answers better than a pipeline. What the pipeline makes cheap is trying: a market is a line that starts on a date and can be stopped on a date.
How a second language is planned- 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.
One market at a time, or five at once.
Both are strategies. Only one of them produces a number you can act on before the budget runs out.
Opening every market at once
- Five plans to review, five cadences, five languages nobody on the team reads
- A monthly line per market from the first month, before any of them has reported
- No market proves itself before the next one starts competing for the same attention
- A quiet market hiding inside a total, so nothing gets cut
- A translation project per language, each one justified separately
One market, then the next
- Start with the market you already sell in, or the one nobody has planned against
- A plan, a calendar and its own Search Console site from the first day
- A number you can read at the end of a month: keep it, cut it, or add a publishing day
- The next market is a new line in the same week, not a new project
- No per-word invoice, no quote per article, nothing to re-justify each quarter
Every market proves itself in its own reports.
Connect Search Console read-only and each site reports its own clicks, impressions and average position. A market that is quiet looks quiet on its own numbers instead of hiding inside a total, which is what makes the decision to keep it or cut it an easy one.
1,204
Clicks
48,910
Impressions
12.4
Avg. position
Where the honest limits are.
Two things a content pipeline should not pretend to handle in a market it was not hired to know.
Regulation and the last mile of the language
The pipeline writes and checks the article. It does not certify it for a jurisdiction: anything that differs by country — a required disclosure, a regulated term, a certification — belongs on a page your team owns, with posts linking to it. Discard any post that would need a claim you are not ready to make in that market.
And the review is a fact-check, not a native ear. If a market’s copy needs to be signed off internally, that happens before the publish date — which is exactly why the whole first week is visible on the calendar before anything ships.
What your team still decides.
Opening a market is a business decision with a price on it. The pipeline makes the content side of it cheap; it does not tell you which markets are worth the 20€ and the attention.
- Which markets are worth opening, and which are a distraction
- The legal claims that differ by country — and there are more of them than teams expect
- Whether a market gets its own domain, its own subdomain, or a path
- Who inside the company signs off on what a market says
- When a market has earned a bigger share of the publishing days
Related use cases
- SEO content API
Every post as JSON — the article, its metadata, its status and URL.
- Multilingual SEO content
A language is an editorial line, not a translation of your English pages.
- Hosted blog
A blog on your own domain behind one DNS record, maintained for you.
- llms.txt
The summary file for language models, and what ours contains.
- For AI search
Be the source the answer cites.
- For AI Overviews
Publish the page the block can summarise.
Questions buyers ask before a second market.
Including who reads the German copy before it publishes.
How do we choose which market to open next?
By who already publishes in it and by who already writes to you. The honest method is to look at the language your customers use in the emails they send, check what the results for their queries look like, and start the line you can judge inside a quarter — the plan is cheap to correct, and a market that is quiet on its own numbers is easy to stop.
Can English stay the source of truth?
For the facts, yes: product names, terminology and the claims your business stands behind carry across. For the queries, no. A language is its own set of questions, and a plan built by translating English keywords targets phrases nobody in that market types. English can be the source of the facts; it cannot be the source of the searches.
What does a second market cost to run?
Twenty euros a month per site and language, whatever the market publishes — one article a week or five. There is no per-word invoice and no quote per article, so testing a market and scaling one cost the same. A translation agency quotes per word; this is priced per line.
Who checks the copy in a language we do not speak?
The pipeline does: every post is reviewed against the grounding facts before it can publish, and anything unsupported or thin is discarded rather than shipped. That review is not a native-speaker proofread, so if a market’s copy has to be signed off internally, the entries are there to review before their dates — and discarding one costs nothing.
What about local regulations and claims?
Keep them out of the pipeline and on pages you own. The plan can target the query, but anything that varies by country — a required disclosure, a certification, a regulated term — belongs on a page your team can stand behind, and posts can link to it. Discard any post that would require a claim you are not ready to make in that market.
Where is the competition thinner?
In languages where fewer companies publish structured pages, which is most languages outside English. We will not name a market of the year: the honest signal is what the results for your own queries look like in that language, and whether the pages ranking there are ones you can beat by answering the question properly.
Start with one market
Open the market you keep postponing.
Connect the domain, pick the language and review the first week: the German, Dutch and English lines run side by side, each on its own calendar.
20€ / site / language / monthPer-market Search Console reporting3 days free, no card