Fixes

How to fix “Alternate page with proper canonical tag” on Next.js

If Search Console shows “Alternate page with proper canonical tag” on your Next.js 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 Next.js. A React framework. Server-side and static generation hand Googlebot ready-made HTML; metadata is managed with the Metadata API.

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

Contents
  1. What does this status mean?
  2. Likely causes on Next.js
  3. Step-by-step fix on Next.js
  4. Extra checks for Next.js
  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 Next.js

  • 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.
  • Next.js note: Give every page an absolute canonical with metadata.alternates.canonical and set metadataBase. On dynamic routes make sure parametrised URLs do not repeat content.

Step-by-step fix on Next.js

  1. In your Next.js admin go to: The metadata object in app/layout.tsx and page files, app/robots.ts, app/sitemap.ts and next.config.js.
  2. Give every page an absolute canonical with metadata.alternates.canonical and set metadataBase. On dynamic routes make sure parametrised URLs do not repeat content.
  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 Next.js

  • redirects and 404: Define permanent (permanent: true) redirects with redirects() in next.config.js and avoid chains and loops. On missing routes return a real 404 with notFound().
  • sitemap: Generate a dynamic sitemap with app/sitemap.ts; split large sites with generateSitemaps. List only canonical URLs that return 200.

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 Next.js?

The metadata object in app/layout.tsx and page files, app/robots.ts, app/sitemap.ts and next.config.js.

Related pages