What Does

What Does "Crawled – Currently Not Indexed" Mean and How Do You Fix It?

You publish a page, everything looks good on your end, check back in Search Console a few days later and expect to see it live – and instead you see this line sitting quietly under Excluded: “Crawled – currently not indexed.” Not a typo. Not a get-out clause. Nothing. Just... Then Google came along and read the page and decided it wasn't worth indexing. Reasons not given.


If you've found this one, here's what's really going on and how to work through it.


What This Status Is Really Telling You


It's a weird place to be in because it's really two separate statements stapled together.


  1. Crawled means the page was crawled. Googlebot found it, asked for it, fed back the content. It wasn't crawling.
  2. Not Indexed at the moment means that Google has read it, but decided not to index it at the moment.

Now the word “currently” is more important than people realize. That may mean it is not permanent -- Google may come back and index it later on its own time, no action needed on your part.


In practice, though, pages left in this status typically just stay there forever, unless something actually changes, either to the page itself or to its surroundings.


It’s worth separating this from its cousin “Discovered – currently not indexed,” where Google has found the URL but hasn’t even crawled it yet – usually a crawl budget or prioritization thing. Here the crawl is already done. Google read it and still greenlit it.


Start With The Boring Stuff


Before you go down the content-quality rabbit hole, rule out the dumb technical stuff first, since it takes two minutes to check.


  1. Accidentally set page to noindex?
  2. Robots.txt blocking? Is there any (This would be a different status, but it's good to check anyway - misconfigurations happen.)
  3. Is it really in your sitemap and not canonicalized to some other URL?
  4. Will it do a clean 200? Or is there something funny about the response?

If those are wrong. That is your answer. Repair it, request indexing again, continue.


If The Basics Check Out, Ask A Harder Question


The more common reason is quieter and a little more uncomfortable . If nothing is technically broken , Google crawled the page, read the page and decided it just wasn’t worth adding.


The big thing is thin content – short pages, boilerplate product descriptions, anything that doesn’t really add much beyond what’s already sitting elsewhere on your site. These days, Google doesn’t like to index pages that don’t add anything new.


Another common reason is near-duplicate content. If a product variant has a template, a location page that just swaps out a city name, a syndicated article pulled from somewhere else — Google may have just decided that the “real” version already covers this.


Sometimes it's just trust. That doesn’t mean the pages are wrong, but that Google doesn’t have enough confidence in the site to index everything right away, which can happen with small or new sites.


And sometimes it’s internal linking – a page with almost no internal links reads as low-priority, even if the content is perfectly good.


Is It One Page or Layout?


This is the part you're wanting to pull back for. One page stuck in this state is probably just the content of that page.


Another whole different conversation, a dozen or hundreds of pages stuck here at once, usually pointing at something structural, a templated section producing thin pages at scale, a linking gap across an entire content type or a broader quality signal Google’s reacting to.


Actually hard to see when you click through Search Console one URL at a time - it will show you the list but not the why behind it.


With a full site crawl it’s much easier to actually see the pattern, as thin content, near-duplicates and orphaned pages with weak internal linking are flagged all in one pass.


Running something like KWT Spider over the affected section tends to help here, because its content tabs surface thin content and text to HTML ratio flags right alongside the internal linking view – so instead of guessing whether a given “not indexed” page is thin, duplicate or just poorly linked, you can actually see which one it is.


Fixing It (Not Just Asking Again)


Most of the time, clicking "Request Indexing" in the URL Inspection tool without changing anything is not very effective — if Google previously crawled the page, submitting the same URL again usually gets you the same result. First, the real fix has to come:


  1. Create thin content with a small amount of useful information, not just filler for the sake of filler
  2. Differentiate near duplicate pages or merge with a canonical if it makes more sense to merge than to keep both
  3. Broken URL linked to other pages already indexed

Make it something not on the site elsewhere – original data, a real example, specifics nobody else bothered to include. It is only worth resubmitting when something has actually changed.


In that moment Just Hold On (Indexing decisions don't change instantly, even with a real fix. It takes a few weeks, so don't assume that nothing worked.


If you're monitoring a URL in Search Console, don't refresh it every day. It's not going to change overnight and obsessively watching it isn't going to make it change any faster.


The Real Takeaway


“Crawled – currently not indexed” is less a bug to squash than a judgment call you’re trying to overturn.


While ticking off the technical checklist is easy, the real solution is usually to make the page (or the section it lives in) really worth indexing: more substance, less duplication, better internal linking -- not just asking Google to take another look at the same page it already passed on.