"Discovered — currently not indexed" is Google Search Console's way of saying: we know this URL exists, we tried to crawl it, and we decided not to index it. No explanation. No timeline. Just limbo.
For JavaScript sites, this status is often permanent until you fix the underlying rendering problem. Here's how to diagnose it.
Check what Googlebot actually sees
The first thing to do is fetch your page as Googlebot and look at the output. You want to know: how many words does Googlebot see? Is there any product content? Does the page look like a SPA shell?
Try it with the bot view tool below:
Try it on your site
Full tool with more detailsWhat the numbers mean
A word count below 50 on a product page almost always means Googlebot is getting a SPA shell. The SPA flag confirms it. Googlebot doesn't index pages with almost no content, so the URL sits in "Discovered — currently not indexed."
Fixing it
The fix is getting the rendered content into the HTML Googlebot receives. You have a few options depending on your setup:
- Switch to server-side rendering or static generation in your framework (requires code changes, may not work for dynamic content like pricing)
- Add pre-rendering via PerfectSearch middleware (two lines of code in Next.js) or DNS proxy (zero code changes)
After you fix it
Request reindexing in Google Search Console after deploying your fix. Google doesn't re-crawl on a fixed schedule, and manual resubmission moves the URL up the queue. Expect indexing to reflect the change within 2–4 weeks for most sites.