Blog

Crawled - Currently Not Indexed: What It Means and How to Fix It

Google crawled the page and chose not to index it. How to tell if that matters, why it happens, and the fixes that change Google's decision.

TL;DR: "Crawled - currently not indexed" is a Google Search Console status meaning Googlebot fetched the page but Google chose not to add it to the index. It is a judgment about the page, not a crawl error, so resubmitting the URL rarely helps. Fix it by confirming the page should be indexed, then making it clearly unique, useful and well linked, and validating the fix in the Page indexing report.

Crawled currently not indexed is the status Google gives a URL that Googlebot has already visited and processed, but that Google decided not to store in its index for now. Google's own definition in the Page indexing report documentation is short: "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." Everything below follows from that sentence: the crawl already happened, so the fix is never "get it crawled again". The fix is giving Google a reason to keep the page.

What does "Crawled - currently not indexed" mean in Google Search Console?

"Crawled - currently not indexed" means Google reached the URL, received a response, rendered the content, and then left it out of the index. You find it in Search Console under Indexing > Pages, in the "Why pages aren't indexed" table, with the source listed as Google systems rather than Website.

That source label matters. Statuses with source Website (for example "Excluded by 'noindex' tag" or "Blocked by robots.txt") are caused by something on your site that you can switch off. Crawled currently not indexed has no single switch. Google has seen the page and decided, at least for now, that it does not add enough to be worth indexing.

Compare it with its neighbour:

• Discovered - currently not indexed: Google knows the URL but has not crawled it yet. The last crawl date is empty. That is a crawl scheduling problem. See our guide to discovered currently not indexed.
• Crawled - currently not indexed: Google has crawled it, and the last crawl date is filled in. That is an indexing decision.

Is this status always a problem?

No. Google states in the same report documentation that "Non-indexed URLs can be fine" and that most sites have some unindexed pages. Before fixing anything, sort the affected URLs into two groups:

1. URLs that should not be indexed anyway. Typical examples: tag and author archives, ?page=2 pagination, internal search results, filter and sort parameters such as ?color=red&sort=price, feed URLs like /feed/, thin attachment pages in WordPress, staging or print versions. For these, the right move is usually to stop generating or linking them, add noindex, or canonicalize them, not to push them into the index.
2. URLs you need in Google. Product pages, articles, landing pages, docs. These are the ones worth work.

Google also notes that sites with fewer than 500 pages probably do not need to study this report at all and can use site: searches for their key pages instead. If your homepage and main pages are indexed and a handful of archive URLs sit in this bucket, there is nothing to fix.

What should you check first when pages show up there?

Start by confirming the issue still exists, because the report lags behind reality.

1. Open the issue in Indexing > Pages and export the example URLs. The list is capped at 1,000 rows and is not guaranteed to be complete, so for large sites also filter the report by a sitemap that contains only the pages you care about.
2. Run each important URL through the [URL Inspection tool](https://support.google.com/webmasters/answer/9012289). Check whether it now says "URL is on Google". Pages often get indexed days after the report was refreshed.
3. Check the last crawl date. If the crawl was months ago and the page has changed a lot since, the decision was made on an old version.
4. Run a live test ("Test live URL"). Confirm the page returns HTTP 200, is not blocked, has no noindex, and that the rendered screenshot shows the main content. If the rendered HTML is an empty JavaScript shell, Google indexed nothing because it saw nothing.
5. Compare the user-declared and Google-selected canonical. If Google picked a different URL as canonical, you are looking at a duplication problem, not a quality one.

Our free URL health checker, noindex checker and canonical URL checker run the same basic checks on any public URL without a Search Console login.

Why does Google crawl a page and then not index it?

Google does not publish a per-URL reason, so you diagnose by elimination. These are the causes that come up again and again, roughly in order of how often they explain the status:

• Thin or near-duplicate content. Programmatic pages that differ only by a city name, product variants with identical descriptions, or short posts that restate what dozens of other pages already say. Google's systems, in its own words on the recrawl documentation, "prioritize the fast inclusion of high quality, useful content".
• Too many low value URLs on the site. If thousands of parameter or archive URLs are crawlable, the important ones compete with them. This is a site level signal, not just a page level one.
• Weak internal linking. A page linked only from the XML sitemap and nowhere in the navigation looks unimportant. Orphan pages are a frequent pattern in this bucket.
• Rendering problems. Content injected late by JavaScript, content behind a click, or a blocked API call can leave the rendered HTML nearly empty.
• Soft 404 behaviour. Empty category pages, "no results found" pages, or out of stock pages with no content often land here or in Soft 404.
• The page is simply new. Google says in the Page indexing report docs that it can take "a week or so" to crawl and index a new page. Some URLs sit in this status for a few days before moving to Indexed with no action at all.

How do you fix it?

The fix is to change what Google sees when it crawls the page next. Work through these in order and stop when the important URLs are indexed.

1. Make each page worth indexing on its own

Ask one question per page: what does this page give a searcher that the pages already ranking do not? Concrete fixes:

• Merge thin pages that target the same intent into one stronger page and 301 redirect the rest.
• Add the specific detail that is missing: specs, prices, steps, screenshots, original data, a comparison table.
• For programmatic pages, make sure each page has unique data. If 80% of the text is a template, Google sees 80% duplication.
• Remove or noindex pages that exist only for navigation and have no standalone value.

2. Cut the low value URLs Google keeps finding

Reduce the noise so the important URLs stand out. Return 404 or 410 for pages you deleted. Google's crawl budget guide notes that a 404 is "a strong signal not to crawl that URL again", while soft 404 pages "will continue to be crawled, and waste your budget". Remove faceted and parameter URLs from internal links, and keep them out of the sitemap.

3. Strengthen internal links to the pages you want indexed

Link to each important URL from at least one relevant, already indexed page with descriptive anchor text, not only from the footer or the sitemap. A link from the homepage or a top category page is the strongest signal you control.

4. Make sure the content renders

Check the live test screenshot and the "View tested page > HTML" output. The main text, headings and links should be in the rendered HTML. If they are not, move to server-side rendering or static generation for that template.

5. Keep the sitemap honest

List only canonical, indexable URLs that return 200. Keep <lastmod> accurate: Google's sitemap documentation says it uses lastmod only when it is "consistently and verifiably" accurate, and it ignores <priority> and <changefreq> entirely. A single sitemap file is limited to 50,000 URLs or 50MB uncompressed. Our sitemap validator flags non-200 and non-canonical URLs inside a sitemap.

6. Then request indexing, once

After a real change, use "Request indexing" in the URL Inspection tool for your most important URLs. There is a daily quota per property, and Google is explicit that requesting a recrawl several times for the same URL will not get it crawled any faster. Requesting indexing on an unchanged page asks Google to make the same decision again.

How do you run validation in Search Console?

After fixing all instances you care about, open the issue in the Page indexing report and click Validate fix. Google's documented process:

• Search Console immediately checks a few pages. If the issue is still present on them, validation stops.
• Otherwise it queues only the affected URLs for recrawl, not the whole site.
• Validation "typically takes up to about two weeks, but in some cases can take much longer".
• A single remaining instance fails the validation. Do not click Validate fix again until the current cycle has passed or failed.

Google's own tip: create a sitemap with only your most important pages, filter the report by it, and validate against that subset. It finishes faster than validating every affected URL. An issue disappears from the table 90 days after its last instance is gone.

For this status specifically, validation is less meaningful than for errors like a 5xx or a redirect loop, because the "fix" is a quality judgment. Many SEOs skip validation here and simply track the indexed count for the sitemap of important pages.

How long does it take for a crawled page to be indexed?

There is no fixed time. Google's ask Google to recrawl page says crawling "can take anywhere from a few days to a few weeks", and that requesting a crawl "does not guarantee that inclusion in search results will happen instantly or even at all". For a page that was improved, expect at least one more crawl before the status changes. Pages that stay in this bucket for more than a month after real changes usually need consolidation or stronger internal links, not more requests.

Which popular fixes do not work?

Some popular advice wastes time or carries risk:

• Hitting Request indexing every day. Google's documentation says it does not speed things up, and it burns the daily quota.
• Using the Google Indexing API for normal pages. Google restricts the Indexing API to pages with JobPosting or BroadcastEvent structured data, and its spam policies apply to anything submitted through it. See our guide to the Google Indexing API.
• Buying links to the page or using "indexer" services. These do not change the page Google already judged.
• Changing the URL and republishing the same content. You get a new URL with the same content and often a new duplicate.

How can you get other crawlers to see the page faster?

Google's decision is one search engine. Bing powers ChatGPT search, and Bing, Yandex, Naver, Seznam and Yep accept IndexNow pings, up to 10,000 URLs per request. Notifying them when you publish or update a page means the improved version is crawled outside Google quickly, regardless of how long Googlebot takes. Read what IndexNow can and cannot do before relying on it: it notifies, it does not force indexing.

IndexLinks sends each new or updated page you own to those channels, to your Search Console, and to the AI crawlers, and shows a receipt for every verified crawl. A crawl is what it guarantees, within 24 hours; indexing remains each engine's decision. To see which signals on your site might block indexing, run the free site check on the IndexLinks homepage.

FAQ

Should I resubmit URLs that show "Crawled - currently not indexed"? Not without changing them. Google's report documentation says there is "no need to resubmit this URL for crawling". Improve the page first, then request indexing once.

Can "Crawled - currently not indexed" hurt my rankings? The status itself is not a penalty. Pages in it simply do not rank. A large share of the site in this bucket can, however, be a sign of thin or duplicate templates that are worth fixing site wide.

Why did an indexed page move to "Crawled - currently not indexed"? Google re-evaluates pages on each crawl. Pages can drop out after a content change, after similar pages were published elsewhere on the site, or as Google reassesses quality across the web.

What is the difference between crawled and discovered currently not indexed? Discovered means Google knows the URL but has not fetched it, so the last crawl date is empty. Crawled means it fetched the page and declined to index it.

Does a sitemap fix this status? No. A sitemap helps discovery. This page has already been discovered and crawled; the sitemap only helps by keeping the list of important URLs clean and the lastmod dates accurate.

Use this information as a starting point, then verify the page-level evidence available to you.