Crawled, currently not indexed is a Google Search Console status meaning Googlebot fetched the page, evaluated it, and chose not to add it to the index for now. It is not a technical error. It is a judgement that the page does not add enough value relative to what Google already has, and resubmitting it rarely changes that.
That distinction matters because most of the advice online treats this status like a crawl bug: resubmit the sitemap, hammer Request Indexing, buy an “instant indexing” service. None of that addresses the reason Google said no. This guide covers what the status means, how it differs from its neighbour in the report, why it happens, the order to diagnose it in, which fixes work, which do not, and why it now costs you AI visibility as well as rankings. For the discovery and crawl side of the problem, read how to get pages indexed faster first. This post picks up where that one stops: the page was crawled, and it still was not indexed.
What does “Crawled, currently not indexed” mean in Search Console?
It appears under “Why pages aren’t indexed” in the Page indexing report. Google’s own description is short: the page was crawled but not indexed, it may or may not be indexed in the future, and there is no need to resubmit it for crawling. Read that last clause carefully. Google is telling you the crawl worked. Asking for another crawl of the same page tends to produce the same answer.
Two things follow. First, the fix is almost never in your sitemap or your server configuration. Second, the decision is relative. A page is not judged in isolation; it is judged against everything else Google already has for the same intent, including other pages on your own site. A perfectly competent article can sit in this bucket simply because twenty stronger pages already answer the same question.
What is the difference between crawled and discovered, currently not indexed?
The two statuses look alike and point to opposite problems. Discovered means Google has the URL in its queue but has not fetched it. Crawled means Google fetched it and declined it. The neighbouring duplicate statuses are worth knowing too, because they often explain a crawled page that you assumed was unique.
| Status | What Google did | What it usually means | Main lever |
|---|---|---|---|
| Discovered, currently not indexed | Found the URL, has not fetched it | Low crawl priority, weak internal links, or a host Google is wary of overloading | Internal links and crawl hygiene |
| Crawled, currently not indexed | Fetched and evaluated the page, declined to index | Not enough unique value, duplication, or a site-level quality judgement | Consolidate, improve, or prune |
| Duplicate without user-selected canonical | Treated the page as a copy of another URL | No canonical declared and the content overlaps another page | Declare a canonical or merge |
| Duplicate, Google chose different canonical than user | Ignored your canonical and picked another URL | Your signals disagree: canonical, internal links, sitemap, and redirects point different ways | Align every signal on one URL |
| Excluded by noindex tag | Respected your instruction | Intentional, or a stray noindex left from staging | Remove the tag if the page should rank |
If your affected pages are in the Discovered row, this is the wrong guide; the crawl and priority fixes in the indexing speed guide apply. If they are in the Crawled row, keep reading.
Why does Google crawl a page but not index it?
Google does not publish a per-URL reason, so diagnosis is pattern matching. In practice the causes fall into six groups, and most affected sites have more than one.
- Thin or templated content. Programmatic location pages, near-empty category pages, auto-generated tag archives, and product variants where only the colour changes. When hundreds of pages share a template and differ by a handful of words, Google indexes a few and declines the rest.
- Duplication against your own site. Two posts targeting the same query, a print version, a parameter variant, or an old and new version of the same guide both live. Google picks one and leaves the other out.
- Duplication against the web. Manufacturer descriptions, syndicated articles, and AI-drafted pages that restate what the top ten results already say. If the page adds nothing the index lacks, there is little reason to store it.
- Weak internal links. A page reachable only through the sitemap, or linked once from a deep archive page, signals that even its own site does not consider it important. Google tends to agree.
- Canonical confusion. The canonical tag says one URL, internal links point to another, the sitemap lists a third, and a redirect sends some traffic to a fourth. Mixed signals make Google less confident about every version.
- Site-wide quality reassessment. This is the one teams miss. When a large share of a site is low value, Google can lower how much of the whole site it is willing to index. The signature is a sudden jump in crawled-not-indexed URLs, including decent pages, while the total indexed count falls. Fixing individual pages will not reverse it. Reducing the volume of weak pages will.
There is also a technical lookalike. If the main content only appears after client-side JavaScript runs and rendering fails or times out, Google evaluates an almost empty shell and declines it as thin. The page looks fine in your browser. It does not look fine to the crawler.
How do I diagnose crawled, currently not indexed pages?
Work in this order. Each step either solves the problem or rules out a cause cheaply before you reach the expensive step of rewriting content.
- Export and group by pattern. Export the affected URLs from the report and sort them by directory or template. If 90 percent share a path like
/tag/or/locations/, you have a template problem with one fix. If they are scattered, you have page-level problems. - Decide which ones you actually want indexed. Tag pages, internal search results, filtered listings, and thin utility URLs are often correctly excluded. Take them out of your sitemap and move on. Only the URLs that should earn traffic need fixing.
- Inspect the rendered page. Run a few affected URLs through URL Inspection in Search Console and look at the crawled page and screenshot. If the main content is missing, you have a rendering problem, not a quality problem.
- Check canonical signals. Confirm the canonical tag with the Canonical Checker, confirm no redirect chain sits in front of it with the Redirect Checker, and confirm the sitemap lists the same URL. Run the file through the XML Sitemap Validator while you are there; our guide on how to use the XML Sitemap Validator covers how to filter it for junk URLs.
- Look for an internal competitor. Search your own site for the page’s target query. If another of your pages already answers it, the crawled page is a duplicate in all but name.
- Count the internal links. How many pages link to it, and are any of them pages Google crawls often? The Internal Linking Optimizer surfaces weakly linked pages and suggests where links should come from.
- Compare honestly against what ranks. Open the top results for the target query. If your page says the same things with less depth, less evidence, and no first-hand detail, that is the answer.
- Check the site-wide trend. Look at the indexed count over the last three months. A falling line alongside a rising crawled-not-indexed count means the problem is the site, not the page.
How do I fix crawled, currently not indexed?
Four fixes do almost all the work. Which one you need depends on what the diagnosis found.
1. Consolidate duplicates into one strong page
When two or more of your pages compete for the same intent, merge them. Keep the URL with the best links and history, fold the useful content from the others into it, and 301 redirect the rest. Then make every signal agree: canonical, internal links, and sitemap all point to the survivor. Google’s guide to consolidating duplicate URLs lists the signals and how strongly each one counts.
2. Improve the page with something the index lacks
Adding words is not improving. Add the things competing pages do not have: original data, worked examples, screenshots of the real process, a comparison table, a clear answer to the sub-questions the top results skip. Google’s guidance on creating helpful content is the closest thing to a published rubric. For older pages that used to be indexed and slipped, the content refresh strategy guide covers what a real refresh changes, and the Content Decay Revival tool diagnoses a single page. See how to use the Content Decay tool for the workflow.
3. Link to it from pages Google already values
Internal links are the importance signal you fully control. Add contextual links from your homepage, a relevant hub, and two or three related posts that are already indexed and getting traffic. A link from a page Google crawls daily does more than ten links from deep archive pages. The reasoning and the patterns are in internal linking for AI search, and how to use the Internal Linking Optimizer shows how to find the right source pages quickly.
4. Prune what should not exist
When the cause is site-wide, the fix is subtraction. Delete and redirect pages with no traffic, no links, and no purpose. Noindex the ones users need but searchers do not, such as thin filtered views. Stop generating templated pages that differ by a word. It feels backwards to remove pages to get pages indexed, but a smaller site with a higher share of valuable pages is a site Google is willing to index more of. Run the Website Grader on a sample of the survivors to make sure the pages you keep clear the basics.
After any of these, request indexing once for the most important URLs in URL Inspection. Once, after the change, not before it.
What does not fix crawled, currently not indexed?
Most of the time spent on this status goes into actions that cannot work, because they all target discovery and crawling, which already succeeded.
- Resubmitting the sitemap. The sitemap got the page discovered. Resubmitting it repeats a step that already worked.
- Clicking Request Indexing every day. It is quota limited, and recrawling unchanged content tends to reproduce the same decision. It is useful once, after a real change.
- Bumping the date. Changing lastmod or the visible publish date without changing the content is a freshness signal with nothing behind it. Inaccurate lastmod values also teach Google to distrust your sitemap dates generally.
- Third-party instant indexing tools. Many of these push URLs through Google’s Indexing API, which Google documents for job posting and livestream pages only. Even when a crawl follows, the quality decision is the same.
- Padding the word count. Five hundred extra words that restate the first five hundred make a thin page longer, not better.
How long does it take to get out of crawled, currently not indexed?
For a single page that you have materially improved and linked from strong pages, a recrawl on an active site often comes within days and the indexing decision can follow within a few weeks. Site-wide reassessments are slower, because Google needs to recrawl and reevaluate a meaningful share of the site before its view of the whole changes. Expect that to take months rather than weeks. Measure at four and eight weeks against the URL list you exported at the start, and do not judge a pruning project on its first fortnight.
Why does crawled, currently not indexed matter for AI search?
Because unindexed pages cannot be retrieved. Google’s documentation on AI features is explicit that to appear as a supporting link in AI Overviews or AI Mode, a page must be indexed and eligible to be shown in Search with a snippet. There are no extra AI-specific requirements and no way around that one. A page in this bucket has zero chance of being cited in Google’s AI answers, however well it is structured for extraction.
Other assistants run their own crawlers and indexes, as covered in how AI crawlers work, so a page Google declines is not automatically invisible everywhere. In our experience, though, the qualities that get a page declined by Google, thin coverage and duplication of what already exists, are the same qualities that make an assistant skip it when choosing what to cite. Fixing indexing is therefore the first step of any AI visibility work, not a separate SEO chore. Once the page is indexed, why your content is not cited by ChatGPT and the generative engine optimization guide cover the citation side, and the AI Visibility Score measures whether assistants are actually mentioning you.
If you take one thing from this guide: treat Crawled, currently not indexed as editorial feedback, not a ticket for the developer. The search engine read the page and was not convinced. The work is to make it convincing, merge it into something that is, or remove it so the rest of the site is judged on its best pages. Google’s Search Essentials set the floor; everything above it is a judgement about value.
Frequently Asked Questions
What does Crawled, currently not indexed mean?
It means Googlebot fetched the page, looked at it, and decided not to add it to the index for now. It is not a crawl error or a penalty. Google is judging that the page does not add enough value compared with what it already has, and it may or may not index it later.
What is the difference between Crawled and Discovered, currently not indexed?
Discovered means Google knows the URL exists but has not fetched it yet, which usually points to crawl priority, weak internal links, or server capacity. Crawled means Google fetched the page and declined it, which points to the content or its duplication. The first is a priority problem, the second is a value problem.
Should I keep clicking Request Indexing?
No. Request Indexing asks Google to recrawl the URL. The page has already been crawled, so another crawl of the same content tends to produce the same decision. Request indexing once, after you have changed something substantial, and spend the rest of the effort on the page itself.
Is it normal to have some pages crawled but not indexed?
Yes. Almost every site has some, and for tag archives, filtered listings, paginated pages, and thin utility URLs it is the right outcome. It becomes a problem when the affected URLs are pages you need to rank, or when the count climbs steadily while your indexed count falls.
How long does it take for a fixed page to get indexed?
After a substantial improvement and stronger internal links, a single page on an active site is often recrawled within days, and the indexing decision can follow within a few weeks. Site-wide quality problems take longer because Google has to reassess many pages. Judge the fix over four to eight weeks.
Can a page that is not indexed appear in AI Overviews?
No. Google states that a page must be indexed and eligible to be shown in Search with a snippet to appear as a supporting link in AI Overviews or AI Mode. A page stuck in Crawled, currently not indexed is invisible to those features, however good it is.