How to use
- Paste each language version with its URL, or choose your build folder and enter its base URL.
- Review the matrix: each alternate's code, target and return-link status, plus canonical conflicts.
- Fix invalid codes, missing self-references and return links, duplicate codes and relative URLs; export the CSV.
Worked example
hreflang="en-UK" is flagged: the region code for the United Kingdom is GB, so it should be en-GB.
Supported formats and limits
| Input | Pasted HTML of one or more pages with their URLs, A folder of HTML files plus the base URL it is published at |
|---|---|
| Output | Pages × languages matrix, Problems per page, Report (CSV) |
| Limits | Folders up to 2,000 HTML pages. Analyses HTML you paste or open. Pages are not fetched (browsers block reading other sites, and this site has no server): copy the page source (Ctrl+U) and paste it. |
| Engine | DOMParser analysis; codes checked against Google's documented subset (ISO 639-1 language, optional script and ISO 3166-1 alpha-2 region, x-default) using the browser's Intl language data |
Limitations
- Return links can only be confirmed for alternate pages you provide.
- hreflang in XML sitemaps and HTTP headers is not read.
Questions
Why is en-UK flagged?
hreflang uses ISO 3166-1 alpha-2 region codes, and the code for the United Kingdom is GB, so the value should be en-GB. The tool suggests the correction for common mistakes such as en-UK and the old iw code for Hebrew.
How are return links checked?
If page A lists page B as an alternate, B should list A too. This can only be confirmed for pages whose HTML you add; alternates you did not provide are counted, not checked. hreflang in sitemaps and HTTP headers is not read.
Privacy
Runs on your device. Files and text are processed in this browser tab and are not uploaded.
See the privacy policy for how toolsdocks handles data.