SEO & AI search · Guide
How to Fix Discovered - Currently Not Indexed in WordPress
Short answer
To fix Discovered - Currently Not Indexed on WordPress, check that the page is published and linked from other pages, clean your sitemap so it lists only live pages you want indexed, and check your server health in Search Console. Then request indexing for a few key pages only, and wait a few days to a few weeks for Google to crawl them.
Key takeaways
- Discovered - Currently Not Indexed means Google knows a page exists but has not crawled it yet, so it cannot appear in search results.
- A Discovered page has not been fetched, while a Crawled - Currently Not Indexed page was fetched and still left out of the index.
- Google says a new page or site can take about a week to start being crawled, and crawling can take from a few days to a few weeks.
- WordPress has built a sitemap at /wp-sitemap.xml since version 5.5, and each sitemap lists up to 2,000 URLs as of November 2026.
- Requesting indexing again for the same URL will not get it crawled faster, and a request does not guarantee indexing.
- Validation of a fix in Search Console typically takes up to about two weeks, but in some cases can take much longer.
What does “Discovered - Currently Not Indexed” mean?
It means Google knows a page exists but has not crawled it yet, so the page cannot appear in search results.
Google's Page indexing report help page puts it this way: the page was found, but not crawled yet. It says Google typically wanted to crawl the URL but expected that to overload the site, so it rescheduled the crawl. That is why the last crawl date is empty. (Page indexing report)
This status is a queue position, not an error or a penalty. The same help page notes that not every URL needs to be indexed, and that some pages stay out of the index for good reasons. Your job is to work out whether the pages in this state are pages you want found.
How is it different from “Crawled - Currently Not Indexed”?
The difference is crawling: a Discovered page has not been fetched yet, while a Crawled page was fetched and still left out of the index.
The Page indexing report help page describes the Crawled status as a page Google crawled but did not index. It adds that Google does not index all pages on the web, so this message is common. (Page indexing report)
The Discovered status points at the crawl queue, while the Crawled status points at the page after a fetch. Keep the two apart, because each one needs a different fix.
| Status | What Google did | What to check first |
|---|---|---|
| Discovered - currently not indexed | Knows the URL, has not fetched it | Links, sitemap, server speed |
| Crawled - currently not indexed | Fetched the page, did not index it | Page content and quality |
| Indexed | Fetched and indexed the page | Nothing, unless it drops out |
Where do you find the status in Search Console?
You find it in Search Console under Indexing, then Pages, in the table called “Why pages aren't indexed”.
Open the property for your site, click “Indexing” in the left menu, then “Pages”. Scroll to the “Why pages aren't indexed” table and click the “Discovered - currently not indexed” row.
The detail page shows the affected URLs, the date Google first found them, and a chart of the count over time. The same help page notes that the example list in the report is limited to 1,000 items. (Page indexing report)
That list is not guaranteed to show every URL in a status, even when fewer than 1,000 URLs are affected, so treat the count as the main signal.
For one single page, use the URL Inspection tool instead. Google's help page states that the Page indexing report is not used to check the index status of specific pages. (URL Inspection tool)
Why does Google leave pages in this state?
Google leaves a page in this state when it found the URL but has not yet had room in its crawl queue to fetch it.
The usual reason given is server load: crawling the URL was expected to overload the site, so Google rescheduled the crawl. On a small site the cause is often simpler, in that Google found the URL and put it behind pages judged more useful to fetch first.
Google's crawl budget guide explains the queue with two parts: crawl capacity limit and crawl demand. Capacity is how much Google can crawl without overloading your server. (Crawl Budget Management)
Demand is how much Google wants to crawl, based on size, update frequency, page quality, and relevance. When either part is low, fewer pages get fetched.
That guide is written for very large sites: 1 million or more pages that change weekly, or 10,000 or more pages that change daily. It also names sites with a large share of URLs in this Discovered status as a target audience.
For most smaller sites, the same guide says keeping the sitemap up to date and checking the Page Indexing report is enough. You do not need a crawl budget plan for a small blog.
On a WordPress site, these patterns often sit behind a growing Discovered count:
- New pages on a new site, still waiting in the queue
- Pages with few or no internal links pointing to them
- A sitemap that lists old, duplicate, or removed URLs
- A slow or unstable server that makes Google hold back
- Thousands of low-value URLs, such as tag pages, that use up the queue
How do you check whether your important pages are affected?
Compare the Discovered count with your list of important pages, and inspect a few of those pages one by one.
- Open “Indexing”, then “Pages”, and note the Discovered count and whether the trend line is flat, rising, or falling.
- List your important pages: the home page, main service or product pages, and your newest posts.
- Paste each important URL into the URL Inspection tool at the top of Search Console and read its index status.
- Check the Discovery section of the result, which shows the sitemap or referring page Google used to find the URL.
- If an important page shows no last crawl date, it is still waiting, so act on it first.
Google's help page says that if your site has fewer than 500 pages, you probably do not need the Page indexing report at all. Instead, search for “site:yourdomain.com” in Google to see which key pages appear, and use the URL Inspection tool for single pages. (Page indexing report)
Do not expect every URL to be indexed. The same help page says duplicate URLs should not be indexed, and that non-indexed URLs can be fine when the reason is sound. Focus on pages that should bring visitors.
How do you fix it step by step?
Work through the checks in order, fix what you find, then request indexing only for your most important pages and wait.
You need these before you start:
- Access to Search Console as an owner or full user
- Access to your WordPress dashboard
- Your sitemap address, usually “/wp-sitemap.xml” or “/sitemap_index.xml”
- About 1 hour for the checks, plus waiting time after
Step 1: Confirm the page should be indexed
Open the page in WordPress and check that it is published, not a draft, and that it has real content a visitor would want. Check “Settings”, then “Reading”, and make sure “Discourage search engines from indexing this site” is unchecked.
WordPress's Learn site says this box must be clear before the core sitemap will work, and its lesson walks through the check. (Building a Sitemap for a Site)
If Yoast SEO controls your titles and indexing, review its settings before you change anything else. Yoast SEO settings explained covers each screen in the plugin.
Step 2: Give the page a clear path in
Add a link to the page from a related post or page that Google already crawls, and add it to your main menu if it matters. Google's help page says Google needs a way to find a page: a link from a known page, or a sitemap. (Page indexing report)
A page with no links pointing to it is easy for Google to leave waiting. Link new posts from older posts on the same topic, and from a category or hub page.
Step 3: Clean the sitemap
Open your sitemap in a browser and check that every URL in it is a live page you want indexed. WordPress has built a sitemap at “/wp-sitemap.xml” since version 5.5, and each sitemap lists up to 2,000 URLs. (Building a Sitemap for a Site)
If you use Yoast SEO, its sitemap index lives at “/sitemap_index.xml” instead. Check its sitemap settings in the plugin, and submit the index address, not each small file.
How to set up Yoast SEO walks through the plugin settings, including its sitemap.
Submit the sitemap index in Search Console under “Sitemaps”. Google's recrawl guide says a sitemap is an important way for Google to discover URLs, and is very helpful after a launch or a site move. (Ask Google to Recrawl Your Website)
Keep the lastmod dates honest. The sitemap protocol says lastmod is the date the page was last changed, not the date the sitemap file was built. (Sitemaps XML format)
Google's crawl budget guide recommends including the lastmod tag when a site has updated content, so a correct date helps Google plan its next crawl. (Crawl Budget Management)
Step 4: Check the server and crawl stats
Open “Settings”, then “Crawl stats”, then “Open report” in Search Console, and look at host status and average response time. Google's crawl budget guide says the capacity limit falls when a site slows down, answers with 5xx server errors, or sends rate-limit signals such as HTTP 429.
If you see those signals, ask your host to look at server errors and slow responses first. A host that cannot fix repeated 5xx errors is a hosting problem, not a Search Console problem.
Web.dev gives a rough guide for time to first byte: 800 milliseconds or less is good, and more than 1,800 milliseconds is poor. A slow server does not prove the Discovered count is a server problem, but rule it out first. (Time to First Byte)
Does page speed affect SEO explains how speed and search results connect on a WordPress site.
If the server is the bottleneck and your host cannot fix it, a move may be the answer. How to change hosting without losing SEO covers a move that keeps your search presence intact.
Support HTTP caching where you can. Google's crawl budget guide notes that a 304 Not Modified answer tells Google to reuse its cached copy, which saves your server work. Ask your host or developer about caching if you are not sure how your site handles it.
Step 5: Request indexing for a few key pages
Use the URL Inspection tool for a few important URLs only, and click “Request indexing” on each result. Google's recrawl guide says you must be an owner or full user of the Search Console property to request indexing. (Ask Google to Recrawl Your Website)
The same guide says there is a quota for individual URL requests, and that asking again for the same URL will not get it crawled faster.
Do not request indexing for hundreds of pages one by one. Google's URL Inspection help page says that if you want many pages indexed, you should submit a sitemap instead. (URL Inspection tool)
Requesting indexing also does not guarantee the page will appear in the index. It puts the URL in the crawl queue, and Google still decides whether to index it.
Step 6: Trim the low-value URLs
Cut the URLs Google does not need to crawl. Google's crawl budget guide says duplicate content wastes crawl time, and recommends consolidating duplicates, blocking unimportant URLs in robots.txt, and returning 404 or 410 for pages that are gone for good. (Crawl Budget Management)
On WordPress, that often means noindexing thin tag pages, blocking filtered shop URLs, and deleting old drafts instead of leaving them in the sitemap. Keep the sitemap to pages you want found.
For a page that moved, set up a redirect rather than leaving the old URL in the sitemap. How to use Yoast SEO redirects explains the redirect settings in the plugin.
How long does it take to clear?
Google gives no fixed date, but its recrawl guide says crawling can take from a few days to a few weeks.
For a new page or site, Google's help page says it can take about a week for Google to start crawling and indexing. If the page is new, wait a few days before you treat the status as a problem. (Page indexing report)
Indexing after a request is usually faster. Google's URL Inspection help page says indexing typically takes only a day or so, but can take much longer in some cases. A request does not guarantee the page will appear in the index. (URL Inspection tool)
Validation takes longer still. The Page indexing report help page says validation typically takes up to about two weeks, but in some cases can take much longer. Do not click “Validate fix” again until validation has succeeded or failed.
How do you know the fix worked?
The fix worked when the Discovered count falls and your important pages gain a last crawl date in the URL Inspection tool.
- Re-inspect a key URL after 1 to 2 weeks and look for a last crawl date.
- Watch the Discovered count in “Indexing”, then “Pages”, and check that it falls over 2 to 4 weeks.
- Search for “site:yourdomain.com” with a phrase from the page to see if it appears.
A falling count alone is not proof for one page. Google's help page notes that the report is not used to check single pages, so confirm each important page with the URL Inspection tool. (Page indexing report)
If the count does not move after a month, go back to the sitemap and server checks. Google does not promise a date for any single URL, so a page that stays in the queue after a month needs another look at links, duplicates, and server health.
What mistakes should you avoid?
Avoid the shortcuts that waste crawl budget and hide pages you want found.
- Requesting indexing for the same URL again and again, which Google says will not speed up the crawl.
- Submitting every small sitemap file instead of the sitemap index.
- Leaving removed, duplicate, or noindex pages in the sitemap.
- Blocking important pages in robots.txt, which stops Google from crawling them at all.
- Deleting the sitemap or switching SEO plugins without submitting the new sitemap address.
- Treating every Discovered URL as a problem, when Google says some pages should stay out of the index.
- Clicking “Validate fix” before every affected page is fixed, which stops validation at the first page still broken.
Frequently asked questions
Is Discovered - Currently Not Indexed an error?
No, it is a status, not an error or a penalty. It means Google found the URL and put it in the crawl queue but has not fetched it yet. Google says some pages should stay out of the index, so only act when the affected pages are ones you want found.
How long should I wait before worrying about this status?
Wait a few days for a new page, and a few days to a few weeks for crawling in general. Google says a new page or site can take about a week to start being crawled. If important pages are still waiting after a month, check links, the sitemap, duplicates, and server health.
Does requesting indexing guarantee my page will be indexed?
No. Requesting indexing puts the URL in the crawl queue, but Google still decides whether to index it after the crawl. Google says indexing typically takes only a day or so but can take much longer, and asking again for the same URL will not make it faster.
Should I noindex all my Discovered pages to clear the report?
No. Only noindex pages you truly do not want in search results, such as thin tag pages or filtered URLs. Noindexing important pages hides them on purpose and makes the problem worse. Fix the links, sitemap, and server first, and leave pages you want found alone.
Can a new WordPress site have hundreds of Discovered pages?
Yes. A new site has no crawl history, so Google may find many URLs through the sitemap before it has fetched them. Google says a new page or site can take about a week to start being crawled, so a large count on a new site is normal at first.
Will deleting the pages fix the report?
Deleting a page only helps if the page is gone for good, and Google recommends a 404 or 410 status for removed pages. Do not delete pages you want found just to clear a count. Fix the discovery path instead, and keep the sitemap to live pages.
Sources
- Page indexing report Google Search Console Help
- Crawl Budget Management Google for Developers
- Ask Google to Recrawl Your Website Google for Developers
- URL Inspection tool Google Search Console Help
- Building a Sitemap for a Site Learn WordPress
- Time to First Byte (TTFB) web.dev
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
