“Discovered — currently not indexed” means Google knows the URL but has not crawled it in the reported state. It does not, by itself, establish a content, canonical, or rendering problem.
Google's Page indexing documentation says the crawl was typically rescheduled because Google expected it to overload the site. Check that possibility against the site's actual response history rather than assuming the server is the cause.
Check whether the report is current
Open a few important examples in URL Inspection and compare their current status with the grouped report's update date. Check CDN or server logs for verified Googlebot requests to those exact URLs.
If a URL was requested after the report's last update, investigate its newer state. Do not change internal links to fix a label that no longer describes the page.
Compare similar pages
Choose an affected page and a crawled page with the same purpose and a similar publication date. Compare where they are linked, whether they are in the sitemap, and how they respond.
This example shows the kinds of differences to record:
| Check | Uncrawled product | Crawled product |
|---|---|---|
| Publication date | July 20 | July 20 |
| First category link | Pagination page 18 | Category page 1 |
| Sitemap | Listed with July 20 lastmod | Listed with July 20 lastmod |
| Verified Googlebot requests | None through July 28 | Requested July 21 |
| Response checks | Stable 200 | Stable 200 |
| Other exposed URLs | Several filter and alias variants | One final path |
These are illustrative values. Fill in your own URLs and dates before drawing a conclusion.
Look for response problems
Compare crawl activity and response health around the time the delay began. Check for 5xx, 429, timeouts, connection failures, or slower responses, and match them with hosting, CDN, cache, or deployment changes.
One successful request from your laptop does not rule out intermittent errors or a rule affecting Google. Compare the affected URLs and a working sample through the same public request path.
Check how many URLs the site exposes
Look for a recent increase in sitemap entries or crawlable filters, calendars, archives, aliases, and redirect URLs. Compare the URL patterns Google requests with the final pages you want it to visit.
Stop generating and promoting unintended variants at the template or sitemap that creates them. Keep crawl controls separate from instructions to remove a page from search: Google cannot read a noindex directive on a page it is blocked from crawling.
Check links to the affected pages
Confirm that relevant categories, navigation, pagination, or related articles contain real links to the page. Inspect the output visitors receive, rather than assuming the link exists because a component was added to the source code.
If affected pages are buried or orphaned while similar pages have clear links, repair that specific path. Adding every URL to the footer is not a substitute for useful navigation.
When no clear cause appears
Keep the current URL sample and its dates. You can request indexing for a few important pages, but repeated submissions do not accelerate crawling or guarantee indexing. Google's recrawl guidance explains those limits.
After a change, check both the live result and Google's later crawl. Moving from discovered to crawled confirms a crawl happened; indexing is a separate result.