Discovered - currently not indexed: What It Means and How to Fix It
Updated: Nov 12

"Discovered - currently not indexed" means Google knows the page exists but has not fetched it yet. On a new or small site, the first move is to wait a little and help Google find the page. If the same pages stay on this list for weeks, check the links pointing to them and your sitemap first.
What does "Discovered - currently not indexed" mean?
Google has the address, perhaps from your sitemap or a link, but has not visited the page. Google's help gives its usual reason in plain terms: "Typically, Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl. This is why the last crawl date is empty on the report."
In other words, nothing has been judged yet. Google has not read a word of the page, so this is not a verdict on its quality. It is a place in a queue.
Should you wait or act?
Wait if the pages are new and your site is small. Act if important pages have sat here for several weeks, or if new pages keep joining the list faster than old ones leave it. Google's own help notes that a site with fewer than 500 pages probably does not need this report at all.
Your situation | Wait or act | Why |
You published the pages in the last week or two | Wait | Google says new pages can take a week or so to be crawled |
The pages are linked from your menu or other pages, and in your sitemap | Wait, then request indexing for the most important one | Google can already find them |
The pages are linked from nowhere on your site | Act: add links | Google finds pages through links and sitemaps |
The pages are missing from your sitemap | Act: fix the sitemap | A sitemap is one of the two ways Google finds pages |
Hundreds of similar pages, such as filtered lists | Act: cut the copies | Google may spend its visits on addresses that do not matter |
URL Inspection reports "Hostload exceeded" | Act: talk to your host | Google holds back when the server cannot keep up |

From Capron Media: the free Lite subscription

Is your site in good shape? See it in plain words
See what on your site needs fixing, counted by urgency, with the top three in plain words. Lite does not include the work on your site. Starter does.
Is crawl budget the reason on a small site?
Rarely, by Google's own account. Crawl budget is how many pages Google will fetch from a site in a given time, and Google's guide to it says it is written mainly for large sites. If your site does not have many pages that change fast, Google says, "you don't need to read this guide."
The guide names three kinds of site it is meant for: very large sites, sites over about 10,000 pages whose content changes daily, and sites with a large share of their pages in this exact status. So the honest answer is mixed. A small site is unlikely to have a budget problem, but a long list of discovered pages is one of the signs Google itself lists.
Why Google finds a page and then waits
Google's help names one reason, a crawl rescheduled so the site is not overloaded. Owners also see this status when Google has little reason to hurry: the page is linked from nowhere, or sits among many near-identical pages. The table below gives each likely reason, a way to check it, and what to change.
Likely reason | How to check | What to change |
Google rescheduled to avoid overloading your server | URL Inspection or your host reports slow responses | Ask your host about capacity |
No page on your site links to it | Search your own menus and posts for a link to it | Link to it from related pages |
It is only in the sitemap | It is in sitemap.xml but nowhere in your navigation | Add links as well; Google calls a sitemap a hint |
Many similar addresses compete for visits | Hundreds of filter, tag or parameter pages | Remove or consolidate the copies |
The page is very new | Published in the last week or so | Wait |
On our own site, when Wix last inspected it for us on October 5, 2026, Google had 11 of our 109 pages in this status. All 11 were blog posts, and all 11 were already listed in our sitemap. Being in the sitemap had not been enough on its own.
How to check discovered pages in Search Console
The report lists the addresses; URL Inspection tells you how Google found each one. That second part matters here, because the fix depends on whether Google learned of the page from your sitemap, from a link, or from neither.
Go to Indexing, then Pages, then scroll to "Why pages aren't indexed".
Click "Discovered - currently not indexed" and look at the example addresses.
Open an important one in URL Inspection.
Expand Page indexing and read Discovery: the Sitemaps line and the Referring page line.
An empty Referring page line can mean no page links to it, or only that Google is not showing one.
Click Test live URL to confirm the page loads and can be indexed.
How to fix "Discovered - currently not indexed", step by step
The fix is to give Google a clear path to the page and a reason to fetch it soon. Start with links from your own site, then the sitemap, then a single request. Much of this is work you do once and every later page benefits from.
Pick the pages on the list that matter to your business.
Add a link to each from your menu, your home page or two related pages, with words that describe it.
Check each page is in your sitemap, and that the sitemap is submitted in Search Console.
Remove or merge near-identical pages that add nothing, such as duplicate tag or filter pages.
If URL Inspection mentions a server or host problem, raise it with your host.
Open URL Inspection on your most important page and click Request indexing.
Step 2 is the easiest one to miss. A sitemap tells Google a page exists; a link from a page Google already visits tells it the page matters.

Stuck on "Validation started"? What it means and what to do
It means Google is still working through the list, not that it failed. After you click Validate fix, Google checks a few pages at once, then rechecks the rest as it gets to them. For a status about pages Google has not visited, that can take a while. Google's own guide says to wait for the cycle to finish.
The validation shows Started while it works, and Looking good once the first rechecked page passes. It ends as Passed when every listed page is fixed, or Failed as soon as one still shows the problem. Google says validation "typically takes up to about two weeks, but in some cases can take much longer." While you wait, do not click Validate fix again, and keep adding links to the pages that are still waiting.

Helping Google reach the page on Wix and Squarespace
Both platforms build and update a sitemap for you, so the work that is left is linking and patience. Here is what each one's help says about this status and about sitemaps, read on November 2, 2026. The link-building steps above work the same on WordPress and Shopify.
Wix. Wix keeps your sitemap current on its own: its help says "Wix automatically updates your sitemap when you make changes to your site," and when you connect Search Console through the Wix SEO Setup Checklist, Wix submits the sitemap to Google for you. Wix's article on this status suggests testing the page with Test Live URL in Google's URL Inspection tool, and giving each page text that is not repeated on your other pages. To check every page's status in one place, use Site Inspection under SEO & GEO, then Tools and settings.
Squarespace. Squarespace's help describes this status in one line: the page "was found by Google, but hasn't been crawled yet," and points you to Google's documentation. Squarespace handles its own robots.txt file, so the levers you control are links between your pages and your content.
How to confirm Google has reached the page
Open the page in URL Inspection. Once Google has fetched it, the last crawl date fills in and the status changes, to indexed or to another reason. Either way the page has left the queue. How soon is not fixed: Google puts a crawl at "anywhere from a few days to a few weeks".
If the status changes to "Crawled - currently not indexed", Google has now read the page and chosen not to keep it, which is a different problem with a different fix. Our guide to "Crawled - currently not indexed" covers it.
Other "page not indexed" reasons, and where this one fits
This status is the earliest point in Google's process: the address is known, nothing else has happened. Every other reason below comes after Google has tried to fetch the page, or after it has read it. The second column says what has happened in each case that has not happened here.
Status | What has happened that has not happened here |
"Crawled - currently not indexed" | Google fetched and read the page, then left it out |
Blocked by robots.txt | Google tried and your robots.txt file told it not to fetch the page |
Excluded by 'noindex' tag | Google read the page and found an instruction to leave it out |
Soft 404 | Google read the page and took it for an empty or missing one |
Page with redirect | Google reached the address and was sent on to another page |
Alternate page with proper canonical tag | Google read the page and filed it as a copy, as your tag asked |
Duplicate without user-selected canonical | Google read the page and filed it as a copy on its own judgement |
Duplicate, Google chose different canonical than user | Google read the page and disagreed with your choice of main version |
Ways to see which pages Google is not reaching
Start with the waiting pages your own site links to least. Google's tools show the status after the fact; a crawl of your site shows the links before Google decides. These options cover both, from the free tools you already have to a full review of the site.
Option | What it shows about pages Google has not reached | Cost |
Page indexing report | The addresses waiting in this status, as a sample | Free |
URL Inspection | How Google learned of one address, and whether it can fetch it now | Free |
A crawler, such as Screaming Frog | Internal links and link counts for each page it crawls | Free version crawls up to 500 URLs, as of November 2, 2026 |
Capron Media (ours) | Free check, with a free Lite subscription: a short, plain read of a website: what to fix first across the site, on its home page, and in its local results | Free |
For the full list of what needs fixing on your site, with the fixes, the SEO Audit on our SEO audit services page is checked by a person before it reaches you; prices are on our pricing page. Our SEO audit guide explains what an audit contains, and our technical SEO audit guide covers crawling and indexing checks.
Questions about discovered pages
What does "URL is unknown to Google" mean, and how is it different?
It is a message in URL Inspection, not a row in this report. It means Google has not seen the address at all. "Discovered" means Google has the address and has not fetched it. For an unknown address, Google's advice is to request indexing for it.
What does "not indexed" mean?
It means the page is not stored in Google's index, so it cannot appear in search results. The reason row tells you why. For this row, the why is that Google has not fetched the page yet.
Should I request indexing for every discovered page?
No. Google limits how many individual requests you can make, and asking twice does not speed things up. Request indexing for your most important pages, and let links and your sitemap carry the rest.
What does "indexed" mean?
Indexed means Google has fetched the page, processed it and stored it, so it is eligible to appear in search. Eligible is the key word: being indexed is the step before ranking, not a promise of a place in results.
From Capron Media: the free Lite subscription

See what to fix first on any website
Your own site doesn't use up a check. You can check up to three other sites, each once every 30 days. Lite does not include the work on your site. Starter does.
Written by Spencer Capron, founder of Capron Media, a Middleborough, Massachusetts SEO service for small business owners. Spencer is HubSpot SEO II certified, holds CompTIA Security+, and has run recurring SEO programs for 30+ small-business clients. He wrote this post in collaboration with our AI agents, and he reviews everything published here.





Comments