Google Found Your Page. It Just Hasn’t Indexed It Yet.
Here’s The Difference.
A new page sitting in Google Search Console marked “Discovered – currently not indexed” looks like bad news. Most of the time it just means Google hasn’t gotten around to the page yet – and the fix has almost nothing to do with the page itself.
“Discovered – currently not indexed” in Google Search Console means Google knows a page exists but hasn’t crawled it yet – it is not an error, a penalty, or proof the page is broken. It is a scheduling status, not a quality judgement. The page usually clears on its own once it’s properly linked from elsewhere on the site, though a brand-new or poorly-linked page can sit in this status for weeks. Clicking “Request Indexing” on one important page can help; doing it repeatedly across many pages does not.
A small business owner publishes a new service page, waits a few weeks, then checks Google Search Console to see how it’s doing. Instead of an indexed page with impressions, there’s a line in the Pages report reading “Discovered – currently not indexed.” No error message, no clear next step – just a status that sounds like something went wrong.
Almost nothing went wrong. This is one of the most common statuses a small or newer website sees in Search Console, and in the large majority of cases it resolves itself once the page has the internal signals Google expects to see before prioritising a crawl – not after a technical fix to the page.
“Discovered – Currently Not Indexed” Means Google Found The URL But Hasn’t Crawled It Yet
Google learns a URL exists in a few ways – most commonly through your XML sitemap, or by following a link from another page it has already crawled. Once it knows the URL exists, that URL gets added to a queue of pages Google intends to visit. “Discovered” just means the URL made it onto that list. It does not mean Google visited the page, read its content, or made any judgement about it at all.
This is a completely different situation from a page Google has already crawled and then chosen not to index – and mixing the two up is the single most common reason business owners panic over a status that, on its own, usually isn’t a problem.
“Crawled – Currently Not Indexed” Is The One Worth Worrying About
If Search Console instead shows “Crawled – currently not indexed,” Google did visit the page and then deliberately decided not to add it to the index – usually because the content looked thin, too similar to another page already indexed, or otherwise not worth serving in search results. That status points at the page itself. “Discovered – currently not indexed” points at Google’s own scheduling, not at your content.
| Status | What Google Has Actually Done | What It Usually Means |
|---|---|---|
| Discovered – not indexed | Knows the URL exists. Has not crawled it yet. | A scheduling/priority delay, not a content problem |
| Crawled – not indexed | Visited and read the page in full. | Google judged the content not worth indexing as-is |
| Indexed | Visited the page and added it to the index. | The page can appear in search results |
This Status Is Common For New And Small Sites, Not A Sign Something Is Broken
Google does not crawl every discovered URL on the same schedule. How often and how quickly it revisits a site depends partly on how important it currently judges that site and that specific page to be – a mix of signals like how many other pages already link to it, how established the domain is, and how often the site tends to publish and get linked to from elsewhere. A newer domain, or a page that’s only reachable through the sitemap and not linked from anywhere a visitor would actually click, sits lower in that queue almost by definition.
None of this means the page is penalised. It means Google hasn’t yet had a reason to treat crawling that specific URL as urgent – and for a small business site publishing one new page at a time, that is the normal, expected starting position, not a red flag.
Four Checks Rule Out An Actual Problem Before You Blame Google’s Queue
Before assuming the delay is simply Google’s own scheduling, it’s worth ruling out the handful of genuine technical mistakes that can also produce this exact status.
Confirm robots.txt isn’t blocking the page
A single accidental Disallow rule can keep an otherwise fine page sitting undiscovered indefinitely.
Check the page doesn’t carry a stray noindex tag
Some page builders and SEO plugins apply a site-wide default that can accidentally catch a new page.
Confirm the page returns a normal 200 status
A redirect loop or an intermittent server error can look identical to a simple scheduling delay from the outside.
Check the page is actually linked from somewhere
A page only reachable through the sitemap, with zero internal links pointing to it from the rest of the site, is the single most common real cause of a long delay.
A business publishes a new service page two different ways
The page is added to the sitemap and left there – no link from the homepage, the nav, or any existing blog post. It sits in “Discovered, not indexed” for weeks.
The same page is also linked from the homepage services section and mentioned in one relevant blog post. It’s typically crawled and indexed within days.
Discovered is not broken. It’s a page waiting its turn, not a page Google rejected.
Internal Links And A Resubmitted Sitemap Help More Than Repeatedly Clicking “Request Indexing”
Search Console’s URL Inspection tool has a “Request Indexing” button, and using it once on a genuinely important page – a new core service page, say – is a reasonable thing to do. It does not, however, scale as a strategy: it has a daily quota, it does not change how Google prioritises your site overall, and clicking it repeatedly on the same page does nothing to address the actual reason Google deprioritised it in the first place.
The more durable fix is giving the page the same signals an already-indexed page has: a link from the homepage or a relevant nav menu, a mention from an existing, already-indexed blog post, and – if the page genuinely matters – a link from somewhere outside the site entirely, the same way a new business listing or social mention tells Google a page is worth paying attention to sooner.
Link to the new page from at least one already-indexed page on the same site – the homepage, a relevant service page, or a blog post that naturally mentions it – before resubmitting the sitemap. A single relevant internal link usually does more than repeated manual indexing requests.
A Few Weeks’ Wait Is Normal; Months Without Any Change Is Worth A Second Look
There is no official published timeline for how long “Discovered – currently not indexed” is supposed to last, and it genuinely varies by site. Many small business pages clear this status within days to a few weeks once they’re linked properly. A handful of pages sitting in this status briefly, especially right after publishing, is normal on almost every site.
It becomes worth a closer look when a page that genuinely matters – a core service page, not a minor tag or archive page – stays in this exact status for months despite passing the four checks above and having a real internal link pointing to it. At that point, the more useful next question usually isn’t “why hasn’t Google indexed this,” but whether the page itself offers something genuinely different from what’s already indexed elsewhere on the site.
Being Found Eventually Isn’t The Same As Being Found Fast
Both Hamara Ashiyana and Hashika Vyas DT started from a website with no existing authority or crawl history behind it – the same starting position as any new page sitting in “Discovered, not indexed” today. Neither result came from a single trick that sped things up overnight; both came from steadily building the ordinary signals – internal links, consistent content, a site worth returning to – that eventually make a page or a whole site worth crawling and ranking on its own schedule, not Google’s slowest one.
Questions business owners ask about Search Console indexing
What does “Discovered – currently not indexed” mean in Google Search Console?
It means Google’s systems know a URL exists – usually from your sitemap or a link somewhere – but Google has not yet crawled it. The page has not been rejected or penalised; it is simply waiting in a queue Google has not gotten to, based on how it currently prioritises crawling your site.
Is “Discovered – currently not indexed” the same as “Crawled – currently not indexed”?
No, and the difference matters. “Discovered” means Google has not visited the page at all yet – a scheduling issue. “Crawled – currently not indexed” means Google did visit the page and then made an active decision not to index it, usually because the content looked thin, duplicate, or otherwise not worth adding to the index. The second one is a content problem; the first one usually is not.
How long does it take for Google to index a page stuck in “Discovered, not indexed”?
There is no officially published timeline, and it varies by site. Many small business pages clear this status within a few days to a few weeks once they are properly linked internally and the site has some existing crawl history. A brand-new domain with very few internal or external links pointing anywhere can wait considerably longer, simply because Google has little reason yet to visit it often.
Does clicking “Request Indexing” repeatedly help get a page indexed faster?
Using the URL Inspection tool’s “Request Indexing” once for a specific, important page is reasonable and often helps that one page. Clicking it repeatedly across many pages does not speed up your site’s overall crawl priority, has a daily quota, and does not fix the underlying reason Google is deprioritising those pages – which is usually weak internal linking or a lack of signals suggesting the page matters.
Should I worry if only one or two pages show this status?
Not usually. A handful of newer or less-linked pages sitting in “Discovered, not indexed” for a short while is normal on almost every small site, including ones that are otherwise healthy and ranking well. It becomes worth investigating only when an important page – like a core service page – stays in this status for months despite being properly linked and technically sound.
Want Someone To Check Why
Your Pages Aren’t Indexed?
We’ll go through your Search Console account, tell you which pages are genuinely stuck and why, and fix the internal linking and technical issues that are actually holding them back.
Talk to Us on WhatsApp