Fixes

How to fix “Duplicate, Google chose different canonical than user” on React SPA

If Search Console shows “Duplicate, Google chose different canonical than user” on your React SPA site, you are in the right place. You declared a canonical but Google picked another URL. 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?

Your page carries a canonical but Google judged another URL more fitting from content and other signals. The URL Google picked stays in the index, not the one you pointed at.

Likely causes on React SPA

  • Two pages are almost identical in content, so Google picks one.
  • The canonical, internal links, sitemap or redirects point at different URLs.
  • The URL you canonicalised to is slow, broken or weak.
  • The canonical tag is changed afterwards with JavaScript.
  • 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. Find the "Google-selected canonical" in URL inspection and compare the two pages to see why.
  4. Make the pages genuinely different, or if they are real duplicates merge them at one URL with a 301.
  5. Make the sitemap, internal links, canonical and redirects all point at the same URL.
  6. Keep the canonical fixed in the raw HTML and do not change it on the client.
  7. After fixing, send your preferred URL for indexing and wait a few weeks.

Extra checks for React SPA

  • robots.txt: Add public/robots.txt; without it many server setups return index.html in place of robots.txt. Do not block /static or JS files; Google needs them to render the page.
  • redirects and 404: Client redirects (window.location, Navigate) are not 301s. Do real redirects on the server (nginx, Netlify _redirects, Vercel vercel.json) and return a 404 status for unknown routes; otherwise every URL returns 200 and creates soft 404s.

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 I have to accept Google's choice?

No, but nothing changes unless you change the signals. If the chosen URL is fine, making it your preferred one is the easiest fix.

Does it lower rankings?

Not directly. But if the wrong URL stays indexed, visitors may land on a page you did not intend.

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