Part of the Crawling & Indexing series. For the full picture, start with Crawling and indexing: how search engines find your pages, and what stops them.
Few Search Console messages cause more worry than a growing Crawled - currently not indexed count. It looks like an error, but it isn’t one: Google fetched the page, looked at it, and decided it wasn’t worth keeping for now. Its sibling, Discovered - currently not indexed, means Google hasn’t even fetched it yet.
Both are fixable, but not by clicking “Request indexing” (or by the Indexing API, which only covers job postings and livestreams). This guide explains what each status means, when it matters, how to find the cause, and how to fix it for a whole template at once.
What does “Crawled - currently not indexed” mean?
It means Google crawled the URL and chose not to index it. Search Console’s Page indexing report help puts it this way: “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.”
There’s no error to fix in the usual sense. The page loaded and was allowed to be indexed; Google simply didn’t consider it worth adding. Google is open that this is normal: “Indexing isn’t guaranteed; not every page that Google processes will be indexed” (how Google Search works).
How is it different from “Discovered - currently not indexed”?
| Status | What Google says | What it usually points to |
|---|---|---|
| Discovered - currently not indexed | “The page was found by Google, but not crawled yet. Typically, Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl.” | Crawl capacity: slow servers, too many URLs, weak signals of importance |
| Crawled - currently not indexed | “The page was crawled by Google but not indexed. It may or may not be indexed in the future” | The page itself: duplicate, thin, low value or weakly linked |
Discovered is a crawling problem; see crawl budget. Crawled is an indexing decision; most of this guide is about that.
When is it a real problem?
Look at which URLs are in the list before you worry about how many. Many belong there:
- Parameter and filter URLs, sort orders, session IDs
- Paginated archives and tag pages with little unique content
- Feeds, print versions, attachment pages
- Old URLs you’ve since replaced
It’s a problem when the list contains pages you want to rank: product pages, articles, category pages, location pages. If a whole template shows up (every product variant, every new article for a month), that’s a pattern worth fixing.
Why does Google crawl a page and not index it?
Google doesn’t give a reason per URL, so diagnosis means checking the usual causes. In rough order of how often they explain it:
| Cause | What it looks like | How to confirm |
|---|---|---|
| Duplicate or near-duplicate | Variants, filtered views, syndicated or templated text | URL Inspection shows a different Google-selected canonical; a crawl finds the duplicates |
| Thin or low-value content | A few lines of text, empty categories, placeholder pages | Word count; compare with the pages that are indexed |
| Weak internal linking | Linked once, from deep in a paginated archive, or only from the sitemap | Inlinks and click depth in a crawl |
| Content depends on JavaScript | Raw HTML nearly empty; text appears after rendering | Raw vs rendered word count |
| Looks like an error page | “No products found”, “Out of stock” with no other content | The page as Google rendered it in URL Inspection |
| It’s new | Published days ago | Wait and check again |
Google’s guide to helpful, people-first content is the best reference for the second cause. Its questions, such as whether content provides “a substantial, complete, or comprehensive description of the topic”, are the ones to ask of a page Google keeps declining.
How do you diagnose it, step by step?
1. Export the URLs and group them
Export the affected URLs from the Page indexing report and sort them by path. Patterns appear quickly: /tag/, ?color=, /products/…-variant-, articles from one author or one month. Diagnose a group, not a URL.
2. Inspect a sample in Search Console
Open a few URLs from each group in URL Inspection. Compare the user-declared canonical with the Google-selected canonical: if Google picked another URL, you have a duplicate problem, not a quality problem. Use the live test to see the page as Google renders it now.
Crawlens can run the same inspection without leaving the crawl: open a URL, go to its Search tab and click Inspect URL. It shows Coverage, Indexing, robots.txt, Page fetch, Last crawled, Crawled as, and the Google-selected and declared canonicals side by side (up to 2,000 inspections a day per property, Google’s limit).
3. Crawl the affected URLs
Paste or import the exported URLs into a URL list crawl to check every one, then run a normal crawl so you also get link data. The checks that usually explain Crawled - currently not indexed:
| Check | What it tells you |
|---|---|
| Duplicate content, Near-duplicate content | The page competes with others for the same content |
| Missing canonical tag, Canonicalised pages | How duplicates are, or aren’t, consolidated |
| Thin content (under 200 words) | Too little on the page |
| Pages with only one internal link, Pages more than 4 clicks from the start | Weak signals that the page matters |
| Orphan pages | In the sitemap, linked from nowhere |
| Content depends on JavaScript | Text only after rendering (needs Render JavaScript) |
4. Find the rest of the pattern with Search Console data
The Page indexing report only shows a sample. With Search Console connected, Indexable pages with no search impressions lists every indexable page in the crawl that didn’t appear in Google search in the period, which catches pages in the same situation that the report doesn’t list.
5. For “Discovered”, check the logs
If the problem is Discovered - currently not indexed, import server logs. Indexable pages Googlebot did not crawl shows which pages Googlebot never requested, and the log views show where its requests went instead. See log file analysis for SEO.
How do you fix it?
| Cause | Fix |
|---|---|
| Duplicates | Choose one URL per page; redirect or canonicalise the others; stop linking to the variants. See duplicate content and canonical errors |
| Thin pages that should rank | Add what a searcher needs: specifics, answers, data, comparisons. See thin content |
| Thin pages that shouldn’t rank | Merge them, noindex them, or remove them, so they stop diluting the site |
| Weak internal linking | Link from relevant, strong pages with descriptive anchors; bring pages within a few clicks of the homepage. See the internal linking audit |
| JavaScript-dependent content | Server-side render or pre-render the main content. See JavaScript SEO |
| Pages that look like errors | Return a real 404 for empty results, or give the page useful content |
| Discovered, not crawled | Speed up the server, cut low-value URLs, and strengthen links to the pages. See crawl budget |
What about “Request indexing”?
It’s for telling Google about a page you’ve just fixed, not a fix in itself. Google’s URL Inspection help says “submitting a request does not guarantee that the page will appear in the Google Index” and “there is a daily limit to how many index requests you can submit.” For Crawled - currently not indexed, Google already says there’s “no need to resubmit.” Fix the pattern, keep the pages in an accurate sitemap, and let Google recrawl.
How long until the pages are indexed?
Google says crawling “can take anywhere from a few days to a few weeks” (ask Google to recrawl), and a recrawled page still has to be judged worth indexing. Track the count in the Page indexing report over a month or two, and re-crawl your site to confirm the fixes are live: in Crawlens, Compare shows which duplicate, thin and linking issues have gone.
For how these statuses fit with the rest of crawling and indexing, see the crawling and indexing guide.
Checklist
- Affected URLs exported and grouped by template or path
- Groups that shouldn’t be indexed accepted (parameters, feeds, thin archives)
- Sample URLs inspected: Google-selected vs declared canonical, rendered page
- Affected URLs crawled for duplicates, thin content, weak links and JavaScript dependence
- Duplicates consolidated to one URL
- Pages that should rank improved and linked from strong pages
- Pages that shouldn’t rank merged, noindexed or removed
- For Discovered: server speed, crawl waste and logs checked
- Sitemap lists only the pages you want indexed
- Count tracked over the following weeks; site re-crawled and compared
Frequently asked questions
What does Crawled - currently not indexed mean?
Google crawled the page but chose not to add it to its index. Google says it may or may not be indexed in the future and that there's no need to resubmit the URL. It's a decision about the page, not a technical error.
What is the difference between Crawled and Discovered - currently not indexed?
Discovered means Google knows the URL but hasn't crawled it yet, typically because crawling it was expected to overload the site. Crawled means Google fetched the page and still decided not to index it. The first is usually about crawl capacity, the second about the page itself.
Should I request indexing for these pages?
Only after fixing them, and only for a handful. Google says requesting indexing doesn't guarantee a page appears in the index, there's a daily limit on requests, and for Crawled - currently not indexed it says there's no need to resubmit.
How long does it take for these pages to be indexed after a fix?
Google says crawling can take anywhere from a few days to a few weeks. Pages also need to be judged worth indexing once recrawled, so track the number of affected URLs over a month or two rather than day by day.
Is it normal to have pages that are not indexed?
Yes. Google says indexing isn't guaranteed and not every page it processes will be indexed. Parameter URLs, feeds, thin archives and duplicates often belong in this list. It's only a problem when pages you want to rank are in it.