A kitchen-appliance shop has one page about oven repair in English, another in Malay, and a third in Simplified Chinese. All three describe the same service. How can a visitor—and Google—find the right version without being sent to the wrong language?
First give each translation a useful page at a stable URL. Then connect the equivalent pages with hreflang.
What Is Multilingual SEO?
Multilingual SEO helps people discover and use your content in more than one language. A multilingual site serves different languages; a multi-regional site explicitly targets different countries or regions. The same site can do both. Add a country code to a language annotation when that version is intended for people in that country, rather than assuming the code from your office address.
Give each substantial translation a separate, crawlable URL, such as an English page and corresponding /ms/ and /zh/ pages. Keep the main content and navigation understandable in that language. Google determines a page's language from its visible content, not from its URL, HTML lang attribute, or hreflang alone.
What Does Hreflang Do?
hreflang identifies pages that are language or regional versions of one another. It helps Google choose which URL to show to a searcher. It does not create translations, guarantee indexing, or directly improve a page's rank.
For the oven-repair page, the English, Malay, and Chinese versions form one alternate set. An oven product page is not an alternate of an oven-repair page. Pair pages by the answer they give, not by a shared keyword.
Which Pages Should You Pair?
Start with pages that genuinely serve the same purpose: the same article, service, product, or category presented for different audiences. The wording and examples can be localized; they need not be sentence-for-sentence copies. But a Malay page containing only a translated menu and an English article is not a complete Malay version.
If the shop has not published a Chinese repair page yet, do not point its English repair page to an unrelated Chinese homepage. Keep the available English–Malay pair and add Chinese when the equivalent page is ready. Preserve a visible language switcher so readers can choose another version themselves instead of being forced through an automatic redirect.
How Does a Three-Language Set Work?
Suppose the shop publishes the same oven-repair guide at three stable URLs. Here is a planning example; the addresses are not live pages.
| Version | Example URL | hreflang value |
|---|---|---|
| English for Malaysia | https://example.com/oven-repair/ | en-MY |
| Malay for Malaysia | https://example.com/ms/oven-repair/ | ms-MY |
| Simplified Chinese without a country target | https://example.com/zh/oven-repair/ | zh-Hans |
The URL folder and hreflang code do different jobs. /zh/ is simply a site path; zh-Hans describes Simplified Chinese without assuming a China-specific audience. Use a region suffix only when that page targets a specific region.
In HTML, each page's <head> should list all three fully qualified alternate URLs, including its own. The three pages should return the same set of alternates, so every pair points both ways. For example, each page can include this set in its HTML <head>:
<link rel="alternate" hreflang="en-MY" href="https://example.com/oven-repair/">
<link rel="alternate" hreflang="ms-MY" href="https://example.com/ms/oven-repair/">
<link rel="alternate" hreflang="zh-Hans" href="https://example.com/zh/oven-repair/">Google also supports equivalent annotations in HTTP headers or XML sitemaps. One method is enough; if you use more than one, keep their mappings consistent. An optional x-default can identify a real fallback or language-selector page.
How Do Canonical and Hreflang Work Together?
A canonical URL expresses which URL you prefer among duplicate or very similar versions. hreflang expresses which localized versions correspond. If the English and Malay pages contain complete translations, each should normally use its own URL as canonical. Pointing both at English conflicts with the goal of serving the Malay version.
Check that each translated URL is indexable and uses a canonical consistent with the version you intend Google to serve. If several near-identical pages exist within the same language, resolve that duplicate decision first, then annotate the preferred URLs as alternates.
What Should You Check Before Publishing?
- Open each exact URL. Check that it loads directly, returns the intended language, and does not require a cookie, login, or forced language redirect.
- Read the page as a visitor. Confirm that the main answer, title, navigation, and important links make sense in that language. Translate intent rather than mechanically copying keywords.
- Compare the alternates. Inspect the rendered
<head>or sitemap. Each available version should list itself and its true equivalents with full URLs and reciprocal references. - Check index signals. Verify canonical,
noindex, status, and redirects on every URL. Do not annotate a broken or unpublished page. - Use the language switcher. From the oven-repair page, each option should lead to the corresponding repair page, not a language homepage.
Test one important page set before repeating the pattern. Keep a page-by-page locale inventory as the site grows; every page does not need every language on day one.
Frequently Asked Questions
What Is Hreflang in SEO?
It is an annotation that tells Google which URLs are localized versions of the same page, helping it present a suitable version to searchers. The actual page content still needs to be in the intended language.
How Do I Add Hreflang?
Choose equivalent, accessible URLs, then list each version—including itself—using full URLs in HTML <link rel="alternate" hreflang="..."> tags, HTTP headers, or an XML sitemap. Make the references reciprocal and check the published output.
Do I Need a Version in Every Language?
No. Publish a language version only when its page is useful and ready. Link the versions that actually exist; do not invent an alternate URL or send readers to an unrelated homepage.