What Is Crawled Currently Not Indexed and How Do You Fix It?

Short answer
What Is Crawled Currently Not Indexed?
Crawled currently not indexed means Google crawled your page but decided it did not deserve a spot in the index. Googlebot visited the page and read it. However, it concluded the page was not worth adding to search results right now.
This status is not a technical error. Googlebot reached your page, downloaded the code, and evaluated the content. So the decision usually comes down to content quality, not a server or access problem. The good news is that Google treats this decision as reversible.
If this is the first time you see this report, there is no reason to panic. Many sites run into it at some point. The fix almost always starts with a clear diagnosis, not a quick technical tweak.
This status also rarely touches your whole site at once. Instead, it usually affects one specific group of pages. So spotting which template keeps showing up in the list points you straight to the cause.
Where Does This Status Appear in the Page Indexing Report?
Open the Pages section from the left menu in Search Console. There, Google groups unindexed URLs by reason. Click the crawled currently not indexed row and you see every URL in that group, along with sample pages.
The report also includes a last crawled column. This column proves Googlebot actually visited the page. In fact, Google's own Search Console help documentation describes this status as "the page was crawled but not indexed," and notes it may change later.
By contrast, pages Google has never crawled sit in a different row. That row shows an empty last crawled date. So treating these two groups separately, instead of lumping them together, saves you from chasing the wrong fix.
It also helps to export the sample URL list into a spreadsheet. That way you can group pages by template and spot the shared pattern fast, instead of opening fifty pages one by one.
How Does Crawled Currently Not Indexed Differ From Pages Google Never Crawled?
On a page Google never crawled, Googlebot simply has not visited yet. So the last crawled date stays empty. With this status, though, the crawl already happened and that date field is filled in.
This difference matters in practice. For pages Google never crawled, you usually look at discovery and crawl capacity first. For this status, you look at content quality first instead. Apply the wrong fix to the wrong group, and you waste real time.
Keeping this line clear tells you which lever to pull first. For a page Google hasn't crawled, check internal links and your sitemap. For this status, check the content itself before anything else.
Say a hundred pages on a new blog have never been crawled at all. There, you strengthen discoverability first. If fifty pages were crawled but stayed out of the index, you instead shift straight to content quality.
What Is the Difference Between Crawled and Discovered Currently Not Indexed?
With discovered currently not indexed, Google knows the URL exists but has not crawled it yet. With crawled currently not indexed, the crawl is already done, so the decision now hinges on content evaluation. Mixing up these two statuses leads to the wrong fix.
The table below lines up the three statuses site owners confuse most often. For the fuller picture, our dedicated article on discovered currently not indexed covers discovery and crawl capacity in depth, so we won't repeat that here.
| Status | What Google did | Last crawled date | Typical first step |
|---|---|---|---|
| Crawled currently not indexed | Crawled it, did not index it | Filled in | Review content quality and overlap |
| Discovered currently not indexed | Knows about it, hasn't crawled yet | Empty | Check server capacity and internal links |
| Excluded by a noindex tag | Crawled it, respected the tag | Filled in | Confirm you set the tag on purpose |
Once you separate these three statuses clearly, you and your team speak the same language. In practice, explaining the gap between "never crawled" and "crawled but not indexed" to a developer speeds up the whole fix.
Why Does Google Crawl a Page but Not Index It?
Google does not automatically index every page it crawls. Instead, it also weighs whether the page offers readers genuine, distinct value. That way, Google spends its limited index space on content that actually helps people.
No single factor decides this on its own. Content depth, overlap with similar pages, and your site's overall quality perception all play a part together. These factors also shift over time, so a page skipped today can land in the index months later.
Picture twenty pages describing the same product that differ only by color name. In that case, Google will likely pick just a couple of them. Indexing the rest adds nothing new for someone searching, so there is no reason to prioritize them.
This selectivity is not a punishment, either. Google simply tries to keep results useful. After all, you would not want to scroll through ten near identical answers yourself.
How Does Low Content Quality Trigger This Status?
Short, shallow content, or text you copied from other sources, rarely carries enough distinct value in Google's eyes. For example, a page where you only swapped the title but kept a body that overlaps an existing page falls straight into this category.
Pages that leave the reader's question half answered send a similar low quality signal. So does a page that offers nothing beyond a thin list. Before you publish, ask yourself one simple question: what does this page actually add for the reader?
Distinct value does not require a long page, though. A short page that fully answers the reader's question with concrete examples beats a long, unfocused page almost every time.
If you cannot answer that question clearly, step back and rethink the page before you publish it. Otherwise, fixing a half finished page later almost always costs more time than getting it right the first time.
How Does Overlap With Similar Pages Create This Problem?
When many pages on the same site present nearly the same information under different titles, Google picks one. It then leaves the rest in this status. You run into this most often on templated city, product, or category pages.
To dig deeper into near duplicate content, see our guide to duplicate content. It covers the broader SEO impact of overlap, so here we only focus on the link to indexing.
Rather than fixing every overlapping page one at a time, pick the strongest page first. Then redirect the rest to it, or merge them. That gives readers and Google one stronger source instead of several weak ones.
How Does Overall Site Quality Perception Affect Indexing?
Google factors in your site's overall quality perception, even when it evaluates a single page. So on a site with many low quality pages, even a page you wrote well can take a hit from that broader perception.
That's why hunting for the problem on one URL rarely helps. Instead, reviewing similar pages across the site in bulk gets you further. In short, fixing one page rarely solves a quality problem that built up site wide.
This is also why a short, site wide quality sweep on a regular schedule pays off. You identify the weakest page group, then improve or remove it. Put this sweep on your calendar every quarter, and you catch the issue while it is still small.
Which Types of Sites Run Into This Status Most Often?
E-commerce sites, listing platforms, and city based service sites run into this status more often, mainly because they generate many pages from templates. Newer sites without much authority yet also fall into this group.
- E-commerce sites that list thousands of product variants with nearly identical descriptions.
- Service pages where you copy the same text for every city and only swap the place name.
- New sites that publish large batches of short, shallow blog posts.
All three groups share one root cause: volume outpaced depth. So deepening a handful of sample pages first, then watching the result, is far safer than touching thousands of pages at once.
As a team that manages several client sites, we see this exact pattern most often in shared templates. Whoever builds the template is usually the last person to check whether each page is actually distinct.
How Long Does It Take for Crawled Currently Not Indexed to Change?
Google makes no firm commitment on timing here. A page might land in the index within days, or it might never get there at all. So there is no honest answer to "when will this fix itself."
What matters instead is making the necessary improvements and then letting Google re-evaluate the page on its own schedule. Resubmitting the same URL out of impatience will not speed things up. It only burns your daily request quota.
The most practical approach is to note the date you made your fix. Then reopen the same report four to six weeks later. That window gives Google reasonable time, while sparing you from checking every single day.
What Steps Do You Take to Strengthen the Content?
Raising content quality is the most effective way to fix this status. The steps below outline a practical order for making a page worth re-evaluating.
- Redefine exactly which question the page answers, and give that answer clearly in the opening paragraph.
- Find sections that overlap with similar pages on your site and expand them with genuinely distinct information.
- Add a practical example, comparison table, or step list that gives the reader real value.
- Merge or remove thin pages that aren't adding real value for readers.
Try this sequence on one page first. You can then track the outcome in Search Console within a few weeks. Once you see a positive result, apply the same pattern to the rest of that page group.
It also helps to have a colleague skim the page before you publish. You read the same text every day, after all, so you may miss a gap that a fresh set of eyes catches right away.
How Does Internal Linking Speed Up Indexing?
When you add a natural internal link from a strong, already indexed page, you signal to Google that the new page has a meaningful place in your site. This keeps the page from looking like an isolated, orphaned leaf.
Internal links also send readers to related content, which lifts time on page. That, in turn, indirectly supports quality perception. So supporting a brand new page with a link from a page that already performs well is simply good practice.
When you add that link, pick a context the reader would actually click. Otherwise, a forced link annoys readers and, over time, works against you with Google too. Once you spread this habit site wide, indexing issues tend to drop off noticeably.
How Do You Resubmit a Page Through URL Inspection?
Once you've strengthened the content, open the URL Inspection tool and paste in the address. The tool first runs a live test, then offers the option to request indexing. Google's own URL Inspection help page states plainly that this request does not guarantee indexing.
- Paste the updated address into the URL Inspection tool.
- Check the live test result to confirm the page looks eligible for indexing.
- Click request indexing, and make sure you stay within your daily quota.
After you submit the request, the only thing left to do is wait. Submitting the same URL several times a day won't change the outcome. It only drains your quota.
Keeping a small log of which URLs you submitted, and when, also stops you from resubmitting the same address by mistake. That small habit saves real time, especially when more than one person works on the site.
How Does a Sitemap Relate to This Status?
A current XML sitemap tells Google which URLs are important and which ones you just updated. This helps your crawl priority. However, it cannot carry a low quality page into the index on its own.
If you're wondering how to build and maintain a sitemap, our XML sitemap guide covers that in detail. So here we focus on content quality instead of repeating it.
Some site owners assume updating the sitemap alone solves the problem. In reality, a sitemap is just a signpost. If you don't strengthen the content at the destination, the signpost changes nothing by itself.
How Do You Tell This Status Apart From Content Decay?
Content decay describes pages that were indexed before and are now losing traffic over time. Crawled currently not indexed, on the other hand, describes a page that never made it into the index in the first place. The two sit on completely different timelines.
To examine that distinction with real Search Console data, see our content decay article. It covers the topic in depth, so here we simply want you to keep the two concepts apart.
The fastest practical test is checking whether the page ever earned traffic at all. A page that never saw traffic is a candidate for this status. A page that performed well and then dropped points to content decay instead.
Does Crawl Budget Play a Role Here?
Crawl budget is the capacity that determines how many pages Google crawls on a site within a given period. It mainly matters for very large sites. On small and mid sized sites, the root cause of this status is usually content quality, not crawl budget.
For the full picture on why Googlebot sometimes crawls less, see our crawl rate article. It covers the reasons behind a drop in crawl frequency.
If your site sits well under ten thousand pages, you generally don't need to put crawl budget first. Instead, putting that same energy into content quality and overlap makes a far bigger difference.
Can a Canonical Tag Error Trigger This Status?
A wrong canonical tag tells Google the real page lives at a different address. That, in turn, can indirectly affect whether the target page gets indexed. This won't show up directly in the report, but it can produce similar symptoms.
You can find out how to detect canonical errors in our canonical tag article. There, we cover the common error types and how to fix them in detail.
We often see canonical tags still pointing at old addresses after a migration or a theme change. That one small detail alone can make a perfectly healthy page look unindexed.
Is Index Bloat Connected to This Status?
Index bloat happens when a large number of low value URLs try to enter the index. That indirectly drags down overall quality perception. In turn, this can raise the risk of your genuinely valuable pages falling into this status.
For a broader look at this, see our index bloat article. It covers the topic in depth, so here we only touch on the link between the two concepts.
Hundreds of near identical URLs created by filter parameters are a classic index bloat example. Reviewing those addresses regularly, and keeping only the ones you need, protects your site's overall quality perception.
What Do You Check Before You Publish to Prevent This Status?
Before you publish a new page, check whether your site already has one covering the same topic. This heads off the overlap problem before it starts. That small habit costs far less time than a bulk cleanup after hundreds of pages pile up.
Planning at least one internal link for every new page also helps. So does writing the title around the exact question readers will search for. Together, these habits help the page settle into a meaningful spot on your site.
A short pre-publish checklist helps too. Is the title unique? Does the opening paragraph answer the question directly? Does the page carry at least one internal link? If you can answer yes to all three, your page starts from a stronger position.
Are Page Experience Signals Connected to This Status?
Google does factor page experience into ranking and indexing decisions. However, these signals alone don't explain this status. Improving page speed while content value stays low does nothing for the root cause.
So it makes more sense to focus on content quality first, then technical signals second. Trying to fix both at once makes it much harder to tell which change actually moved the needle.
Still, we wouldn't recommend ignoring technical signals altogether. A page that loads painfully slowly, or renders poorly on mobile, loses value in a reader's eyes even when the content itself is strong.
How Do You Prioritize When Many Pages Share This Status?
When dozens or hundreds of pages pile up in this list, start with the pages carrying the highest business value. Don't touch all of them at once. Instead, pull high traffic, conversion adjacent pages to the front and test on a small group first.
Once that test group shows a positive result, roll the same fix pattern out to the rest of the family in stages. Changing the whole site at once makes it far harder to measure what actually worked.
It's also worth weighing product or service profitability during prioritization. After all, fixing the page group closest to a sale first means you see the payoff from your effort much sooner.
How Do You Report the Results of This Work?
For each page group you fix, keep a short record of the date, the change you made, and the previous status. This gives your team transparency. So months later, you can quickly answer "what did we do to this page."
This record also reveals which fix type works best on your particular site. Over time, you build a checklist based on your own experience, instead of starting from scratch with every new issue.
You can keep this record in a simple spreadsheet or in your project management tool; the format matters less than the consistency. As your team grows, this habit also helps new people work to the same standard.
What Are the Most Common Mistakes People Make?
The mistakes we see most often while fixing this status usually come from misdiagnosing the problem first. The list below rounds up the patterns we run into again and again.
- Resubmitting the same URL many times a day and burning through your quota.
- Sending a page back to the inspection tool repeatedly without changing the content itself.
- Treating crawled currently not indexed and discovered currently not indexed as the same problem.
- Searching for the problem on a single page instead of reviewing similar pages across the site.
What these mistakes share is impatience paired with the wrong diagnosis. So working through the right order, with patience, gets you to a result far faster.
Handing the whole responsibility to a developer is another common mistake. Content quality decisions usually sit with whoever wrote the page. A developer can only help with submission and measurement.
What Roadmap Do You Follow in the End?
When you run into this status, start by reviewing content quality and overlap. Then connect the page to the rest of your site through internal links. Finally, resubmit through URL Inspection, and track Google's decision without expecting a fixed timeline.
You can also use our free SEO checker tool to quickly review similar signals on your own site, such as titles, meta descriptions, and indexability. That way, you spot which pages carry a similar risk ahead of time.
One last thing worth remembering: this is not a one time fix. As your site grows, new page groups go through the same evaluation. So keeping up the habit of strong content and internal linking is what pays off over the long run.
Core guide: What Is Digital Marketing? Its types, examples and how it is done, on one page with an interactive film that travels through the brain.



