Search Console Page indexing: Why pages aren't indexed

Crawled - currently not indexed: what it means

Google crawled the page and chose not to index it for now. What Google says about it, what to rule out, and what can change the decision.

Google fetched the page and decided not to index it, at least for now. There is no error to fix and Google does not say why. Rule out a noindex, a canonical pointing elsewhere and a page that renders empty, then make the page clearly worth indexing and link to it from pages Google already indexes.

What "Crawled - currently not indexed" means

Google: "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." It is a decision, not a fault. After crawling, Google says each page is "evaluated, consolidated, and assessed to determine its suitability for the index", and this one did not make it in. The report gives its source as "Google systems" rather than "Website", and Google says you can generally fix only issues whose source is the website.

Is it a problem?

Depends on the URL

It depends on the page. For tag archives, thin variants and old posts, not being indexed is often reasonable. For a page you want ranking it is a real loss, but there is no setting to switch back, and resubmitting an unchanged page does not help.

Causes, most likely first

Google judged the page not useful enough to index at the time. Google says its systems "prioritize the fast inclusion of high quality, useful content", and that a crawl request does not guarantee inclusion "instantly or even at all".
The page is close to another page on the site or elsewhere, and Google consolidated it without saying so in this status.
The page was crawled recently and the decision may change. Google says it "may or may not be indexed in the future".
The content Google rendered is thinner than what a browser shows, because scripts or resources failed during rendering.

How to confirm it

Inspect the URL. Google notes the live test cannot check this status, so read the indexed result: the last crawl date, "Indexing allowed?", and the user-declared and Google-selected canonicals.
Run the indexability checker to rule out a noindex, a canonical pointing at another URL or a redirect. Those are fixable, and they are different statuses.
Open View crawled page and compare the HTML Google received with what a browser shows.

Indexability checker

How to fix it

Fix anything technical first: a noindex, a wrong canonical, or content that does not render for Googlebot.
Make the page clearly distinct from similar pages on the site, or merge them and redirect the weaker one to the stronger.
Link to the page from relevant pages Google already indexes, and keep it in your sitemap.
After a substantial change, request indexing once in URL Inspection. Google says not to bother asking for a recrawl unless there is an important change.

How long recovery takes

Google gives no timeline for this status and says the page "may or may not be indexed in the future". After a substantial change a recrawl can take "anywhere from a few days to a few weeks", and requesting one does not guarantee inclusion.

After a fix, Validate fix on the issue asks Google to recheck the affected URLs. Google says validation "typically takes up to about two weeks, but in some cases can take much longer". Without it, the count still updates as Google recrawls, and an issue leaves the table once 90 days pass with no instance.

Would monitoring have caught it?

No. Nothing in this status is a change to a status code, a robots.txt rule, a noindex, a redirect or a canonical tag, which are what the monitor watches, so it would not have warned you before Google reported it. The checks above are how to investigate it.

Six checks when a site disappears from Google

Sources

Every claim above about how Google behaves is from Google's own documentation, read on 2026-10-06. If Google has changed a page since, Google's page wins and we would like to know.