Fixes

How to fix “Excluded by 'noindex' tag” on React SPA

If Search Console shows “Excluded by 'noindex' tag” on your React SPA site, you are in the right place. The page has noindex, so Google deliberately leaves it out. 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?

The page says "noindex" through a robots meta tag or an X-Robots-Tag header. Google obeys and does not add the page, or removes it from the index.

Likely causes on React SPA

  • A site-wide noindex turned on during development or maintenance.
  • The page is marked noindex in an SEO plugin.
  • The server or CDN adds noindex through an HTTP header.
  • A template adds noindex conditionally to certain page types.
  • React SPA note: 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.

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. 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.
  3. Check the page source for the robots meta tag and the response headers for X-Robots-Tag.
  4. If noindex is not intended, remove it and verify with a free indexability check.
  5. Make sure the page is not blocked by robots.txt, otherwise Google cannot see the noindex.
  6. Do not leave noindex URLs in the sitemap.
  7. After removing it, request indexing in URL inspection and send the link through an indexing panel.

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.
  • 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

How long after removing noindex until it is indexed?

Typically days to a few weeks, depending on how often the site is crawled.

Do logged-in pages need noindex?

Yes, noindex is right for account, cart and thank-you pages.

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