A backlink page sitting in Discovered - currently not indexed has never been fetched by Googlebot. Google knows the URL exists and has postponed the visit. There is no fixed expiry for that state: some pages leave it in days, others sit for months, and a share never gets crawled at all. The practical question is not "how long does it take" but "after how long should I stop waiting and act" - and the workable answer for link builders is 14 days.
What the status actually tells you
Google's own documentation describes this state as: the page was found, but crawling was deferred - typically to avoid overloading the site. For donor pages (pages that host links to your site), the status means your link has never been read. Not devalued, not ignored - simply never seen. Whatever weight the placement could pass does not exist yet.
That distinction matters because the fix is different from the better-known Crawled - currently not indexed. A crawled-but-not-indexed page was fetched and declined on quality grounds; more crawling will not help it. A discovered-only page has a delivery problem: nothing pushed the crawler to it strongly enough.
What the waiting time depends on
Observed windows vary by page type. These are industry-range estimates, not measurements:
- Established editorial sites (news, active blogs): a new post with internal links from the homepage usually gets crawled within hours to a few days.
- Ordinary guest-post hosts: one to three weeks is common when the post sits one or two clicks from a crawled hub page.
- Forum threads, profile pages, directory entries: weeks to never. Deep pagination, few internal links, and low site authority push these to the back of the queue indefinitely.
Three variables move the queue more than anything else: how often the host site is crawled overall, how many internal links point at the specific page, and how fast the server answers. A slow or intermittently failing server causes Google to throttle its own crawling - which is precisely the "avoid overloading" scenario the documentation describes.
The comparison that sets expectations
| Page type | Typical wait (estimate) | Chance of indefinite stall | What moves it |
|---|---|---|---|
| Post on an active, frequently crawled site | Hours - days | Low | Nothing needed |
| Guest post on a mid-tier blog | 1-3 weeks | Moderate | Internal links, sitemap freshness |
| Forum thread / comment page | Weeks - months | High | External crawl paths, submission |
| Profile / directory page | Often never | Very high | Submission; often replacement |
The 14-day decision rule
Waiting costs nothing but time; the problem is unbounded waiting. A practical protocol:
- Day 0: record the donor URL list with placement dates. Normalize URLs - final destination after redirects, no tracking parameters.
- Day 7: run the list through a bulk index check - for example, see which backlinks made it into the index. Pages already indexed leave the worry list.
- Day 14: re-check the remainder. Anything still unindexed with no crawl evidence goes into active treatment: submission to an indexing service, or a request to the site owner to link the page from a crawled hub.
- Day 30: final check. Donors that resisted both waiting and submission are replacement candidates - the page itself is the problem, not the queue.
If you own or manage the hosting property, you can read the exact state instead of inferring it: the URL Inspection API exposes the coverage verdict per URL, and a script that pulls coverage verdicts for a URL list turns that into a CSV. For third-party donors the API is unavailable by design, which is why live-index checks remain the only scalable measurement.
What does not help
Refreshing the page in a browser, pinging dead ping services, and resubmitting the same URL to Search Console's inspection tool daily - none of these change crawl priority. Rewriting the content does not help either, because nobody has read it yet; content quality only becomes a factor after the fetch, at which point a stalled page moves to Crawled - currently not indexed and needs a different playbook (see the reference on the discovered status for donor pages for the field-by-field breakdown).
Caveats
Movement from Discovered to Crawled - currently not indexed is progress, not failure: the fetch happened. Expect wave behavior on borderline sites - pages entering and leaving the index across weeks. And no method, paid or free, guarantees indexing; the final call always belongs to the algorithm. Google's crawl-budget documentation (developers.google.com, "Managing crawl budget for large sites") is the authoritative description of why deferrals happen at all.
Start with the free 200 tokens if you want to test the submission path on a batch of stalled donors.