International SEO · language source evidence

Check HTML language, Content-Language and hreflang signals

Inspect a public page for its HTML language, text direction, UTF-8 declaration, HTTP and meta Content-Language values, hreflang alternates, self-reference, x-default, canonical context, and crawl/indexability context.

FETCHLIVE HTMLLANGUAGEBCP 47EXPORTCSV + JSON

Evidence boundary: OpenWebmaster inspects one bounded live source-level preflight response. It does not detect translation quality, negotiate locale variants, render JavaScript, inspect personalized locale routing, prove Google-selected language, prove indexing, estimate rankings, traffic, conversions, or cause.

Ready for a public localized page.

No sample detected language, translation-quality verdict, locale-routing result, Google-selected language, ranking impact, traffic claim, or manufactured international SEO score appears before a live page is checked.

International SEO workflow

Make the page language obvious before you scale localized content

Declare the document language

The HTML lang value helps browsers, assistive technology, translation tools, and search systems interpret the page. Use a valid BCP 47 language tag that matches the main visible content.

Keep alternates complete

When a page has translated or regional equivalents, hreflang should point to the equivalent URLs, include a self-reference, and avoid duplicate language values.

Check the final page

Redirects and canonical tags can change which URL is actually reviewed. Inspect the terminal localized page, then compare every language variant with the hreflang manager.