The 3 mistakes bilingual sites make
Most Malaysian bilingual sites we audit have at least one of the same three problems, and these problems are why they rank below monolingual competitors that have less authority but cleaner SEO setup.
Mistake 1: One URL, two languages swapped via JavaScript
The pattern: a single URL (say example.com/about) that shows English or Chinese depending on a JavaScript toggle, with no change to the URL itself. From a user perspective this looks elegant. From Googlebot's perspective there's only one page, and only one of the two languages is going to be indexed — usually whichever is the default. The other language never gets any search traffic because Google has never seen it.
Mistake 2: hreflang tags pointing to the wrong URLs
The pattern: hreflang tags exist but the URLs they point to are inconsistent — sometimes including trailing slashes, sometimes not; sometimes the canonical URL, sometimes a query-string variant. Google's hreflang validator (in Search Console) is unforgiving about this, and when the validation fails, hreflang is essentially treated as not present.
Mistake 3: Chinese content that reads as machine translation
The pattern: the site was clearly written in English and run through a translation tool (or a non-native translator) to produce the Chinese version. Native Chinese readers spot this in the first sentence, bounce, and Google's user-engagement signals deteriorate. Lower engagement → lower ranking → fewer visits → less data → lower ranking still. The cycle is hard to recover from without rewriting the content.
Each of these is fixable. The rest of this guide is the fix.
URL structure: subfolder, subdomain, or query
The first decision is where the languages live structurally. Three options, in order of preference for most Malaysian SMEs.
Subfolder — /en/ and /zh/ (recommended default)
URLs like example.com/en/about and example.com/zh/about. Each language has its own URL, both inherit the domain's accumulated authority, both are easy to track separately in Search Console. This is what most well-built bilingual sites use, and what we'd recommend for any new build.
Subdomain — en.example.com and zh.example.com
Each language gets its own subdomain. Works, but Google treats subdomains as separate sites for ranking purposes. The Chinese subdomain doesn't automatically inherit the English subdomain's authority — you're building two reputation profiles in parallel. Reasonable choice if you have significantly different teams managing each language, or for very large sites; usually unnecessary complexity for SMEs.
Query string — ?lang=zh
The simplest to build but the most fragile for SEO. Some pages get indexed correctly; others get collapsed by Google into a single canonical URL, with one language disappearing from search results. If you must use query strings (because you're retrofitting an existing site that can't easily restructure URLs), be very deliberate: each language version must have its own canonical pointing to itself, hreflang tags must be perfect, and you should accept that ranking will be harder than with subfolders.
Our own site uses the query-string approach as a transitional pattern (since it's a single-page React app), but we explicitly tell clients building new sites to start with subfolders. It's the easiest pattern to get right and the most forgiving long-term.
hreflang done right
The hreflang tag tells Google which URL serves which language to which audience. It's the single most important technical signal for a bilingual site, and the one most commonly broken.
Minimum correct setup for an EN/中文 page targeting Malaysian audiences:
<link rel="alternate" hreflang="en" href="https://example.com/en/about" />
<link rel="alternate" hreflang="zh" href="https://example.com/zh/about" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/about" />Key rules that catch most teams out:
- Self-referencing is required. Each language version must include the hreflang for itself. The English page's
<head>must containhreflang="en"pointing to itself, plushreflang="zh"for the Chinese version. The Chinese page must do the mirror. - Use absolute URLs. Always full
https://example.com/...URLs, never relative paths. - Be consistent with trailing slashes. If your canonical is
/en/about/, all hreflang references to that page must include the trailing slash. - x-default is for the page that should be served when no language matches. For Malaysian sites, the English version is the safe default.
- Refine with country codes when needed. Use
hreflang="zh-MY"if you want to flag the Chinese version as specifically Malaysia-targeted, especially useful if you want to outrank China-targeted Chinese sites in google.com.my.
Language switching Google understands
A good language switcher needs to do two things: serve users the right language pleasantly, and tell Googlebot that both versions exist as real navigable pages.
What works:
- Real anchor tags (
<a href>) linking to the alternate-language URL. Googlebot follows these. - The href points to the same page in the other language — not the home page of the other language. A user reading your /en/about page who clicks "中文" should land on /zh/about, not /zh/.
- The
<html lang="...">attribute is set correctly —lang="en"for English,lang="zh-CN"for Simplified Chinese targeting Malaysia/Singapore.
What doesn't work for SEO (even if it looks the same to users):
- JavaScript-only switching that doesn't change the URL — Googlebot only sees one URL.
- A switcher that always sends users to the home page of the other language — Googlebot can't tell which page is the equivalent.
- Forcing one language via IP detection without giving users (and Googlebot) a way to switch — both Google and your users will hate this.
Sitemap & structured data
Two more technical layers that most bilingual sites do incompletely.
Sitemap
Your sitemap should list each language version of each page, with hreflang annotations linking them together. One sitemap is fine for most sites; the format looks like:
<url>
<loc>https://example.com/en/about/</loc>
<xhtml:link rel="alternate" hreflang="en" href="https://example.com/en/about/"/>
<xhtml:link rel="alternate" hreflang="zh" href="https://example.com/zh/about/"/>
<xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/en/about/"/>
</url>
<url>
<loc>https://example.com/zh/about/</loc>
<xhtml:link rel="alternate" hreflang="en" href="https://example.com/en/about/"/>
<xhtml:link rel="alternate" hreflang="zh" href="https://example.com/zh/about/"/>
<xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/en/about/"/>
</url>Both language versions appear as separate <url> entries, each with the full hreflang set.
Structured data
Your JSON-LD structured data should reflect the language of the page it's on. The inLanguage property is the explicit signal:
- On
/en/...pages:"inLanguage": "en"in your Article / Service / WebPage schema. - On
/zh/...pages:"inLanguage": "zh"(or"zh-CN") on the same schema. - If your business serves multiple languages, the LocalBusiness schema should declare
"knowsLanguage": ["en", "zh", "ms"]so Google understands you can serve customers in all three.
Content: translation vs rewriting
This is the part that technical SEO can't fix. The Chinese version of your site needs to be written for Chinese readers, not translated for them. Two different things.
A translated site reads as a translation. Native Chinese readers know it within the first sentence. Phrasing feels stiff, sentence structures mirror English in ways Chinese doesn't naturally do, idioms come across as direct word-for-word renderings. The result is content that's technically correct but emotionally cold — and content that bounces.
A rewritten site reads as native. The same idea is expressed in the natural rhythm and register of Malaysian Chinese (马来西亚华语), with cultural references that fit and tone that matches what a local reader expects. The translation is loose; the meaning is faithful.
Practical workflow we use:
- Write the English version with English readers as the audience.
- Pass the meaning (not the words) to a native Malaysian Chinese writer.
- Have that writer produce Chinese with Chinese readers as the audience — same message, freely worded.
- Cross-check that both versions cover the same points and end in the same place, but don't try to match sentence-by-sentence.
Machine translation as a starting draft is fine if you have a native editor doing a substantial rewrite afterwards. As a finished product, it consistently underperforms in SEO because user engagement metrics suffer.
Local SEO signals that matter
Beyond the bilingual technical setup, a few local-SEO signals disproportionately help Malaysian bilingual sites.
Google Business Profile in both languages. Your GBP listing should have its description, services, and posts available in both English and Chinese — GBP supports multiple-language post updates. This is one of the strongest local-SEO levers for SMEs.
LocalBusiness JSON-LD with knowsLanguage. Include all the languages you genuinely serve. This helps Google match you to bilingual or multilingual searches.
Local citations in both languages. Malaysian business directories (MyBizList, Malaysia Yellow Pages, SME Corp) often allow Chinese descriptions. Use them — most competitors won't.
Reviews in both languages. Customer reviews on GBP and other platforms in mixed languages are a strong authenticity signal for bilingual operations.
Geographic targeting in Search Console. Set your international targeting to Malaysia in GSC's legacy international targeting tool (still operational despite being labelled "legacy"). This is especially important if your top-level domain is .com rather than .com.my or .my.
Pre-launch + post-launch checklist
The full bilingual-SEO checklist we work through for client launches.
| Stage | Item | How to verify |
|---|---|---|
| Pre-launch | Each language has its own URL (subfolder) | Visit /en/ and /zh/ — different URLs visible |
| Pre-launch | hreflang in every page's <head>, self-referencing | View source on both versions; verify with Search Console URL Inspector |
| Pre-launch | <html lang> attribute correct per page | View source; should change between /en/ and /zh/ |
| Pre-launch | Language switcher uses real anchor tags pointing to equivalent page in other language | Right-click the switcher → Inspect |
| Pre-launch | sitemap.xml lists both versions of every page with hreflang alternates | Open sitemap directly in browser; validate XML |
| Pre-launch | JSON-LD includes inLanguage matching the page's language | Google Rich Results Test on both URLs |
| Pre-launch | LocalBusiness schema declares knowsLanguage | Rich Results Test |
| Pre-launch | Chinese content written by native Malaysian Chinese writer (not machine-translated) | Native reader review |
| Post-launch | Submit sitemap to Search Console | GSC → Sitemaps |
| Post-launch | Set international targeting to Malaysia | GSC → Legacy tools → International Targeting |
| Post-launch | Request indexing for both language versions of key pages | GSC → URL Inspection → Request Indexing |
| Post-launch | Monitor "International Targeting" report for hreflang errors | GSC → Legacy tools → International Targeting → Language |
| Post-launch | Set up GBP in both languages | business.google.com |
双语网站常犯的 3 个错误
我们审查的马来西亚双语网站，大部分至少有下面三个问题中的一个，这也是为什么它们排在权威值更低、但 SEO 设置更干净的单语对手后面。
错误 1：一个 URL，靠 JavaScript 切换两种语言
常见模式：一个 URL（比如 example.com/about），靠一个 JavaScript 按钮显示英文或中文，URL 本身不变。从用户角度看，这设计很优雅。从 Googlebot 角度看，只有一个页面，两种语言里只有一种会被索引——通常是默认那种。另一种语言永远没有搜索流量，因为 Google 从来没看过它。
错误 2：hreflang 标签指向错误的 URL
常见模式：hreflang 标签是有，但指向的 URL 不一致——有时带斜杠，有时没；有时是 canonical URL，有时是带参数的版本。Google 的 hreflang 验证器（在 Search Console）对这种很严格，一旦验证失败，hreflang 基本上就当不存在。
错误 3：中文读起来像机器翻译
常见模式：网站明显是用英文写的，然后跑一次翻译工具（或非母语译者）产出中文版。母语中文读者第一句话就看得出来，弹出离开，Google 用户参与度信号下降。低参与度 → 低排名 → 流量少 → 数据少 → 排名更低。这个恶性循环，不重写内容很难翻身。
每一项都可以修。这篇文章接下来就是修法。
URL 结构：子文件夹、子域名、还是参数
第一个决定是两种语言在结构上放哪里。三个选择，按对大部分马来西亚中小企业的优先顺序排：
子文件夹 — /en/ 和 /zh/（推荐默认）
URL 像 example.com/en/about 和 example.com/zh/about。每种语言有自己的 URL，两种都继承域名累积的权威值，在 Search Console 里也都容易分开追踪。大部分做得好的双语网站都用这个，我们也建议任何新项目从这里开始。
子域名 — en.example.com 和 zh.example.com
每种语言有自己的子域名。能用，但 Google 在排名时把子域名当作不同的网站。中文子域名不会自动继承英文子域名累积的权威——您是在并行建立两份信誉档案。如果两种语言由明显不同的团队管理，或网站非常大，这选择合理；对中小企业一般是不必要的复杂度。
参数字符串 — ?lang=zh
建起来最简单，但 SEO 上最脆弱。某些页面会被正确索引，另一些会被 Google 合并成单一 canonical URL，其中一种语言就从搜索结果消失。如果非用参数不可（因为您在改造现有网站，URL 结构没法轻易重做），就要非常刻意：每种语言版本必须有指向自己的 canonical，hreflang 标签必须完美，而且要接受排名会比子文件夹方案更难做。
我们自己的网站用参数方案作为过渡（因为它是单页 React 应用），但我们明确告诉做新项目的客户：从子文件夹开始。这是最容易做对的模式，长期来看也最宽容。
hreflang 标签正确用法
hreflang 标签告诉 Google 哪个 URL 给哪个语言的哪类受众。它是双语网站最重要的单一技术信号，也是最常被弄错的那个。
面向马来西亚受众的 EN/中文页面最低正确设置：
<link rel="alternate" hreflang="en" href="https://example.com/en/about" />
<link rel="alternate" hreflang="zh" href="https://example.com/zh/about" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/about" />大部分团队会踩到的关键规则：
- 必须自指向。每个语言版本必须包含指向自己的 hreflang。英文页的
<head>必须有指向自己的hreflang="en"，加上指向中文版的hreflang="zh"。中文页要做镜像的设置。 - 用绝对 URL。永远用完整的
https://example.com/...URL，不要用相对路径。 - 结尾斜杠要一致。如果您的 canonical 是
/en/about/，所有 hreflang 引用都要带结尾斜杠。 - x-default 是当没有语言匹配时该送出的页面。马来西亚网站，英文版作默认是稳的。
- 需要时用国家码精炼。用
hreflang="zh-MY"来明确标记中文版面向马来西亚，特别适合您想在 google.com.my 上压过面向中国的中文网站时。
Google 看得懂的语言切换机制
一个好的语言切换器要做两件事：愉快地把用户送到正确语言、告诉 Googlebot 两种版本都是真实可导航的页面。
有效的做法：
- 真实的 anchor 标签（
<a href>）链到另一种语言的 URL。Googlebot 会跟进去。 - href 指向另一种语言的同一页——不是另一种语言的首页。读者在 /en/about 页面点"中文"应该到 /zh/about，不是 /zh/。
<html lang="...">属性设置正确——英文是lang="en"，面向马来西亚/新加坡的简体中文用lang="zh-CN"。
SEO 上行不通的（就算用户看起来一样）：
- 只靠 JavaScript 切换、不改 URL 的——Googlebot 只看到一个 URL。
- 切换器永远把用户送到另一种语言的首页——Googlebot 没办法知道哪一页是对应的。
- 靠 IP 检测强制锁定一种语言、不给用户（和 Googlebot）切换方式——Google 和您的用户都会讨厌这个。
Sitemap 和结构化数据
大部分双语网站做得不完整的两个技术层。
Sitemap
您的 sitemap 应该列出每个页面的每种语言版本，附带 hreflang 标记把它们连起来。大部分网站用一份 sitemap 就够，格式像这样：
<url>
<loc>https://example.com/en/about/</loc>
<xhtml:link rel="alternate" hreflang="en" href="https://example.com/en/about/"/>
<xhtml:link rel="alternate" hreflang="zh" href="https://example.com/zh/about/"/>
<xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/en/about/"/>
</url>
<url>
<loc>https://example.com/zh/about/</loc>
<xhtml:link rel="alternate" hreflang="en" href="https://example.com/en/about/"/>
<xhtml:link rel="alternate" hreflang="zh" href="https://example.com/zh/about/"/>
<xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/en/about/"/>
</url>两种语言版本都作为分开的 <url> 项出现，各自带完整的 hreflang 集合。
结构化数据
您的 JSON-LD 结构化数据要反映它所在页面的语言。inLanguage 属性是明确信号：
- 在
/en/...页面：Article / Service / WebPage schema 里写"inLanguage": "en"。 - 在
/zh/...页面：同样的 schema 里写"inLanguage": "zh"（或"zh-CN"）。 - 如果您的生意服务多种语言，LocalBusiness schema 要声明
"knowsLanguage": ["en", "zh", "ms"]，这样 Google 才知道您可以用三种语言服务客户。
内容：翻译还是重写
这是技术 SEO 修不到的部分。您网站的中文版需要写给中文读者看，而不是翻译给他们看。两件事不一样。
翻译过来的网站读起来就像翻译。中文母语读者第一句话就知道。措辞生硬、句法结构镜像英文（中文本身不会自然这样讲）、习语像逐字直翻。结果是技术上没错、但情感上冷冰冰的内容——也是会被弹出的内容。
重写的网站读起来像母语。同一个意思用马来西亚华语自然的节奏和语域表达，文化引用合适、语气符合本地读者期待。翻译松散，但意思忠实。
我们用的实际流程：
- 把英文版面向英文读者写出来。
- 把意思（不是字）传给马来西亚华语母语写手。
- 让那位写手面向中文读者产出中文——同样的讯息，自由措辞。
- 交叉检查两个版本覆盖同样的要点、落到同样的结论，但不要逐句对应。
机器翻译作起草稿没问题，前提是后面有母语编辑做大幅重写。作为完成品，它在 SEO 上稳定表现不佳，因为用户参与度指标会受影响。
真正重要的本地 SEO 信号
除了双语技术设置之外，几个本地 SEO 信号对马来西亚双语网站特别有帮助。
Google Business Profile 用两种语言。您的 GBP 列表应该用英文和中文都提供描述、服务、贴文——GBP 支持多语言贴文更新。这是中小企业最强的本地 SEO 杠杆之一。
LocalBusiness JSON-LD 含 knowsLanguage。把您真正服务的所有语言都列进去。这帮 Google 把您对应到双语或多语搜索。
两种语言的本地引用。马来西亚商业目录（MyBizList、Malaysia Yellow Pages、SME Corp）经常允许中文描述。用上——大部分对手不会用。
两种语言的评价。客户在 GBP 和其他平台上用混合语言留下的评价，对双语运营来说是很强的真实性信号。
Search Console 里设地理定位。在 GSC 的旧版国际定位工具里把目标国家设为马来西亚（虽然标签写"旧版"但还能用）。如果您的顶级域名是 .com 而不是 .com.my 或 .my，这一项特别重要。
上线前 + 上线后清单
我们给客户上线前后过的完整双语 SEO 清单。
| 阶段 | 项目 | 怎么验证 |
|---|---|---|
| 上线前 | 每种语言有自己的 URL（子文件夹） | 访问 /en/ 和 /zh/，看到不同 URL |
| 上线前 | 每页 <head> 里有 hreflang，含自指向 | 两个版本都看源代码；用 Search Console URL 检查工具核实 |
| 上线前 | 每页 <html lang> 属性正确 | 看源代码；/en/ 和 /zh/ 之间应该不同 |
| 上线前 | 语言切换器用真实 anchor 标签指向另一语言的对应页 | 右键切换器 → 检查 |
| 上线前 | sitemap.xml 列出每页的两种版本，含 hreflang 替代 | 浏览器直接打开 sitemap；XML 验证 |
| 上线前 | JSON-LD 含与页面语言匹配的 inLanguage | 用 Google Rich Results Test 测两个 URL |
| 上线前 | LocalBusiness schema 声明 knowsLanguage | Rich Results Test |
| 上线前 | 中文内容由马来西亚华语母语写手写（不是机器翻译） | 母语读者审稿 |
| 上线后 | 提交 sitemap 到 Search Console | GSC → Sitemaps |
| 上线后 | 设国际定位为马来西亚 | GSC → 旧版工具 → 国际定位 |
| 上线后 | 对重点页面的两种语言版本请求索引 | GSC → URL 检查 → 请求编入索引 |
| 上线后 | 监测国际定位报告里的 hreflang 错误 | GSC → 旧版工具 → 国际定位 → 语言 |
| 上线后 | 用两种语言设置 GBP | business.google.com |
Frequently asked questions常见问题
Subfolder /zh/, subdomain zh.example.com, or query string ?lang=zh — which should I use?子文件夹 /zh/、子域名 zh.example.com、还是参数 ?lang=zh — 该用哪个？
Subfolder is the safest default for Malaysian bilingual sites. URLs like /en/about and /zh/about give Google two distinct addresses for the same logical page, are easy to track in Search Console, and let each language inherit the domain's accumulated authority. Subdomains (zh.example.com) work but Google treats them as separate sites for ranking purposes. Query strings (?lang=zh) are the riskiest — they sometimes get indexed correctly, sometimes get collapsed into one page. If you do use query strings, be very deliberate with hreflang and canonical tags.
马来西亚双语网站，子文件夹是最稳的默认选择。/en/about 和 /zh/about 这样的 URL 给 Google 同一逻辑页面两个明确地址，在 Search Console 里容易追踪，两种语言都继承域名累积的权威值。子域名（zh.example.com）能用，但 Google 在排名时把它们当不同网站。参数字符串（?lang=zh）最冒险——有时被正确索引，有时被合并成一页。非要用参数的话，hreflang 和 canonical 标签必须非常刻意。
Do I need a separate sitemap for each language?每种语言要分开做 sitemap 吗？
Not strictly. One sitemap with hreflang annotations on each URL works fine and is what most bilingual sites use. The advantage of separate sitemaps is cleaner reporting in Search Console — you can see indexing health per language at a glance. For sites with under ~50 pages per language, one combined sitemap is fine; for larger sites where you want per-language visibility, split them.
不强制。一份 sitemap 加上每个 URL 的 hreflang 标记就够用，大部分双语网站都这样做。分开 sitemap 的好处是 Search Console 里报告更干净——可以一眼看到每种语言的索引健康度。每种语言 50 页以下，一份合并 sitemap 就行；大网站要按语言分别监测的，就分开。
Should I write Chinese first and translate to English, or vice versa?该先写中文翻译成英文，还是反过来？
Write each language natively — neither as a translation. The biggest mistake we see Malaysian bilingual sites make is writing English first then running it through translation, producing Chinese that reads awkwardly and feels foreign. Malaysian Chinese readers have a specific register (马来西亚华语) that differs from PRC Chinese. Write the English with English readers in mind, then have a native writer produce the Chinese with Chinese readers in mind — same message, different sentences.
每种语言都要原生写——不要当翻译。马来西亚双语网站最常见的错误就是先写英文然后跑翻译，做出来的中文读起来别扭、感觉外来。马来西亚华语读者有自己的语域（马来西亚华语），跟中国大陆中文不同。英文面向英文读者写，然后让母语写手面向中文读者产出中文——同样的讯息，不同的句子。
Does Google rank Simplified vs Traditional Chinese differently?Google 对简体和繁体中文排名不同吗？
Yes, indirectly. They're treated as different language variants. For Malaysian audiences, Simplified Chinese is the dominant choice — Malaysian schools teach Simplified, and most Malaysian Chinese users search using Simplified characters. Singapore is similar (Simplified). Hong Kong, Taiwan, and parts of the diaspora use Traditional. If your audience is Malaysian-first, use Simplified. If you serve Hong Kong / Taiwan customers significantly, consider a third language variant rather than trying to compromise.
是的，间接的。它们被视为不同语言变体。对马来西亚受众，简体中文是主流选择——马来西亚学校教简体，大部分马来西亚华人用简体字搜索。新加坡类似（简体）。香港、台湾、部分华侨用繁体。如果您的受众以马来西亚为主，就用简体。如果显著服务香港 / 台湾客户，考虑加第三种语言变体，而不是在两者之间妥协。
Should the Chinese version use hreflang zh-CN, zh-SG, zh-MY, or just zh?中文版的 hreflang 该用 zh-CN、zh-SG、zh-MY，还是只用 zh？
For a Malaysian-targeted site, use a combination: declare zh as the primary hreflang (broad targeting), and optionally add zh-MY explicitly to flag Malaysian targeting to Google. Avoid using only zh-CN unless your audience is genuinely China-based — it can suppress your site in google.com.my results. Multiple alternates work too (zh-MY plus zh-SG if you serve both).
面向马来西亚的网站，组合用：把 zh 作为主要 hreflang（广覆盖），可以再额外加 zh-MY 明确告诉 Google 您面向马来西亚。除非受众真的在中国，不要只用 zh-CN——它会压低您在 google.com.my 结果里的排名。也可以用多个替代项（同时服务两边的话，zh-MY 加 zh-SG）。
How do I prove to Google I have a real bilingual audience?怎么向 Google 证明我有真实的双语受众？
The signals Google watches: language toggle gets used, both language URLs accumulate inbound links, Chinese search queries land on the Chinese pages (visible in Search Console's Performance report filtered by query language), and engagement metrics (time on page, bounce rate) are reasonable for both languages. The honest reality is you need real bilingual traffic to prove this — you can't fake it. A solid hreflang setup ensures Google serves the right language; actual rankings then follow real user behaviour.
Google 关注的信号：语言切换器有人用、两种语言的 URL 都累积入站链接、中文搜索查询落到中文页（在 Search Console 的 Performance 报告里按查询语言筛选可见）、两种语言的参与度指标（停留时间、跳出率）都合理。老实说，您需要真实的双语流量来证明这一点——这件事造不了假。扎实的 hreflang 设置保证 Google 把对的语言送给对的人；实际排名跟着真实用户行为走。
