Crawled – currently not indexed: what it means and what to do
Short answer: “Crawled – currently not indexed” means Google fetched the page and did not add it to its index. Google calls this “a common message for many sites” that “doesn't necessarily indicate an issue that needs attention”, so the first question is whether the page matters. If it does, rule out blockers, compare the page with your indexed ones, wait and look again; no button forces indexing, and Google names no reason for this status.
What does “Crawled – currently not indexed” mean?
Search Console's Page indexing report sorts every address Google knows about into “Indexed” and “Not indexed”. In the table “Why pages aren’t indexed”, this status carries Google's own description: “The page was crawled by Google but not indexed.” You find the full text in Google's help for the Page indexing report. It has two halves:
- Crawled: Google requested the page and received it.
- Not indexed: Google did not store it in its index, so it cannot appear in search results.
For a single address, the URL Inspection tool says “URL is not on Google” and names the reason in its Page indexing section.
Google's description is short. It says the message is common, mentions no penalty and gives no cause. Google's guide on crawl budget states the general rule: “not every page that is crawled will necessarily be indexed”. After crawling, each page “must be evaluated, consolidated, and assessed to determine its suitability for the index”. Google does not say at which of these steps your page stopped.
Does the page matter? Decide before you fix anything
The Page indexing report help is blunt about coverage: “Don't expect every URL on your site to be indexed. Some URLs might be duplicates or might not contain meaningful information.” Only the key pages count, so sort your addresses first:
| Your page | What to do |
|---|---|
| A variation you never wanted in search, such as a filtered or sorted list, or a duplicate | Usually nothing. Google lists duplicates and filter variations among pages it does not index. |
| An important page: a service, a product, an article you want found | Work through the five checks below. |
| Many pages with this status at once | Look for what the addresses share, such as a folder or a template. Fix that, not each page. |
Google adds that if your site has fewer than 500 pages, you probably do not need the report at all. A search for site: followed by the exact address, for example site:https://your-site.example/your-page, tells you whether a key page is indexed.
Crawled – currently not indexed: five checks for an important page
Google names no cause for this status, so these checks come from what Google documents and from our own view. We mark the second kind.
- Read the stored result, then run the live test. In URL Inspection, read the Page indexing section. It is a snapshot: Google's URL Inspection help says “This is not a live test” and that the page “may have changed or become unavailable since Google last saw it”. Then choose “Test live URL” and open “View tested page” to see how Google renders the page. If the live test shows an error or an empty page, fix that first. A clean live test is not a verdict, though: Google says it “does not test for all possible indexing issues, including whether this is a duplicate or alternate page”.
- Rule out blockers anyway. Google's technical requirements list three: Googlebot is not blocked, the page answers with HTTP 200, and it has indexable content. Meeting them does not mean the page will be indexed: “indexing isn't guaranteed”. Search Console reports a noindex tag, a robots.txt block, a soft 404 and a redirect under their own statuses, and our reading is that they are usually not behind this one. Check anyway, because the stored status can be older than your last change. Our article on a website not showing up on Google walks through those checks. Two commands for a quick look are below the list.
- Compare the page with your indexed pages. Google says it does not index duplicate copies of a page, and that some URLs “might not contain meaningful information”. Our view, not Google's: put the page next to the indexed page on the same topic and ask what it adds. If two pages answer the same question, merge them and send the weaker address to the stronger one with a 301 redirect. If a page is little more than a heading and a template, give it real content or accept that it stays out.
- Link to it from related, indexed pages. Our view: a page that hangs on the sitemap alone, or sits several clicks deep, shows little sign that you consider it important. Link it from indexed pages on neighbouring topics, in a way that fits the text.
- Wait, then look at the same address again. Google gives no time for this status. Its general statements are about crawling: “It can take a week or so” for a new page or site, and indexing “is never instant”. Our reading: look again after several days, not every hour. Google's help says to ask for a recrawl only after an important change that Google has not noticed for “a week or more”. You must be an owner or full user of the property, and there is a quota.
For check 2, this prints the status code and final address after redirects, then any X-Robots-Tag header. A 200 and no header line is what you want:
curl -s -L -o /dev/null -w "%{http_code} %{url_effective}\n" https://your-site.example/your-page
curl -s -D - -o /dev/null https://your-site.example/your-page | grep -i x-robots-tagDiscovered – currently not indexed: the neighbouring status
The two statuses sit side by side in the report:
| Status in Search Console | Google's description | What it means |
|---|---|---|
| Crawled – currently not indexed | “The page was crawled by Google but not indexed.” | Google read the page and left it out. |
| Discovered – currently not indexed | “The page was found by Google, but not crawled yet.” | Google knows the address but has not fetched it. The last crawl date is empty. |
For “Discovered”, Google gives a typical reason: it “wanted to crawl the URL but this was expected to overload the site”, so it rescheduled the crawl. The crawl budget guide lists sites with “a large portion” of URLs in this status among the sites it is written for. Those are large sites: 1 million or more unique pages with moderately frequent (about weekly) changes, or 10,000 or more with very rapidly changing, daily updated content. Google calls the numbers “a rough estimate” and not exact thresholds. For a site without a large number of fast-changing pages, the guide says that keeping your sitemap up to date and checking the Page indexing report regularly “is adequate”.
What you can do on such a site is limited. Keep the server fast and stable: Google lowers its crawl limit when a site slows down or answers with server errors (5xx) or rate limiting (429). Keep the sitemap current, then wait. Google has not fetched these pages yet, so the status says nothing about their content.
What SEOgrinder shows, and what it cannot
SEOgrinder is our tool, and we build it. For this status:
- The free scan at seogrinder.com cannot read your Page indexing report. It does not connect to your Search Console account. The “Google Search” tab accepts an uploaded export of the Performance report (queries, pages, clicks, impressions). Index statuses are not in that data.
- A local installation connected to Search Console can ask URL Inspection about the scanned page and show Google's answer in its own words, as the finding “Google has not indexed this page”. It is a task if the page is meant to be found (it is in your sitemap, it is the home page, or Search Console showed impressions for it). Otherwise it appears under “For your information”.
- Checks near the causes Google hints at. The “Indexing” card in the “Page on Google” tab shows whether the page can be indexed and whether the URL may be crawled. The website crawl lists page pairs that are nearly identical, pages with little text and pages that no internal link points to. These are properties of your pages. Whether Google left a page out because of one of them, SEOgrinder cannot tell, and Google does not say.
Common mistakes
- Chasing the report down to zero. Google writes that “non-indexed URLs can be fine”. Only the key pages need to be in.
- Requesting indexing again and again. Google's page on recrawl requests says that asking repeatedly for the same URL “won't get it crawled any faster”, and that a request “does not guarantee that inclusion in search results will happen instantly or even at all”. The page was crawled already; it needs a reason to be judged differently, not a repeat request.
- Starting “Validate fix” for a status with no fix. Google's help says validation ends as “Failed” when Google finds one remaining instance of the issue, and that “it might not always make sense to fix and validate a specific issue”. Our reading: for this status Google names nothing to fix, so URLs that still carry it make a failed validation the expected result.
- Changing the date to look fresh. Google's page on helpful content lists changing the date of pages to make them seem fresh, when the content has not substantially changed, among the warning signs.
- Sending one page to the indexing-problem form. Google points to the form only for a complete, site-wide problem with indexing, after you have fully diagnosed potential issues.
- Resubmitting the sitemap and expecting a change. A sitemap helps Google discover addresses, but this one was discovered and crawled already.
FAQ
Is “Crawled – currently not indexed” a penalty?
Google's description mentions no penalty and no manual action. It calls the message common and says it does not necessarily point to a problem.
Why does a page stay in this status for weeks?
Google gives no reason and no schedule for this status. It says indexing “is never instant” and that it does not guarantee that all pages everywhere end up in its index. Our reading, not Google's statement: a page that adds nothing to what Google already holds may stay out.
Can I force Google to index the page?
No. “Request indexing” asks Google to crawl an address. It is not an order to add it.
Why did the validation of this status fail?
Because validation ends as “Failed” as soon as Google finds one URL that still carries the issue, and Google names no fix for this status. Judge each key page with the five checks above instead.
Your next step
Open the Page indexing report, click the status and pick the two or three addresses that matter to you. Run the free scan of SEOgrinder on them and read the “Indexing” card in the “Page on Google” tab. Fix whatever is red, press “Check again”, then improve what the page says compared with its indexed neighbours and link it from related pages. Look at the same addresses again after a few days. If the page is brand new, see our steps to rank on Google fast.