Fixes

How to fix “Page with redirect” on React SPA

If Search Console shows “Page with redirect” on your React SPA site, you are in the right place. The URL redirects elsewhere, so it is not indexed. 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 · 2 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 URL returns a redirect; Google indexes the target, not the redirecting URL. Usually healthy, but if the sitemap and internal links still point at the old URL, crawl budget is wasted.

Likely causes on React SPA

  • The http address redirects to https or the non-www to www.
  • Old post and product URLs were redirected to new ones.
  • The sitemap or menu still lists the old URLs.
  • The redirect chain has several hops.
  • 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. Confirm the redirect is intended; if so this line is not a problem.
  4. Update the sitemap and internal links to the final target.
  5. Collapse chains: the old URL should 301 straight to the final one.
  6. If you use a temporary redirect (302) for a permanent move, change it to 301.
  7. Check with URL inspection that the target is indexed; if not, send it.

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

Does a redirecting page get indexed?

No, the target does. That is why links should point at the target.

What is the difference between 301 and 302?

301 signals a permanent move, 302 a temporary one. Use 301 for permanent moves.

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