AI AI Tools Guidebook
Indie Dev & Website Building

AdSense on Bilingual Sites — The Gotchas No One Tells You

A specific guide to AdSense on English+Chinese (or any bilingual) sites — language detection, RPM differences, policy edge cases, and the structural decisions to make before applying.

Published: Author: AI Productivity Guide Team 🌐 查看中文版本

AdSense was built for single-language sites and most of its documentation assumes that. If you run a bilingual site — English + Chinese, English + Spanish, whatever combo — there are specific traps in approval, ad targeting, language-mismatch ads, and revenue per visitor that the standard guides miss. Here is the bilingual-specific version.

Background

AdSense supports a long list of languages, but the level of support varies. English ad inventory is the largest and pays the most; Chinese ad inventory exists but pays significantly less and has different policy nuances. When you run a bilingual site, you are essentially running two ad markets on one domain — and AdSense’s defaults do not always handle that correctly. The structural decisions you make in URL design, language signaling, and ad placement all affect both approval odds and revenue.

How to tell

  • You run a bilingual site (e.g. /en/ and /zh/ paths) and are applying for AdSense.
  • You are approved but your Chinese pages show English ads (or vice versa).
  • Your Chinese pages have a much lower RPM than your English pages and you want to know if that is normal.
  • You are considering whether to apply with the bilingual domain or split into two separate sites.

Quick verdict

Apply with the bilingual domain — splitting is rarely worth it. Use proper hreflang + lang HTML attribute on each page so AdSense can target ads in the right language. Expect Chinese RPM to be 30-60% of English RPM. Place ad units with language-neutral containers that work for both languages’ typography.

Step by step

  1. Before applying, ensure language signaling is correct. Each page must have <html lang="en"> or <html lang="zh"> matching the page content. AdSense reads this to target ad language.
  2. Ensure hreflang is set up correctly (see the dedicated hreflang article). Bilingual sites without hreflang see worse ad targeting because AdSense cannot reliably detect language alternates.
  3. Apply once for the whole domain. AdSense reviews the site as a unit; your approval covers both language sections. Splitting into two AdSense accounts is unnecessary and creates payout complications.
  4. After approval, monitor ad language in both sections. Open the English section in a private browser and confirm English ads serve; same for Chinese. If you see language-mismatched ads, your lang attribute is probably wrong on those pages.
  5. Compare RPM between sections in AdSense reports. Filter by URL path (/en/ vs /zh/). If Chinese RPM is below 20% of English, double-check that ad inventory is loading correctly — that gap is too wide and suggests a config problem.
  6. For ad placement, use containers that handle both languages’ character widths. Chinese characters are denser than English; an ad slot that fits cleanly in English might cause awkward wrapping in Chinese context. Test on real pages in both languages.

Common pitfalls

  • Using <html lang="en"> on every page including the Chinese ones. AdSense serves English ads on Chinese pages — annoying to users, lower CTR, and a policy-edge issue for “deceptive content matching”.
  • Splitting bilingual content into two separate domains thinking it will “concentrate authority”. This rarely helps and makes AdSense approval, hreflang setup, and content management all harder.
  • Assuming Chinese RPM should equal English. It won’t. Chinese ad inventory is smaller and CPC is typically 30-60% of English equivalents. Plan revenue projections accordingly.
  • Applying for AdSense before hreflang is set up. Bilingual sites without language signaling look like duplicate-content sites to reviewers and approval rates suffer.
  • Using language switchers that change URL parameters (?lang=zh) instead of separate paths (/zh/). Path-based language sections are easier for AdSense and Google to understand. Parameter-based is technically valid but introduces complexity.

Who this is for

Bilingual content site owners — whether English+Chinese, English+Spanish, or any combo — applying for AdSense or already approved and trying to optimize.

When to skip this

Single-language sites — none of these gotchas apply. Or sites where the “bilingual” content is just machine-translated; AdSense reviewers detect this and may reject for low-value content.

FAQ

  • Should I apply with the bilingual domain or split into two sites?: Almost always one bilingual domain. Single-domain approval covers both languages, hreflang ties the language versions together, and SEO authority is shared. Splitting is for very specific cases (e.g. legal entity separation).
  • Why is my Chinese RPM so much lower than English?: Smaller ad inventory and lower CPC in Chinese-language AdSense. A 40-60% gap is normal. A 90%+ gap suggests a setup issue (wrong lang, ads not loading, or geo-targeting misconfigured).
  • Can I run different ad densities per language?: Technically yes, with separate manual ad units conditionally rendered. In practice it is more maintenance than it is worth — use the same density and let RPM differ naturally.
  • Does AdSense have separate policies per country?: The program policies are global, but some content types are restricted in specific regions. For example, certain financial / health topics have stricter standards in some Asian markets. If you write in those areas, check region-specific guidelines.

Tags: #Indie dev #AdSense #Monetization #Bilingual #hreflang

Related Articles