Quick answer: “Discovered – currently not indexed” means Google knows the URL but has not crawled it yet. In WordPress, first confirm the page deserves indexing, then check that it returns a stable 200 response, is not blocked, appears as the correct canonical URL in the Yoast sitemap, and has crawlable internal links. Improve thin or duplicative pages before requesting indexing. A sitemap and an indexing request are hints, not guarantees.
What “Discovered – currently not indexed” means
Search Console uses this status when Google has discovered a URL—often through a sitemap, an internal link, or a previously known URL—but has not yet fetched it. This is different from “Crawled – currently not indexed”, where Google already visited the page and decided not to add it to the index at that time.
The status is not automatically an error. Google says most sites should not expect same-day crawling, and new pages can take several days or longer to be noticed. You should investigate when important, unique pages remain in this state for an extended period, the affected count keeps rising, or Crawl Stats shows availability problems.
Step 1: Decide whether the URL should be indexed
Do not try to index every WordPress URL. Search results, tag archives, author archives, attachment pages, filtered URLs, duplicate category paths, and expired content may not provide standalone value. Open the example list in Search Console and separate the URLs into two groups:
- Important canonical pages: original posts, useful landing pages, product pages, or other URLs intended for search.
- Low-value or duplicate URLs: archives, parameters, empty pages, test content, or alternate versions that should not compete with the canonical page.
Work only on the first group. Removing unwanted URLs from the sitemap and linking consistently to the canonical version keeps discovery signals cleaner. If duplicate URLs are involved, follow the WordPress canonical troubleshooting guide.
Step 2: Inspect one representative URL
In Search Console, paste an affected URL into URL Inspection. Record the referring sitemap, referring page if shown, last crawl information, user-declared canonical, and Google-selected canonical. Then select Test live URL.
A successful live test confirms that Google can currently retrieve the page, but it does not promise indexing and does not reproduce every indexing-time check. Verify these items directly:
- The final URL returns HTTP 200 and does not enter a redirect chain.
- The page is not blocked by robots.txt.
- The HTML does not contain a
noindexdirective. - The canonical points to the same preferred URL.
- The rendered page contains the main text and important links.
If the URL redirects, diagnose it with the Page with Redirect WordPress guide. If robots.txt prevents crawling, use the robots.txt troubleshooting steps before changing directives.
Step 3: Check the Yoast sitemap and canonical URL
Open https://yourdomain.com/sitemap_index.xml, select the relevant post-type sitemap, and search for the exact preferred URL. Yoast should normally include published, indexable canonical posts automatically.
If the URL is missing, check the page’s Yoast advanced settings, publication status, post type visibility, and canonical field. Do not add redirects or custom canonicals merely to make a warning disappear. The sitemap should contain only URLs you want Google to show, and Google treats sitemap submission as a hint rather than a guarantee of crawling or indexing.
If Search Console cannot read the sitemap itself, resolve that separate problem with the Yoast sitemap “Couldn’t fetch” checklist.
Step 4: Add useful, crawlable internal links
A page that exists only in a sitemap can be harder for users and crawlers to reach than a page connected to the site’s normal navigation. Add one or more relevant HTML links from already indexed pages, a category hub, or a useful guide. Use descriptive anchor text that explains the destination.
Do not create large blocks of repetitive sitewide links. A contextual link from a closely related article is usually more useful than an unrelated footer link. Confirm that the link is a normal <a href> link and is present on the mobile version, because Google indexes the mobile version of pages.
Step 5: Improve pages that do not justify a crawl
Technical access is necessary, but it is not the whole decision. Google states that it tries to crawl high-quality, user-valuable content and that pages may still be excluded when there is not enough value or user demand. Review the affected page as a visitor:
- Does it solve a specific problem more clearly than your other pages?
- Does it provide original instructions, examples, evidence, or firsthand testing?
- Is the answer visible near the top?
- Is the content substantially different from category, tag, or near-duplicate pages?
- Are the title and main heading accurate rather than exaggerated?
Merge overlapping pages when one complete resource would serve users better. Do not pad the article to reach a word count, change dates without meaningful updates, or publish many templated variations. Those actions increase the URL inventory without necessarily increasing value.
Step 6: Check server health and Crawl Stats
Open Search Console → Settings → Crawl stats. Review host availability, server errors, response time, and crawl requests. If Googlebot encounters repeated 5xx errors, timeouts, or “Hostload exceeded” messages, fix availability before requesting more crawling.
For a WordPress site, check hosting error logs, uptime, PHP errors, cache behavior, firewall rules, and whether heavy plugins make uncached requests fail. Do not disable security or caching globally just to test indexing. Make the smallest evidence-based correction and verify that both visitors and the live inspection tool receive a complete page.
Step 7: Reduce unnecessary URL discovery
WordPress themes and plugins can generate parameters, internal search URLs, duplicate archives, calendar paths, and other low-value URLs. These may distract attention from important pages, particularly when a site exposes a much larger URL inventory than its useful content warrants.
Keep canonical signals consistent, exclude non-search pages from XML sitemaps, avoid linking to parameter variants, and return a real 404 or 410 for content that no longer exists. Do not repeatedly add and remove directories from robots.txt to manipulate crawl allocation; Google specifically advises against that approach.
Step 8: Request indexing only after a real fix
After the page is accessible, valuable, canonical, internally linked, and included in the correct sitemap, run a live URL test and select Request indexing. Use this for a small number of important URLs. Repeating the request every day does not force Google to crawl or index a page faster.
For a group of affected URLs, use the Page indexing report’s validation flow only after you have corrected the shared cause. Monitor the status over the following days or weeks; Google’s reports update after recrawling, not immediately after a WordPress edit.
How to verify the fix
- Open the public URL in a signed-out browser and confirm it loads normally.
- View the source and confirm an indexable robots directive and self-referencing canonical.
- Confirm the preferred URL appears in the correct Yoast sitemap.
- Follow the internal links to the page on desktop and mobile.
- Run Search Console’s live URL test and confirm the page is available to Google.
- After Google recrawls it, check whether URL Inspection reports the page as indexed and whether impressions begin appearing in Performance.
If the status changes to “Crawled – currently not indexed,” discovery is no longer the immediate problem; review content value, duplication, rendering, and canonical selection using the dedicated crawled-not-indexed guide linked above.
When no fix is needed
No action is normally required for deliberately excluded archives, duplicate URLs, recently published pages still within a reasonable discovery period, or pages with no search value. Search Console explicitly notes that “Not indexed” is not necessarily bad. Focus on important canonical pages and the trend, not on making the excluded count reach zero.
Primary sources
