How to fix “Soft 404” on React SPA
If Search Console shows “Soft 404” on your React SPA site, you are in the right place. The page looks empty or like an error but returns 200. 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.
Contents
What does this status mean?
The server says "success" (200) but the content reads to Google like a missing page: an empty list, a "product not found" message or almost no content. Google does not index the URL.
Likely causes on React SPA
- An empty category, empty search result or out-of-stock product page.
- Deleted content shows a custom error page while returning 200.
- JavaScript content fails to load and the page stays empty.
- Template pages with very little text.
- 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
- In your React SPA admin go to: public/index.html, react-helmet or similar head management, public/robots.txt and server redirect settings.
- 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.
- A large JS bundle delays rendering. Use code splitting, lazy loading and caching, and prerender critical pages on the server where you can.
- Return 404 for pages that truly do not exist, or 410 if permanently removed.
- If a close replacement exists, redirect to it with a 301.
- Set empty category and search pages to noindex or add content.
- Verify that JavaScript loads the content with "Test live URL" in URL inspection.
- Start validation after fixing.
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.
- 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.
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
Is a soft 404 penalised?
No, but it spends crawl budget and the page is not indexed. Many soft 404s can be a poor quality signal for the site.
What if a real page shows as soft 404?
Enrich the content and confirm it appears in the raw or rendered HTML.
Where are these settings on React SPA?
public/index.html, react-helmet or similar head management, public/robots.txt and server redirect settings.