"Discovered - currently not indexed: what Google means and how to fix it"

Read this with AI

Read with ChatGPT Read with Claude Ask Gemini

Short answer: "Discovered - currently not indexed" means Google knows your page exists but has decided not to crawl it yet, so it cannot appear in search. Google is saying the page is not worth its time right now. The fix is to make it worth crawling: better content, links from your strong pages, and a clean, fast site.

You published a new page. You were proud of it. Then you opened Google Search Console, checked the Page indexing report, and saw those four words sitting next to your URL: "Discovered - currently not indexed." It reads like something is broken. Nothing is broken. Google found your page. It just hasn't bothered to look at it yet.

That distinction is the whole article. The page is not rejected. It is waiting in a queue, and Google decides the order of that queue based on how worthwhile a page looks before it ever reads it. Your job is to move up the queue, not to kick the door.

What "Discovered - currently not indexed" actually means

Google does two separate things with a web page. First it discovers the URL, usually from your sitemap or a link pointing at it. Then, later, it crawls the URL, which means it actually downloads and reads the page. Indexing comes after that. A page can only be indexed once it has been crawled.

"Discovered - currently not indexed" is the gap between step one and step two. The SEO firm Onely explains it plainly: Google knows the URL exists but has not crawled it yet, so it cannot be indexed yet. The page is on Google's radar. It is not in Google's library.

That matters because the fix for "found but not read" is completely different from the fix for "read and rejected." You are not fighting a penalty. You are waiting for attention, and you can earn that attention faster.

Why Google found your page and walked away

Google does not crawl every page it finds the moment it finds it. It has a rough budget of how much of your site it will bother to read, and it spends that budget on the pages it expects to be useful. When a new URL does not look promising, Google parks it in the "discovered" pile and comes back later, or not at all.

A few things push a page into that pile:

The content looks thin or low value, so Google guesses the crawl is not worth it.
The page has almost no internal links pointing at it, so it looks unimportant and hard to reach.
Your site has a lot of near-duplicate or low-value URLs, so Google spreads its attention thin.
Your server was slow or overloaded when Google tried, so it backed off.

That last one is easy to miss. Rank Math's documentation notes the status can appear when Google tried to crawl the URL but your site was overloaded, so it rescheduled the crawl for later. In plain terms: Google knocked, your site took too long to answer, and Google decided to try again another day. Server performance is a real cause, not just a content one.

Here is the pattern I see again and again on owner-run sites. Someone publishes ten pages in a weekend, all short, all on a site with barely any internal links, hosted on a cheap plan that chokes under load. Every new page lands in "Discovered - currently not indexed," the owner panics, and the real problem was never any single page. It was that nothing about the site told Google these pages were worth the trip. Fix the signals, and the queue starts clearing.

Site owners on r/TechSEO have spent long threads working through exactly this, trying to pin down whether their cause was thin content, weak linking, or a slow server. The honest answer from those threads is that it is usually a mix, and the only way to know is to work through the likely causes one at a time. That is what the rest of this does.

If you run a small site, you probably don't need to panic

Before you change anything, a dose of calm. If your site is small, under roughly ten thousand pages, and your content is genuinely useful, this status very often clears on its own. Onely makes the same point: for small sites with good-quality content, "Discovered - currently not indexed" tends to resolve by itself, and it is the recurring, site-wide cases that point to a real content or crawl problem.

Google's own Search Console Help backs up the patience angle too. It notes that newly discovered content can simply take time to be crawled, and that pages land in the "Not indexed" group for a reason worth reviewing rather than a reason worth fearing. A brand-new page showing this status in its first week or two is normal, not a red flag.

So here is when to relax and when to act. One or two new pages showing the status, on a healthy site, a few weeks old? Wait. Give it time. Half your pages stuck in "discovered" for a month or more? Now it is a signal, and you work the fixes below in order.

Fix 1: Make the page worth crawling

Start with the page itself, because this is the lever with the most leverage. Google is guessing at your page's value from the outside. Give it less to guess about.

A useful page answers a real question fully, in a way a searcher would thank you for. A bakery's "do you do wedding cakes" page that is two sentences long looks skippable. The same page with your actual process, your lead time, a price range, and three photos looks like something worth reading. You did not stuff keywords. You made it genuinely more useful, and useful is what earns the crawl.

Ask one blunt question of every stuck page: if a customer landed here, would they get what they came for, or would they bounce back to Google? If the honest answer is bounce, that is your first fix, and no amount of requesting indexing will paper over it. Our guide on how to rank a brand-new website walks through the quality baseline a fresh page needs before it can compete at all.

Fix 2: Link to the page from your strong pages and your sitemap

Google judges how important a page is partly by how many other pages point at it, and how important those pages are. An orphan page, one with no internal links, looks like a dead end. Google sees no reason to hurry.

So link to the stuck page from pages that already get crawled and indexed. Your homepage, your main service pages, a popular blog post: each internal link is a small vote that says "this one matters, go read it." Three or four good links from strong pages will do more than thirty from a buried footer. Our walkthrough on internal linking for small business sites shows where those links actually carry weight.

Then confirm the page is in your sitemap, the file that lists every URL you want Google to know about. If you are not sure what that is or whether yours is working, start with what a sitemap is and how to check yours. A page that is both linked internally and listed in a clean sitemap is far harder for Google to ignore.

Fix 3: Clean up your site so Google isn't wasting crawls

Google spends a limited amount of attention on your site. Every junk URL it crawls is attention it did not spend on the page you care about. When a small site has thousands of thin tag pages, filtered product variants, or near-empty archive pages, Google burns its budget on noise and leaves your good pages in the "discovered" pile.

The fix is to stop feeding it noise. Trim or block the low-value URLs. Make sure you are not generating dozens of near-identical pages by accident, which is common on shop platforms that spin up a new URL for every color, size, and sort order. Fewer, better URLs means Google reaches the pages that matter sooner.

Speed belongs in this cleanup too. Remember Rank Math's point about overloaded servers rescheduling the crawl. If your site is slow to respond, Google crawls less of it. A faster site is a more crawlable site, which is why site speed and crawling are tied together more tightly than most owners expect.

Fix 4: Request indexing for a few key pages, not all of them

Only now do you reach for the button everyone wants to press first. In Search Console, the URL Inspection tool has a "Request indexing" function, and Google's Search Console Help confirms this is the supported way to ask Google to crawl a page that is missing from search.

It works. It is also not a volume tool. Requesting indexing nudges Google to look sooner at a specific, genuinely important page. It does not raise a thin page's quality, and hammering it across fifty URLs does nothing except waste your afternoon. Use it for the handful of pages that truly matter, once, after you have done the work above. Then leave it alone.

If indexing is a broader headache across your whole site, not just this one status, our general guide on getting Google to index your site covers the wider checklist that surrounds this single report.

How long to wait, and how this differs from "Crawled - currently not indexed"

Give a healthy fix two to four weeks. Crawling is not instant, and Search Console's report can lag behind reality by days. If you have improved the page, linked to it well, and your site is clean and fast, the status clearing is a matter of Google getting around to it.

One contrast worth knowing. "Discovered - currently not indexed" means Google has not read the page yet. "Crawled - currently not indexed" means Google did read it and chose not to index it anyway. The second is a harder message, because it is about the page's quality or its similarity to pages already indexed, not about crawl priority. If your status shifts from "discovered" to "crawled but not indexed," that is progress of a sort: Google finally looked. Now the work is purely about making the page clearly better and more distinct. If your page is still hidden for broader reasons, why your website isn't showing on Google covers the fuller list.

Frequently asked questions

Is "Discovered - currently not indexed" bad for my whole site?

No. On its own it is normal, especially for new pages on a small site. It only signals a real problem when it affects a large share of your pages for weeks, which points to a site-wide content or crawl issue rather than one slow-to-crawl page.

Will requesting indexing fix it?

Sometimes, for one important page, and only after the page is worth crawling. The URL Inspection tool's "Request indexing" function asks Google to come sooner, but it does not improve a thin page or make a slow server faster. Do the quality and linking work first, then request indexing for your few key pages.

How long until Google crawls the page?

For a healthy page on a clean site, usually within a few weeks. Google's documentation notes that newly discovered content can simply take time. If nothing has changed after a month and you have already improved the page and its internal links, that is when to dig into server speed and site architecture.

What's the difference between "discovered" and "crawled" not indexed?

"Discovered - currently not indexed" means Google has found the URL but has not read it yet. "Crawled - currently not indexed" means Google read it and decided not to index it. The first is about crawl priority; the second is about the page's quality or how similar it is to pages already in the index.

Google found your page and walked away because nothing told it the trip was worth making. So tell it. Make the page genuinely useful, link to it from the pages Google already trusts, keep your site clean and fast, and give it a couple of weeks. That is the work Fonzy does quietly in the background for small-business sites, so the pages you are proud of stop sitting in a queue and start showing up.

Sources

Roald

Founder Fonzy. Obsessed with scaling organic traffic. Writing about the intersection of SEO, AI, and product growth.