International Readiness — hreflang and languages per domain

For each domain: declared language, hreflang coverage, x-default, and whether the site is genuinely multilingual. Identifies companies selling across borders, and those doing it wrong.

Identify who sells across borders, and who is doing hreflang wrong.

What you get

One row per domain, with these columns:

• htmlLang
• isMultilingual
• hreflangCount
• hasXDefault
• hasLanguageSwitcher
• hreflangDuplicates

Real output

Measured on https://www.hubspot.com/:

{
  "htmlLang": "en",
  "isMultilingual": true,
  "hreflangCount": 7,
  "hasXDefault": true,
  "hasLanguageSwitcher": true,
  "hreflangDuplicates": 0
}

Input

Give it a list of domains:

{ "domains": ["example.com", "another.com"] }

Or chain it after any actor that produces a list — Google Maps Scraper, a CRM export, a prospect list — by passing that dataset as items and naming the column that holds the website:

{ "items": [{ "title": "Acme", "website": "acme.com" }], "field": "website" }

Domains it could not read

A domain that blocks the scan, times out, or errors comes back with measured: false, a reason, and every data column null — never a zero and never a false.

That matters at bulk. One fabricated false in a sheet of ten thousand rows is worse than a missing row, because nobody audits the row that looks plausible. Filter on measured and you know exactly what you are looking at.

Roughly one site in eight refuses an automated reader.

Notes

• Reads the homepage only, one page per domain.
• Loads each page in a real browser, so it sees client-rendered content.