AdSense unsupported language — which languages are eligible
AdSense only serves ads in languages it supports, and the list is published by Google rather than inferred. If your language genuinely is not on it, there is no fix — the site is not eligible until Google adds support. More often the site is in a supported language and something has told the reviewer otherwise.
How to fix it
- Check the current list rather than a blog post. Google maintains the supported-language list and changes it. Any list you find republished elsewhere is a snapshot of whenever it was copied.
- Declare the language in your HTML. Set lang on the html element to the language you actually publish in. A site left at the theme default of lang="en" while publishing in another language is describing itself incorrectly.
- Decide what the primary language is. A site that mixes languages page by page is hard to classify. Pick one per site, or separate them properly by subdomain or directory with correct hreflang.
- Remove auto-translated sections. Machine-translated duplicates of your own pages add a second problem — duplicate or low-value content — on top of the language question.
The only rejection with no argument on the other side
Every other item in this list involves a judgement about your site. This one is a
capability limit. AdSense matches ads to content, and it can only do that in
languages it has advertiser inventory and classification for. If your language is
not supported, there is no appeal, because nothing has been decided against you.
The practical consequence is that this is the one rejection where the answer may
genuinely be "wait", and where no amount of improving the site changes anything.
Check Google's list, not a copy of it
The supported-language list is maintained by Google and it changes — languages
have been added over the years. Any list you find republished on another site,
including the date this page was written, is a snapshot of whenever the author
copied it.
This is precisely the kind of detail that goes stale without anyone noticing, so
it is worth going to the source rather than trusting a summary.
Most flagged sites are in a supported language
If your language is on the list and you were flagged anyway, the site is probably
describing itself incorrectly. Two causes account for nearly all of it.
The declared language is wrong. A theme installed with lang="en" and never
changed, on a site publishing in another language entirely. Every automated
check — AdSense, search engines, screen readers — reads that attribute and
believes it. Setting it correctly takes one line.
The site mixes languages. Half the pages in one, half in another, sometimes
both within a page. Classification becomes a guess, and the guess may not be the
one you want.
If you genuinely publish in more than one language, separate them properly:
different subdomains or directories, correct hreflang annotations, and a
consistent language per URL. That is more work than a language switcher widget,
and it is the arrangement that actually classifies cleanly.
Translation is not a shortcut
The tempting response is to run the site through a translation tool and publish
an English version. This trades one problem for a worse one.
Machine-translated duplicates of your own pages are, from a reviewer's
perspective, both duplicate content and low-value content: they add nothing that
was not already published, and they read as machine output. You would move from
"not eligible yet" to "rejected for content quality", which is a harder position.
A genuinely written section in a supported language, kept separate and properly
annotated, is a real option. A machine translation of everything is not.
Frequently asked
- Which languages does AdSense support?
- Google publishes and updates the list, and it has grown over time, so the only reliable source is Google's own documentation. Any list republished on another site is a snapshot from whenever the author copied it, and this is exactly the kind of detail that goes stale silently.
- My language is supported. Why was I flagged?
- Usually because the site declares itself as something else. A theme left at lang="en" while publishing in another language tells every automated check the wrong thing. Mixed-language sites are the other common case — if half the pages are in one language and half in another, classification becomes a guess.
- Can I publish in an unsupported language and serve ads anyway?
- No. Ads are matched to content, and without language support there is no inventory to match. This is a capability limit rather than a policy judgement, and there is nothing to appeal.
- Should I translate my site into English to qualify?
- Only if you can do it properly. Machine-translated copies of your own pages create duplicate content and read as low-value, which trades an eligibility problem for a content one. A genuinely written English section, kept separate with correct hreflang, is a different proposition.
Check whether this is still blocking you
The free Monetific checker tests your site against this and every other mechanical requirement, and tells you what is still outstanding before you re-apply.
Run the free check