For sites in more than one language
Check that every language version points at all the others
Read each language version's hreflang tags and confirm they all point at one another.
The problem
hreflang only works when it is reciprocal: the English page lists the German one and the German page lists the English one back. One template that drops a locale, or one market that launches on its own CMS, breaks the set, and search engines go back to guessing which version to show.
How domscout handles it
Two extract fields read every link[rel='alternate'][hreflang] on the rendered page: one collects the language codes and the other the URLs, in the same order. Run the request for each language version, then check that each one lists all the others and itself, and that x-default is there if you use it. Once every page's tags are in one place, the comparison is a few lines of code.
Where it shows up
- A release check across every localised home page.
- An audit when a new market or language launches.
- A check after moving locales between domains or folders.
The request
POST /scrape. extract starts at Pro and costs 2 credits a page. To check many pages in one request, /batch on Business takes up to 100.
Go further
More in SEO and site health: SEO regression checks · Link preview checks · Find every page on a site · Website migration checks · JavaScript SEO checks · Page weight and load metrics · Backlink checks · JSON-LD structured data checks · Website audits for prospects · All use cases
Give your product a browser.
Get clean web content and visual proof into your workflow in minutes.