“Crawled - Currently not Indexed” Finally Explained - ZipTie.ai - AI Search Intelligence
“Crawled – Currently not Indexed” Finally Explained
ZipTie Team
4 min read
Published: June 1, 2023
Crawled but not indexed is a common reason that a page isn’t indexed. Let’s explore how to fix this issue for your website! What do we know about Crawled – Currently not Indexed? This could mean one of two things: Three most common reasons for “Crawled – Currently not Indexed” There are three most common […]
Crawled but not indexed is a common reason that a page isn’t indexed. Let’s explore how to fix this issue for your website!
What do we know about Crawled – Currently not Indexed? This could mean one of two things:
- The page was indexed beforehand, but later, it was deindexed. This is still quite common.
- The page has never been indexed. It was crawled, but Google chose not to include it in its index.
Three most common reasons for “Crawled – Currently not Indexed”
There are three most common reasons:
- Google considers the page irrelevant or low-quality.
- There are problems caused by JavaScript SEO issues (i.e. Google doesn’t see content generated by JavaScript).
- The most surprising reason: Google isn’t convinced about the website overall.
Let’s look deeper into these three reasons
- Google isn’t convinced about the website overall.
It might be surprising, but a page might not be indexed because Google isn’t convinced about the overall quality of the website. John Mueller from Google explains that when Google’s algorithms aren’t sure about the overall quality of a website, they might crawl the URL but decide not to index it.
Let me quote John Mueller:
- “A lot of the pages that I’ve seen on Twitter that get flagged for kind of these issues where they fall into discovered not indexed or crawled not indexed. It tends to be that the website overall is kind of in this murky area.”
- “A common situation is really that our algorithms are just not sure about the overall quality of the website. And in cases like that, we might crawl the URL, we might look at the content and say: “I don’t know”.”
2. Website suffers from JavaScript SEO issues
Sometimes a page might be high quality, but Google can’t see its value because it can’t render the website properly. This could be due to JavaScript issues.
To check if this is the problem, use the URL Inspection tool in Google Search Console to see how Google renders your content. Make sure important elements are visible and accessible.
To illustrate the problem I like to use the Disqus.com case. Users get a fully-featured website.
And Google is getting an empty page. This is something that you will notice by using the URL Inspection tool in Google.
Expand table
| How users see the page | How Googlebot sees the page |
If you see your page as high quality, but still the page is classified as “Crawled – currently not indexed”, check in the URL Inspection Tool to see how Google renders your content.
- Check the screenshots – to see if some crucial elements are missing.
- Check the HTML tag to see if Google can see all the important elements.
3. A page is unhelpful or low quality
Google aims to provide users with relevant and high-quality content. If a page is low quality or outdated, it might not be indexed.
To objectively assess your content’s quality, use Google’s list of Content and Quality questions.
How to check if a page is classified as “Crawled – currently not indexed”?
To find affected pages, go to Google Search Console and click on Indexing -> Pages.
Click on “Crawled – currently not indexed” to see a sample of up to 1,000 URLs.
Remember that the report might show outdated information, so double-check using the URL Inspection tool.
The workflow to fix “Crawled – Currently not Indexed”.
Here’s a workflow to fix “Crawled – but not Indexed” issues:
- Identify the reason why the page isn’t indexed (e.g., low-quality content, JavaScript issues, or website quality).
- Address the specific issue (e.g., improve the content, fix JavaScript problems, or enhance overall website quality).
Take control of your deindexed pages
In this article, I explained that one reason for the status “Crawled – but not Indexed” is when a previously indexed page gets removed from the index. This occurrence is quite common, particularly during core updates.
Luckily, ziptie.ai/ provides an Indexing Monitoring module that can help you with this. By using ZipTie, you can easily identify the specific URLs that have been deindexed by Google. Don’t hesitate to give it a try and see the benefits for yourself! Check out our 14-day trial!
Related content
\ \ February 2024\ \ How to fix Discovered Currently not indexed\ \ “Discovered – Currently not indexed” is a common indexing issue in Google Search Console. It means Google knows your page exists, but hasn’t visited it yet. This article explains why this happens and provides solutions. Four reasons for “Discovered – currently not indexed” There are four reasons for “Discovered – currently not indexed”: Let’s explore […]](https://ziptie.ai/blog/how-to-fix-discovered-currently-not-indexed/) \ \ February 2024\ \ How to fix Crawled – currently not indexed \ \ Crawled – currently not indexed is one of the most common reasons that a page isn’t indexed. Let’s explore how to fix this issue on your website! When Google shows "Crawled – currently not indexed" in Search Console, it means Google has seen your page but decided not to include it in search results. This […]](https://ziptie.ai/blog/how-to-fix-crawled-currently-not-indexed/) \ \ June 2023\ \ The Pitfalls of Dynamic Rendering: How Disqus.com Lost 90% of Traffic \ \ A few years ago, in 2018, I noticed a significant decline in traffic for Disqus.com, a website for a popular commenting plugin. Intriguingly, this drop coincided with Google’s March 2018 update. They haven’t recovered since then. However, they could implement a simple fix to get back on track. A Misguided Recovery Effort You might assume […]](https://ziptie.ai/blog/the-pitfalls-of-dynamic-rendering-how-disqus-lost-90-of-traffic/) \ \ June 2023\ \ Fixing “Discovered – currently not indexed” in Google Search Console\ \ “Discovered – Currently not indexed” is a common issue in Google Search Console. It means Google knows about your page through links or via a sitemap, but hasn’t visited it yet. This article explains why this happens and provides solutions. Four reasons for “Discovered – currently not indexed” There are four reasons for “Discovered – […]](https://ziptie.ai/blog/fixing-discovered-currently-not-indexed-in-google-search-console/) \ \ June 2023\ \ Google Search Console is not enough to solve your indexing problems \ \ People frequently ask us about the differences between ziptie.ai/ and the indexing reports provided by Google Search Console (GSC). While GSC is a useful tool, it has limitations that can make it challenging to use for certain tasks. Here are five ways in which GSC might fall short: GSC Doesn’t Show all Unindexed URLs GSC’s […]](https://ziptie.ai/blog/google-search-console-is-not-enough-to-solve-your-indexing-problems/) \ \ June 2023\ \ How to deal with “Duplicate, Google chose different canonical than user” \ \ In this article, we will simplify a commonly seen Google-indexing problem: “Duplicate, Google chose different canonical than user.” In simple terms, this status means that Google didn’t agree with your canonical hints and chose a different page to the canonical version. As a result, the page is not in Google’s index. Canonical proposed by the […]](https://ziptie.ai/blog/duplicate-google-chose-different-canonical-than-user/)
7-Day Free Trial
Monitor ChatGPT, Google AI Overviews, and Perplexity with no strings attached.
×
Help us improve ziptie.ai
We use first-party analytics to understand how visitors use this site. No third parties, no tracking across other sites. See our Privacy Policy for details.
RejectAccept