An e-commerce site serves five languages, with carefully crafted pages in each. Yet Search Console keeps flagging "duplicate hreflang" or "not matched" warnings, and a Spanish-language searcher still lands on the English page. This scenario repeats almost like clockwork on multilingual sites: hreflang is conceptually simple, yet in practice it's one of the most frequently misconfigured elements of technical SEO.
Having worked on the frontend and technical SEO side for over a decade, I can say that hreflang mistakes rarely come from carelessness — they come from a specification that isn't well understood. The tag's syntax is simple, but for it to work correctly, every language version has to point to every other version reciprocally and consistently; a single missing or incorrect reference undermines the credibility of the entire structure in the eyes of the search engine. Hreflang consulting is the work of setting this structure up correctly from the start and keeping it from breaking down over time.
In this article, we look at what hreflang actually does in multilingual SEO, the most common mistakes made with it, and what proper consulting in this area should cover.
What Hreflang Actually Does
The hreflang tag tells a search engine "the equivalent of this page in this language and/or this region is located at this address." Its purpose is to prevent search engines from treating different language versions of the same content as duplicates, and to show each user the correct version for their language or region. It is not a ranking factor — setting it up correctly won't push you higher in the results — but setting it up incorrectly or incompletely can cause the wrong pages to be shown to the wrong users, or even cause some language versions to be ignored by the search engine altogether.
The Most Common Mistakes
Most of the mistakes seen in practice fall into a handful of patterns. Lack of reciprocity: if page A points to page B but page B doesn't point back to A, the search engine won't trust the relationship and will usually disregard it. Wrong language/region code: for example, using just "es" instead of "es-ES" for Spanish as spoken in Spain, or mixing up codes, breaks the targeting. Missing self-reference: every page needs to include a hreflang reference to itself alongside the references to other languages; this step is skipped surprisingly often. Conflict with canonical: when a page's canonical tag points to one URL while its hreflang tags use a different URL structure, that contradiction makes it unclear to the search engine which signal to trust.
Choosing a URL Structure: Getting It Right From the Start
When setting up a multilingual site, you generally choose between a subdirectory (site.com/es/), a subdomain (es.site.com), or a country-specific domain (site.es). Each option has its own advantages and management overhead; a subdirectory structure usually carries the least technical burden and benefits the most from your existing domain authority. Because changing this decision later carries a serious risk of major restructuring and temporary ranking loss, consulting needs to make this call at the very start of the project, with growth plans already factored in.
x-default and Users With No Detected Language
The x-default tag, used to determine which page to show a visitor who doesn't match any of the targeted languages, is either left out entirely or pointed at the wrong page on most multilingual sites. When configured correctly, it typically routes the user to a language-selection page or to the most general/default language version, improving the experience while also sending a clear signal to the search engine.
Managing Hreflang on Dynamic Sites
On sites built on a content management system or a custom platform where content is added frequently, managing hreflang tags by hand quickly becomes unsustainable. In that situation, the tags need to be generated automatically and dynamically, driven by the content database; when a new language version is added or a page is removed, all the corresponding reciprocal references need to update automatically, which prevents the mistakes that manual management inevitably introduces. This is an automation layer that consulting needs to build together with the technical team.
What to Look for When Evaluating This Service
When looking for hreflang and multilingual SEO consulting, it's worth checking whether the person evaluates not just tag syntax, but the site architecture, canonical structure, and its relationship with the content management system as a whole. An approach that regularly monitors the international targeting reports in Search Console and catches errors proactively resolves problems before they grow.
Building a multilingual site is a substantial investment, and getting a return on that investment depends on each language reaching the right users. Working with an experienced specialist who knows the technical details of things like hreflang and can assess your site's architecture holistically is the most reliable way to make sure that investment actually pays off.