Fixes

How to fix “Indexed, though blocked by robots.txt” on React SPA

If Search Console shows “Indexed, though blocked by robots.txt” on your React SPA site, you are in the right place. The URL is blocked by robots.txt yet still in the index. 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: 05.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?

Google did not crawl the URL because robots.txt forbids it, but it knows the address from links on other pages and indexed it without content. The result usually shows "No information is available for this page".

Likely causes on React SPA

  • Only robots.txt was used to hide the page.
  • External and internal links announced the address to Google.
  • The page was indexed first and blocked in robots.txt later.
  • The sitemap still lists the URL.
  • React SPA note: Add public/robots.txt; without it many server setups return index.html in place of robots.txt. Do not block /static or JS files; Google needs them to render the page.

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. Add public/robots.txt; without it many server setups return index.html in place of robots.txt. Do not block /static or JS files; Google needs them to render the page.
  3. 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.
  4. If you do not want it indexed, remove the robots block and add noindex; allow crawling so Google can see the noindex.
  5. Protect content that must stay private with a password or login; do not rely on robots.txt alone.
  6. For urgent removal use the Removals tool in Search Console temporarily.
  7. If you want it indexed, remove the robots block and send the URL.
  8. Take blocked URLs out of the sitemap.

Extra checks for React SPA

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

Why noindex first, then robots?

Google must be able to crawl the page to see noindex. Let noindex take it out of the index first, then close it with robots.txt if you like.

Is this an error?

It is a warning; a content-less listing may be undesirable for your brand.

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