What Is “Crawled – Currently Not Indexed”?
“Crawled – currently not indexed” is a reason in Google Search Console's Page indexing report for URLs that Googlebot has fetched but that Google has, for now, decided not to add to its index.
Google's full description is one sentence: “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” (Page indexing report). Google writes the label with a hyphen (“Crawled - currently not indexed”). It sits in the report's “Not indexed” group, which Google says covers pages that “have not been indexed, but not necessarily because of an error.”
It differs from its neighbour status. With “Discovered – currently not indexed”, Google knows the URL but has not fetched it yet, usually because crawling was postponed; that is a crawl-scheduling problem, covered in our guide to fixing “Discovered – currently not indexed”. With “Crawled”, Google has the page and has passed on it. Google does not publish a per-URL reason. Its How Search works guide explains the general picture: during indexing Google groups similar pages, chooses a canonical, and stores information “in the Google index”, but “Indexing isn't guaranteed; not every page that Google processes will be indexed.” The common indexing issues it names are low content quality, robots meta rules that disallow indexing, and site design that makes indexing difficult.
So the work is diagnostic: rule out the technical reasons you can see, then decide which pages deserve a place in the index and make that case through the page itself.
How to Fix “Crawled – Currently Not Indexed” at a Glance
| Step | Action | Expected result |
|---|---|---|
| 1 | Open the Page indexing report and size the problem, filtered by sitemap | A count, and a split between submitted and unsubmitted URLs |
| 2 | Inspect a sample of affected URLs and view the crawled page | You see what Google fetched, when, and which canonical it chose |
| 3 | Rule out technical causes: error-like pages, unrendered content, near-duplicates | Each sample URL either has a technical fix or is cleared |
| 4 | Sort URLs into keep, merge or remove | A short list of pages you actually want indexed |
| 5 | Improve the substance of the pages you keep | Each page offers something the rest of your site and the web do not |
| 6 | Link to those pages and list them in the sitemap | Clear signals of which pages matter |
| 7 | Request indexing for a few changed pages, then monitor | Some URLs move to indexed over days to weeks; others may not |
Time: two to four hours of diagnosis on a small site (our estimate); content work varies; results take days to weeks. Tools: Google Search Console and access to your CMS. Cost: none beyond your time. Skill level: intermediate; Step 3 may need a developer.
What You Need Before Starting
- A verified Search Console property, ideally a Domain property. To request indexing you must be an “owner or full user of the Search Console property” (Ask Google to recrawl).
- A list of the pages you want people to find in Google, so you can separate them from URLs that do not need to be indexed.
- Edit access to the pages, templates and redirects, or a developer who has it.
- A submitted sitemap, so you can filter the report by it. See how to submit a sitemap to Google and Bing.
Step 1: Size the Problem in the Page Indexing Report
Open the Page indexing report and select “Crawled - currently not indexed” in the table Google titles “Why pages aren't indexed”. Note the number of URLs and compare it with the indexed count.
Process: use the filter above the chart to switch between “All known pages”, “All submitted pages” and “Unsubmitted pages only” (Page indexing report). Submitted URLs in this status are pages you asked Google to index that it declined; unsubmitted ones are often variations you never meant to offer, such as parameter, tag or archive URLs. Scroll the example list for patterns: a shared folder, a template type, a date range.
Expected result: a count and a rough picture of which page types are affected. How to verify: you can name the two or three page types that make up most of the list. Common mistake: treating the example list as complete. Google says it “is limited to 1,000 items, and isn't guaranteed to show all URLs in a given status”.
Step 2: Inspect a Sample and View the Crawled Page
Inspect five to ten affected URLs with the URL Inspection tool, choosing examples from each page type you found in Step 1.
What to read:
- Last crawl: when Google fetched the page. If it predates a major improvement, Google has not yet seen the improved version.
- User-declared canonical and Google-selected canonical: a mismatch tells you Google sees the page as a duplicate of another URL.
- View crawled page: Google says this shows “the HTTP request and response, and the returned HTML”. Check the main content is actually in it.
- Test live URL, then View tested page: the live test adds a screenshot of the rendered page, which Google says is “available only in a live test”.
Expected result: for each sample you know what Google fetched, when, and whether it treats the page as canonical. How to verify: the screenshot and HTML show the same content a visitor sees. Common mistake: reading a passing live test as a promise. Google says the live test “only confirms if Google-InspectionTool can access your page for indexing” and does not test for duplicates or quality. For a fuller walkthrough of the tool, see how to check if a page is indexed by Google.
Step 3: Rule Out Technical Causes That Look Like Quality Problems
Check each sample for three technical problems before judging content, because each can make a reasonable page look empty or redundant to Google.
- Error-like pages served with HTTP 200. Google says that when a 200 page's content “suggests an error”, such as “an empty page or an error message”, Search Console shows a soft 404 (HTTP status codes and Google). Empty category pages, “no results” search pages and out-of-stock templates fall close to this. Fix: return 404 or 410 for pages that no longer exist; give thin templates real content or keep them out of the index.
- Content that depends on JavaScript. Google says Googlebot “queues pages for both crawling and rendering” and that rendering happens “once Google's resources allow” (JavaScript SEO basics). If the crawled HTML in Step 2 lacks the main text and the screenshot is blank or partial, Google may be judging a shell. Fix: server-side rendering or pre-rendering, which Google calls “still a great idea”, and check that scripts and APIs the page needs are not blocked.
- Near-duplicates. Pages that differ only by a parameter, a sort order or a few words compete with each other. Google's canonical guide ranks redirects and
rel="canonical"as strong signals and sitemap inclusion as weak (Consolidate duplicate URLs). Fix: consolidate them; see what a canonical URL is.
Classification from Google Search Central, not a measurement
Source: Google Search Central, How to specify a canonical URL with rel="canonical" and other methods (last updated July 10, 2026).
Google lists the three methods in order of how strongly they can influence canonicalization; bars reflect that order, not measured weights. Google also uses site-setup signals such as HTTPS preference, which it does not rank against these.
Expected result: each sample URL either has a technical fix or is cleared of these three causes. How to verify: after a fix, run the live test again and check the HTML and screenshot. Common mistake: assuming every URL in this status has a content problem when a template is serving Google an empty shell.
Step 4: Sort the URLs Into Keep, Merge or Remove
Decide for each page type whether it belongs in Google at all. Google says it is “Absolutely” fine for some pages not to be indexed, naming duplicates and “variations of a page with different filters applied” (Page indexing report).
| Page type | Decision | How |
|---|---|---|
| Unique page you want found (a guide, product, service, press release) | Keep and improve | Steps 5–7 |
| Several thin pages on the same subject | Merge | Combine into one stronger page; 301-redirect the others to it |
| Parameter, sort or filter variation | Consolidate | rel="canonical" to the main version, or leave as is |
| Page that should never appear in search (thank-you, internal search, staging) | Keep out deliberately | noindex; see noindex vs robots.txt Disallow |
| Obsolete page with no replacement | Remove | Return 404 or 410 |
Expected result: a short list of pages that genuinely deserve indexing. How to verify: every URL type from Step 1 has a decision. Common mistake: blocking unwanted URLs in robots.txt. Google says that for a noindex rule to work, the page “must not be blocked by a robots.txt file”; if it is, “the crawler will never see the noindex rule” (Block indexing with noindex).
Step 5: Improve the Substance of the Pages You Keep
Rewrite or expand each page you kept so that it offers something the rest of your site, and the pages already ranking, do not. Google lists “The quality of the content on page is low” as a common indexing issue (How Search works).
A practical test is Google's self-assessment list in Creating helpful, reliable, people-first content. Questions that apply directly to a page Google skipped include: does it “provide original information, reporting, research, or analysis”; does it give “a substantial, complete, or comprehensive description of the topic”; and does it provide “substantial value when compared to other pages in search results”. That guide is written about ranking, but the same questions help decide whether a page adds anything to the index.
For company sites, common candidates are press releases republished word for word from a wire, location or service pages that differ only by a place name, and tag or author archives. Adding facts only you have (figures, quotes, product details, named people) is more useful than adding length.
Expected result: each kept page has a clear purpose and content that is not available elsewhere on your site. How to verify: compare the page side by side with your most similar page; a reader should be able to say how they differ. Common mistake: changing the date or a few sentences and resubmitting. Google is assessing the page, not its timestamp.
Step 6: Show Google Which Pages Matter
Link to each kept page from relevant, already-indexed pages on your site, and make sure it is listed in your sitemap with an accurate lastmod. Google's Page indexing help says that starting from the homepage, Google should be able to index other pages “if your site has comprehensive and properly implemented site navigation”.
Process: add contextual links with descriptive anchor text from your strongest related pages, not only from footers or tag clouds. Remove the merged, redirected and noindexed URLs from Step 4 from the sitemap. The Discovered guide covers sitemap clean-up and crawl capacity in more detail.
Expected result: every kept page is reachable within a few clicks and listed in the sitemap. How to verify: in URL Inspection, the Sitemaps field lists your sitemap once Google has processed it; a Referring page may also appear, though Google says that field is not always available. Common mistake: leaving the sitemap full of URLs you decided not to index, which sends the opposite signal.
Step 7: Request Indexing for a Few Changed Pages, Then Monitor
Inspect each substantially improved page and click Request indexing. Do this only after a real change: for an unchanged page Google says there is “no need to resubmit this URL for crawling.”
Limits (URL Inspection tool; Ask Google to recrawl): there is “a daily limit to how many index requests you can submit”; “requesting a recrawl multiple times for the same URL won't get it crawled any faster”; and “Submitting a request does not guarantee that the page will appear in the Google Index.” Google says indexing “typically takes only a day or so, but can take much longer”, and that crawling “can take anywhere from a few days to a few weeks”. For many changed pages, Google's advice is to submit a sitemap instead.
Expected result: over days to weeks, some inspected URLs show “URL is on Google”. How to verify: see below. Common mistake: requesting indexing for every affected URL; the quota runs out and the unimproved pages are still declined.
How to Verify It Worked
- URL Inspection: the status for an improved page changes to “URL is on Google” and the Last crawl date is after your change.
- Page indexing report: the count for “Crawled - currently not indexed” falls over several weeks, especially under “All submitted pages”. Google notes the report can lag: if URL Inspection shows no problem but the report still lists the URL, “You might have fixed the error after the URL was last crawled”.
- Performance report: filter by the page URL and look for impressions starting after the indexing date.
Indexing is still not guaranteed. Google says it “doesn't guarantee that it will crawl, index, or serve your page, even if your page follows the Google Search Essentials” (How Search works). For typical timings, see how long Google takes to index a new page.
How to Choose a Fix for Your Situation
| Situation | Recommended action | Why |
|---|---|---|
| A few new pages, published days ago | Wait, link to them, check again in two weeks | Google says the status “may or may not” change and resubmitting is unnecessary |
| Crawled HTML or screenshot is missing the main content | Fix rendering (server-side or pre-rendering) | Google indexes from the rendered HTML |
| Empty or “no results” pages returning 200 | Return 404/410 or add real content | Google treats error-like 200 pages as soft 404s |
| Google-selected canonical differs from yours | Consolidate duplicates | Google picks one canonical from each group of similar pages; that is the page that may be shown in results |
| Many similar thin pages | Merge and 301-redirect | Removes near-duplicates; Google lists low-quality content as a common indexing issue |
| Unsubmitted parameter or filter URLs | Leave them, or canonicalise | Google says it is fine for such variations not to be indexed |
| Important unique page still declined after improvement | Strengthen internal links, request indexing once | Signals importance; the request quota is limited |
Common Problems and Fixes
| Problem | Likely cause | Fix |
|---|---|---|
| Live test passes but page stays unindexed | The live test does not assess duplication or quality | Work through Steps 3–6; a pass only confirms access |
| Request indexing unavailable | You are not an owner or full user, or the live test finds the page non-indexable | Get the right permission; fix the blocking issue first |
| Count rises after a site redesign | New templates produce thin or duplicate pages, or content moved behind JavaScript | Compare crawled HTML before and after; fix templates |
| Blog tag and archive pages dominate the list | Many near-identical listing pages | Noindex or prune them; link to the articles directly |
| Republished press releases not indexed | Same text exists on the wire and other sites | Add original material, or link to the canonical version |
| Report still shows a URL that is now indexed | Report data predates the latest crawl | Trust URL Inspection for a single URL; recheck the report later |
| Pages drop out after a robots.txt change | Disallow rule hides content and noindex tags from Google | Remove the block for pages you want indexed or noindexed |
What Not to Do
- Do not request indexing repeatedly. Consequence: Google says it “won't get it crawled any faster”, and you use up the daily quota. Correction: request once, after a real change.
- Do not block the URLs in robots.txt to “clean up” the report. Consequence: Google can no longer see the page or its noindex tag, and the URL can still appear without a description. Correction: use noindex, a redirect or a 404/410.
- Do not mass-delete pages that serve users. Consequence: you lose content and links that may be indexed later. Correction: improve or merge first; delete only obsolete pages.
- Do not use the Removals tool here. Consequence: Google says Removals requests last about six months (removal documentation) and hide URLs; they do nothing to get a page indexed. Correction: use the steps above.
- Do not buy indexing services that promise inclusion. Consequence: Google says it does not accept payment to crawl a site more frequently. Correction: fix the page and its links.
Frequently Asked Questions
What is the difference between Crawled and Discovered currently not indexed?
Discovered means Google knows the URL but has not fetched it yet, usually because it postponed the crawl. Crawled means Google fetched the page and decided not to index it for now. The first is a crawl-scheduling problem; the second is about whether Google chooses the page.
Is Crawled currently not indexed an error?
Not necessarily. Google lists it among reasons in the Not indexed group, which it says are not necessarily errors, and says it is fine for duplicates and filtered variations not to be indexed. It matters only for pages you want people to find in Google.
Should I resubmit pages that are crawled but not indexed?
Not unless you have changed them. Google says there is no need to resubmit these URLs for crawling, that there is a daily quota for indexing requests, and that repeat requests for the same URL do not speed up crawling.
How long does it take for a crawled page to be indexed?
Google gives no fixed time. It says these pages may or may not be indexed in the future, that indexing after a request typically takes a day or so but can take much longer, and that crawling can take from a few days to a few weeks.
Does Crawled currently not indexed mean my site has a penalty?
No. The status is part of normal indexing decisions. Manual actions are reported separately, in Search Console's Manual Actions report, which Google says to check if an indexed page is missing from results.
Can JavaScript cause Crawled currently not indexed?
It can contribute. Google renders pages in a separate queue and indexes from the rendered HTML. If the crawled HTML and the live-test screenshot do not show the main content, Google may be evaluating a nearly empty page.
Should I noindex pages in this status?
Only pages you never want in search, such as internal search results or thank-you pages. For pages you do want indexed, a noindex rule guarantees they stay out. Do not combine noindex with a robots.txt block, because Google cannot see a noindex on a page it is not allowed to crawl.
Why does URL Inspection say the page is indexed while the report still lists it?
The report reflects data from Google's last processing of the URL, while URL Inspection shows the current indexed status. Google notes that a fix made after the last crawl will not show in the report until the URL is crawled again.
Sources and Methodology
This guide is built from Google Search Central documentation and Search Console Help, read on October 8, 2026. Google does not publish per-URL reasons for this status, so the diagnostic steps combine the causes Google documents (content quality, duplication, rendering, soft 404s) with the report's own filters; the sorting table and time estimates are our editorial guidance. We did not test any site for this guide and make no claim about how often each cause occurs.
- official Google Search Console Help, Page indexing report. Status definitions, filters, example limits, validation and FAQ. Read October 8, 2026.
- official Google Search Console Help, URL Inspection tool. Crawled page, live test, request indexing limits. Read October 8, 2026.
- official Google Search Central, In-depth guide to how Google Search works. Indexing stage and common indexing issues. Read October 8, 2026.
- official Google Search Central, Ask Google to recrawl your URLs. Read October 8, 2026.
- official Google Search Central, Creating helpful, reliable, people-first content. Read October 8, 2026.
- official Google Search Central, How to specify a canonical URL with rel="canonical" and other methods. Read October 8, 2026.
- official Google Search Central, How HTTP status codes, and network and DNS errors affect Google Search. Soft 404 definition. Read October 8, 2026.
- official Google Search Central, Understand the JavaScript SEO basics. Rendering queue. Read October 8, 2026.
- official Google Search Central, Block Search indexing with noindex. Read October 8, 2026.
- official Google Search Central, Remove a page hosted on your site from Google. Removals duration. Read October 8, 2026.