Fixes

How to fix “Duplicate without user-selected canonical” on React SPA

If Search Console shows “Duplicate without user-selected canonical” on your React SPA 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 React SPA. A React app that runs only in the browser (Create React App, Vite). Content is drawn with JavaScript, so you depend on Google's rendering queue; prerendering or server-side rendering is recommended.

Updated: 18.11.2026 · 3 min read · Türkçe

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

  • 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.
  • React SPA note: Produce title, description and canonical separately on each route with a library such as react-helmet; otherwise every route carries the same head and can look duplicated. Server-side prerendering solves this at the root.

Step-by-step fix on React SPA

  1. In your React SPA admin go to: public/index.html, react-helmet or similar head management, public/robots.txt and server redirect settings.
  2. Produce title, description and canonical separately on each route with a library such as react-helmet; otherwise every route carries the same head and can look duplicated. Server-side prerendering solves this at the root.
  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 React SPA

  • sitemap: The app does not build its own sitemap; generate sitemap.xml with a build script, put it in public and list only real routes.
  • speed and crawling: A large JS bundle delays rendering. Use code splitting, lazy loading and caching, and prerender critical pages on the server where you can.

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 React SPA?

public/index.html, react-helmet or similar head management, public/robots.txt and server redirect settings.

Related pages