Discovered Currently Not Indexed: How Does It Differ From Crawled?

This point matters a lot. The same report also lists crawled currently not indexed, and that status describes a different stage. In that case, Google already crawled the page but decided not to index it. With discovered currently not indexed, the crawl step itself has not happened yet. So you should not mix the two statuses up; a later section compares them in a table. Also, a general SEO truth is worth keeping in mind here: Google rarely indexes every single page on a large site, so a few entries in this list are not an alarm on their own.

In short, discovered currently not indexed is not an error code. It simply reflects where a URL sits in Google's crawl queue. Reading the status correctly, before you react to it, saves you from chasing the wrong fix. It also keeps you from wasting time on fixes that target the wrong stage of the process.

How Does Discovered Currently Not Indexed Differ From Crawled Currently Not Indexed?

One sentence sums up the difference. With discovered, Google has not visited the page at all. With crawled, Google has visited the page but chose not to index it. This difference points you toward a different root cause.

Crawled currently not indexed usually relates to content quality or overlap with similar pages. It can also relate to the site's overall quality signals. Discovered currently not indexed, on the other hand, usually ties back to crawl prioritization, server capacity, or low site authority. So the fix differs too: one path is content work, the other is access and capacity work.

For a deeper look, see our crawled currently not indexed guide. It walks through pages Google already crawled but skipped, so we will not repeat that here. Instead, here is a quick way to tell the two statuses apart: open a sample URL and check its last crawl date. An empty date usually points to discovered currently not indexed.

Where Do You See This Status in Google Search Console?

You find this status inside the page indexing report. Google's own Search Console help article confirms that this report splits your URLs into indexed and not indexed groups. Discovered currently not indexed sits among the not indexed reasons. For the source itself, see the official page indexing report help page.

Menu names can shift over time. So instead of naming an exact button, here is what to expect in practice. Once you open the report, the list of reasons shows this label. Clicking a reason then reveals sample URLs you can inspect one by one. How does Google order that list? Usually, it puts the reason affecting the most pages near the top.

The report also shows a trend chart covering roughly the last three months. Watching that trend tells you more than a single snapshot does. For example, a number that keeps climbing tells a different story than one that stays flat.

How Does Google Discover a Page in the First Place?

Google discovers a URL through three main paths. First, an internal link from another page on your site. Second, an entry in your XML sitemap. Third, an external link pointing in from another site. Discovery differs from crawling; it only means Google has learned the URL exists.

Google also discovers URLs you submit manually through Search Console. It still crawls them only once their turn comes up. So getting a page discovered does not mean Google crawls it right away. Instead, the gap between the two depends on your crawl capacity and Google's overall prioritization.

A canonical tag can also act as an indirect discovery signal. Google may learn about the URL a canonical tag points to while processing another page. Still, a canonical tag alone never guarantees discovery; it only adds one more signal to the mix.

What Does a Real-World Scenario Look Like?

The following scenario is not a real client case; it only illustrates how the process plays out. Suppose you publish a new blog post and add it only to your sitemap, without any supporting internal links.

In this scenario, Google learns about the page through the sitemap alone. Because no internal link backs it up, the page carries a weak importance signal. As a result, its crawl turn can lag behind pages that receive more internal links. This example shows why internal linking matters so much.

Why Do Large, Multi-Page Sites See This Status More Often?

Sites with thousands of pages, such as e-commerce stores, listing platforms, and news sites, tend to show up in this report more often. The reason is simple: as the URL count grows, Google's available time per URL shrinks.

Filter combinations and auto-generated parameter URLs often drive this growth. For example, a store with color and size filters can generate a separate URL for every combination. That pushes the crawl turn for genuinely important pages further back. So the priority for large sites is clear: cut unnecessary URL generation, and add stronger internal links to the pages that matter.

What Usually Causes Discovered Currently Not Indexed?

Official Google Search Central sources point to three main factors behind this status. Let's list them first, then unpack each one below.

• Crawl prioritization: Google does not crawl every known URL at once; it prioritizes among the URLs it already knows about.
• Server capacity and response issues: a slow or error-prone server makes Google pull back on crawling.
• A new or low-authority site: sites without many links or trust signals tend to sit further back in the queue.

These three factors can also compound each other. For instance, a new site on a resource-limited host often shows this status more than either factor alone would cause.

How Does Crawl Prioritization Drive This Status?

Google's own crawl budget guide for large sites explains this well. Crawl budget combines a crawl capacity limit with crawl demand. Google tries to crawl all or most known URLs on a site, but it always prioritizes that work.

So if you carry many low-value or duplicate URLs, Google spreads part of its time across those pages too. As a result, your valuable pages can end up waiting longer. The same guide also ties crawl demand to popularity and freshness. In other words, pages people visit often, or pages you update often, earn higher crawl demand.

For more detail on which sites need to manage this, see our crawl budget guide; we will not repeat that explanation here.

How Do Server Capacity and Response Problems Delay Crawling?

Google adjusts its crawl rate based on how your server behaves. This mainly protects your server from overload. When your server responds slowly or throws frequent 5xx errors, Google throttles its crawl requests.

So a page can sit in the discovered bucket even after Google learns about it. The reason is simple: its crawl turn has not arrived yet. Checking your hosting resources and your server response time on a regular basis pays off here, especially right before traffic spikes.

Three signals are worth tracking in practice: average response time, your 5xx error rate, and your timeout count. If those signals look unhealthy, fix the server side before any content-level fix. For more on this, see our crawl rate drop guide.

Why Do New and Low-Authority Sites See This Status More Often?

A newly launched site has not built much of an internal link network yet. It also lacks external links and user signals. As a result, Google may treat it as a lower-priority source and shape its crawl time accordingly.

That said, this stage does not last forever. As your site grows and earns quality links, your crawl frequency tends to rise too, usually over months rather than overnight. Our Google sandbox guide looks at why new sites rank late from a different angle; we mention it here only as a related signal.

Also, adding a brand-new property to Search Console tends to show a higher rate at first. Google simply has not fully mapped that property yet. The rate usually improves on its own as consistent signals build up. A steady publishing schedule, a solid internal link structure, and natural external links can all help that process move faster than average, even though no fixed shortcut exists.

Does Discovered Currently Not Indexed Always Signal a Problem?

No, it does not always signal a problem. Google does not have to index every page on a site. Leaving some URLs unindexed is normal behavior. Tag pages, archive pages, and internal search result pages show up in this list often, and they usually carry little weight on their own.

On the other hand, an important page sitting in this status for weeks is worth a closer look. Separating pages that genuinely need attention from pages going through a normal wait matters here. For example, tag pages, archive pages, and internal search result pages often sit safely in this list without needing any action at all.

When Should You Act, and When Should You Wait?

The two lists below give you a rough guide. First, here are the cases where waiting makes sense.

• The page just went live, and Google is crawling the rest of your site at a healthy pace.
• Only a handful of URLs are affected, and they are low-value or parameter-based anyway.
• Your sitemap is current, and the page already appears in it.

Now, here are the cases that call for closer attention.

• An important product, service, or category page has sat in this status for weeks.
• Your server response time runs long, or your error rate stays high.
• The count of affected pages keeps climbing relative to your total page count.

How Does Internal Linking Help Fix This Status?

Google reads a page as more important when it receives more, and stronger, internal links. Orphan pages, meaning pages with no internal links at all, sit at the biggest disadvantage for discovery and crawling alike.

So link a freshly published page from relevant category pages and your top navigation. This helps Google discover and crawl it faster. It also helps your human visitors find the page, so internal linking serves two purposes at once. First, it clarifies which pages matter most on your site. Second, it spreads authority from your strongest pages toward newer ones.

Anchor text quality matters here too. Instead of a vague "click here" link, use anchor text that summarizes the target page. That gives Google extra context about the page's topic. Breadcrumb navigation works the same way; it clarifies where a page sits in your site's hierarchy.

How Does an XML Sitemap Speed Up Discovery?

A current, accurate XML sitemap tells Google directly about your important URLs. This speeds up discovery, though it never guarantees the crawl or index stage that follows. You should accept that limit upfront.

1. Confirm your sitemap includes the newly published page.
2. Resubmit the sitemap through Search Console.
3. Remove low-value, redirecting, or broken URLs from the sitemap.

Keeping the lastmod value accurate also helps Google judge which pages deserve priority. A lastmod value that never changes weakens that signal. For the full setup process, see our XML sitemap guide.

When Does URL Inspection Actually Help?

The URL Inspection tool in Search Console lets you request a manual crawl. This works best for a handful of genuinely important pages. It gives you a fast signal when you need one.

However, your daily submission quota is limited. Submitting hundreds of pages one by one is simply not practical. For large-scale issues, the real fix comes from structural steps instead: your sitemap, your internal linking, and your server performance. Treat manual requests as a supplement, not a lasting fix on their own.

The same tool also runs a live test of the page. This test shows how Google renders the page right now. That can differ from the older data stored in the report, so weigh both together.

What Steps Should You Follow to Fix This Status?

The steps below give you a practical path for important pages stuck in this status.

1. Decide whether the affected pages genuinely matter, and filter out low-value or duplicate URLs.
2. Add at least one, ideally several, internal links to pages that matter.
3. Check your server response time and error rate, and scale up hosting if needed.
4. Update your sitemap and resubmit it through Search Console.
5. For a small number of urgent pages, request indexing through URL Inspection.
6. Track the report for a few weeks afterward; results rarely show up instantly.

Can a Noindex Tag Get Confused With This Status?

Yes, this is another point people mix up in practice. A noindex tag only kicks in after Google crawls a page. With discovered currently not indexed, Google has not crawled the page yet, so it has not read any noindex tag either.

Robots.txt sits at an even earlier stage; it blocks the crawl outright. A URL blocked by robots.txt normally stays uncrawled even once discovered. The report lists that as a separate reason. For the full mechanism, see our noindex tag guide; here we only draw the line between discovery, crawling, and indexing.

Is There a Link Between This Status and Index Bloat?

Yes, an indirect link exists. A large number of low-value or parameter-based URLs eats into your overall crawl budget. As a result, Google can take longer to discover and crawl your important pages.

Our index bloat guide covers that topic in depth already, so we will not repeat it here. Still, tackling both issues together tends to pay off faster than treating them separately, since they often share a root cause.

What Are the Key Differences Between Discovered and Crawled Currently Not Indexed?

The table below lines up both statuses side by side. This helps you quickly spot which stage applies to your page. One detail makes the table easy to apply: open a sample URL's detail panel and check whether its last crawl date is empty or filled. An empty date points to discovery, while a filled date points to a completed crawl that simply did not lead to indexing.

Which Tools Can You Use to Track This Status?

The page indexing report stays your main source. It lets you track the affected URL count over time. The sitemap report and the URL Inspection tool sit in the same panel, and both complement that main report nicely.

So how should you use these three tools together? First, open the report. Then, review sample URLs. Finally, apply internal linking and sitemap fixes to the pages you prioritize. Repeating that loop on a regular basis gives you the healthiest result over time, and it also helps you catch new issues before they grow into bigger ones.

Server logs add an advanced layer worth checking too. They show how often Googlebot actually visits your site. Comparing that log data against the Search Console report helps you pin down the real bottleneck.

How Often Should You Check This Report?

A small, low-page-count site usually only needs a monthly check. On the other hand, a site running thousands of pages that change often benefits from a weekly routine.

What should you watch for during that check? A rising count can point to a new structural issue. A falling count, on the other hand, means your internal linking and sitemap work is paying off. That turns the report into a progress indicator, not only a warning list. If you work with a team, assign this check to one specific person so it does not slip through the cracks. Also, tracking this number alongside other technical SEO metrics on one simple dashboard gives your team a shared reference point.

What Mistakes Should You Avoid Around This Status?

The first mistake is overreacting. Not every discovered currently not indexed entry calls for urgent action. The second mistake is resubmitting the same URL several times a day. This burns your quota without speeding anything up.

A third mistake is treating this as a purely technical setting. Skipping content quality and internal linking altogether limits your results. Instead, the most lasting fixes usually combine the technical side with the content side.

A fourth mistake is checking the report once and never again. Publishing activity, redesigns, and server changes all shift this number over time. So turning this into a monthly habit, at minimum, helps you catch problems early. A fifth mistake is reaching for shortcuts that break the rules, such as a third-party "instant indexing" tool or duplicate content spread across several URLs. These routes rarely deliver, and they can hurt your site's overall quality signals. Instead, stick with the structural fixes this guide covers.

Conclusion: What to Remember About Discovered Currently Not Indexed

In short, this status describes the stage where Google knows a page exists but has not crawled it yet. So never confuse it with crawled currently not indexed. No fixed turnaround time exists either; the status can clear in days or take weeks, and no source guarantees either outcome.

For a quick read on your own site's internal linking, sitemap, and server performance signals, try our free SEO Checker tool. Our team has supported clients through this kind of technical indexing issue for years in the field, and the same checklist above applies whether your site runs a handful of pages or several thousand.

Core guide: What Is Digital Marketing? Its types, examples and how it is done, on one page with an interactive film that travels through the brain.