How to fix “Redirect error” on React SPA
If Search Console shows “Redirect error” on your React SPA site, you are in the right place. The redirect loops or the chain is too long. 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?
Google could not follow the redirect to the end: a loop, a very long chain, or an empty or overly long target address. The page cannot be indexed.
Likely causes on React SPA
- http/https or www rules redirect into each other endlessly.
- Plugin and .htaccess redirects conflict.
- Several migrations left old URLs forming a chain.
- The redirect target is generated empty or malformed.
- 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.
- Trace the URL with a redirect checker or curl -IL and find the loop.
- Remove conflicting rules; define the domain rule in one place only (server or CDN).
- Shorten chains: each old URL should 301 directly to the final one.
- Verify the target address is absolute and valid.
- After fixing, start validation and resend the URL.
Extra checks for React SPA
- 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.
- noindex and visibility: A forgotten noindex tag in index.html affects every route. Code that adds or removes noindex on the client can behave inconsistently even after rendering; keep noindex static in the HTML.
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
How long a chain is a problem?
Google follows only a few hops. One hop is best.
Can cookies cause a loop?
Yes; redirects that need cookies can become loops for Googlebot. Make redirects work without cookies.
Where are these settings on React SPA?
public/index.html, react-helmet or similar head management, public/robots.txt and server redirect settings.