Fixes

How to fix “Alternate page with proper canonical tag” on Drupal

If Search Console shows “Alternate page with proper canonical tag” on your Drupal site, you are in the right place. The page canonicalises to another URL; usually expected. This page covers the causes and a step-by-step fix for Drupal. A flexible, module-based CMS. The Metatag, Simple XML Sitemap and Redirect modules provide indexing control.

Updated: 06.11.2026 · 2 min read · Türkçe

Contents
  1. What does this status mean?
  2. Likely causes on Drupal
  3. Step-by-step fix on Drupal
  4. Extra checks for Drupal
  5. After fixing
  6. More information

What does this status mean?

This page declares itself a copy of another URL and Google accepts that. It is normal for parametrised and mobile URLs; it is only a problem if you wanted this page indexed.

Likely causes on Drupal

  • The page canonicalises to another URL on purpose.
  • A template or plugin adds a wrong canonical to every page (for example always the home page).
  • An AMP or separate mobile version points to the main version.
  • Every paginated page canonicalises to page one.
  • Drupal note: The Metatag canonical field uses [current-page:url] by default. Stop view filters and pager parameters from surfacing as separate URLs.

Step-by-step fix on Drupal

  1. In your Drupal admin go to: Configuration > Search and metadata (Metatag, Simple XML Sitemap, Redirect).
  2. The Metatag canonical field uses [current-page:url] by default. Stop view filters and pager parameters from surfacing as separate URLs.
  3. First decide whether you want this URL indexed; if not, nothing needs doing.
  4. If you do, change the canonical to point at itself (self-referencing).
  5. Check the page source to make sure the template is not adding the same canonical everywhere.
  6. Give paginated pages their own addresses as canonicals.
  7. After fixing, send the URL for indexing.

Extra checks for Drupal

  • speed and crawling: On the Performance screen enable page and block caching and CSS/JS aggregation; the dynamic page cache lowers server load.
  • noindex and visibility: In the Metatag module check the "robots" value per content type; a noindex left over from a fresh install can spread to every node.

After fixing

In Search Console start "Validate fix" for this status and resubmit the page with URL inspection. First confirm the blocker is gone with the free Free indexability checker tool; for many URLs follow Bulk URL indexing: how to send thousands of pages to Google. Google makes the indexing decision itself and timing ranges from days to weeks.

More information

Frequently asked questions

Must I fix this warning?

No. If it is deliberate it is working as intended; fix it only on pages that should be indexed.

Why does it canonicalise to the home page?

Usually a plugin or template setting mistake. Every page should reference its own address.

Where are these settings on Drupal?

Configuration > Search and metadata (Metatag, Simple XML Sitemap, Redirect).

Related pages