What is a self-referencing hreflang tag?

A self-referencing hreflang tag is a rel=alternate hreflang link element on a page that points back to the page itself. For example, the English version of a page must include hreflang="en" pointing to its own URL, in addition to listing all other language alternates. Google requires every URL in a hreflang group to point back to all the others — including itself — for the cluster to be considered valid.

What happens if I omit the self-referencing hreflang?

Google may treat the entire hreflang cluster as broken. Without the self-reference, the return-tag check fails: each language version cannot confirm that the others list it back. Google often falls back to ignoring the hreflang signals entirely, which means the wrong language version may show in search results, and your geographic targeting collapses.

Do self-referencing hreflang and canonical tags conflict?

No. The self-referencing hreflang tag and the self-referencing canonical tag complement each other. The canonical tells Google which URL is the master version of this content; the hreflang tells Google which language and regional variant this URL serves. Each language version should have a self-referencing canonical (pointing to itself) AND be included in the hreflang set with a self-reference.

By SitemapFixer Team

Updated April 2026

Self-Referencing Hreflang: The Return Tag Rule Explained

Audit your hreflang setup freeScan hreflang free

Of all the rules governing hreflang implementation, the self-referencing requirement is the one most commonly missed in real-world deployments. The premise sounds counterintuitive at first: why does the English version of a page need to declare itself as the English version, when the URL it sits on is already the English page? The answer is buried in how Google validates hreflang clusters — and getting it wrong is the single fastest way to have all your hreflang signals silently dropped. This guide explains exactly what self-referencing hreflang means, why Google requires it, how to implement it across HTML, HTTP headers, and XML sitemaps, and the patterns of failure that show up most often in audits.

What Self-Referencing Hreflang Actually Means

A self-referencing hreflang tag is a <link rel="alternate" hreflang="..."> declaration on a page where the href attribute points back to the URL of that same page. If https://example.com/en/pricing is your English pricing page, the self-referencing hreflang on that page is <link rel="alternate" hreflang="en" href="https://example.com/en/pricing">. The English page is declaring, in machine-readable terms, that it is the English version.

The rule is: every page that is part of a hreflang cluster must include itself in the list of alternates, not just the other languages. If you have five language versions, each of those five pages must output the same set of five hreflang links — and that set must include the page's own URL with its own language code. Skipping the self-reference because "the page already knows what language it is" is the most common implementation mistake.

To put it precisely: the hreflang group is a flat, complete list of every language/regional variant in the cluster. The list does not change depending on which page is rendering it. Page A, page B, page C — they all output the identical hreflang block, and that block names all of them by language code, including the one currently being viewed.

Why Google Requires the Return Tag

The technical name for this rule in Google's documentation is the "return tag" requirement. Quoting Google's guidance directly: if page X links to page Y via hreflang, page Y must link back to page X. This is a bidirectional confirmation — it prevents a single page from unilaterally claiming a relationship with another page that hasn't agreed to the relationship.

The self-reference is a special case of this same rule. The return tag check expects every URL named in the hreflang group to confirm membership in the group by also listing itself as part of it. From Google's perspective, a page that lists four other languages but not itself is incomplete: there are four declared members, but the page hosting the declaration has not asserted its own membership. The cluster fails the integrity check.

This is why omitting self-references doesn't just "leave one language untargeted" — it can cause Google to drop the entire cluster. A broken return tag chain is treated as evidence that the hreflang configuration is unreliable across the board, not just for the one missing entry.

Correct Self-Referencing Hreflang in the HTML Head

Here is the canonical pattern for a five-language site (English, Spanish, French, German, Japanese), as rendered on the English page. The same block must be output verbatim on every other language version of the same content:

<!-- Rendered inside <head> on https://example.com/en/pricing -->
<link rel="alternate" hreflang="en" href="https://example.com/en/pricing" />
<link rel="alternate" hreflang="es" href="https://example.com/es/pricing" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/pricing" />
<link rel="alternate" hreflang="de" href="https://example.com/de/pricing" />
<link rel="alternate" hreflang="ja" href="https://example.com/ja/pricing" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/pricing" />

Notice the first line: the English page declares hreflang="en" pointing to its own URL. That is the self-reference. Without that line, the cluster would name four other languages but not the page outputting the declaration — which is exactly the broken pattern Google penalises.

Now compare this to the same block as it must appear on the Spanish page, https://example.com/es/pricing. The block is identical — the order of entries doesn't change, the URLs don't change, only the rendering page changes:

<!-- Rendered inside <head> on https://example.com/es/pricing -->
<link rel="alternate" hreflang="en" href="https://example.com/en/pricing" />
<link rel="alternate" hreflang="es" href="https://example.com/es/pricing" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/pricing" />
<link rel="alternate" hreflang="de" href="https://example.com/de/pricing" />
<link rel="alternate" hreflang="ja" href="https://example.com/ja/pricing" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/pricing" />

The Spanish page's self-reference is the second line, where hreflang="es" points back to /es/pricing. Every page renders the same complete list, and each finds itself somewhere in that list.

What a Missing Self-Reference Looks Like

This is the most common broken pattern. The developer reasons: "the page already knows it's English, so I only need to point to the other languages." The result is a hreflang block that fails the return-tag check on every page in the cluster:

<!-- BROKEN: Rendered on https://example.com/en/pricing -->
<!-- The English self-reference is missing -->
<link rel="alternate" hreflang="es" href="https://example.com/es/pricing" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/pricing" />
<link rel="alternate" hreflang="de" href="https://example.com/de/pricing" />
<link rel="alternate" hreflang="ja" href="https://example.com/ja/pricing" />

<!-- BROKEN: Rendered on https://example.com/es/pricing -->
<!-- The Spanish self-reference is missing -->
<link rel="alternate" hreflang="en" href="https://example.com/en/pricing" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/pricing" />
<link rel="alternate" hreflang="de" href="https://example.com/de/pricing" />
<link rel="alternate" hreflang="ja" href="https://example.com/ja/pricing" />

From the Spanish page's perspective, when Googlebot crawls it, the page lists English, French, German, and Japanese as alternates. Then Googlebot fetches each of those alternates to confirm the return tag. The English page lists Spanish, French, German, Japanese — but not English itself. Googlebot now has an inconsistency: the cluster declares five languages but the English URL never confirms it's the English version. Google often resolves this by discarding the hreflang signals entirely.

An almost-as-bad variant is putting the self-reference on only one language version (usually the one the developer was looking at while building the feature). This produces an asymmetric cluster where some pages pass the return tag check and others fail. Search Console will report "No return tags" errors on the failing pages.

Self-Referencing Hreflang in XML Sitemaps

For large multilingual sites, declaring hreflang in the sitemap is more maintainable than per-page HTML output. The same self-reference rule applies: every <url> entry must include itself in its <xhtml:link> alternates list.

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <url>
    <loc>https://example.com/en/pricing</loc>
    <xhtml:link rel="alternate" hreflang="en" href="https://example.com/en/pricing" />
    <xhtml:link rel="alternate" hreflang="es" href="https://example.com/es/pricing" />
    <xhtml:link rel="alternate" hreflang="fr" href="https://example.com/fr/pricing" />
    <xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/en/pricing" />
  </url>
  <url>
    <loc>https://example.com/es/pricing</loc>
    <xhtml:link rel="alternate" hreflang="en" href="https://example.com/en/pricing" />
    <xhtml:link rel="alternate" hreflang="es" href="https://example.com/es/pricing" />
    <xhtml:link rel="alternate" hreflang="fr" href="https://example.com/fr/pricing" />
    <xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/en/pricing" />
  </url>
  <url>
    <loc>https://example.com/fr/pricing</loc>
    <xhtml:link rel="alternate" hreflang="en" href="https://example.com/en/pricing" />
    <xhtml:link rel="alternate" hreflang="es" href="https://example.com/es/pricing" />
    <xhtml:link rel="alternate" hreflang="fr" href="https://example.com/fr/pricing" />
    <xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/en/pricing" />
  </url>
</urlset>

Each <url> block has three xhtml:link entries — and the URL in <loc> always appears as one of them. The English URL block contains an hreflang="en" entry pointing back to the English URL. Same for Spanish and French. This is the sitemap equivalent of the HTML self-reference, and it is required.

One advantage of the sitemap approach: you can validate self-referencing hreflang programmatically before submitting. A simple parser can check that every <loc> URL appears in its own block's xhtml:link list. See the hreflang sitemap guide for full implementation patterns.

Self-Referencing Hreflang via HTTP Link Header

For non-HTML resources — PDFs, images served at canonical URLs, or other binary files — you cannot embed <link> elements in a <head>. The HTTP Link response header is the alternative. The self-reference rule still applies.

# HTTP response for https://example.com/en/whitepaper.pdf
HTTP/1.1 200 OK
Content-Type: application/pdf
Link: <https://example.com/en/whitepaper.pdf>; rel="alternate"; hreflang="en",
      <https://example.com/es/whitepaper.pdf>; rel="alternate"; hreflang="es",
      <https://example.com/fr/whitepaper.pdf>; rel="alternate"; hreflang="fr",
      <https://example.com/de/whitepaper.pdf>; rel="alternate"; hreflang="de",
      <https://example.com/en/whitepaper.pdf>; rel="alternate"; hreflang="x-default"

# Nginx configuration to emit the header for the English PDF:
location = /en/whitepaper.pdf {
  add_header Link '<https://example.com/en/whitepaper.pdf>; rel="alternate"; hreflang="en", <https://example.com/es/whitepaper.pdf>; rel="alternate"; hreflang="es", <https://example.com/fr/whitepaper.pdf>; rel="alternate"; hreflang="fr", <https://example.com/de/whitepaper.pdf>; rel="alternate"; hreflang="de"';
}

The English PDF's response header includes itself with hreflang="en" as the first entry. Each language version of the PDF must serve its own complete Link header, and that header must include the URL serving the response. The same return-tag logic Google applies to HTML pages applies here.

Combining Self-Reference with x-default

The x-default hreflang value designates a fallback language for users whose browser locale doesn't match any declared variant. It is not a substitute for the self-reference — both must coexist.

Common confusion: developers see x-default on their English page and assume it counts as the English self-reference. It does not. x-default is a separate semantic — it tells Google "this is the page to show if no other language matches" — while hreflang="en" tells Google "this is the English-language version." The English page typically needs both:

<!-- Both entries point to the same URL but serve different roles -->
<link rel="alternate" hreflang="en" href="https://example.com/en/pricing" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/pricing" />

The en entry satisfies the return-tag requirement. The x-default entry tells Google to use this URL as the fallback for unmatched locales. They are independent declarations on the same URL, and you need both for a properly-configured English-fallback site. For deeper coverage of how hreflang interacts with canonical, see the hreflang and canonical guide.

Common Self-Referencing Hreflang Mistakes

Self-reference URL doesn't match the canonical URL. If the page renders at https://example.com/en/pricing/ (with trailing slash) but the self-reference points to https://example.com/en/pricing (without trailing slash), Google sees a URL mismatch. The return-tag check fails because the URL listed in the cluster does not exactly match the URL Google crawled. Always use the exact canonical URL in the self-reference, character-for-character.

Self-reference points to a redirected URL. If https://example.com/en/pricing 301 redirects to https://example.com/en/plans, but your hreflang self-reference still names the old URL, the cluster is broken. Update self-references whenever you change a URL — and remember that the corresponding entry on every other language page also needs to be updated.

Self-reference uses the wrong language code. The self-reference must use the language code that matches the page's actual language. A common mistake is copy-pasting the hreflang block across language directories without updating which entry points to self. The result: the Spanish page has hreflang="en" pointing to the Spanish URL, which Google reads as "the Spanish URL is the English version." This is worse than missing entirely — it actively misleads Google's language detection.

Self-reference exists in HTML but not in the sitemap (or vice versa). If you declare hreflang in both places, they must agree. Conflicting declarations across HTML and sitemap can cause Google to discard one or both. Pick one source of truth — usually the sitemap for large multilingual sites, HTML head for smaller ones — and stick to it.

Self-reference uses an absolute path instead of a fully-qualified URL. Hreflang requires absolute URLs with protocol and domain. href="/en/pricing" is invalid. href="https://example.com/en/pricing" is required. This is one of the most frequent hreflang errors caught in audits.

The Five-Language Hreflang Audit Table

For a 5-language site, a quick audit pattern is to build a 5x5 matrix and check each cell. Rows are the page being audited; columns are the alternates each page should list. The diagonal is the self-reference. Every cell — including the diagonal — must be filled in.

Page \ Alternate listed       en    es    fr    de    ja
---------------------------------------------------------
/en/pricing  (English)         [SELF] yes   yes   yes   yes
/es/pricing  (Spanish)         yes  [SELF]  yes   yes   yes
/fr/pricing  (French)          yes   yes  [SELF]  yes   yes
/de/pricing  (German)          yes   yes   yes  [SELF]  yes
/ja/pricing  (Japanese)        yes   yes   yes   yes  [SELF]

Cells on the diagonal = self-references. Must all be present.
Off-diagonal cells = cross-references. Must all be bidirectional.
Total declarations expected per page: 5 (4 alternates + 1 self)

Any empty cell on the diagonal is a missing self-reference. Any asymmetric off-diagonal pair (page A lists page B but page B doesn't list page A) is a missing return tag. SitemapFixer's hreflang audit produces this matrix automatically across all clusters on your site, flagging both missing self-references and missing return tags by URL.

Debugging and Validating Self-Referencing Hreflang

Google Search Console. The International Targeting report (legacy, still active for hreflang) flags "No return tags" errors at the cluster level. Pages reported as missing return tags are typically the ones lacking self-references — Google's nomenclature treats the missing self-reference as a return-tag failure of the cluster itself. Open URL Inspection on a flagged URL and use "View crawled page" to see exactly which hreflang links Google extracted.

Google's Rich Results Test. Paste any URL and check the "HTML" tab. The fully-rendered HTML shows the hreflang block as Googlebot saw it after JavaScript execution. If your self-reference is added by client-side code (e.g., a React effect appending to document.head), confirm here that it is present in the rendered output — Googlebot's first-wave crawl reads raw HTML and may miss client-side additions.

Ahrefs Site Audit. The hreflang report under "Issues" lists pages with "Hreflang return links missing" — this includes pages missing their own self-reference. Ahrefs displays the cluster graph, so you can see which pages are part of a cluster but failing the symmetry check.

Sitebulb hreflang reports. Sitebulb's "International" section produces a per-cluster validity score. Pages missing self-references are flagged with "Missing self-referential hreflang" — the most direct naming of the issue across audit tools.

Manual curl check. A quick command-line check for any single page:

# Verify self-reference exists on a page
URL="https://example.com/en/pricing"
curl -s "$URL" | grep -E 'rel="alternate"[^>]+hreflang' | grep "$URL"
# Empty output = missing self-reference

Implementing Self-Reference Generation in Code

The most reliable way to never miss a self-reference is to generate the hreflang block from a single canonical list of language variants, with the current page's URL always derived from the same source. Build the alternates array first, then render every entry — including the one matching the current locale.

The anti-pattern is conditional logic that says "if not the current language, output a hreflang link." That logic structurally guarantees the self-reference will be missing on every page. Replace it with unconditional output: every locale in the array gets a link, full stop. The page hosting the block will naturally include itself because its own locale is in the array.

For Next.js App Router and similar metadata-driven frameworks, build the alternates.languages object from a constant locale list, then map each locale (including the current one) to its absolute URL. Confirm via view-source on a deployed page that every locale appears in the rendered head, and that the current page's URL appears as one of them. For background on how this fits with the broader hreflang spec, see rel alternate hreflang.

Related Guides

Validate every hreflang cluster on your site

Free analysis in 60 seconds

Analyze My Site Free

Related guides