How to fix “Discovered - currently not indexed” on WordPress
If Search Console shows “Discovered - currently not indexed” on your WordPress site, you are in the right place. Google knows the URL but has not crawled it yet. This page covers the causes and a step-by-step fix for WordPress. The most widely used open-source CMS. Most indexing controls live in an SEO plugin such as Yoast SEO, Rank Math or All in One SEO.
Contents
What does this status mean?
The URL was discovered from your sitemap or a link, but Googlebot has not visited it yet. It usually comes from crawl budget, server load or the page being treated as low priority.
Likely causes on WordPress
- The site is large and Google cannot get to every URL.
- The server is slow or throws errors and Googlebot slows down to be polite.
- Many low-value URLs (filters, parameters) fill the crawl queue.
- No internal links; an orphan page known only from the sitemap.
- WordPress note: WordPress 5.5 and later serves /wp-sitemap.xml; Yoast and Rank Math use /sitemap_index.xml. Do not publish two sitemaps at once; submit only one to Search Console.
Step-by-step fix on WordPress
- In your WordPress admin go to: Settings > Reading and the post or page box of your SEO plugin.
- WordPress 5.5 and later serves /wp-sitemap.xml; Yoast and Rank Math use /sitemap_index.xml. Do not publish two sitemaps at once; submit only one to Search Console.
- A caching plugin, image compression and decent hosting raise crawl speed. Remove unused plugins; a slow server makes Googlebot crawl less.
- Link to important pages directly from the home page and category pages.
- Put only canonical, 200-returning URLs you want indexed in the sitemap.
- Take filter and parameter URLs out of crawling with robots.txt or canonicals.
- Lower server response time and error rate; watch response time in Search Console crawl stats.
- Send priority URLs through an indexing panel and follow progress with URL inspection in Search Console.
Extra checks for WordPress
- robots.txt: WordPress serves a virtual robots.txt; edit it in your SEO plugin or replace it with a real file in the web root. Review any Disallow lines beyond /wp-admin.
- canonical and duplicate URLs: Core and SEO plugins add the canonical tag automatically; override it per post in the plugin canonical field. Check whether category, tag and paginated archives are indexed on their own.
After fixing
In Search Console start "Validate fix" for this status and resubmit the page with URL inspection. First confirm the blocker is gone with the free Free indexability checker tool; for many URLs follow Bulk URL indexing: how to send thousands of pages to Google. Google makes the indexing decision itself and timing ranges from days to weeks.
More information
Frequently asked questions
What is the difference between "Discovered" and "Crawled"?
"Discovered" means Google knows the URL but has not visited; "Crawled" means it visited but did not index. The first is usually about crawl priority, the second about content quality.
Thousands of my pages have this status. What now?
First decide which ones truly need indexing and remove the rest from the sitemap and internal links. Work in priority order instead of forcing every URL at once.
Where are these settings on WordPress?
Settings > Reading and the post or page box of your SEO plugin.
Related pages
- WordPress: Duplicate without user-selected canonicalFixes
- WordPress: Duplicate, Google chose different canonical than userFixes
- WordPress: Alternate page with proper canonical tagFixes
- WooCommerce: Discovered - currently not indexedFixes
- Shopify: Discovered - currently not indexedFixes
- Wix: Discovered - currently not indexedFixes