SEO

Hreflang Checker

Verify correct implementation of your multilingual hreflang tags.

Field note

Read a Hreflang Checker card

  1. 01

    Enter a page URL.

  2. 02

    Run the check. The page is not downloaded.

  3. 03

    Read the language, URL, and reciprocal columns.

  4. 04

    View the live source for link rel alternate tags before you change them.

Detail

Labels Hreflang Checker prints

TermMeaning
hreflangA link relation that pairs a language code with a URL.
ReciprocalEach alternate URL points back to the others.
x-defaultThe fallback URL when no listed language matches.
link rel alternateThe HTML element that carries hreflang.
Language codeA tag such as en or en-PK. The sample does not read yours.

Read this

A Hreflang Checker walkthrough

Input

Type https://example.com/pricing. The table shows language rows and reciprocal notes that were not parsed from example.com.

What you should see

View source and search for hreflang. Those link tags are the ones to fix. Use the hreflang generator when you are ready to write new tags.

On this tool

Under the Hreflang Checker labels

Reciprocal hreflang means each language URL points back to the others. A missing return tag is a common break in multilingual setups. This screen shows that kind of table without downloading the URL.

Reciprocal hreflang means each language URL points back to the others. A missing return tag is a common break. This screen shows that kind of column without opening the host. Confirm tags in the page source.

Language is one of the values Hreflang Checker puts on screen. hreflang carries a language or language-region code. The sample rows invent codes for the URL you typed. Those codes are not read from your link tags.

Read URL column on its own before you mix it with the other rows. Each alternate points at the URL of that version. The sample fills URLs locally. Do not redirect a locale because a sample URL looked wrong.

Reciprocal note answers a narrower question than the headline number. Each version should point back. The note is part of the sample table. A missing return tag has to be seen in the live HTML.

Treat x-default as a label with a specific job. x-default is the fallback when no language matches. The sample may or may not show it. Add x-default in the generator when you have a real fallback URL.

The Empty state line is worth a full stop. A checker should say when it found nothing. An empty message here is not a crawl result. Look at the live head anyway.

An empty state can say no rows were produced. That empty state is still not a crawl of your head. Generate real tags with the hreflang generator, then paste them into each language version.

If you remember one sequence from Hreflang Checker, remember the fields in the order they change a decision. Language matters because hreflang carries a language or language-region code. In practice, The sample rows invent codes for the URL you typed. The mistake to avoid is this: Those codes are not read from your link tags. URL column matters because Each alternate points at the URL of that version. In practice, The sample fills URLs locally. The mistake to avoid is this: Do not redirect a locale because a sample URL looked wrong. Reciprocal note matters because Each version should point back. In practice, The note is part of the sample table. The mistake to avoid is this: A missing return tag has to be seen in the live HTML. x-default matters because x-default is the fallback when no language matches. In practice, The sample may or may not show it. The mistake to avoid is this: Add x-default in the generator when you have a real fallback URL. Empty state matters because A checker should say when it found nothing. In practice, An empty message here is not a crawl result. The mistake to avoid is this: Look at the live head anyway. After that, the checks are simple. You did not edit locales from the sample rows. You did not trust the reciprocal note. You planned to view source. x-default will be checked on the live pages. The generator is the place to write tags, not this table.

The worked example for Hreflang Checker, read as one scene, is this. Type https://example.com/pricing. The table shows language rows and reciprocal notes that were not parsed from example.com. View source and search for hreflang. Those link tags are the ones to fix. Use the hreflang generator when you are ready to write new tags.

Final notes for Hreflang Checker, written as decisions rather than as a table. When Language is in front of you, decide using this: hreflang carries a language or language-region code. Those codes are not read from your link tags. When URL column is in front of you, decide using this: Each alternate points at the URL of that version. Do not redirect a locale because a sample URL looked wrong. When Reciprocal note is in front of you, decide using this: Each version should point back. A missing return tag has to be seen in the live HTML. When x-default is in front of you, decide using this: x-default is the fallback when no language matches. Add x-default in the generator when you have a real fallback URL. When Empty state is in front of you, decide using this: A checker should say when it found nothing. Look at the live head anyway. Then apply the checks without skipping one. You did not edit locales from the sample rows. You did not trust the reciprocal note. You planned to view source. x-default will be checked on the live pages. The generator is the place to write tags, not this table.

Keep Hreflang Checker as this step only. When the job moves on, the Hreflang Generator is the next page: Hreflang Generator builds alternate link tags from one row per language, each with a URL, a language, and an optional region. The Robots.txt Generator covers a different piece of the same work: Robots.txt Generator builds a robots.txt file from an allow or disallow default, optional paths, a crawl delay, and a sitemap URL.

Where Hreflang Checker fits

Hreflang Checker asks for a page URL and then lists language rows with a reciprocal note. It is a sample screen for people learning the shape of hreflang results. The URL is not fetched, so the rows are not the live tags from that host.

The language table is a sample. This page does not fetch the URL, so the rows are not the live link rel alternate tags.

What Hreflang Checker returns

  • The columns match a reciprocal audit: language, URL, and a return note.
  • You can learn the failure mode without touching production.
  • The URL is not fetched.

Before you trust Hreflang Checker

  • You did not edit locales from the sample rows.
  • You did not trust the reciprocal note.
  • You planned to view source.
  • x-default will be checked on the live pages.
  • The generator is the place to write tags, not this table.

Easy to misread Hreflang Checker

Adding tags to match the sample rows

The rows are not your locales.

Trusting a reciprocal pass

The note was not computed from your HTML.

Ignoring x-default on the live site

This table does not prove the fallback exists.

Fetching in your head

The URL stayed in the browser.

From the form

Hreflang Checker limits

Does the hreflang checker open the page?

No. The rows are shown in the browser and the URL is not fetched.

What is the reciprocal column?

A note in the sample about whether a row points back. It is not a live check.

How do I see the real tags?

View the page source and look for link rel alternate.

Where do I write new tags?

Use the hreflang generator, then paste the tags into each version’s head.

Field note

After Hreflang Checker

Write down the hostname only. Hreflang Checker did not look it up. Hreflang Generator is a different sample, not a live confirm.

WhatsApp Advisor
Enroll Now