Menu
Request a storefront

LinkToLooks · Guides · Creator Desk

Creator Desk

Why are creator pages ‘discovered but not indexed’?

Google’s own definition says the page was found and not yet crawled. That makes it a fetching question rather than a quality verdict, and it is worth checking whether the bucket that matters on your site is the one Google has never heard of.

Part of: For creators

“Discovered — currently not indexed” means Google found the URL and has not crawled it. Google’s own Page indexing help says the crawl was typically rescheduled because it was expected to overload the site, and that this is why the report shows no last crawl date for these pages.

That inverts the usual advice, which treats the discovered bucket as the problem to solve and assumes a page Google knows about is a page Google has considered. It has not considered it. It has not read it. And there is a second bucket the report does not show you: URLs Google has never encountered, which the URL Inspection tool reports as “URL is unknown to Google”. Count both before you decide which one is your problem.

Table of four page states in URL Inspection: indexed, discovered but not indexed, crawled but not indexed, and unknown to Google, showing which have a last-crawl date and where to work on each.
Discovered, currently not indexed means Google found the URL and never fetched it, so the work is links and crawl priority, not a rewrite.Illustration: LinkToLooks

What the label actually means

Google’s own wording for this state is that the page was found but not crawled yet: typically Google wanted to crawl it, the crawl was expected to overload the site, and so the crawl was rescheduled. Two words in that do the work.

Not crawled. The page has never been fetched. Google’s help page says this is why the last crawl date is empty for these URLs, so the quickest test of the state is whether a last-crawl date exists at all.

Not judged. Nothing about the page’s content has been assessed, because the content has not been read. Reading the label as “Google saw it and thought it was thin” is the single most common mistake made about it, and it sends people to rewrite pages that were never opened.

Sorting your own pages by state

The split between these states depends on the site, so nobody else’s numbers will tell you yours. Measuring it takes an afternoon.

  1. Draw a sample across the whole sitemap. Take every nth URL from your sitemap rather than your newest pages. A sample weighted toward recent posts measures the queue, not the site.
  2. Inspect each URL. Use the URL Inspection tool in Search Console, or the URL Inspection API on a verified property. Google sets a daily limit on inspections per property, so a few dozen URLs is a practical sample.
  3. Put each one in a state, using the table below, and note whether a last-crawl date is shown.
  4. Split by page type if you have a theory. If you suspect one kind of page is being skipped, give it its own column and test the theory rather than assuming it.
  5. Repeat the same sample a month later. Same URLs, same method. Part of the discovered bucket is a queue, and only a repeat shows you whether it is moving.
StateWhat URL Inspection showsWhat it meansWhere to work
IndexedURL is on Google, with a last-crawl dateFetched and keptNothing to fix here
Discovered — currently not indexedNot on Google, no last-crawl dateFound, never fetchedCrawl priority: links from pages already crawled, fewer competing URLs
Crawled — currently not indexedNot on Google, with a last-crawl dateFetched, not kept for nowThe page itself. Google says there is no need to resubmit these for crawling
Unknown to Google“URL is unknown to Google”Never encounteredDiscovery: a sitemap entry and links from your other pages

Most advice fixates on the second row. Before working on it, check the size of the fourth: a page Google has never encountered cannot be helped by anything you do to its content, and the fix for it is discovery, not quality.

Keep reading

The causes you can and cannot tell apart

Search Console reports the state, never the reason. Here is what can be supported for each common explanation, and where to look.

CauseCan you tell?What to check
Crawl budget — the site is not worth much fetching yetPartlyGoogle’s crawl-budget guide is written mainly for very large sites, but it names sites with a large share of URLs in this state among its readers, and says URLs that are more popular on the internet tend to be crawled more often. The Crawl Stats report shows how often Google fetches a root-level property.
The page is genuinely thin or duplicatedNoGoogle has not read it, so this cannot be the reason it was skipped. It can still be a reason it fails later.
Discovered too recently to be reachedPartlyGoogle’s indexing help says indexing is never instant, even when you request a crawl. Some of the bucket is simply a queue, and it clears without anyone doing anything.
Internal linking too weak to signal importancePartlyGoogle says every page you care about should have a link from at least one other page on your site. Count the internal links pointing at each discovered URL; an orphan is the first thing to fix.
Technical blocking — robots, noindex, canonicalYesURL Inspection reports whether robots.txt allowed the crawl and whether the page disallowed indexing, and shows the canonical. Rule these out first; they are the causes the tool names outright.

The row marked “No” is the one worth dwelling on, because it is the one most advice tells you to fix.

The advice that does not follow

What actually moves a page out of the bucket

  1. Link to it from a page that is already indexed. Those are the pages a crawler demonstrably visits, and Google says it uses links to find new pages to crawl. This is the only lever most creators hold outright, and it costs nothing.
  2. Give the crawler less to choose from. Fewer, better pages beats more pages when the constraint is fetch budget rather than quality.
  3. Earn a link from somewhere already crawled often. Slow, unglamorous, and the only thing that changes the budget itself. It has to be earned — bought and exchanged links are against Google’s policies and we do not use them.
  4. Wait, and re-measure rather than re-guess. Part of this bucket is a queue, and Google says indexing is never instant. Re-inspect the same sample a month later before you change anything.

Frequently asked

What does ‘Discovered — currently not indexed’ mean?

Google knows the URL exists and has not crawled it. Google’s Page indexing help says the crawl was typically rescheduled because it was expected to overload the site, which is why the report shows no last crawl date for these pages.

Is it a quality penalty?

It cannot be a judgement of the content, because the content has not been read. It is a fetching decision, not an assessment.

Is discovered-not-indexed the biggest bucket?

Not necessarily, and you can check. A URL Google has never encountered is not ‘discovered’ at all: the URL Inspection tool reports it as ‘URL is unknown to Google’. Inspect a sample spread across your sitemap and count both buckets before deciding which one to work on.

Will publishing more pages help?

On a fixed crawl budget it works against you: more candidate URLs means a smaller share of them gets fetched. Google’s crawl-budget guide warns that time spent crawling URLs it shouldn’t can stop its crawlers exploring the rest of a site.

How do I check which state my pages are in?

The URL Inspection tool in Search Console, one URL at a time, free, within a daily limit per property. The field that matters most is whether a last-crawl date exists at all.

Sources and limits

Keep reading

Last verified 29 September 2026 against the Google Search Console Help and Google developer documentation pages listed above

How this page was made. Drafted with AI (Claude); not yet independently re-checked. How we work

LinkToLooks Creator Desk — the linking desk’s pages for creators and influencers: how links, disclosure and payouts work on each platform. How we work · published 3 September 2026 · updated 10 October 2026.