crawlmouse

Discovered – Currently Not Indexed: Why It Happens and How to Fix It

·9 min read
Quick answer
“Discovered – currently not indexed” means Google knows your page exists but hasn’t crawled it yet, so it’s a crawl-priority problem, not a penalty. The most reliable fix is stronger internal linking: add contextual links to the page from established, related pages, reduce its click depth, and stop it being an orphan.

Few things in Search Console are as quietly maddening as a page that returns a clean 200, sits in your sitemap, has no errors — and still won’t index. You submit it, you wait, you click “Request indexing” again, and nothing moves. Usually the culprit isn’t a bug or a penalty. It’s that Google hasn’t been given a strong enough reason to prioritise the page — and the strongest reason you control is how your own site links to it.

What “Discovered – currently not indexed” actually means

This status means Google is aware of the URL — it found it via your sitemap or an internal link — but hasn’t crawled it yet, so it hasn’t evaluated the content and hasn’t indexed it. Google’s own framing is that the URL is known but scheduled for crawling later based on system priority. It is not a penalty; it’s a priority delay. And if your site is new or still building authority — under a few months old especially — a lot of pages sitting in this state is normal. Google is rationing its crawl of your site until it has more reason to trust and prioritise it.

How is “Crawled – currently not indexed” different?

The two statuses look similar but sit at different stages. With Discovered, Google hasn’t crawled the page yet. With Crawled – currently not indexed, Google has visited the page and made a deliberate choice not to index it — which points to a quality, duplication, or intent-match problem rather than a crawl-budget one. Roughly: discovered is usually a crawl-priority and internal-signal issue, while crawled is usually a “this page didn’t clear the bar” issue. Neither is a penalty; both are Google being selective about what earns a place in a finite index.

Why Google skips your pages

The common causes, roughly in the order worth checking:

  • Weak internal linking and orphan pages. A page with few or no internal links pointing to it gives Google no signal that it matters. Orphan pages — those with zero inbound internal links — are one of the most common and most fixable causes of both not-indexed statuses.
  • Too much click depth. Pages buried four or five clicks from the homepage get crawled far less often. Keeping important pages shallow — via hubs and contextual links — raises their crawl priority. (More on crawl depth.)
  • Sitemap-only discovery. A URL Google only knows from your sitemap, with no internal links reinforcing it, tends to sit low in the crawl queue. The sitemap says the page exists; internal links say it matters.
  • Duplication and thin content (mostly for crawled cases). If the page closely mirrors another, or doesn’t add much beyond what’s already indexed, Google may crawl it and decline. Consolidate duplicates with canonicals and make sure the page earns its place.
  • Slow or unreliable server, and low overall site authority. A slow site gets crawled more conservatively, and a young domain simply hasn’t earned much crawl demand yet. Time and consistency help here.

How to fix it (start with internal linking)

The single most effective lever you control is internal linking, and it’s the one most people skip in favour of hammering the “Request indexing” button. Requesting indexing without changing anything rarely works; strengthening the page’s internal signals does. Concretely:

  1. Link the page from established, related pages. Find pages on your site that are already indexed and topically relevant, and add a contextual internal link to the stuck page with descriptive anchor text. Even a single strong internal link from a well-regarded page can change how Google weighs the target’s importance. A useful trick: search site:yourdomain.com “your topic” to find natural linking spots.
  2. Pull the page shallower. If it’s buried deep, add a link from a hub or a higher-level page so it sits within a few clicks of the homepage.
  3. Make it a publishing habit. Link every new page from two or three existing relevant pages on the day you publish, so it never enters the queue as an orphan.
  4. For “crawled” cases, raise the page’s value. Expand thin content, add genuine information the indexed pages lack, and resolve duplication with canonicals — then request a re-crawl.

Research consistently points the same way: strengthening internal linking can meaningfully raise how often Googlebot crawls a site, and pages that go from orphaned to well-linked are far more likely to be picked up. It won’t force Google’s hand — indexing is always Google’s decision — but it removes the most common structural reason a good page gets skipped.

How to find which of your pages are affected

Start in Search Console under Indexing → Pages → “Why pages aren’t indexed” to see the exact URLs in each status. That tells you what’s stuck; to fix it you need to know why — which of those pages are orphaned or buried. Crawling your own site surfaces that directly. Crawlmouse maps your internal-link graph and flags the pages with zero inbound links and the ones sitting too deep — the exact structural causes behind most “not indexed” statuses — for free, in the browser. Cross-reference that orphan and depth list against your not-indexed URLs, and the fixes usually name themselves. (It’s the same crawl behind a full internal-link audit.)

Does this matter for AI search too?

Increasingly, yes. ChatGPT, Claude, Perplexity, and other AI systems lean on indexed web content to answer questions and cite sources. A page that never gets indexed is largely invisible to them as well as to Google. The reassuring part is that the fixes overlap almost entirely: clear internal linking, a sensible structure, and pages worth keeping are what earn a place in Google’s index and a citation in an AI answer. And because tools like Crawlmouse grade the static HTML — what a non-rendering AI crawler actually sees — you’re fixing the site both audiences read.

You can’t make Google index a page. What you can do is remove every structural excuse for it not to — link it well, keep it shallow, make it worth keeping — and give a young site the time it needs to earn the crawl.

Frequently asked questions

What does "Discovered – currently not indexed" mean?
It means Google knows your URL exists — usually from your sitemap or an internal link — but has not crawled it yet, so it has not been added to the index. It is a crawl-priority delay, not a penalty, and it is very common on new or low-authority sites.
How is "Crawled – currently not indexed" different?
With "Crawled – currently not indexed", Google has already visited the page and made a deliberate decision not to index it. That points to a quality, duplication, or intent-match issue rather than a crawl-budget one, so it usually needs a content or structural fix, not just patience.
How do I fix "Discovered – currently not indexed"?
Start with internal linking, because weak links and orphan pages are among the most common causes. Add contextual internal links to the page from a few established, topically related pages, reduce how deep it sits from the homepage, keep your sitemap clean, and give the page a reason to be crawled. Repeatedly clicking "Request indexing" without structural changes rarely helps.
Do orphan pages cause indexing problems?
Yes — a page with no internal links pointing to it gives Google no signal that it matters, so it is often deprioritised in the crawl queue or left unindexed. Linking orphan pages from relevant, established pages is one of the most direct fixes for both "discovered" and "crawled" not-indexed statuses.
Does being indexed matter for AI search?
It does. ChatGPT, Claude, Perplexity, and similar systems draw on indexed web content to answer and cite sources. A page that is not indexed is largely invisible to them too, so the same fixes that help Google index a page also help it be discoverable in AI answers.

Keep reading