imbahub
Menu +
EN
Talk to us
IMBAHUB / Knowledge & guides

Review page relationships before reviewing tags.

A hreflang review starts with an editorial question: which pages help the same audience complete the same task in different languages? Once that relationship is confirmed, check URLs, self references, return links and fallback behaviour.

1. Build a language matrix around each page’s purpose

Record page ID, language, URL, search intent and status. Mark each genuine equivalent and why the pages belong together. Leave the cell empty if a page is missing, still a draft or serves a different purpose.

This prevents the language selector and hreflang from turning a topic guess into a technical fact. Start with a small group, such as the homepage or a service page, then expand once the relationships are reviewed.

2. Check every annotation in both directions

Each page in the group should list itself and the other real alternatives. Open every destination and check that it links back. Google’s guidance notes that missing return links can prevent annotations from being processed.

Use fully qualified HTTPS URLs and language or region codes that match the content. Check spelling, trailing slashes and that each address reaches the intended page without a redirect chain.

3. Review canonical as a separate signal

Inspect each page’s HTML and compare its canonical with its own preferred URL. A language version should not point to Swedish just because it came first. An exception needs a specific reason and must agree with the indexing decision.

The sitemap and internal links should use canonical URLs. Hreflang does not replace canonical, and a sitemap does not replace useful internal links or a working language switcher.

4. Test fallback and revisit changes

Switch languages on desktop and mobile. If an equivalent page exists, the visitor should reach it. If it does not, the fallback should be predictable and must not be presented as a translation.

Update the matrix when a page moves, is removed or gains a language version. Record the decision and retest the whole group so old return links do not survive a partial change.

TestQuestion
RelationshipDo the main content and user task genuinely correspond?
Return linkDoes each alternative link back to the group?
CanonicalDoes the page identify its intended canonical URL?
SwitchingDoes the equivalent or clear fallback work on mobile?

Sources and further reading

Questions, answered

Must every URL exist in every language?

No. Connect only finished, relevant alternatives. A partial but accurate group is better than invented translations.

Are HTML hreflang and sitemap hreflang different signals?

Google describes HTML, HTTP headers and sitemaps as equivalent methods. Choose one that is practical to maintain and avoid unnecessary duplication.

What if two pages do not link back to each other?

First confirm that they are genuine alternatives. Add the missing return relationship only if the equivalent page exists.

IMBAHUB

What would you like to make possible?

Choose one language group and complete the matrix before the next release.

Talk to us
Product interface set to English in an isolated environment with fictional English demo content.

Product interface set to English in an isolated environment with fictional English demo content.