How to troubleshoot recurring hreflang tag errors on multilingual websites?

“The page has clearly been translated, so why does Google still show the English page to German users?” Many foreign trade companies encounter similar challenges when expanding their multilingual websites. More commonly, developers have added hreflang, yet webmaster tools continue to report inconsistencies or missing return links, or the indexing and organic traffic of pages in different languages never improve.

How can persistent errors in hreflang markup on multilingual websites be resolved? The key is not repeatedly modifying a single tag, but troubleshooting it as a mechanism through which “multiple versions of a page declare their relationships to one another.” hreflang tells search engines which URLs are versions of the same content for users in different languages or regions. It does not guarantee rankings, but it can reduce the likelihood of language-version mismatches and give users a better chance of landing on pages suitable for reading, making inquiries, and placing orders.

First, confirm: Does your website really need hreflang?

If a website has only Chinese and English versions, and the content, currency, logistics, and contact information are all the same, with only the interface language differing, using zh and en is usually sufficient. If both versions are in English, but the US site uses US dollars and inches while the UK site uses pounds sterling and millimeters, then it is more appropriate to further distinguish them as en-US and en-GB.

Do not mechanically generate dozens of regional codes simply to “cover more markets.” For a page without independent differences in content, pricing, services, or conversion paths, forcibly splitting it into versions such as en-DE and en-FR will instead increase maintenance costs and may make it difficult for search engines to determine page relationships. For B2B foreign trade websites, establishing versions based on core languages and priority markets is often more reliable than creating a large number of regional pages with minimal differences.

The most easily overlooked rule: Every version must fully “recognize” one another

hreflang does not end with an English page pointing to a Chinese page. A valid language-version group should include all corresponding pages, and every URL must contain the same set of declarations, including itself. For example, for Chinese, English, and Japanese product pages, all three should list the corresponding links for zh, en, and ja at the same time.

<link rel="alternate" hreflang="zh" href="https://example.com/zh/product-a/" />
<link rel="alternate" hreflang="en" href="https://example.com/en/product-a/" />
<link rel="alternate" hreflang="ja" href="https://example.com/ja/product-a/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/" />

Among these, x-default is suitable for pointing to a language selection page, an international homepage, or a default page where users can switch languages themselves. It is not mandatory, but it is helpful for brand websites targeting customers across multiple countries. Note that the default page itself should be a real page that is accessible and indexable, rather than an intermediary URL that immediately forces a redirect.

Troubleshooting along this path is more effective than “staring at tags and making changes”

1. Are URLs matched one-to-one, rather than having the entire site point to the homepage?

This is the most common hidden issue on multilingual e-commerce and marketing websites. An English product detail page should correspond to its Chinese and Japanese product detail pages; an English blog article should correspond to articles on the same topic in other languages. If all English internal pages use hreflang to point to the Chinese homepage, or translated content has not yet gone live and temporarily points to a category page, search engines will find it difficult to regard them as equivalent versions.

For content that has not yet been translated, it is better not to establish a hreflang relationship for that language than to pair pages arbitrarily. Especially when building sites in batches, check whether discontinued products, URL revisions, pagination, and filter pages have left outdated mappings behind.

2. Are return links missing, or are version lists inconsistent?

Suppose page A declares page B as its English version, but page B does not declare A as its Chinese version. This is what is commonly referred to as a “missing return link.” Another more subtle situation is that the Chinese page lists zh/en/ja, while the English page lists only zh/en. Although every page appears to have tags, the language sets are inconsistent, which may likewise cause the signals to become ineffective.

It is recommended to first maintain page relationships in a table: each row represents a content group, and each column represents a language or region. Confirm the URLs before having the system output them consistently. Do not rely on manually copying and pasting across different templates. Once a website has hundreds of product pages, missed updates are almost unavoidable.

3. Can target pages be crawled and indexed normally?

URLs referenced by hreflang must return a 200 status code. They cannot be 301 or 302 redirect URLs, nor should they be 404 pages, soft 404 pages, pages blocked by robots.txt, or pages with noindex. Common issues include mobile devices automatically redirecting to another domain, region-detection plugins forcing redirects, CDN rules rewriting URLs, and links from testing environments mistakenly being carried over to the live site.

Also check canonical tags. Usually, each language version’s canonical should point to itself. If an English page has a canonical pointing back to a Chinese page while also using hreflang to state that it is an independent English version, these two signals will conflict with each other. Search engines will often prioritize canonicalization issues, making hreflang difficult to apply effectively.

4. Are the language and region codes correct?

Languages use ISO 639-1 two-letter codes, such as en, de, fr, and zh. When specifying a region, use the “language-region” format, such as en-US, pt-BR, and zh-CN. Do not use only a country code such as US, and do not mix in nonexistent or nonstandard custom abbreviations.

In addition, a page’s lang attribute serves a different purpose from hreflang: the former helps browsers and assistive reading tools understand the language of the page, while the latter is used for version matching in search. They are recommended to remain consistent, but they cannot replace each other.

Where to place tags: Choose one of the three methods and maintain it consistently

hreflang can be placed in the <head> section of HTML, submitted through HTTP response headers, or submitted through an XML Sitemap. Most standard corporate websites and content sites use head tags; non-HTML files such as PDFs can use HTTP headers; and cross-border e-commerce sites with many language versions and a large number of pages can have the system generate an XML Sitemap for centralized management.

Technically, multiple methods can exist at the same time, but only if the data is completely consistent. In practice, template tags, plugins, and Sitemaps are often maintained by different teams, making conflicts such as “one set on the page and another in the sitemap” particularly likely. If there is no clear management capability, it is recommended to establish one primary data source and avoid duplicate output through other channels.

After making changes, do not just look at the source code

Opening the page source code to confirm that tags are present is only the first step. You should also spot-check each link to verify that it is an absolute URL, returns 200, has a self-referencing canonical, and that the corresponding language page contains complete reverse declarations. For large websites, first select the homepage, core product pages, priority landing pages, and high-traffic article pages for sample checks, then use crawler tools to export issues in batches.

Google Search Console’s URL Inspection tool can help confirm whether a page can be crawled and how its canonical page is determined; server logs can also help observe whether search engines have successfully accessed different language versions. Do not expect immediate changes after modifications, as search engines need to recrawl and process page relationships. At this point, it is more important to keep URLs, tags, and the sitemap stable, rather than changing the directory today and altering redirect rules tomorrow.

Incorporate hreflang into the website-building process, rather than treating it as a post-launch patch

The challenge of multilingual SEO usually lies not in the tags themselves, but in whether content, URL architecture, translation progress, and technical templates are synchronized. For websites that continuously add products, blogs, and advertising landing pages, it is best to include four checks in the publishing workflow: language-version mapping, index status, canonical, and hreflang.

Intelligent website-building and marketing services such as Yiyingbao, which serve businesses expanding overseas, place greater emphasis on planning multilingual paths from the website architecture stage rather than fixing pages one by one after indexing issues arise. Regardless of which website-building system is used, companies should retain maintainable language mapping rules: update tags when content is updated, and remove associations when pages are taken offline. With this approach, hreflang can truly become a clear and reliable route between global users and the right pages.