Discovered — Currently Not Indexed: The Silent Cause Nobody Checks
“Discovered — currently not indexed” means Google knows your page exists but hasn’t crawled it — and if pages sit there for weeks, Google is telling you it can’t find a good path to them. We know because it happened to this site: every blog post we published sat in that state for months. The cause wasn’t content quality or crawl budget. It was broken internal links severing the crawl paths — and we were completely blind to it.
The Story: A Blog Google Refused to Read
We ship a content blog for the usual reason: earn search traffic in a category we know well. Posts went out, the sitemap listed them, and Search Console showed them as discovered. Then… nothing. Week after week, every post stayed at “Discovered — currently not indexed.” No errors. No warnings. No traffic.
The instinct is to blame content quality, or to resubmit the sitemap and wait harder. We did both. What finally cracked it was crawling our own site the way Googlebot does — starting at the homepage and following links. The crawl never reached the blog. The links that should have led there were broken, so every post behind them was unreachable by any crawl path. The sitemap said “these pages exist”; the site itself offered no way to walk to them. Google believed the site.
One fix to the internal links later, the posts started moving into the index. Months of invisibility, caused by a bug that took sixty seconds to see — once we actually looked.
What Each Indexing Status Actually Tells You
Search Console’s page-indexing statuses get conflated constantly. They mean very different things, and the fix is different for each:
| GSC status | What it means | Most common cause |
|---|---|---|
| Discovered — currently not indexed | Google knows the URL exists but hasn't even crawled it yet | Weak or severed internal links, few external links, low perceived priority |
| Crawled — currently not indexed | Google fetched the page and chose not to index it | Thin or duplicative content, quality signals, near-duplicates |
| Excluded by 'noindex' tag | You told Google not to index it | A noindex meta tag or X-Robots-Tag header — sometimes left in by mistake |
| Blocked by robots.txt | Google isn't allowed to fetch the page at all | A disallow rule covering the path — often broader than intended |
| Alternate page with proper canonical tag | Google indexed a different URL it considers the original | Canonical pointing elsewhere — intentional or a template bug |
The one this post is about — Discovered, not crawled — is the pre-crawl state. Google hasn’t judged your content at all yet. Which is exactly why content-side fixes don’t move it: the problem is upstream, in whether crawlers can and want to reach the page.
Why Broken Internal Links Are the Silent Killer
Googlebot discovers the web by following links. Your sitemap is a hint, not a crawl path — a page that appears in the sitemap but that no internal link points to (an orphan page) is a page your own site never vouches for. Crawlers deprioritize it, often indefinitely.
Broken internal links create orphans wholesale. One dead link in a navigation component can sever the path to an entire section — every page behind it loses its referrer in the link graph at once. And nothing tells you. The pages still render fine when you visit them directly. The sitemap still lists them. Analytics just shows the slow flatline of traffic that never arrives.
The Same Failure Hides You From AI Search
Here’s the part most technical-SEO writeups miss: the crawlers behind AI answers — OAI-SearchBot (ChatGPT search), Claude-SearchBot, PerplexityBot — discover pages the same way Googlebot does. A severed crawl path doesn’t just cost you Google rankings; it makes your pages unquotable and uncitable by every answer engine. If AI can’t reach the page, it can’t cite you — it cites whoever it could reach.
How to Diagnose It in 60 Seconds
The check is mechanical, and you can do it by hand:
- Crawl from your homepage, following internal links only. Note every page you can reach.
- Diff that set against your sitemap. Anything in the sitemap you never reached is orphaned or behind a broken link.
- Check the blockers while you’re at it: robots.txt rules broader than intended, stray noindex tags on pages you sitemap, canonicals pointing somewhere else — and whether your robots.txt blocks the AI search bots outright.
Or let a crawler do it. We turned the exact diagnosis that saved this blog into a free tool: it walks your site like Googlebot, diffs the result against your sitemap, checks the robots/noindex/canonical blockers and AI-crawler access, and — because most of these fixes are one-line code changes — hands you a copy-paste prompt for your coding agent (Claude Code, Cursor, Hermes) that repairs the causes and opens a pull request.
Is your site invisible? Check it in 60 seconds
Type your domain. See every orphan page, broken internal link, and blocked crawler standing between your pages and the index — Google’s and AI’s alike.
Run the free crawl checkFrequently Asked Questions
What does "Discovered — currently not indexed" mean in Google Search Console?
It means Google knows the URL exists — usually from your sitemap — but hasn't crawled it yet, and therefore can't index it. The page is in Google's to-do list, not its index. If pages sit in this state for weeks, it's a signal Google doesn't consider them worth fetching, most often because too few links point at them.
How do I fix "Discovered — currently not indexed"?
First verify the page is actually reachable by following links from your homepage — this is the step almost everyone skips. If a page is only listed in your sitemap and no internal link leads to it (an orphan page), fix the internal linking: add links from your navigation, a listing page, or related content. Then confirm robots.txt and noindex aren't interfering, and request indexing in Search Console. Sitemap submission alone rarely fixes it, because the sitemap is a hint, not a crawl path.
Can broken internal links stop Google from indexing my pages?
Yes — this is one of the most common silent causes. Googlebot discovers most pages by following links. If the link from your homepage to your blog index is broken, every post behind it loses its crawl path and can sit at "Discovered — currently not indexed" indefinitely, even while the sitemap dutifully lists every URL. Nothing errors and nothing warns you; the pages simply never surface.
What is an orphan page?
A page that exists and may even be in your sitemap, but that no internal link on your site points to. Crawlers that discover by following links either never find it or treat it as low priority. Orphan pages are invisible in the truest sense: your own site never vouches for them.
Do broken crawl paths affect AI search engines like ChatGPT and Perplexity too?
Yes. The crawlers behind AI search — OAI-SearchBot for ChatGPT search, Claude-SearchBot, PerplexityBot — discover pages the same way Googlebot does: by following links and reading sitemaps. A page that Googlebot can't reach is a page AI engines can't read, quote, or cite. Fixing crawl paths is a prerequisite for both traditional SEO and AI search visibility.
How can I check if my site has broken crawl paths?
Crawl your own site the way Googlebot does: start at the homepage, follow every internal link, and compare the set of pages you reached against your sitemap. Anything in the sitemap you couldn't reach is orphaned or behind a broken link. openllmrank's free crawl check does exactly this in about a minute — no signup — and hands you a fix prompt for your coding agent.
Cited is the goal
The crawl check tells you whether engines can reach your pages. The openllmrank report tells you whether ChatGPT, Claude, Gemini, Perplexity, and Grok actually cite your brand — and who they cite instead. $29.99, delivered in about fifteen minutes.
Get my report — $29.99