Canonical target indexability

The canonical target indexability check shows whether the URL named in a page’s canonical tag is itself indexable. This is a useful quality check because a canonical signal is much stronger when it points to a page that search engines can actually index.

A canonical tag may look technically correct on the source page, but if the target is not indexable, the setup becomes weaker and potentially confusing. That is why this is a valuable canonical QA signal.

What it is

A canonical tag tells search engines which URL should be treated as the preferred version of a page.

This check looks one step further and asks: is that canonical target actually indexable?

If the value is TRUE, the canonical target is considered indexable. If the value is FALSE, the target has some issue that makes it non-indexable, such as a blocking directive, a problematic status code, or another technical conflict.

SEOlerts monitors this as a simple boolean so you can quickly see whether your canonical destinations are valid candidates for indexing.

Why it matters

Canonical tags are meant to consolidate signals towards the preferred version of a page. That only works properly when the destination is a page search engines can treat as indexable.

If a page canonicalises to a non-indexable target, the signal becomes less coherent. Search engines may receive the instruction to prefer one URL while also seeing that the preferred URL is blocked, redirected, non-self-canonical, or otherwise unsuitable for indexing.

This matters because canonical problems are often not caused by the source page alone. The destination also has to be technically sound.

What can go wrong if unchecked

If a canonical target becomes non-indexable, pages may begin pointing search engines towards URLs that are not good indexing candidates.

Common causes include:

• the canonical target gaining a noindex directive
• the target returning a non-200 status
• the target being blocked by robots.txt in a way that affects indexability
• the target canonicalising elsewhere
• migration or template changes leaving canonicals pointed at the wrong destination

If this goes unnoticed, the canonical relationship may become weak or contradictory. That can create ambiguity around which URL should be indexed and where signals should consolidate.

Not every non-indexable target causes immediate visible problems, but it is rarely a clean setup for important pages.

Why monitoring it matters

Monitoring canonical target indexability helps you validate canonical tags as a complete signal rather than just checking whether they exist.

This is useful because many canonical reviews stop at the source page. In practice, the target page also needs to be healthy. A page may still output a canonical tag perfectly, while the destination has quietly become non-indexable because of a deployment, directive change, or URL handling issue.

This makes the check especially valuable after migrations, canonical rewrites, template updates, robots changes, and broader indexing changes.

What an alert may mean

An alert means the canonical target’s indexability state has changed.

If the value changes from TRUE to FALSE, the canonical target is no longer considered indexable. In practice, that could mean:

• the target now has noindex
• the target status code changed
• canonical logic on the target changed
• a robots or header directive now blocks indexability
• the preferred destination is no longer a clean canonical endpoint

If the value changes from FALSE to TRUE, the canonical target is now indexable. That could mean:

• a previous blocking issue has been fixed
• the target status has been corrected
• directives or canonical conflicts were resolved
• the canonical destination is now a healthier indexing candidate

The alert is not automatic proof that the source page will lose visibility, but it does mean the canonical relationship has changed in technical quality and should be reviewed.

What to check next

Start by requesting the canonical target directly and reviewing its current indexability signals.

Then check:

• whether the target returns 200
• whether the target has any noindex directives
• whether the target is blocked by robots.txt
• whether the target is self-canonical or points elsewhere
• whether recent template, migration, or SEO changes explain the issue

It is also worth reviewing the source page’s canonical href to confirm it still points to the right destination. If the target is no longer indexable, the fix may involve either restoring the target’s indexability or updating the canonical to a better URL.

Key takeaway

The canonical target indexability check shows whether the URL named in a page’s canonical tag is itself a valid indexing candidate. Monitoring it helps you catch weak or contradictory canonical setups where pages point to destinations that search engines should not or cannot index. An alert means the canonical target’s indexability has changed, and that should be reviewed to keep canonical signals clean and reliable.