Fixes

How to fix “Duplicate without user-selected canonical” on Next.js

If Search Console shows “Duplicate without user-selected canonical” on your Next.js site, you are in the right place. Google found duplicates of the content and you did not declare a canonical. 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?

The same or very similar content sits on several URLs and none of them has a canonical pointing at your preferred one. Google then decides which one goes in the index.

Likely causes on Next.js

  • The www and non-www, http and https versions all open.
  • Parametrised URLs (sorting, tracking, session) repeat the same page.
  • The same product or post is reachable through several category paths.
  • Addresses with and without a trailing slash behave as separate pages.
  • 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. Add a rel=canonical pointing at your preferred absolute address to every page.
  4. Redirect domain versions (http/https, www) to a single one with 301.
  5. Make sure internal links and the sitemap always use the canonical address.
  6. Strip needless parameters from internal links or canonicalise them to the clean address.
  7. After fixing, start validation in Search Console and send the canonical 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

Do duplicate pages get my site penalised?

Usually not, but signals get split and an unwanted URL can end up indexed. A canonical gathers them.

Is canonical a directive?

No, it is a strong hint. Google may choose another URL if other signals contradict it.

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