“Discovered – Currently Not Indexed”: Why Google Ignores Your Pages
Google knows your page exists. It just doesn’t think it’s worth crawling yet. That stings, but it’s fixable once you understand what the status is really telling you.
Few things in SEO sting quite like opening Search Console's Pages report and finding hundreds of URLs sitting under "Discovered - currently not indexed." Google knows those pages exist. It looked at the URL, shrugged, and decided crawling them could wait. Indefinitely, in some cases.
This status has exploded across sites in the past couple of years, and the usual advice ("just request indexing!") barely scratches it. Let's talk about what's actually going on.
What the status really means
Google separates discovery, crawling, and indexing into distinct stages. "Discovered - currently not indexed" means stage one happened (Google found the URL, probably in your sitemap or a link) but stage two hasn't: Googlebot hasn't fetched the page yet.
Its close cousin, "Crawled - currently not indexed," means Google did fetch the page, read it, and still declined to add it to the index. Different problem, related causes.
Either way, Google is making a value judgment. Crawling costs Google money, the web is functionally infinite, and its systems constantly predict whether fetching a given URL is likely worth it. When your pages pile up in these buckets, the prediction machine is saying: based on what we know about this site, these URLs probably don't add much.
Harsh. Also useful, once you treat it as feedback instead of a bug.
The real causes, starting with the most common
1. Thin or templated content at scale. Sites that generate thousands of near-identical pages (location pages with swapped city names, tag archives, filtered category combinations, auto-generated content) train Google to expect low value per crawl. Once that expectation sets in, even your good new pages inherit the skepticism.
2. Weak internal linking. A page that's only reachable through the sitemap, with zero contextual links from real pages, looks unimportant. Google reasons about your site partly through your own link graph. If you don't link to a page, why would Google prioritize it?
3. Site-wide quality or trust deficits. New domains with no reputation, sites recovering from spammy history, or sites where the indexed-to-valuable ratio is poor. Indexing rates are increasingly a site-level trust signal playing out URL by URL.
4. Server health during crawl attempts. If your host responds slowly or throws 5xx errors when Googlebot visits, Google backs off politely and your crawl capacity shrinks. Check the Crawl Stats report (Settings, Crawl stats) for response-time spikes and error rates. People forget this report exists; it's a goldmine.
5. Genuine crawl budget limits. Mostly a large-site problem (hundreds of thousands of URLs). Small sites with indexing trouble almost never have a budget problem; they have a quality-perception problem. Worth saying twice, because "crawl budget" gets blamed for everything.
What actually works
Cut the dead weight first. This is counterintuitive and it's the most effective move: reduce the number of URLs you're asking Google to index. Noindex the tag archives, the filtered duplicates, the placeholder pages, the 40 thin posts from 2019 nobody visits. Consolidate overlapping articles into one strong page with redirects. When the ratio of quality-to-junk in your sitemap improves, Google's per-crawl payoff improves, and its appetite for your remaining URLs visibly increases. A careful pruning is often what gets a stuck site indexing normally again.
Build internal links to stranded pages. For every important unindexed URL, add contextual links from your strongest indexed pages: the homepage, top category hubs, high-traffic posts. Not a footer link dump; real in-content links with descriptive anchors. This is the single fastest legitimate signal that a page matters.
Fix what the Crawl Stats report shows. Average response time creeping past 600ms or error spikes during crawls? Address hosting and caching before anything else. A faster, more reliable origin measurably increases pages crawled per day.
Keep the sitemap honest. Only canonical, indexable, 200-status URLs. Every redirect, 404 and noindexed page in there erodes trust in the file. Update lastmod truthfully when content changes, and don't fake it: Google has said it ignores lastmod from sites that lie about it.
Use Request Indexing sparingly, for what it is. It nudges a single URL into the crawl queue. Fine for your important new page; useless as a strategy for 500 URLs, and it does nothing about the underlying judgment.
What doesn't work
Resubmitting the same sitemap daily. Pinging services. Indexing APIs used off-label (the official Indexing API is meant for job postings and livestream pages; bulk-abusing it for regular content has been publicly discouraged and increasingly filtered). Deleting and re-adding the property. Adding more thin pages to "give Google more to find," which is like curing a hangover with breakfast whiskey.
Three follow-up questions, answered honestly
How long should I wait before worrying? For a new page on an established, healthy site: a few days to two weeks is normal. For a new domain: weeks, sometimes a couple of months, while trust builds. Worry becomes justified when important pages sit unindexed past a month despite good internal links, or when your indexed-page count trends steadily down without you deleting anything. Trends matter more than snapshots here.
Does posting to social media or getting the page shared help? Links from crawled pages anywhere on the web can speed up discovery, and a link from a genuinely popular page absolutely gets Google's attention. But discovery was never your problem with this status; Google already found the URL. What external signals really contribute is evidence of value, and one decent editorial link outweighs a hundred social shares for that purpose.
Should I delete pages stuck in "crawled - currently not indexed"? Not reflexively. First decide what each page is for. If it exists for users arriving from other channels (support docs, campaign landing pages), it's fine unindexed; leave it alone or noindex it deliberately. If it was supposed to earn search traffic and Google passed on it, treat that as a review: the page probably needs to be meaningfully better or merged into something stronger, not just resubmitted with crossed fingers.
A note on patience and expectations
Some pages will never be indexed, and honestly, some shouldn't be. Google's index is no longer a completionist archive of everything on the web; it's curated by predicted usefulness. The practical goal isn't 100% indexation. It's making sure the pages that matter to your business are indexed fast and reliably, which follows from a site where most crawlable URLs genuinely deserve the visit.
Prune hard, link deliberately, keep the server quick, and give it four to eight weeks. That combination deals with the usual causes of stuck indexing, without a single trick involved.
Free tools for this topic
Check your own site in 30 seconds
Run a free SEO audit and see exactly where your pages stand on the issues covered in this article.
Run Free SEO AuditKeep reading
Surviving Google Core Updates: What to Do When Your Traffic Tanks
A core update hit and your charts fell off a cliff. Before you panic-delete half your site or buy a "recovery service," read this. Recovery is real, but it doesn’t work how most people think.
Mobile-First Indexing Problems That Are Costing You Rankings
Googlebot is a phone now. Full stop. Whatever your mobile visitors can’t see, Google can’t rank, and plenty of "responsive" sites still hide half their value on small screens.