Supported languages

A complete reference of the 32 language codes supported by the Rankability API, including special values, what the language field controls, and practical examples for creating non-English content.

The language field on a content job controls the language used throughout the entire content pipeline. This article lists every supported code and explains how the field works.

What the language field controls

When you set a language code on a job, it affects four stages of the pipeline:

1. SERP results language — The language and locale used when fetching competitor pages from search engines.
2. Brief language — The language the content brief (headings, outline, and recommendations) is written in.
3. Draft language — The language the final article draft is generated in.
4. Entity extraction language — The language used when identifying entities, FAQs, and semantic topics from the research data.

When set to a non-English value (for example "he" for Hebrew), the entire output — headings, title tag, meta description, entities, FAQs, and the draft itself — will be generated in that language.

Special values

Code	Behavior
auto	Auto-detect: uses English for SERP queries with no forced language instruction in prompts. The AI writes naturally based on topic context.
none	No language targeting: same behavior as auto.

If you omit the language field entirely, the default is "en" (English US).

Language reference table

Code	Language
en-US	English (US)
en-GB	English (UK)
ar	Arabic
bn	Bengali
zh	Chinese
cs	Czech
da	Danish
nl	Dutch
tl	Filipino
fi	Finnish
fr	French
de	German
el	Greek
he	Hebrew
hi	Hindi
hu	Hungarian
id	Indonesian
it	Italian
ja	Japanese
ko	Korean
ms	Malay
no	Norwegian
pl	Polish
pt	Portuguese
ro	Romanian
ru	Russian
es	Spanish
sv	Swedish
th	Thai
tr	Turkish
uk	Ukrainian
vi	Vietnamese

Base codes like "en" are also accepted and treated as "en-US".

Practical examples

Creating Hebrew content

curl -X POST https://app.rankability.com/api/agent/v1/copywriter/jobs \
  -H "Authorization: Bearer rk_live_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "topic": "best crm for small business",
    "intent": "discover",
    "mode": "auto",
    "language": "he"
  }'

The SERP research will target Hebrew-language results, and the brief, outline, draft, title tag, meta description, entities, and FAQs will all be generated in Hebrew.

Creating Spanish content

curl -X POST https://app.rankability.com/api/agent/v1/copywriter/jobs \
  -H "Authorization: Bearer rk_live_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "topic": "mejores herramientas seo",
    "intent": "discover",
    "mode": "auto",
    "language": "es",
    "location": "Mexico City, Mexico"
  }'

Combining language with location gives you geo-targeted SERP data and a draft written entirely in Spanish.

Creating Japanese content

curl -X POST https://app.rankability.com/api/agent/v1/copywriter/jobs \
  -H "Authorization: Bearer rk_live_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "topic": "SEO best practices",
    "intent": "educate",
    "mode": "auto",
    "language": "ja"
  }'

Even though the topic is entered in English, the output will be fully in Japanese. The system fetches Japanese SERP results and generates all content in Japanese.

How non-English content works

When a non-English language is selected:

• SERP queries are adapted to target that language and locale.
• Competitor pages may still be in English (especially for niche topics), but the AI uses them as reference material and produces the final output in your target language.
• Entity extraction identifies entities relevant to the target language and cultural context.
• FAQs and structured data (JSON-LD schema) are generated in the target language.

This means you can use English-centric keyword research to generate content in any of the 32 supported languages.

Related articles

• Creating content jobs — Full reference for the POST /copywriter/jobs endpoint, including the language field.
• Getting started with the API — End-to-end walkthrough of your first API content job.