If your pages are stuck as discovered and not indexed, Google knows they exist but has chosen not to crawl them yet. Who hits this problem? Site owners who publish new pages, add products, or rebuild a section and then wait weeks while nothing appears in search. What you are seeing in Search Console is a queueing decision, not always an error on the page itself.
When does it happen? Usually after a burst of new URLs, a migration, or steady publishing on a site with limited authority. Where does Google make the decision? On its side, based on how much crawling your server can handle and how valuable the page looks compared with everything else waiting. Why it matters is simple: a page that is never crawled can never be indexed or rank, no matter how well it is written.
How do you fix it? You work through the causes in order, from server and crawl demand to content quality and internal linking. This guide is the hands-on diagnostic version: what the status means, how to test each likely cause, and the exact order to run your checks so you stop guessing.
Discovered means Google found the URL, usually through a sitemap, an internal link, or an external link, and added it to a crawl queue. It has not yet fetched the page. That is different from crawled but not indexed, where Google did fetch the page and then decided not to store it.
Open the Page indexing report and select the discovered status to see the affected URLs and when they were last updated. Then inspect a single URL to confirm Google has no fetch record for it. Note the pattern: is it five pages, fifty, or thousands, and do they share a folder, template, or publish date?
Google does not crawl every known URL on every site every day. It balances how much a site wants to be crawled against how much the server can safely handle. A slow or fragile server teaches the crawler to visit less often and to leave more URLs waiting in the queue.
Rate-managed systems are familiar across Google services, as Google support documentation shows elsewhere. Crawling follows the same logic: demand is throttled when capacity looks limited.
Sometimes the queue is a quality judgement in advance. If Google has crawled similar pages on your site and found them thin, near-duplicate, or rarely useful, it may delay crawling more pages that look the same. Product variants, location pages with swapped place names, and short posts built from one template are classic triggers.
Internal linking sends the same signal from inside your site. A page linked only from a sitemap, buried many clicks deep, or given vague anchor text looks unimportant. If your own site barely points to a page, Google has little reason to prioritise it over better-connected URLs.
Work in this order and stop when you find a clear fault. Requesting indexing for dozens of URLs rarely fixes the underlying cause.
As you work through fixes, reading related case notes on the Seovaro blog can help you compare your pattern with other indexing problems, so you do not confuse a queueing delay with a quality rejection. Keep notes on what you changed and when, because timing is your best evidence.
Ready to check your supporting assets while you fix the queue? Try the QR Code Generator to create clean codes that send visitors straight to your priority pages, and use the response to confirm those destination URLs load fast, resolve correctly, and are worth crawling.
On healthy, established sites, new pages are often crawled within hours or a few days. On newer or larger sites, a wait of one to two weeks can still be normal. A growing backlog that never shrinks is the warning sign, not a short delay.
It can prompt a crawl for a single important URL, but it does not fix crawl budget, server, or quality causes. Use it after you have fixed the underlying issue and only for priority pages, not as a bulk routine.
A sitemap alone rarely causes it, but a bloated sitemap full of weak, duplicate, or outdated URLs can add to the queue and dilute priority. Keep sitemaps limited to canonical pages you genuinely want indexed.
Not immediately. First check capacity, linking, and quality, and try to improve or merge the page. Delete or consolidate only when the page has no distinct purpose, no audience, and no realistic path to earning a crawl.