How to Fix "Discovered - currently not indexed" in Google Search Console
Technical SEO August 6, 2026 10 Min Read

"Discovered - currently not indexed" in GSC: Why Google is Ignoring Your New Posts

Adnan Naseem

Adnan Naseem

WordPress Developer & SEO Expert

Fix Discovered Currently Not Indexed Error in GSC

You spend five hours writing the perfect blog post. You format it beautifully, hit publish in WordPress, and immediately open Google Search Console (GSC) to request indexing. A few days pass, and your traffic hasn't moved. You check GSC again, look at your Page Indexing report, and see your new URL sitting in a gray, frustrating limbo:

"Discovered - currently not indexed"

You click "Request Indexing" again. Another week passes. Nothing changes. Is your site penalized? Is your sitemap broken? Did Google's algorithm suddenly decide to hate your domain?

Don't panic. This is not a manual penalty, and your website is not broken. In 2026, as the internet continues to flood with millions of AI-generated pages every single day, Google has become incredibly picky about how it spends its server resources. Today, I am going to explain exactly what this status means, why Google is ignoring your post, and the exact steps you can take to force Google's hand and get your URL indexed.

Table of Contents

1. What Does "Discovered - currently not indexed" Actually Mean?

According to Google's official documentation, this status means exactly what it sounds like: Google knows your page exists (usually because it found the URL in your XML sitemap or via an RSS feed), but the Googlebot has not actually visited the page yet to read the content.

Why wouldn't Google visit the page? Google explains: "Typically, Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl."

However, for 99% of WordPress bloggers on standard hosting, your site wasn't actually going to be overloaded. The real reason is that Google looked at the URL from the outside and decided it wasn't a high enough priority to spend server resources on it *today*.

Discovered - currently not indexedCrawled - currently not indexed
Google knows the URL exists, but has not read it yet.Google visited the page, read the text, and decided it wasn't good enough to put in the search results.
Usually a Crawl Budget or Site Architecture problem.Usually a Content Quality or Duplicate Content problem.

2. The Root Cause: Google's "Crawl Budget"

Google doesn't have infinite server power. Every time Googlebot visits a webpage, downloads the HTML, and parses the CSS/JS, it costs Google money. Therefore, Google assigns every website a "Crawl Budget"—a specific number of pages it is willing to crawl per day.

If your website is relatively new, has very few backlinks, or publishes content infrequently, your Crawl Budget is tiny. If you suddenly publish 20 new blog posts in a week, Google might only crawl 2 of them and leave the other 18 in the "Discovered" queue until next month.

To fix this error, you need to send massive signals to Google that this specific URL is important and deserves to skip the line.

The single biggest reason a post stays in "Discovered" limbo is that it is an "Orphan Page." You published it, it sits on your blog roll, but none of your older, authoritative articles actually link to it.

If your own website doesn't think the new post is important enough to link to, why should Google waste time crawling it?

The Fix: Go into your Google Analytics or GSC and find your top 3 highest-traffic, most authoritative blog posts. Open them in your WordPress editor. Find a relevant paragraph, and insert a contextual, keyword-rich internal link pointing directly to your newly published post. Next time Googlebot crawls your popular pages (which it does frequently), it will follow that link, discover the new post, and crawl it immediately.

4. Fix #2: Information Gain & Content Thinness

Sometimes, Google looks at the URL string and the contextual clues surrounding it and assumes the page is "thin content." If your URL is `yoursite.com/tag/blue-shoes` or `yoursite.com/category/updates`, Google knows these are auto-generated archive pages that don't provide unique value, so it leaves them in the "Discovered" queue.

If it is an actual blog post that is stuck, you need to ensure the page has enough "meat" on the bone before requesting another crawl.

🚀 Verify Your Content Depth

Before asking Google to crawl a stuck page again, copy the text and paste it into our free Advanced Word & Character Counter. If your post is under 500 words and lacks structured headings, Google might deprioritize it. Add more depth, embed an original image, or add an FAQ section to increase the page's structural value.

5. Fix #3: Clean Up Your HTML Code Bloat

Remember how we talked about Crawl Budget? If Googlebot arrives at your website and has to download 4 Megabytes of dirty, unoptimized HTML, Javascript, and inline CSS just to read a 1,000-word article, it will abandon the crawl to save resources. This is exactly what causes the "expected to overload the site" error.

If you copy and pasted your article from Google Docs or Microsoft Word directly into WordPress, you likely injected thousands of lines of hidden, garbage span tags that are suffocating the Googlebot.

🚀 Clean the Code for the Crawler

If a post refuses to index, open the WordPress editor, copy the raw text, and run it through our free Advanced Format Cleaner Tool. This instantly strips out all the bloated inline CSS and Word processor junk while preserving your H2s and links. Update the post with the clean code, and hit "Request Indexing" again in GSC. A cleaner DOM size drastically improves crawl rates.

The Bottom Line

The "Discovered - currently not indexed" status is simply a matter of prioritization. By ruthlessly cleaning your HTML code to preserve crawl budget, injecting powerful internal links from your top pages, and ensuring your content isn't deemed "thin," you signal to Google that your new URL is a VIP priority. Do the work, hit Request Indexing one last time, and watch the URL turn green.

Frequently Asked Questions

If you have a new website, it is completely normal for a post to sit in "Discovered" for 1 to 3 weeks. If you have an established site and the post has been stuck for more than 7 days, you need to take action using internal linking.
No. Clicking the button repeatedly does not push you higher up in the queue. In fact, Google will simply ignore redundant requests. Click it once, wait a week. If nothing happens, modify the page (add internal links) and then click it one more time.
No. It is not a penalty, and your site is not broken. It is strictly a resource management decision by Google's crawler. Manual penalties will show up under the "Security & Manual Actions" tab in GSC, not in the Page Indexing report.
This is a terrible idea. Deleting it creates a 404 error for the URL that Google has already discovered. Republishing it with a new URL looks like duplicate content spam. Just improve the existing page and build better internal links to it.
The Google Indexing API is officially only meant for Job Postings and Livestream events. While some SEO plugins use it to force-index standard blog posts, Google has warned against this practice, and using it for normal blogs can sometimes result in spam flags. Stick to standard sitemap submissions.
Yes, significantly. If an authoritative, high-traffic external website links to your stuck URL, Googlebot will follow that link almost immediately. Backlinks are the strongest signal you can send that a page is important enough to crawl.
This is normal and actually a good thing. Tag pages (/tag/seo) and pagination pages (/page/2) offer very low value to searchers. Google intentionally ignores them to save crawl budget for your actual, high-value blog posts. You can ignore these errors.
Yes. If your hosting server takes more than 2-3 seconds to respond to a bot's initial ping, Google will abort the crawl to avoid crashing your site. Using a caching plugin (like WP Rocket) and a CDN (like Cloudflare) ensures your server responds fast enough for Googlebot.
It can. While social media links are "nofollow" and don't pass direct SEO juice, Google does monitor major platforms like X (Twitter) and Pinterest. A surge of real human traffic hitting a URL from a social network signals to Google that the page is currently relevant.
The Page Indexing report in Google Search Console is not real-time. It often lags behind by 3 to 7 days. Even if your post is successfully indexed and appearing in live Google searches today, the GSC report might still say "Discovered" until the next data cycle updates.
Scroll to Top