Crawled - Currently Not Indexed: What It Means and How to Fix It
Crawled - currently not indexed means Google fetched your page and chose to leave it out. See why, which pages to fix, and how to get them indexed.
Crawled - currently not indexed means Googlebot fetched and read the page, then chose to leave it out of Google's index. To fix it, find out why Google left the page out, change the page, and then request indexing in Google Search Console. Requesting a crawl without a change gets the same result. The usual reasons are an empty JavaScript render, duplicate or thin content, a soft 404, or too few internal links.
Your page has sat in the Pages report under this status for weeks, and Search Console doesn't say what Google objected to. The checks below run in the order that finds the cause fastest, starting with the URL Inspection tool. If the page hasn't been crawled at all, the guide to Discovered - currently not indexed covers that status.
Key takeaways
- Crawled - currently not indexed means Googlebot crawled the page and chose to leave it out of the index, which is common on many sites.
- Confirm the status in URL Inspection first, because the Pages report runs a few days behind.
- Feeds, tag archives, filters and pagination in this status are often fine. Products, services and articles are the pages to fix.
- Check the rendered HTML first, since an empty JavaScript render explains many crawled but not indexed pages.
- When the Google-selected canonical differs from yours, align canonical tags, internal links, the sitemap and redirects on one URL.
- Duplicate, thin or off-intent pages need content only you can give them, or a merge into a stronger page.
- Soft 404s, unavailable products and gated pages need a 301, a real 404 or content Googlebot can see.
- Links from related pages that already rank tell Google the page matters.
- Server logs show the status code and response Googlebot got when it made its decision.
- Test a fix on 20 to 50 pages against an untouched group, then request indexing or click Validate fix.
- Validate fix fails when listed URLs still have the status, so run it on a sitemap that lists only the pages you fixed.
- On Blogger, WordPress and Shopify, archive, attachment and variant URLs in this status are usually fine to leave.
- When most of the site has this status, the fix is site-wide: prune weak pages, merge overlapping ones and raise the quality of new ones.
What Crawled - currently not indexed means
Google indexes a page in stages. It discovers the URL, crawls it, renders it if the content depends on JavaScript, and then decides whether the page deserves a place in the index. This status means the page made it through the first three stages and failed the last one.
That decision is deliberate. Google's help page for the report says "Google doesn't index all pages across the web", and calls this a common message for many sites. The status only needs fixing when the page is one you want people to find: a product, a service page, an article, a category.
In the Pages report, the Source column for this status says Google systems. The other possible value is Website, and the same help page says "In general, you can fix only issues where the source is listed as 'Website'." For this status, Search Console has no setting to correct. For important pages, the same help page points you to URL Inspection to look for problems on your site, and most of the checks below start there.
Confirm the status is current
The Pages report runs a few days behind. Before you change anything, paste the URL into the URL Inspection tool in Search Console. If it says "URL is on Google", the page has been indexed since the report was built, and you can move on.
If it still says "URL is not on Google", click "Test live URL". This shows the page as Googlebot fetches it now, including the rendered HTML, the canonical you declared, the canonical Google chose, and whether indexing is allowed. Keep that panel open. Most of the checks below start from it.
Decide which URLs matter
Open Indexing, then Pages, and click "Crawled - currently not indexed" to see every affected URL. Export the list. Sort it by URL pattern before you look at individual pages, because this status usually shows up by template.
A list dominated by tag archives, RSS feeds, internal search results, sort and filter parameters, and paginated pages is often Google making a sensible call. Those URLs rarely deserve to rank, and the table below says what to do with each kind. If the list contains your products, services or articles, those are the pages to work on first.
| URLs in the list | What to do |
|---|---|
| Products, services, articles, product and service categories, locations | Fix: work through the checks below |
| Two of your pages that answer the same question | Merge: 301 the weaker page to the stronger one |
| Sort and filter parameters, internal search results, tag archives | Exclude: canonical to the main page, noindex, or stop linking to them |
| RSS feeds | Ignore: Google is right to skip them |
Paginated pages such as /page/2/ | Ignore: each page keeps its own canonical URL |
Image files such as .webp or .jpg | Ignore: image files aren't pages |
Check what Google rendered
Start with rendering, because an empty render makes every other check pointless. In the live test, open the rendered HTML and the screenshot. If your main content is missing, Google judged a blank page.
This happens on sites that build their content in the browser with JavaScript: React, Vue and Angular apps, and most AI website builders. Google renders JavaScript in a delayed second pass, and a failed API call or a script error can leave the rendered page with no text. A robots.txt rule that blocks the scripts the page needs has the same effect. For example, Disallow: /*?*, added to block tracking parameters, also blocks script files loaded with a version query such as /assets/app.js?v=3, and Google renders an empty page. You can check any page in a few seconds with the free Googlebot Simulator, which shows the HTML and text a crawler receives.
The fix is to send the content as HTML, through static generation, server-side rendering or pre-rendering. The SSR vs SSG vs pre-rendering guide compares the three. Pre-rendering is the one that needs no rebuild: Encited serves every crawler a fully rendered copy of each page after a DNS change that takes about five minutes.
Check which canonical Google picked
In the URL Inspection result, compare "User-declared canonical" with "Google-selected canonical". When they differ, Google has folded your page into another URL. Search Console usually reports that under a canonical status, but a page Google sees as a near-copy of another can also sit here.
The other URL is usually a variant of the same page: www and non-www, http and https, a trailing slash, a parameter or tracking URL, or a print or feed version. Make every signal point to one version. That means the canonical tag, internal links, the sitemap and redirects. The guides to Duplicate without user-selected canonical and Alternate page with proper canonical tag cover the two canonical statuses in detail. When Google picks a genuinely different page as canonical, the two pages are too similar, and one of them needs to change or merge into the other.
Check for duplicate and near-duplicate content
Google leaves out pages that repeat content it already has, on your site or anywhere else. Product pages with the manufacturer's description, location pages that differ only by city name, syndicated articles, and several posts that answer the same question all fall into this.
Search a distinctive sentence from the page in quotes. If other URLs come up with the same text, that's the problem. Rewrite the page so it carries something only you can give it: your own specs, photos, prices, reviews, local detail or data. When two of your own pages cover the same topic, merge them into one stronger page and 301 the weaker URL to it.
Check if the page is thin or off intent
Some pages are unique and still get left out, because they don't answer the search better than pages already in the index. Search the query you want the page to rank for and read page one. If the results are step-by-step guides and your page is a short product blurb, or the results compare tools and yours describes one, Google has little reason to add yours.
Programmatic pages hit this often. A page with a business name, an address and boilerplate gives Google nothing new. Add the information a searcher is looking for, such as prices, opening hours, availability, comparisons or answers to common questions. When a whole template is thin, fix the template before you publish more pages from it.
Check for soft 404s and unavailable pages
A page can return a 200 status and still look empty or dead to Google. Out-of-stock products with no alternatives, expired job and event listings, search results pages with no results, and empty category pages all read as soft 404s.
Decide what each one should be. A discontinued product with a replacement should 301 to it. A page that's gone for good should return a real 404 or 410. A temporarily unavailable product should stay useful, with the specs, reviews and links to similar items that a visitor would still want.
Check gated and private content
If Googlebot hits a login wall, a paywall teaser or a cookie screen that hides the content, it indexes what it can see, and that's often too little. The live test in URL Inspection shows exactly what Googlebot received. If the page should be public, make sure the content loads without a session. If it should stay private, add a noindex tag so it leaves this report.
Check internal links
Pages with no internal links pointing to them land in this status often. Google reads few internal links as a sign that the page doesn't matter to you. Find two or three related pages that already rank and link from them to the stuck page, with anchor text that says what it's about. A search for site:yourdomain.com "your topic" finds candidates quickly.
Check what Googlebot actually received
Search Console shows a sample of Google's view. Your server logs show every request. For pages that stay stuck, check the logs for verified Googlebot visits: the status code Googlebot got, how long the response took, and whether it fetched the URL you want indexed or a variant of it. Verify the bot by reverse DNS or Google's published IP ranges, because fake Googlebots are common.
Encited crawl logs record every known crawler visit with the status it received, the response time, and the snapshot it was served, so you can see what Googlebot got on the day it made its decision.

Test the fix on a small group first
When a whole template is affected, don't change every page at once. Pick 20 to 50 affected URLs from the same template and apply the fix you think is right. Leave a similar group untouched. Track both for three to four weeks in URL Inspection and in the Pages report.
If the test group gets indexed and the control group doesn't, the fix works, and you can roll it out. If neither moves, the cause is somewhere else, and you found out on 50 pages before touching 5,000.
Request indexing after you fix the page
Once the page has changed, request indexing in URL Inspection. For a batch, use Validate fix in the Pages report, as the section on validation below describes. Google rechecks the URLs over the next two weeks or so. Requesting an unchanged page usually brings the same result, or a short stay in the index that ends within days.
For a batch of fixed URLs, also list them in a separate sitemap with an accurate lastmod date and submit it in Search Console. Google's sitemap guide says it uses lastmod only when the date is consistently accurate, so set it to the day the page changed. The Pages report can then be filtered to that one sitemap, which shows the batch on its own as it moves from not indexed to indexed, and lets you validate only those URLs.
Before you request anything, run the changed page through the free SEO audit and confirm its canonical, robots.txt and noindex checks pass.
For each stuck URL, Index Rush recommends already-indexed pages to recrawl, so Google reaches the fixed page through them.

Why Validate fix failed
Validate fix asks Google to recheck the URLs listed under the status. Google's help page says validation "typically takes up to about two weeks", and sometimes much longer. It fails when "a certain threshold of pages still contain this issue", and it stops early when the first URLs Google checks still have it. For this status, that happens often, because the list also holds the feeds, filters and archives you meant to leave out, and Google makes the same decision on them again.
Validate only the pages you fixed:
- Put the fixed URLs in their own sitemap and submit it, as described under Request indexing above.
- In the Pages report, filter to that sitemap, open Crawled - currently not indexed, and click Validate fix. Google's help page says validation then applies only to the items in that sitemap.
- If it fails, click "See details" to see which URLs still have the status, change those pages, and restart validation. A restart rechecks every URL marked Pending or Failed.
Validation reports on the batch as a whole. A page that got indexed during the cycle shows "URL is on Google" in URL Inspection, whatever the validation status says.
On Blogger, WordPress and Shopify
Blogger. If the list is mostly date archive pages such as /2025/03/, they don't need to be indexed. In Settings, under Crawlers and indexing, turn on custom robots header tags and set archive and search pages to noindex. Those URLs then move to "Excluded by 'noindex' tag". Label and search pages sit under /search, which Blogger's default robots.txt blocks, so they show under "Blocked by robots.txt". If the list is your posts, the cause is the post itself: it's short, it repeats what many other blogs already say, or no other post links to it. Link each one from two or three related posts, add what only you can show, such as your own photos, steps you tested or results, then request indexing.
WordPress. Tag, author and date archives, category archives that only list posts, and attachment pages are the usual non-post URLs here. Yoast SEO and Rank Math can set each archive type to noindex and send attachment URLs to the file or the parent post. Posts and pages in the list get the same checks as on any other site.
Shopify. Shopify gives each product a second URL inside every collection it belongs to (/collections/name/products/item) and a URL per variant with ?variant=. Both point their canonical to the main /products/ URL, so they are fine to leave. The pages to look at are thin collection pages and products that carry the manufacturer's description word for word.
When most of the site has this status
If a large share of your important pages sit here, the cause sits at the level of the whole site. Google judges quality across a domain, and a big pile of thin, duplicate or templated pages lowers its opinion of everything else. The fix is pruning the weakest pages, merging overlapping ones, and raising the quality of what you publish next. That takes months to show, because Google has to recrawl enough of the improved site to change its view.
The Google indexing field guide explains how that site-level judgment forms, and the guide to getting Google to index your website covers the full set of steps once the pages are ready.
FAQ
Why isn't Google Search Console indexing my pages?
Search Console shows why Google left each page out. Open Indexing, then Pages, and read the reason next to each URL. The two most common reasons are Crawled - currently not indexed, where Google fetched the page and left it out, and Discovered - currently not indexed, where Google knows the URL and hasn't fetched it yet. A reason with Website as its source, such as a noindex tag or a robots.txt block, points to a setting on your site that you can change.
Why is my website crawled but not indexed in Search Console?
Google fetched the pages and judged them not worth adding to its index. The usual causes are an empty JavaScript render, content that repeats other pages, thin or off-intent pages, soft 404s and pages with few internal links. When most of the site has this status, Google's view of the whole site is the cause, and pruning and merging weak pages comes first.
What does it mean if a page is not indexed on Google?
The page isn't in Google's index, so it can't show up in any search result. Search Console's Pages report gives one reason for each URL. Some reasons mean the site works as intended, such as Page with redirect, Alternate page with proper canonical tag or Not found (404) on a page you deleted. Crawled - currently not indexed on a page you want found means Google read the page and left it out.
How do I fix pages that are not indexed?
Start with the reason in the Pages report and confirm it in URL Inspection. Fix what Google objected to, then request indexing. For Crawled - currently not indexed, run the checks above in order: the render, the canonical, duplicate and thin content, soft 404s and internal links. For Discovered - currently not indexed, the fix is crawl priority. A request on an unchanged page gets the same result.
Is Crawled - currently not indexed an error?
No. Search Console lists it as a reason a page isn't indexed, with Google systems as the source. Whether it's bad depends on the URL. It's a problem when Google crawls pages you want found and leaves them out. It's expected for duplicates, feeds, filters, pagination and thin archive pages, and those often don't need any fix.
How long can a page stay Crawled - currently not indexed?
Indefinitely. Google doesn't retry on a schedule until the page gets in. Without a change to the page or its signals, the status can stay for months.
How long after a fix does the page get indexed?
A single page with a clear fix and a request in URL Inspection often gets recrawled within days, and indexed then if Google accepts the change. Validate fix on a batch typically takes up to about two weeks. Site-wide quality fixes take months, because Google has to recrawl enough of the site to change its view of it.
Should I request indexing for these pages?
Only after you've changed something. A request on an unchanged page asks Google to repeat a decision it already made.
Can a canonical tag cause Crawled - currently not indexed?
Not usually. When Google picks a different canonical from yours, the URL normally shows as "Duplicate, Google chose different canonical than user". A page whose own canonical points elsewhere shows as "Alternate page with proper canonical tag". Still compare the two canonicals in URL Inspection, and when they differ, align your canonical tags, internal links, sitemap and redirects on one version.
Can noindex or robots.txt cause Crawled - currently not indexed?
Not directly. A page with a noindex tag shows as "Excluded by 'noindex' tag", and a URL blocked from crawling shows as "Blocked by robots.txt". Robots.txt can still cause this status indirectly: when it blocks the scripts a page needs, Google renders a page with little or no content and leaves it out.
What's the difference between Crawled and Discovered - currently not indexed?
Discovered means Google knows the URL and hasn't fetched it yet. Crawled means Google fetched it and decided to leave it out, so the fix for Crawled usually lies in what Google found on the page, while Discovered comes down to crawl priority. The Discovered - currently not indexed guide covers Discovered.
Do backlinks fix Crawled - currently not indexed?
Links help Google see a page as worth indexing, but they won't rescue a page that renders empty, duplicates another URL or points its canonical elsewhere. Fix those first. Links help most when the page is already sound.
