Fixes

How to fix “Crawled - currently not indexed” on React SPA

If Search Console shows “Crawled - currently not indexed” on your React SPA site, you are in the right place. Google crawled the page but did not add it to 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: 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?

Googlebot visited the page and read its content but decided it was not worth adding to search results for now. This is a decision, not an error; page quality, uniqueness and site-wide signals all play a part.

Likely causes on React SPA

  • The content is short, shallow or largely the same as other pages.
  • Almost no links from inside the site point to the page.
  • The site is new with few trust signals; Google adds new pages cautiously.
  • The URL is a template, filter or tag page with little value of its own.
  • React SPA note: A large JS bundle delays rendering. Use code splitting, lazy loading and caching, and prerender critical pages on the server where you can.

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 large JS bundle delays rendering. Use code splitting, lazy loading and caching, and prerender critical pages on the server where you can.
  3. The app does not build its own sitemap; generate sitemap.xml with a build script, put it in public and list only real routes.
  4. Make the page truly original and detailed: answer the question completely and add information found nowhere else.
  5. Link to it from strong pages of the site with relevant anchor text and connect it to a menu or hub page.
  6. Merge near-identical pages or point them to one address with a canonical.
  7. Verify the page carries no noindex or robots block and returns 200.
  8. After improving it, request indexing through URL inspection in Search Console and send the link through an indexing panel; allow a few weeks for the result.

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

Does this status mean a penalty?

No. It is an indexing decision, not a penalty. A manual action would appear in its own Search Console section.

How long should I wait?

If you made improvements, wait a few weeks; repeating the request daily does not speed it up.

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