A company spends six months and a serious budget translating its site into five languages. Traffic from those markets barely moves. The natural conclusion is that the translation was not good enough, and the natural response is to commission a review of the copy.

In a large share of cases the copy is fine. What has happened is that the annotations telling search engines which page belongs to which market are inconsistent, so the engine has discarded them and is guessing. Multilingual SEO is unusual in that the most expensive failures are technical and nearly invisible.

What hreflang Is Supposed to Do

An hreflang annotation is a signal that says: this page has an equivalent for a different language or region, and here is where it lives. Done correctly, a searcher in Mexico gets your Mexican Spanish page rather than your Spanish one, and the two pages stop competing against each other.

You can deliver these annotations three ways: as link elements in the head of the HTML, in HTTP headers for non-HTML files such as PDFs, or inside an XML sitemap. Google's own guidance on telling Google about localized versions of a page covers all three, and the sitemap approach is usually the sane choice for a large site because it keeps the entire mapping in one auditable file rather than scattered across thousands of templates.

The Four Ways It Breaks

The first is reciprocity. Annotations have to point both ways. If your English page lists the German one but the German page does not list the English one back, the relationship is unconfirmed and is likely to be ignored entirely. This breaks constantly because the two pages are usually managed by different people.

The second is self reference. Every page in the set must include an annotation pointing at itself. A missing self referencing hreflang is one of the most common findings in any technical audit, largely because it feels redundant to anyone implementing it by hand. It is not redundant. It is how the engine confirms which member of the set it is currently looking at.

The third is malformed codes. The language part uses two-letter language codes and the optional region part uses two-letter country codes, in that order. A region cannot appear on its own. And the code for the United Kingdom is not the same as its internet domain, which produces a specific, very common error that looks correct to almost everyone who writes it.

The fourth is the hreflang canonical conflict, and it is the one that silently destroys the most work. Each language version must declare itself canonical. If your German page carries a canonical tag pointing at the English page, you have told the engine that the German page is a duplicate that should not be indexed, while simultaneously telling it the German page is the right result for German searchers. Faced with a contradiction, it believes the canonical and drops the rest.

Translated Keywords Are Not Keywords

The other half of the problem is upstream of any markup. Teams translate their keyword list, and a translated keyword is not the same thing as the term real people type.

Search behaviour varies by market in ways that have nothing to do with linguistic accuracy. Different countries favour different levels of formality, different loan words, different brand-versus-generic habits. A term with meaningful volume in one Spanish-speaking market can be almost dead in another. This is why international seo keyword research has to be run natively in each target market, with local volume data, rather than derived from the source language list.

Markup problems have a direct editorial cost as well as a technical one. If language and region are declared inconsistently, the wrong version of a story is served to the wrong audience, sometimes an outdated one. Publishers producing international news treat that as an accuracy issue rather than an SEO one.

The practical version of this is that translators need the target keyword before they start, not a finished English page and a deadline. Retrofitting a term into completed copy produces exactly the stilted phrasing that readers notice and engines discount. The best practical guidance on the workflow, including how to brief for it, is set out in these tips on SEO translation and keyword localization.

Structure, and the Redirect Everyone Regrets

Country domains, subdomains and subdirectories all work. Subdirectories are the default recommendation for most organisations because they concentrate authority on one domain, and country domains send the strongest geographic signal at the cost of splitting that authority several ways.

What does not work is automatically redirecting visitors by IP address. It stops crawlers from reaching most of your site, because a crawler arriving from one country will only ever see one version, and it infuriates the substantial minority of users who are travelling or who simply prefer another language. Offer a suggestion banner and let people choose.

Audit Before You Rewrite

Before commissioning anything, run the diagnostic in this order. Confirm every page is self referencing. Confirm every relationship is reciprocal. Confirm no canonical crosses a language boundary. Confirm every annotated URL returns a 200 and is indexable.

Practitioners in communities like r/TechSEO tend to agree that this four-point check resolves the majority of international visibility problems without a single word being retranslated. Good multilingual SEO services will start there too, and any provider proposing a content rewrite before showing you that audit is selling the expensive fix first.