How to fix “Discovered - currently not indexed” on Next.js
If Search Console shows “Discovered - currently not indexed” on your Next.js site, you are in the right place. Google knows the URL but has not crawled it yet. 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?
The URL was discovered from your sitemap or a link, but Googlebot has not visited it yet. It usually comes from crawl budget, server load or the page being treated as low priority.
Likely causes on Next.js
- The site is large and Google cannot get to every URL.
- The server is slow or throws errors and Googlebot slows down to be polite.
- Many low-value URLs (filters, parameters) fill the crawl queue.
- No internal links; an orphan page known only from the sitemap.
- 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.
- Render pages statically or with ISR where possible, split heavy client bundles and use next/image. Slow server responses reduce crawl rate.
- Link to important pages directly from the home page and category pages.
- Put only canonical, 200-returning URLs you want indexed in the sitemap.
- Take filter and parameter URLs out of crawling with robots.txt or canonicals.
- Lower server response time and error rate; watch response time in Search Console crawl stats.
- Send priority URLs through an indexing panel and follow progress with URL inspection in Search Console.
Extra checks for Next.js
- canonical and duplicate URLs: Give every page an absolute canonical with metadata.alternates.canonical and set metadataBase. On dynamic routes make sure parametrised URLs do not repeat content.
- redirects and 404: Define permanent (permanent: true) redirects with redirects() in next.config.js and avoid chains and loops. On missing routes return a real 404 with notFound().
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
What is the difference between "Discovered" and "Crawled"?
"Discovered" means Google knows the URL but has not visited; "Crawled" means it visited but did not index. The first is usually about crawl priority, the second about content quality.
Thousands of my pages have this status. What now?
First decide which ones truly need indexing and remove the rest from the sitemap and internal links. Work in priority order instead of forcing every URL at once.
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.
Related pages
- Next.js: Duplicate without user-selected canonicalFixes
- Next.js: Duplicate, Google chose different canonical than userFixes
- Next.js: Alternate page with proper canonical tagFixes
- React SPA: Discovered - currently not indexedFixes
- Laravel: Discovered - currently not indexedFixes
- Ghost: Discovered - currently not indexedFixes