Crawled or Discovered – Currently Not Indexed? What It Means and How to Fix It

I opened Search Console for this site and saw a grey box that said 109 pages not indexed. Only 47 were indexed. Google knew about 156 pages on txtnode and had left out two thirds of them.

It looks like a disaster. It mostly isn't. When I went through every reason in the report, most of those 109 URLs were exactly what should be left out: deleted posts, a font file, the RSS feed. But two reasons, Crawled – currently not indexed and Discovered – currently not indexed, held the pages I actually care about, including tool pages Google had never opened at all.

This guide covers what each "not indexed" reason means in Google's own words, which ones you can ignore, the difference between Crawled and Discovered, what actually helps, and what I found on my own site. It is the sixth part of my SEO checklist series, after page titles, meta descriptions, canonical tags, H1 tags and image alt text.

The short answers

• What does "Crawled – currently not indexed" mean? Google opened the page, read it, and decided not to put it in the index, at least for now. Google says there's no need to resubmit it.
• What does "Discovered – currently not indexed" mean? Google knows the URL exists but hasn't crawled it yet. That's why the "Last crawled" date is empty.
• Which one is worse? Neither is an error. Discovered usually means Google hasn't seen enough reason to visit yet. Crawled means it visited and wasn't convinced.
• Is it bad to have pages not indexed? Not by itself. Google says plainly: "Don't expect every URL on your site to be indexed" and "Non-indexed URLs can be fine."
• How do I fix it? Make sure the page deserves to be indexed, link to it from pages Google already visits, and then wait. Request indexing helps a few key pages; it doesn't fix a site-wide pattern.
• How long does indexing take? Google says crawling "can take anywhere from a few days to a few weeks."

First: not every page should be indexed

Google says this in several places. From How Search Works: "Google doesn't guarantee that it will crawl, index, or serve your page" and "not every page that Google processes will be indexed." From the Page indexing report's own help page: "Don't expect every URL on your site to be indexed. Some URLs might be duplicates or might not contain meaningful information."

So the grey number is not a score. The question is never "how do I get it to zero". It's "which URLs are in it, and should any of them be indexed?"

The 7 reasons on my site

Here is txtnode's report on 28 October 2026, with Google's definition of each reason and what I did about it:

Four of the seven reasons are your own site doing what you told it to. The 404s are usually fine too. That leaves two reasons worth your time, and on my site they held 65 of the 109 URLs.

Not found (404): usually nothing to fix

My 28 404s were almost all old URLs: articles I deleted months ago, tags I removed, and one cut-off link (/blog/meta-descripti) that someone must have copied badly. Google's position is old and clear: "404 errors are a perfectly normal part of the web; the Internet is always changing, new content is born, old content dies, and when it dies it (ideally) returns a 404 HTTP response code."

Google will keep trying an old URL for a while. In the help page's words, "there is no way to tell Googlebot to permanently forget a URL, although it will crawl it less and less often."

A 404 only needs fixing when:

1. The page should exist. It was deleted by mistake, or its address changed. Restore it, or redirect the old URL to the new one.
2. Your own site still links to it. Then visitors hit a dead end too. Fix the link.

Check the second one with a crawler before you worry. When I crawled txtnode's 88 sitemap pages, none of their 92 internal links returned a 404, so every 404 in the report was an old URL Google remembered, not a broken link on the site.

Crawled – currently not indexed

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

Google visited, read the page, and decided it wasn't worth a place in the index right now.

Why it happens. In a Search Off the Record episode about reading this report (July 2026), Martin Splitt asked whether this status is a sign of a quality problem. John Mueller's answer: "Sometimes. So it's definitely the case if our systems are seriously worried about the quality of a website…" and that "you almost need to take a step back and think about the quality overall."

The common causes:

• The page adds little that isn't already elsewhere. A thin page, a near-copy of another page on your site, or a page that says what a hundred other pages already say.
• It's not really a page. On my site this list included feed.xml, sitemap.xml, a .woff2 font file, favicon.ico and site.webmanifest. Those files exist for browsers and feed readers, not for search results, so them showing up here is no loss.
• It's new. My image alt text article was in this list 4 days after publishing. New pages often pass through it before they're indexed.
• It's old content that was removed. Several entries were articles that no longer exist.

What to do.

1. Open the report, click Crawled – currently not indexed, and sort the URLs into "should be indexed" and "doesn't matter".
2. For each page that should be indexed, ask honestly whether it's the best page on the web for its topic, or at least clearly useful and different from your other pages. If not, improve it, merge it into a stronger page, or accept that it stays out.
3. Link to it from your strong, indexed pages (more on this below).
4. Wait. Don't keep resubmitting. Google says no resubmission is needed for this status.

Discovered – currently not indexed

What it means. Google's definition: "The page was found by Google, but not crawled yet. Typically, Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl. This is why the last crawl date is empty on the report."

The key detail is the empty Last crawled date. On my site, the examples included /pricing, /diff-checker, /hash-generator and /games/snake, all showing N/A. Google knew those pages existed and had never opened them.

Is it crawl budget? For most sites, not in the usual sense. Google's crawl budget guide is written for "Large sites (1 million+ unique pages)" and "Medium or larger sites (10,000+ unique pages) with very rapidly changing content (daily)", and for "Sites with a large portion of their total URLs classified by Search Console as Discovered - currently not indexed." Back in 2017, Gary Illyes wrote that "if a site has fewer than a few thousand URLs, most of the time it will be crawled efficiently."

What the same guide says about demand matters more for a small site. How much Google wants to crawl a site "varies based on a site's size, update frequency, page quality, and relevance, compared to other sites." In other words, Google crawls what it expects to be worth crawling. The 2017 post adds that "having many low-value-add URLs can negatively affect a site's crawling and indexing."

Mueller has also said this status can last a long time: "That can be forever. It's something where we just don't crawl and index all pages," and "it's completely normal for any website that we don't have everything indexed."

What to do.

1. Find out what's in the list. If it's mostly low-value URLs (filters, thin archives, duplicates), that's useful to know too.
2. Link to the important ones from pages Google already crawls. Google's own words: "Google primarily finds pages through links from other pages it already crawled."
3. Give thin pages a reason to exist, or stop pointing Google at them. Either add real content, or leave them out of your sitemap.
4. Request indexing for the few pages that matter most (see below).

Crawled vs Discovered: the difference

What I found on txtnode

Sorting my 109 URLs by type made the pattern obvious.

Most of it was fine. Deleted posts and old tags (404), files that aren't pages (crawled, not indexed), deliberate noindex and robots.txt rules, a few redirects. None of it needed fixing.

My tool pages were the real problem. /diff-checker and /hash-generator are some of the most useful pages on the site, and Google had never crawled them. They're linked from the home page, the tools page and other tool pages, but not from any of my SEO articles, which are the pages Google visits most.

My sitemap was mostly tag pages. The sitemap lists 88 URLs, and 45 of them are tag pages. 30 of those tags have just one article each, so each of those pages is basically a copy of one article's card. That's a lot of low-value URLs to hand Google next to the pages I want indexed. Google doesn't say exactly why a page stays in Discovered, so I can't prove the tags are the cause, but they don't help.

What I'm doing about it. I'm not deleting or noindexing the tag pages. I'm writing more articles on those topics, so each tag page becomes a real collection worth indexing. Next, I'll link the tools from the articles where they're genuinely useful. Then I'll request indexing for the most important pages and give it a few weeks.

How to check your own report

1. In Search Console, open Indexing → Pages.
2. Scroll to Why pages aren't indexed and click a reason.
3. Use Export (top right) to download every URL, not just the examples.
4. Group the URLs by type. A small script makes this quick. Save the exported CSV, then run:

// group-not-indexed.mjs — usage: node group-not-indexed.mjs Table.csv
// Groups an exported Search Console URL list by type, so the pattern shows at a glance.
import { readFileSync } from 'node:fs'

const rows = readFileSync(process.argv[2], 'utf8').split(/\r?\n/).slice(1).filter(Boolean)
const urls = rows.map((r) => r.split(',')[0].replace(/^"|"$/g, ''))

const kind = (u) => {
  const { pathname, search } = new URL(u)
  if (/\.(xml|json|txt|ico|webmanifest|woff2?|css|js|png|jpe?g|webp|svg)$/i.test(pathname)) return 'file, not a page'
  if (search) return 'URL with ?parameters'
  if (/\/(tag|tags|category|categories|author|page)\//i.test(pathname)) return 'archive (tag, category, author, page N)'
  const parts = pathname.split('/').filter(Boolean)
  return parts.length ? `/${parts[0]}${parts.length > 1 ? '/…' : ''}` : 'home page'
}

const groups = {}
for (const u of urls) (groups[kind(u)] ??= []).push(u)
for (const [k, list] of Object.entries(groups).sort((a, b) => b[1].length - a[1].length)) {
  console.log(`\n${k}: ${list.length}`)
  for (const u of list.slice(0, 8)) console.log('  ' + u)
}

It prints groups like "file, not a page: 6" and "archive: 22" with examples. Files and old URLs you can usually ignore. Real pages you want found go on your fix list.

Request indexing: when it helps

In URL Inspection, paste a URL and click Request indexing. It's worth doing for a handful of important pages, such as a new article or your main product page. Know its limits:

• There's a daily quota: "there's a quota for submitting individual URLs."
• Repeating it doesn't speed anything up: "requesting a recrawl multiple times for the same URL won't get it crawled any faster."
• It's not a guarantee: submitting a request "does not guarantee that the page will appear in the Google Index."

It's a nudge for single pages, not a fix for a pattern of 40 thin URLs.

What "Validation Failed" means

On txtnode, "Crawled – currently not indexed" showed Validation: Failed. That sounds worse than it is.

Search Console's help page says Failed means "a certain threshold of pages still contain this issue, after you clicked Validate." It's a status of the validation run, not a penalty. Validation is also optional: "You can also fix issues without validating; Google updates your instance count whenever it crawls a page with known issues."

Validation usually "takes up to about two weeks", and Google asks you not to click Validate fix again "until validation has succeeded or failed". For "Crawled" and "Discovered" in particular, validating mostly just makes Google recheck pages it hasn't changed its mind about. Fix the pages first, then validate if you want the confirmation.

Sitemaps are a hint

A sitemap tells Google which URLs exist. It doesn't make Google index them: "A sitemap helps search engines discover URLs on your site, but it doesn't guarantee that all the items in your sitemap will be crawled and indexed."

Two practical points:

• Put the pages you want indexed in your sitemap, and keep junk out. A sitemap full of thin or duplicate URLs tells Google less about what matters.
• Don't add noindex pages to your sitemap. Asking Google to crawl a page and telling it not to index it in the same breath is a mixed signal.

Platform notes

WordPress

Tag, category, author and date archives create many thin pages, especially on small blogs. Many SEO plugins let you choose which archive types are indexed and which go in the sitemap. Also check that Settings → Reading → "Discourage search engines from indexing this site" is not ticked. It's often left on after building a site.

Shopify

The same product can be reached through several addresses, for example under a collection and at /products/…. Shopify adds a canonical tag pointing to the main product URL, so these show up as Alternate page with proper canonical tag, which is fine. If important products sit in Discovered, link them from your home page and main collections.

Next.js

Check what your sitemap.js or sitemap.ts actually outputs. Generated sitemaps often include every tag, every page of pagination, or routes you never meant to publish. Open /sitemap.xml in the browser and read it once.

A brand-new site that isn't on Google at all

If Google shows nothing for site:yourdomain.com, start with the basics:

1. Add the site to Search Console.
2. Submit your sitemap.
3. Request indexing for the home page.
4. Get at least one link from a site Google already knows, such as your social profile or a directory you're genuinely listed in.

Then give it the "few days to a few weeks" Google talks about.

Questions people ask

Is "Crawled – currently not indexed" a penalty? No. It's a decision not to index that page for now. Google says it "may or may not be indexed in the future".

Why are my pages not indexed by Google? Look at the reason in the report. Four of the seven common reasons (noindex, robots.txt, redirect, alternate canonical) are your own settings. The two "currently not indexed" reasons are Google's choice, usually about how useful the page looks and how well it's linked.

How do I fix "Discovered – currently not indexed"? Link the page from pages Google already crawls, reduce low-value URLs, make sure the page is worth indexing, and request indexing for the few that matter most. Then wait.

Should I delete pages that aren't indexed? Only if they're genuinely useless to visitors too. If a page is useful but thin, improving it is usually better than deleting it.

Does a high "not indexed" count hurt my whole site? The count itself doesn't. Google says non-indexed URLs "can be fine". What can matter is a site made mostly of low-value pages, because that shapes how much Google wants to crawl.

Why does Search Console say "Request indexing" didn't work? Requesting doesn't guarantee indexing, and there's a daily quota. If the page is in "Crawled – currently not indexed", Google has already seen it. Improve the page before asking again.

How long does it take Google to index a new page? Google says crawling "can take anywhere from a few days to a few weeks."

Next in the checklist

This is part 6 of the SEO checklist. Part 1 covers page titles, part 2 covers meta descriptions, part 3 covers canonical tags, part 4 covers H1 tags, part 5 covers image alt text, and the full list is in the SEO audit checklist.

If your export gives you a long list of URLs to sort, paste it somewhere you can mark each one as you go. txtnode opens a notepad at any URL you type, without an account, and Files keeps notes in folders when you sign in.