Seeing discovered, currently not indexed in Search Console sounds worse than it is. Google knows the URL exists but hasn't fetched the page yet, so nothing on it has been judged. For a new page, give it a week or so. If an important page stays stuck, check its internal links, your sitemap and your server speed, then request indexing once.
What the status means
The exact text in the Page indexing report is Discovered - currently not indexed. Google's Page indexing help defines it in one line: "The page was found by Google, but not crawled yet."
To crawl means Google's program fetches your page to read it. To index means Google stores the page so it can show it in results. Your page has passed the first step, being found, and is waiting for the second.
Google also says why this usually happens. It wanted to crawl the URL but expected that to overload your site, so it rescheduled the crawl. That is why the last crawl date for these URLs is empty.
Discovered or crawled: why the difference matters
With this status, Google hasn't read the page. Rewriting the content can't help yet, because Google hasn't seen it.
The similar status Crawled - currently not indexed is the opposite case: Google fetched the page and chose to leave it out. That one is about the page itself, and our guide to crawled, currently not indexed covers it. For discovered pages, look at how Google finds the URL and how fast your server answers.
Why Google puts the visit off
Google limits how hard it crawls each site. Its crawl budget guide splits that limit into two parts.
- Crawl capacity is how much of your server's time Google lets itself use. If your pages answer quickly, the limit goes up. If the site slows down or returns server errors, it goes down and Google crawls less.
- Crawl demand is how much Google wants your pages. It depends on your site's size, how often it changes, page quality and relevance compared with other sites.
That guide is written for big sites: over 1 million pages that change weekly, or over 10,000 pages that change daily. It also covers sites where a large share of URLs sit in this status. A small site is far below those sizes, so the checks below are usually the better place to start.
The 5 checks, in order
Start with check 1 and stop when you find the cause. The order is our view of what most often holds up a small site. Google doesn't rank the causes.
1. Is the page simply new?
Google says a new page can take a week or so to start being crawled. Once Google knows a URL, crawling some or all of your site can take up to a few weeks. Paste the full URL into the inspection bar at the top of Search Console and look for a last crawl date.
We'd give a new page two weeks with no last crawl before you dig deeper.
2. Does another page on your site link to it?
Google says every page you care about should have a link from at least one other page on your site. Its guide to crawlable links adds that Google can generally only follow a normal HTML link: an <a> tag with an href address. Open a related page, view its source and search for the URL.
If the only way in is a button or a script, add a plain text link from a page that is already indexed.
3. Is it in your sitemap, and can Google read the sitemap?
A sitemap is a file that lists the pages you want Google to know about. Google asks you to make sure it is valid and not blocked by robots.txt, the small file at the root of your site that tells search engines what they may not fetch. Open your sitemap address in a browser and search it for the URL.
Then confirm that your robots.txt has no errors blocking the sitemap. If you have no sitemap at all, start with our guide to a missing XML sitemap.
4. Is your server fast and free of errors?
This check matches Google's own explanation for the status. In Search Console, open Settings, then Crawl stats. The report only works if your Search Console property covers your whole site (for example example.com), not a subfolder.
- Host status: "Some availability issues, but not recently" means Google hit at least one serious problem in the last 90 days, but more than a week ago. "Recent availability issue" means it hit one in the last week.
- Average response time: how long, on average, your server took to answer each file Google asked for. When responses get slower, Google crawls less.
- Responses by type: Google says server errors (codes starting with 5, such as 500) should be fixed if possible. Returning "busy, try again later" errors (codes 503 or 429) for more than 2 or 3 days can also make Google crawl less.
Fix the URLs behind any pages returning errors first. If responses are slow across the site, ask your host about it before you request anything.
5. Request indexing once, then wait
For one important page, click Request indexing in the URL Inspection result. Google's URL Inspection help says indexing typically takes a day or so, but can take much longer. A request doesn't guarantee the page gets indexed, and there is a daily limit on requests.
Asking again won't help. Google's page on how to ask Google to recrawl says repeat requests for the same URL won't get it crawled any faster. For many URLs, submit a sitemap instead.
Wait or act: match your URL to a row
Find the row that describes your stuck URL. The last column is what to do next.
| What the URL is | How to tell | What to do |
|---|---|---|
| A page published in the last week or two | URL Inspection shows no last crawl yet | Wait; Google says a week or so for new pages |
| An important page nothing links to | No other page on your site has a link to it | Add a text link from a related, indexed page |
| A page missing from your sitemap | The URL isn't in the sitemap file | Add it and check robots.txt allows the sitemap |
| Many URLs stuck at once | Crawl stats shows slow responses, server errors or availability issues | Fix the server first, then let crawling pick up |
| Filter, sort or internal search URLs | The address has a ? followed by options, such as ?sort=price | Usually leave them; in our view they are rarely worth indexing |
| An important page that passes every check | Old enough, linked, in the sitemap, healthy server | Request indexing once, then give it a few weeks |
A worked timeline for one new page
Say you publish a new service page on a small business site on day 0. This is when to check what, using the times Google gives.
| When | What you see | What to do |
|---|---|---|
| Day 0 | The page is live and linked from your services page | Make sure it is in the sitemap |
| Day 7 | Still discovered, no last crawl | Nothing yet; Google says a week or so |
| Day 14 | Still discovered | Run checks 2, 3 and 4 |
| Day 15 | Every check passes | Request indexing once |
| Day 15 to week 5 | Still waiting | Don't resend; a recrawl can take a few days to a few weeks |
If the page is still discovered after that, go back to Crawl stats. A server that keeps slowing down is the cause Google itself names.
Catch the causes before Google does
UpCrawler crawls your site on a schedule and flags pages returning errors, robots.txt errors and a missing XML sitemap. Its uptime checks and slow-response alerts tell you when your server answers slowly: in the app on every plan, and by email from Starter. From Starter, the Search Console view shows Google's data next to those issues, but it doesn't replace the Page indexing report.
Want to know if your server or sitemap is holding Google back? Run a free audit of your homepage and see what the crawler finds.
Share it with whoever runs your site’s SEO.



