“Discovered – currently not indexed” means Google found the URL, through a link or a sitemap, but has not crawled it yet. It is a queue, not a verdict: Google decided the page could wait. Search Console's own wording adds that Google often postpones a crawl when fetching more would overload the site.
For a new site or a new section, a few weeks in this state is normal. It is a problem when the list keeps growing, when it holds your most important pages, or when pages stay there for months.
Common causes
The site produces more URLs than Google wants to crawl. Filter and sort parameters, calendar pages, session IDs and tag combinations can create tens of thousands of URLs. Google spreads its attention across all of them and leaves many for later.
The server is slow or fails under load. When responses slow down or return server errors, Google lowers the crawl rate to protect the site. Fewer pages get fetched and more wait in the queue. Check Settings → Crawl stats for the average response time and the share of server errors.
The pages look unimportant. A URL that is only in the sitemap, or reachable only through deep pagination, gets a low priority. Internal links from strong pages tell Google a page matters.
The pages look like many others. If Google has crawled a sample of a template and found thin or duplicate content, it may not hurry to crawl the rest of that template.
How to fix it
- Check the server first. Open Crawl stats. If response times are high or there are 5xx errors, fix that before anything else; no amount of linking helps if Google throttles the crawl.
- Cut the URLs nobody needs. Stop linking to parameter combinations, close internal search results with
noindex, and remove empty tag and filter pages. Keep the sitemap limited to canonical, indexable pages that answer 200. - Link to the pages you want crawled. Add links from the homepage, category pages and related content. Make important pages reachable within a few clicks from the homepage.
- Make the pages substantial. If a template is thin, improve the template; the pages behind it will be crawled and indexed more willingly.
- Ask for the most important URLs. Use URL Inspection → Request indexing for a handful of key pages. It does not scale to thousands of URLs; fixing the causes does.
How to check that it worked
- In Indexing → Pages, the count for this reason falls and the indexed count rises over the following weeks.
- In Crawl stats, total crawl requests go up and the average response time stays low.
- URL Inspection for a sample URL shows a recent Last crawl date.
What SignalCrawler checks here
The audit looks for the causes on the site itself: slow server responses and server errors during the crawl, parameter URLs that multiply into a crawl trap, pages that appear only in the sitemap, pages buried deep in the link structure, and sitemaps that list redirects, errors or noindex pages. Each finding lists the affected URLs, grouped by page template.