One Language or Many? Getting the Site Structure Right From Day One

Building a multilingual site looks like a bargain: two markets for the same effort. In practice, two languages mean two content calendars, every piece of copy corrected twice, and a mapping table you have to explain to search engines. If you aren't genuinely doing business in that market, a second language doesn't bring you traffic — it brings you maintenance debt.

We settle the question with three questions. Are you actually selling in this language, or does it just look good? Who is going to keep the second language up to date? And are the terms people search in that language really different — or is this just a translation of the same page? If you can't answer all three clearly, the right move is to be flawless in one language and add the second when you're ready.

If you are going multilingual, the rule is simple: one URL, one language. Each language lives at its own address (a path prefix or a separate domain), each page carries a self-referencing canonical, and the languages are tied together with hreflang — x-default included. Content that changes by visitor at the same address is, to a search engine, two versions of a single page; it decides for itself which one to index, and it usually doesn't pick the one you wanted.

Automatic language redirection is the most expensive good intention there is. Reading a cookie, the browser language or the country and sending the visitor somewhere else looks reasonable for humans. But crawler bots carry no cookies and generally arrive from a single region; for them that address is no longer content, it's a permanent redirect. If your canonical still points at that address, you've sent the site a signal that contradicts itself.

The right answer is to let the visitor choose: every page returns 200 in its own language, there's a visible language switcher in the interface, and the choice is optionally remembered — but nobody gets dragged to a different address. Bot and human see the same answer at the same address.

Removing a language runs on the same discipline: every old address permanently redirects to its new counterpart, hreflang tags are cleaned out, the sitemap drops to one language, and the structured data and page language attribute are updated. Done properly, the authority you've accumulated moves to the new addresses; done halfway, both languages lose their rankings.