How to fix “Indexed, not submitted in sitemap” on Next.js
If Search Console shows “Indexed, not submitted in sitemap” on your Next.js 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 Next.js. A React framework. Server-side and static generation hand Googlebot ready-made HTML; metadata is managed with the Metadata API.
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 Next.js
- 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.
- Next.js note: Generate a dynamic sitemap with app/sitemap.ts; split large sites with generateSitemaps. List only canonical URLs that return 200.
Step-by-step fix on Next.js
- In your Next.js admin go to: The metadata object in app/layout.tsx and page files, app/robots.ts, app/sitemap.ts and next.config.js.
- Generate a dynamic sitemap with app/sitemap.ts; split large sites with generateSitemaps. List only canonical URLs that return 200.
- 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 Next.js
- speed and crawling: Render pages statically or with ISR where possible, split heavy client bundles and use next/image. Slow server responses reduce crawl rate.
- noindex and visibility: Look for robots: { index: false } in metadata; a condition tied to an environment variable can output noindex in production by mistake. Also check that no X-Robots-Tag response header is added.
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 Next.js?
The metadata object in app/layout.tsx and page files, app/robots.ts, app/sitemap.ts and next.config.js.