lucid.page When two language annotations lead to one page
Text size
Read time2 min

# When two language annotations lead to one page

By Ronald McCormick for the Zoechip campaign · 20 November 2026

Contents

A spreadsheet of language annotations can overcount the number of editions a site offers. To see how that happens, compare three lines in the HTML of the Zoechip homepage. Zoechip is a film and television site that advertises third-party streams. This exercise uses its page markup.

Declaration Value Destination path
Canonical URL self-reference /
Alternate language en /
Fallback x-default /

The homepage returned HTTP 200 on 20 November 2026. All three declarations pointed to the same absolute URL, including the trailing slash. The English annotation and the fallback therefore give two language annotations and one distinct destination. An inventory that counted rows as editions would report two.

# Reproduce the count

Open the page in a browser, open the developer console and run this read-only snippet. It prints the declared language alongside the resolved destination, then counts distinct destinations.

js
const alternates = Array.from(
  document.head.querySelectorAll('link[rel~="alternate"][hreflang]'),
  link => ({ language: link.hreflang, destination: link.href })
);
console.table(alternates);
console.log({
  annotations: alternates.length,
  destinations: new Set(alternates.map(link => link.destination)).size
});

The selector excludes the canonical link because it serves a different purpose. When applying this check to another site, keep the complete URL for comparison. A language variant may differ only in its hostname, path, or query string.

The fallback tells a search engine which destination the site designates for an unmatched language. It can share a destination with an explicitly named language. Establishing which translations are available takes a separate check of the content at each distinct destination. Google’s guide to localized versions

End