Google indexing guide 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.
Contents
Where are the settings?
public/index.html, react-helmet or similar head management, public/robots.txt and server redirect settings.
Settings that affect indexing
- 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.
- robots.txt: 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.
- 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.
- 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.
Common indexing problems on React SPA
Open the matching page for steps specific to each status:
- Crawled - currently not indexed
- Discovered - currently not indexed
- Duplicate without user-selected canonical
- Duplicate, Google chose different canonical than user
- Alternate page with proper canonical tag
- Page with redirect
- Soft 404
- Not found (404)
- Blocked by robots.txt
- Excluded by 'noindex' tag
- Server error (5xx)
- Redirect error
- Indexed, though blocked by robots.txt
- Blocked due to unauthorized request (401) / access forbidden (403)
- URL is unknown to Google
- Indexed, not submitted in sitemap
Next steps
Before publishing, run through Google indexing checklist: 15 items before you publish, scan the address with the free Free indexability checker tool and add new pages to the sitemap: How to build a sitemap and submit it to Search Console. For many pages, Google index panel: send, track and resend from one screen makes bulk submission easier; indexing is never guaranteed.
Frequently asked questions
Why is my React SPA site not showing on Google?
Usually because of a noindex setting, a robots.txt block, a missing sitemap or weak content. Check the settings above and the matching status pages in order.
What is the sitemap address for React SPA?
The app does not build its own sitemap; generate sitemap.xml with a build script, put it in public and list only real routes.