Is this a permanent error?

Usually no. It just means the page is waiting in a queue. However, if it stays this way for weeks, you need to intervene.

Can I force Google to crawl it?

You can use the 'Request Indexing' tool in GSC for individual URLs, but for sitewide issues, you must fix the underlying crawl budget triggers.

How to fix 'Discovered - currently not crawled'

This status means Google knows your URL exists (perhaps from a sitemap or a link), but it hasn't actually visited the page yet.

What is wrong

In Google Search Console, this indicates that the URL is in the queue to be crawled, but Google has postponed the visit. This often happens because Google tried to crawl the site but the server was overloaded, or the site is too large for its perceived importance.

It is a sign that your 'crawl budget' is being exceeded or that the URL is so low-priority that Google hasn't bothered to fetch it.

Why it matters

If Google hasn't crawled the page, it cannot understand the content or index it. This is a bottleneck for new content or large site migrations.

This issue often points to underlying performance problems. If your server is slow, Google will reduce its crawl rate to avoid crashing your site, leaving many pages 'discovered' but ignored.

How to fix it

1. Improve server performance

Ensure your hosting can handle frequent bot requests. Use caching and a Content Delivery Network (CDN) to reduce server load and speed up response times.

2. Optimise your crawl budget

Use robots.txt to block Google from crawling low-value areas (like search filter results or admin pages) so it focuses on your important content.

3. Strengthen internal links

Ensure the discovered URL is linked from high-traffic, frequently crawled pages. This signals to Google that the URL is important enough to be moved up the crawl queue.

Platform notes

If using WordPress, ensure you aren't using heavy plugins that slow down your TTFB (Time to First Byte), as this is a primary trigger for crawl rate limiting.

Common questions

Is this a permanent error?: Usually no. It just means the page is waiting in a queue. However, if it stays this way for weeks, you need to intervene.
Can I force Google to crawl it?: You can use the 'Request Indexing' tool in GSC for individual URLs, but for sitewide issues, you must fix the underlying crawl budget triggers.