Fixes

How to fix “Not found (404)” on React SPA

If Search Console shows “Not found (404)” on your React SPA site, you are in the right place. The URL returns 404. 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?

Googlebot visited and the server answered "not found". If you removed the page on purpose this is normal and it will drop out over time; if not, something is wrong with a link, a redirect or publishing.

Likely causes on React SPA

  • The page was deleted or its URL changed without a redirect.
  • The sitemap or internal links list addresses that no longer exist.
  • Links from other sites point at mistyped addresses.
  • A temporary publishing or cache problem made the page 404 for a while.
  • React SPA note: 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.

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. 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.
  3. The app does not build its own sitemap; generate sitemap.xml with a build script, put it in public and list only real routes.
  4. If the page is gone for good, leave the 404 or 410 as it is; that is not wrong.
  5. If a similar page exists, add a 301 redirect.
  6. Remove deleted addresses from the sitemap and internal links.
  7. Redirect externally linked 404s to a relevant page with 301 to keep their link value.
  8. If the page should exist, republish it and verify with URL inspection.

Extra checks for React SPA

  • canonical and duplicate URLs: 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.
  • 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 404s hurt my rankings?

Normal 404s do not. Important pages returning 404 by mistake lose traffic.

Should I redirect them all?

No. Redirect only URLs that have a real counterpart; redirecting to an unrelated page can count as a soft 404.

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