Which language to publish first when budget is one
Pick the language you can answer in, then the one that pays best. A page in a language nobody in the business speaks produces enquiries you cannot serve, and 19 percent of consumers expect a response the same day. Reach is worth nothing without an answer behind it.
Answering capacity comes before reach
The temptation is to choose the largest audience. The better first question is which language somebody in the business can reply in, on the same day, without translating in the browser first.
The reason is measurable. 19 percent of consumers expect a response the same day, and an enquiry in a language nobody handles well goes to the back of the queue by default. A page that generates enquiries you answer late damages the reviews you already have.
This is also the cheapest constraint to test. Count how many enquiries in that language you already receive and how long they took to answer. If the answer is two days, that language is not ready to be marketed in.
Only after that does reach matter, and it is easy to overestimate: a language spoken by many visitors is not the same as a language your enquiries arrive in.
The arithmetic of the choice
Value per enquiry is average order value times closing rate. Run it once per audience. If German speaking enquiries average 900 euros with one in 3 closing, each is worth 300 euros. If Spanish speaking enquiries average 450 euros at the same rate, each is worth 150.
Then multiply by volume you can actually serve. 4 German enquiries a month at 300 euros is 1,200. 12 Spanish enquiries at 150 euros is 1,800. The larger audience wins here, and it lost in the previous example, which is the whole point of doing the sum rather than guessing.
Add one modifier. 45 percent of consumers used an AI tool for local search in 2026 against 6 percent a year earlier, and those tools answer in the language of the question. A language you publish in is a language you can be recommended in.
| Criterion | Question | Where the answer is |
|---|---|---|
| Answering capacity | Can we reply same day | Your own enquiry log |
| Value per enquiry | Order value times closing rate | Invoices and log |
| Serviceable volume | How many can we take | Capacity, not the market |
| Machine visibility | Can we be recommended in it | The language you publish in |
What to do with the second language later
Add it as one page with its own opening answer, not as a translation of everything. That page carries the identity block, the deciding question for that audience, and a way to make contact.
Then declare the versions properly. Reciprocal hreflang annotations and one x-default cost twelve lines across three pages, and without the reciprocity the annotations are ignored.
Questions and answers
Should I start with the biggest audience?
Is machine translation enough to start?
How do I know which language pays best?
Does publishing in a language help with AI answers?
Sources
- BrightLocal, Local Consumer Review Survey 2026 Response expectations and the growth in AI use for local search
- Google Search Central, Localized versions of your pages How to declare the versions once the second language exists
