Crawled or Discovered, Currently Not Indexed? How to Fix Both

Crawled, currently not indexed means Google fetched your page, read it and decided to leave it out of search results for now. Discovered, currently not indexed means Google knows the URL exists but hasn't fetched it yet.

The first is usually a problem with the page, the second a problem with priority, so each needs its own fix. We've had both on launchpanda.dev. Six of our landing pages sat in the first status for months, and as of October 28, 2026, our own post on why your website isn't showing up on Google sits in the second.

What does Crawled, currently not indexed mean?

Google's definition is short: "The page was crawled by Google but not indexed." It adds that the page "may or may not be indexed in the future; no need to resubmit this URL for crawling."

So Googlebot did its part. It fetched the page, nothing blocked it, and Google still chose not to keep it. That's a judgment, not an error. Most of the time Google decided the page adds too little next to what it already has, from your site or from someone else's.

What does Discovered, currently not indexed mean?

Here Google never fetched the page at all. In Google's words: "The page was found by Google, but not crawled yet." It says it usually postponed the crawl because it "was expected to overload the site", which is why the last crawl date stays empty.

On a small site, server load is rarely the real reason. More often Google doesn't think the URL is worth a visit yet, because few links point to it and the rest of the site hasn't earned much crawling. Google's crawl budget guide is written for very large sites, but it names one more group it's for: sites with "a large portion" of their URLs in Discovered, currently not indexed.

What's the difference between the two?

How do you check which status a page has?

1. Open Google Search Console and paste the full URL into the inspection bar at the top.
2. Under Page indexing, read three things: the status, Discovery (the sitemaps and pages that led Google to the URL) and Last crawl.
3. Click Test live URL, then View tested page, to see the HTML Google gets today. If your text isn't in it, Google can't judge it.
4. For the whole site, open Indexing, then Pages, and click a reason in the "Why pages aren't indexed" table to see example URLs.

A site: search gives you a rough idea, but only URL Inspection tells you which status a page has and why.

What happened on our own site?

In April 2026 we published eight keyword landing pages under /launch, aimed at searches like "free startup directories" and "Product Hunt alternatives". They all showed the same directory table, with 91 to 100% of the rows in common. Google crawled six of them between June 29 and July 29 and indexed none. It filed one more as a duplicate, and the last was never crawled at all, even with a link from our homepage. Our read: after a few near copies, Google saw no reason to fetch another.

The pages we actually want in Google have the other problem. On October 28, five of them had been live for 52 to 198 days, and Google hadn't fetched any of them. For three, our sitemap is the only place Google says it found them. Our /launches page sits in the menu on our homepage and was still waiting.

Then we found a bigger cause. Search Console's Sitemaps report said Google had last read the sitemap we submitted on June 8, 2026, and found 35 pages in it. Our sitemap lists over 460 today. In URL Inspection, the newer pages we checked, from September and October, didn't name any sitemap as the place Google found them. A sitemap Google doesn't reread can't tell it about anything new.

Here's what we changed:

• October 26: we set 229 profile pages to noindex and took them out of our sitemap, because they showed Google an empty page.
• October 28: we deleted the eight /launch pages and sent every URL to the closest real page with a 308 redirect, four to the matching blog post and the rest to our directory list.
• October 28: we resubmitted our sitemap to get Google to read it again, linked the stuck pages from our homepage, and started requesting indexing for them.

Search Console still shows the deleted pages with their old statuses and summer crawl dates. That's expected. Google hasn't been back since, and when it returns it will follow the redirects.

How do you fix Crawled, currently not indexed?

Work down this list, biggest impact first:

1. Merge or remove near copies. If a page repeats what your other pages already say, Google keeps one and drops the rest. That's what sank our /launch pages. Fold thin pages into one strong page and send the old URLs to it with a 301 or 308 redirect.
2. Check what Googlebot actually gets. Run Test live URL and read the HTML. When we fetched our /launches page as Googlebot in October, it got 42 words and no product links, because the list only loaded later in the browser. Now the first 48 launches ship in the HTML.
3. Give the page something only it has. Your own numbers, a real example, a working tool. A longer copy of what already ranks isn't new.
4. Link to it from your strongest pages. A page nothing links to tells Google you don't rate it either.
5. Then request indexing, once. Google says there's "no need to resubmit" a page it already crawled, so only ask after a real change.

How do you fix Discovered, currently not indexed?

1. Check when Google last read your sitemap. In Search Console, open Indexing, then Sitemaps. If the last read date is weeks old, or Google found far fewer pages than your sitemap lists, submit it again. Google last read ours in June and found 35 pages in it. It lists over 460 today.
2. Request indexing for the pages that matter. Paste the URL into URL Inspection and click Request indexing. There's a quota, and Google notes that "requesting a recrawl multiple times for the same URL won't get it crawled any faster", so ask once for each of your top pages.
3. Link to it from pages Google already crawls. Your homepage and your most visited posts work best, with the link in the body. A sitemap entry only tells Google a URL exists. A link from a page it visits often tells it the URL matters. A link in our homepage menu wasn't enough for /launches, so combine this with the next two fixes.
4. Cut the pages that waste crawls. Google warns that if it "spends too much time crawling URLs that it shouldn't", its crawlers "might not explore the rest of your site". Delete thin pages, or noindex them and drop them from your sitemap, like we did with our empty profile pages.
5. Earn links from other sites. Google says "URLs that are more popular on the Internet tend to be crawled more often". For a new site, directory listings are the quickest first links. A free Startup Profile keeps your product details ready for every directory, so you stop retyping the same form. The full plan is in how to get your first 10 backlinks.
6. Rule out your server. Slow responses and server errors make Google crawl less. Check Settings, then Crawl stats, in Search Console.

How long should you wait?

Google says "It can take a week or so for Google to start crawling and indexing a new page or site", and that crawling "can take anywhere from a few days to a few weeks". Our rule of thumb:

• Less than a month old: wait. Our Vibe Jams page was 17 days old when we checked, still in Discovered, and we're leaving it alone.
• A month or more, and you need it in search: work down the fix list for its status.
• Pages you don't need in search: leave them. Login screens, filtered lists and thank-you pages are fine in either status. If you have a lot of them, noindex them and keep them out of your sitemap.
• Redirected or deleted URLs: they keep their old status until Google comes back, then drop out on their own.

Start with the one page you most want in Google. Inspect it, check its status and Last crawl date, and work down the matching list above.