LLMention
← All 40 checksInternational Readiness

Alternate language versions are declared

One of 40 checks the scanner runs. This one is worth 2 points inside the International Readiness dimension, which carries 3% of the total score.

Browse sections

What does this check look at?

At least 2 distinct hreflang language codes are declared. Repeated attributes for the same language do not count, and x-default is a default marker rather than a language, so a single-language site declaring `en` plus `x-default` does not satisfy this. A page that declares no hreflang at all is not scored on this rule: with one page fetched, the scanner cannot tell a single-language site from a multilingual one that has not declared its versions, so absence is marked not applicable rather than failed. Declaring exactly one code still fails.

The codes are read from the attributes and the pages they point at are not fetched, so two hreflang tags naming language versions that were never built satisfy this check. It is a declaration check, and like the markdown alternate above it, it is one this scanner cannot close from a single fetch. The rule changed on 2026-10-23: before that date, no declaration was scored as a failure, which cost every single-language site 2 points for a question it was never asked. The change is recorded on /methodology/, which is where a reader should check it rather than here.

How do I fix it?

  1. Declare hreflang for each language version you actually serve, so every version can be retrieved in its own market.

Why is it worth 2 points?

Points are relative weights inside a dimension, and a dimension's weight decides how much of the total it can move. The reasoning for this dimension's weight is published rather than asserted:

DimensionInternational Readiness — 3% of the total score
Points for this check2 of 3 in this dimension
Worth at most2.0 of the 100 points

Low for a single-market site, and the first thing to fix if you serve more than one language.

Which dimension does this belong to?

International Readiness — 3% of the total score, decided by 2 published rules.

Language and region markup decides which language market a page can be retrieved in at all.

None of the five guides covers this rule, which is why this page shows the fix in full rather than pointing at one.

What else is measured in this dimension?

How do I see my own result?

Run a scan on your own domain. The report lists every failed check with the evidence that produced it, so you can tell a real failure from a check that does not apply.

Run a free GEO audit on your own site →

The full method, including the dimensions that are deliberately weighted low and the parts of a picture a single-URL scan cannot see, is on the methodology page.

Questions about this rule

What does this check look at?

At least 2 distinct hreflang language codes are declared. Repeated attributes for the same language do not count, and x-default is a default marker rather than a language, so a single-language site declaring `en` plus `x-default` does not satisfy this. A page that declares no hreflang at all is not scored on this rule: with one page fetched, the scanner cannot tell a single-language site from a multilingual one that has not declared its versions, so absence is marked not applicable rather than failed. Declaring exactly one code still fails.

Why does this dimension carry 3% of the score?

Low for a single-market site, and the first thing to fix if you serve more than one language.

Evidence and sources

GEO can boost visibility by up to 40% overall in generative engine responses, and in the paper's Table 1 the best of the tested methods improve on the no-optimization baseline by 41% and 28%. — Generative Engine Optimization, KDD 2024

This rule is applied by the scanner and published in the rule set it is read from, so the condition on this page is the condition the scan tests rather than a summary of it.

Primary sources