Crawled or discovered, currently not indexed: what it means and how to fix it

What the two statuses mean

Both show up in Search Console under Indexing > Pages, in the "Why pages aren't indexed" table. They look alike, but they point at different problems.

Google's help page for the report is clear on one point: Google doesn't index every page it finds, so "crawled, currently not indexed" is normal for part of any site. You don't need to resubmit a URL that's waiting. Worry when the list holds pages that should bring traffic.

For "discovered", Google says that typically it wanted to crawl the URL but expected that to overload the site, so it rescheduled the crawl. That's why server speed and the number of URLs you expose matter so much here.

Why Google crawls a page but doesn't index it

The same causes come up again and again:

• Thin or unoriginal content. Short pages, boilerplate product descriptions, AI drafts nobody edited, pages that answer the same question as ten others already in the index.
• Near-duplicates. Tag and category archives, filter URLs, print versions, http and https or www and non-www twins. Google picks one and leaves the rest.
• Canonical confusion. A canonical tag pointing somewhere else, or different canonicals in the HTML and the sitemap.
• Weak internal links. A page linked only from the sitemap, or buried five clicks deep, looks unimportant.
• Soft 404s. Empty search results, out-of-stock pages with no content, "coming soon" pages.
• A new site with few links. Google is cautious with sites it doesn't trust yet.

Why Google discovers a page but doesn't crawl it

• Slow or erroring server. If responses are slow or Google sees 5xx errors, it crawls less.
• Too many URLs. Faceted navigation, session IDs and endless calendar pages spread crawling thin.
• Big batches published at once. Thousands of new URLs in a day go into a queue.
• Few internal links to the new URLs. Google finds them in the sitemap but sees little reason to hurry.

How to fix crawled, currently not indexed: step by step

1. Export the list. In Search Console, open Indexing > Pages, click the status and export the URLs.
2. Sort it. Mark each URL as "should rank" or "doesn't need to be indexed". Tag archives, filters, thin author pages and old pagination usually go in the second group. Leave them, noindex them, or remove them.
3. Run a site audit. You want noindex tags, robots.txt rules, X-Robots-Tag headers, canonicals and duplicate titles in one view. SE Ranking's Website Audit puts these in a Page Indexability block on the Overview, with a Crawled Pages report you can filter. Connect Search Console to it too.
4. Improve or merge the pages that should rank. Add what the top results miss: real examples, data, steps, a clear answer. If two pages cover the same thing, merge them and 301 the weaker one.
5. Fix canonicals and duplicates. One version per page, the same canonical in the HTML and the sitemap.
6. Add internal links. Link from strong, indexed pages with descriptive anchor text. Put key pages within three clicks of the homepage.
7. Update the sitemap. Only indexable, canonical, 200-status URLs, with honest lastmod dates.
8. Request indexing. In URL Inspection, run a live test, then click Request indexing for the pages you changed.
9. Wait, then check again. Give it a couple of weeks before you change the page again.

Run a free SE Ranking site audit

Our best SEO audit tools guide compares SE Ranking's audit with Screaming Frog, Semrush and others if you want a second opinion.

How to fix discovered, currently not indexed

1. Check Crawl stats. In Search Console go to Settings > Crawl stats. Look for high response times, 5xx errors and host issues.
2. Speed up the server. Caching, a CDN, a bigger hosting plan, fewer heavy plugins on WordPress.
3. Cut junk URLs. Block filter and session parameters in robots.txt or stop generating them. Fewer URLs means each one gets crawled sooner.
4. Link the stuck pages. Add them to navigation, hub pages or related-post blocks on pages Google crawls often.
5. Publish in smaller batches. If you add hundreds of pages, spread them out.
6. Request indexing for the most important URLs once the site responds fast.

Where an indexing service fits, and where it doesn't

An indexing service gets Googlebot to visit a URL. That can help a page stuck in "discovered" once your server is healthy, or a page you've just improved. It can't make Google keep a page Google doesn't rate, and it can't get round noindex, robots.txt or a wrong canonical.

The clearest use is pages you don't control: guest posts, niche edits and other backlinks on third-party sites. You can't submit those in Search Console. Here's the workflow we recommend:

1. Monitor your backlinks in SE Ranking. Backlink Monitoring shows whether each link is still found on the page and whether the linking page is indexed in Google, with email alerts when that changes.
2. Separate lost links from unindexed ones. Lost links need an email to the site owner, not an indexer.
3. Send live, unindexed pages to a pay-per-result indexer. SpeedyIndex charges only for links that get indexed and returns tokens for the rest on day 7. Packs start at $5, and our link gets you 200 free tokens.

Try SpeedyIndex with 200 free tokens

Compare it with Rapid URL Indexer, Omega and others in our best backlink indexer guide, or read the full SpeedyIndex review.

What about the Google Indexing API?

It comes up in every thread about this problem. Google's own quickstart says the Indexing API is only for pages with JobPosting structured data or BroadcastEvent embedded in a VideoObject. Using it for ordinary blog or product pages isn't supported. For those, stick to sitemaps, internal links and URL Inspection.

How we wrote this guide

The definitions come from Google's Page indexing report help page and the Indexing API documentation, read in November 2026. The causes and steps are standard technical SEO practice that our team applies on its own sites. We haven't published any test figures because we didn't run a controlled study. SE Ranking and SpeedyIndex details come from their official sites. See how we test.