Opening a site to a second language does not end with translating pages. For a search engine the real question is: which language version should I show to which user? If that is not answered cleanly, language versions replace each other, the wrong one ranks, or none does. Below are the points that break most often in multilingual setups.
hreflang does not work one way
hreflang is how you say "the Turkish of this page is here, the English is there." It has one strict condition: the declaration must be reciprocal. If the Turkish page points to its English version but the English page does not point back, the search engine ignores the declaration.
This is a silent failure: the page loads, the tag is visible in the source, no error appears, and the pairing still does not work. Verifying it means checking both sides: by hand in the page source for a few pages, and mechanically across the whole site.
A page must reference itself too
A common omission is listing only the other languages. Each page should include its own language in the hreflang set as well; an incomplete set makes the group invalid.
Alongside this, x-default tells the engine which version to show a visitor who matches none of the listed languages. It is frequently skipped.
canonical must not contradict hreflang
A page's canonical URL should match its own hreflang declaration. If the Turkish page sets the English version as canonical, you are saying both "the master version is English" and "this is the Turkish alternate" at once. Contradictory signals lead the engine to discard both.
URL structure: which model?
- Subdirectory (site.com/en/): shares one domain's authority, easiest to set up and maintain.
- Subdomain (en.site.com): technically separated, authority is shared less effectively.
- Separate domain (site.de): strongest local signal, but every domain has to be grown from zero.
For most businesses the subdirectory is the balanced choice. Whichever model you pick, one language's URL should not carry the other's slug; each language's address should be readable in that language.
Translation matters as much as the content
Machine-translated pages that nobody reviewed cause two problems: low quality for the reader, low value for the search engine. In short strings such as titles and meta descriptions, translation errors hit click-through directly.
Another frequent mistake is translating the body while the title tag and meta description stay in the original language. If a user does not see a title in their own language in the results, they do not click.
Menus, forms and buttons are content too
Translation often stops at body text; menu items, form labels, button text and error messages stay in the original language. That breaks the page's linguistic consistency and directly lowers conversion — a visitor who cannot read the form will not fill it in.
We describe how we build this end to end on the web design and development page.
Checklist
- Does each page include its own language in the hreflang set?
- Does the counterpart page point back?
- Is x-default defined?
- Is canonical consistent with the page's own language?
- Are the title and meta description genuinely translated?
- Are menus, forms and buttons in the target language too?
If you are planning a multilingual project, fill in the quote form and we will map out the setup together.