Yes. Include the current page in its own hreflang alternate set. A self-referencing hreflang entry labels the current URL's language or region alongside its alternatives. It does not replace the entries pointing to the other versions.
The easiest way to avoid omissions is to maintain one shared alternate list for each group of equivalent pages, rather than writing a different list for each translation.
See how the self reference changes with the page
Consider an English setup guide and its German translation. Both pages contain this same block inside the <head>:
<link rel="alternate" hreflang="en"
href="https://example.com/en/setup/">
<link rel="alternate" hreflang="de"
href="https://example.com/de/einrichtung/">
On the English page, the en entry is the self reference and the de entry points to the alternative. On the German page, the de entry is the self reference and the en entry points back to English.
The markup is identical, but each page's relationship to the entries differs. This is why “only link to the other language” is an incomplete implementation.
Fix an alternate only setup
An incorrect English-page setup might contain only this line:
<link rel="alternate" hreflang="de"
href="https://example.com/de/einrichtung/">
Add the missing English entry to that page. Check the German page as well: it needs both entries, not just a link back to English. Correcting one page's self reference does not establish that the other page's annotations are complete.
Self reference and reciprocity address separate checks. The first asks whether a page labels itself. The second asks whether the linked alternative acknowledges the relationship in return. Check both.
Distinguish hreflang from a self canonical
The English guide may also have this canonical tag:
<link rel="canonical"
href="https://example.com/en/setup/">
That tag identifies the preferred URL for canonicalization. It does not declare that the page is English or connect it to the German version. The German page would normally use its own preferred German canonical when both translations are intended for indexing.
A page can therefore have a self canonical and a self-referencing hreflang entry without either being redundant. They describe different relationships.
Maintain the group when another translation is added
When a French guide joins the group, add its entry to the shared list and deploy the revised list to the existing English and German pages as well as the new French page. If you use sitemap annotations instead of HTML, review each relevant sitemap entry for its own URL and the alternatives.
Google's hreflang guidelines describe the complete set and explain how mutually linked subsets may still be processed when full coverage is difficult to maintain. Use that nuance to understand a large site's partial implementation, rather than deliberately omitting self references from a small group.
For an audit, compare the intended URL inventory with what every member actually outputs. The key questions are whether each page appears in its own list, whether equivalent pages return the relationship, and whether the destinations are the intended URLs.

Leave a Reply