How to fix “Indexed, not submitted in sitemap” on React SPA
If Search Console shows “Indexed, not submitted in sitemap” on your React SPA site, you are in the right place. The page is indexed but not in your sitemap. 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.
Contents
What does this status mean?
Google found the URL through a link and indexed it, but it is not in your sitemap. Usually harmless; it can show an incomplete sitemap or unwanted URLs being indexed.
Likely causes on React SPA
- The sitemap is old or does not update automatically.
- Parametrised, paginated or archive URLs got indexed.
- Some content types were left out of the sitemap.
- Test or legacy URLs are still reachable.
- 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
- In your React SPA admin go to: public/index.html, react-helmet or similar head management, public/robots.txt and server redirect settings.
- The app does not build its own sitemap; generate sitemap.xml with a build script, put it in public and list only real routes.
- Add important URLs to the sitemap and make sure it updates automatically with new content.
- Set unwanted URLs to noindex or canonicalise them to the main address.
- Remove legacy and test URLs with 301 or 404.
- Resubmit the sitemap in Search Console.
- Compare the list of indexed URLs with the sitemap regularly.
Extra checks for React SPA
- 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.
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
Is this a problem?
Mostly not. Act only if you see URLs that should not be indexed.
Does a sitemap boost rankings?
Not directly; it makes discovery and crawling easier.
Where are these settings on React SPA?
public/index.html, react-helmet or similar head management, public/robots.txt and server redirect settings.