Practical Lens 34: Language switchers shape the site graph

Why this happens

• Language switchers often link to language homepages instead of equivalent page-level translations.
• Some templates generate different switcher targets on different sections of the website.
• Internal links, sitemap URLs, canonical tags and hreflang annotations can describe different structures at the same time.

What this usually indicates

• Variant drift: English, Slovak, Czech or other variants develop different internal paths.
• Generic language targets: A page-level switcher sends users and bots to /sk/ instead of the matching Slovak page.
• Broken crawl path: Bots cannot move consistently between equivalent language pages.
• Split site graph: Each language version looks like a different website structure rather than one connected entity.

What to verify (evidence-only)

• Does the language switcher link to the equivalent page, not only to a language homepage?
• Do switcher links match the URLs declared in hreflang?
• Are switcher links crawlable as normal <a href> links?
• Do all language variants expose the same primary navigation structure where appropriate?
• Do crawler user agents receive the same switcher links as normal users?

Terminal check example

Replace example.com with the audited domain. The goal is to verify the crawler-visible signals, not to assume the diagnosis.

curl -s https://example.com/en/page | grep -i 'href=.*\/sk'
curl -s https://example.com/sk/page | grep -i 'href=.*\/en'
curl -s https://example.com/en/page | grep -i 'hreflang'
curl -L -s -o /dev/null -w '%{url_effective}
' https://example.com/sk/page

PowerShell check example

Use this on Windows environments to inspect links, resolved URLs and machine-readable annotations.

(Invoke-WebRequest -Uri 'https://example.com/en/page').Links | Where-Object {$_.href -match '/sk'} | Select-Object href, innerText
(Invoke-WebRequest -Uri 'https://example.com/sk/page').Links | Where-Object {$_.href -match '/en'} | Select-Object href, innerText
(Invoke-WebRequest -Uri 'https://example.com/en/page' -MaximumRedirection 5).BaseResponse.ResponseUri.AbsoluteUri