hreflang target blocked

warning hreflang-target-blocked hreflang and language versions

The cluster points at a page that is closed from indexing. The link is there, the destination cannot be used, and the cluster is weaker for it.

What indexgap reports

The finding reads:

warning  hreflang-target-blocked  the alternate … is closed to indexing, or its canonical points elsewhere — the cluster points at something that will not be in the index

How to fix it

Open the alternate page for indexing or drop it from the cluster: a blocked target weakens the whole cluster.

How it behaves at scale

Collapsed when it fires template-wide. If it appears on 90% or more of the pages — or of one language version — of a site with at least 20 pages, it is a property of the template and is reported once, with the count, instead of once per page.

Finding it

pipx install indexgap
cd your-project
indexgap init
indexgap check

Then indexgap brief turns every finding on this page into a work order in indexgap-briefs/, with the thresholds the result has to satisfy and the command to check it.

Related checks in hreflang and language versions

translations-parkedtranslations parked
hreflang-missinghreflang missing
hreflang-no-selfhreflang no self
hreflang-no-returnhreflang no return
hreflang-bad-codehreflang bad code
hreflang-unknown-targethreflang unknown target
hreflang-lang-mismatchhreflang lang mismatch
hreflang-canonical-conflicthreflang canonical conflict
hreflang-static-clusterhreflang static cluster

All checks · hreflang and language versions