Fixes

How to fix “URL is unknown to Google” on React SPA

If Search Console shows “URL is unknown to Google” on your React SPA site, you are in the right place. Google has never discovered the URL. 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 · 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?

URL inspection says Google has never seen this address. The page may be new, or no link or sitemap entry leads to it.

Likely causes on React SPA

  • The page is very new and not discovered yet.
  • It is missing from the sitemap and has no internal links (an orphan).
  • The page is reachable only through a JavaScript-created link.
  • A site-wide noindex or robots block stops discovery.
  • React SPA note: The app does not build its own sitemap; generate sitemap.xml with a build script, put it in public and list only real routes.

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. The app does not build its own sitemap; generate sitemap.xml with a build script, put it in public and list only real routes.
  3. Add the URL to the sitemap and resubmit the sitemap in Search Console.
  4. Link to it from the home page or a hub page with a visible HTML link.
  5. Send the URL with "Request indexing" in URL inspection.
  6. For bulk URLs send through an indexing panel and watch crawl status in Search Console.
  7. If it is discovered but still not indexed, look at content quality.

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 soon is a new page discovered?

Hours on frequently updated sites; days or weeks on new sites.

Does social sharing speed up discovery?

It can help sometimes but is not guaranteed. Sitemap and internal links are more reliable.

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