Internationalization Check
developer/v1/domain/i18nChecks internationalization setup including hreflang tags, language attributes, charset declaration, and RTL (right-to-left) support for multi-language websites.
What It Does
Analyzes the page for i18n configuration: hreflang tag presence, count, and proper x-default usage; HTML lang attribute validity against BCP 47; Content-Language header consistency; charset declaration (UTF-8 verification); and RTL support via dir attributes and CSS rules. Detects language switcher UI elements (informational, not scored). Returns a score with specific recommendations and a confidence indicator reflecting result reliability.
Why It's Useful
Incorrect hreflang tags cause search engines to show the wrong language version to users, losing international traffic. Missing or invalid lang attributes affect screen readers and translation tools. Proper i18n is essential for global reach.
Use Cases
International SEO Audit
Verify hreflang tags correctly map language/region variants to prevent ranking cannibalization.
Ensure the right language page ranks in each country's search results.
Localization QA
Validate that translated pages have proper lang attributes and hreflang cross-references.
Confirm technical setup matches localization strategy.
Accessibility Validation
Check that the lang attribute is set correctly for screen readers and browser translation.
Improve accessibility for users relying on language detection.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
domain | string | Required | The domain to check internationalization forExample: example.com |
Response Fields
| Field | Type | Description |
|---|---|---|
domain | string | The checked domain |
hreflang | object | Hreflang tags: count, languages, x-default, issues |
language | object | HTML lang attribute, validity, Content-Language header |
charset | object | Charset declaration and UTF-8 verification |
rtlSupport | object | RTL detection, dir attribute, CSS RTL support |
languageSwitcher | object | Language switcher UI detection (informational) |
score | number | Internationalization score 0-100 |
grade | string | Letter grade A-F |
gradeDescription | string | Human-readable grade description (e.g., "Good - adequate with room for improvement") |
recommendations | array | Specific i18n fixes to implement |
confidence | object | Result confidence indicator: level (high/medium/low) and limitations list |
Code Examples
curl "https://api.edgedns.dev/v1/domain/i18n" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d "domain=example.com"const response = await fetch(
'https://api.edgedns.dev/v1/domain/i18n?domain=example.com',
{
headers: {
'Authorization': 'Bearer YOUR_API_KEY'
}
}
);
const data = await response.json();
console.log(data);import requests
response = requests.get(
'https://api.edgedns.dev/v1/domain/i18n',
headers={'Authorization': 'Bearer YOUR_API_KEY'},
params={
'domain': 'example.com'
}
)
data = response.json()
print(data)Read the full Internationalization Check guide
Why it matters, real-world use cases, parameters, response fields, and how to call it from Claude, ChatGPT, or Gemini via MCP.
Read the guide →Related Endpoints
External References
Learn more about the standards and protocols behind this endpoint.
Try This Endpoint
Test the Internationalization Check endpoint live in the playground.