URL Structure and Hreflang for a Multilingual Website: Three Steps Before Launch
The most common indexing problem on a multilingual website is not translation quality. It is Google showing the wrong language version to the wrong buyer: a German visitor lands on the English page, a Spanish speaking market gets Chinese results, and the traffic quietly leaks. Two decisions made before launch decide most of this. One is the URL structure. The other is the hreflang setup. The bigger picture on architecture and language planning was covered in an earlier piece at multilingual website architecture and SEO, so this one sticks to structure and tags.
Step One: Pick a URL structure and do not change it later
Three options exist. A subdirectory such as example.com/en/ keeps all languages under one domain, so every version shares the authority the domain has already earned. A subdomain such as en.example.com separates deployment but splits that authority. A separate domain such as example.de carries the strongest local trust signal and costs about as much as running a second website.
For most export businesses the subdirectory wins without much debate. A new domain often needs more than a year to build rankings on Google, and a subdirectory lets the English version start on top of what the Chinese site has earned. Separate domains make sense later, when one market is big enough to justify deep local branding. Changing structure midway means a full redirect exercise and months of re crawling, so decide once and move on.

Step Two: Write hreflang tags by four rules
hreflang tells Google that several pages are language versions of the same content. It adds no ranking points, it only routes traffic, and a wrong setup hurts more than no setup. Four rules, all mandatory.
Every pair of versions needs bidirectional links. If the English page declares the German page, the German page must declare the English one back. One way declarations are ignored as a whole group.
Each page must include a self referencing entry inside its own tag group.
Each declaration points to the matching page, never the homepage. If every German tag points to the German homepage, Google reads the whole group as fake.
Add one x-default entry to catch users whose language matches nothing, usually pointing at the English version. Implementation is simple with link tags in the head, one per language, using ISO 639-1 codes. Keep canonical self referencing as well. A canonical pointing back to the Chinese original can push the English version out of the index entirely.
Step Three: Run three checks before launch
Pick three pages at different levels, the homepage, one product page, one article page, and verify that every tag group is bidirectional and self referencing. Confirm every declared target returns 200, and leave unfinished languages undeclared. After launch, watch the International Targeting report in Google Search Console until errors reach zero, then fold this into the routine laid out in the first 90 days checklist.
Three habits cause most failures after launch. IP based auto redirects block Googlebot from reaching other versions. Language switches that land on the homepage throw away the page the visitor was reading. And a German page with translated navigation but an English FAQ is a frame, not a localized page. The content side of that gap is covered in five localization details beyond translation.
Related Q&A
What happens if hreflang is configured wrong?
Google loses track of which versions belong together. Traffic gets mismatched, versions compete with each other, and a one way declaration voids the entire group. The three pre launch checks exist precisely for this.
We only have English and Chinese. Do we still need hreflang?
Yes. Fewer languages does not mean fewer mismatches, since Chinese users do search in English and overseas buyers do search in pinyin. Two versions still need bidirectional links, self references and one x-default entry. The effort is small.
The site has been live for two years. Can we still change the URL structure?
Yes, but it is expensive. Full redirects, resubmitted sitemaps and months of re crawling before authority settles. If only hreflang is missing, keep the structure and add the tags first, the gain comes fast.