Crawled Currently Not Indexed: A Page-by-Page Triage Checklist

Crawled - currently not indexed is one of the more frustrating statuses in the Google Search Console Page Indexing report. Google confirmed it found and read the page. It just chose not to include it in the index. The report gives you the status but not the reason, and that is where most site owners get stuck.

This checklist walks through the triage process page by page. Work through each check in order. For most pages, the problem becomes obvious by step three or four.

What "Crawled Currently Not Indexed" Actually Means

According to Google Search Central documentation, this status means Googlebot fetched the page but Googles systems decided not to include it in the index at that time. The decision can reverse without any action on your part, but waiting is not a strategy.

The status is distinct from Discovered - currently not indexed, where Google has the URL but has not fetched it yet. If your page shows Crawled - currently not indexed, the content quality and signals on that specific page are what matter.

Before You Start: Pull the Full URL List

Open the Page Indexing report in Search Console. Click Crawled - currently not indexed to filter. Export the URLs using the download button in the top right of the table. This gives you a CSV to work from, one URL per row.

If you have more than a few hundred URLs in this status, sort them by estimated traffic potential before triaging. Pages that rank for impressions in the Performance report but fail to index are higher priority than pages with zero impressions.

Step 1: Run URL Inspection on Each Page

The URL Inspection tool is the fastest first check. Paste the URL, run the inspection, and read the two key fields:

• Google's index status: confirms whether the page is actually excluded
• Last crawl date: tells you when Google last fetched the page and what it saw

If the last crawl was more than 30 days ago, Google may have fetched an older version of the page than you are looking at now. Use the Live URL test inside URL Inspection to see what Googlebot sees on a fresh fetch.

You can also use our free Search Console tool at searchconsoletools.com to pull URL-level data across your whole property faster than clicking through the GSC interface one URL at a time.

Step 2: Check for Thin or Duplicate Content

The most common cause of this status is content that Google judges as thin, low-value, or largely duplicative of another page it has already indexed.

For each page on your list, ask:

Is this page under 300 words? Google does not publish a minimum word count, but very short pages with limited informational value are frequently excluded. If the page exists only to redirect users or repeat content from a parent page, consider whether it needs to exist independently at all.

Does this page repeat content from another URL on your site? Check whether a category page, tag archive, or pagination variant contains the same main content. Google will typically index the version it considers canonical and exclude the others. See the guide on what Google Search Console's crawled not indexed status means in full for a deeper look at how duplication is handled.

Is there a canonical tag pointing elsewhere? Inspect the page source or use URL Inspection to check the canonical. If the page carries a self-referential canonical but Google thinks another URL is the true canonical, the page may be excluded under the Alternate page with proper canonical tag status instead. Confirm you are reading the right status in the report.

Step 3: Check Internal Link Depth

Pages that receive few or no internal links are harder for Google to judge as important. A page buried five clicks from the homepage with zero internal links from other indexed pages gives Google little signal about its value.

Run a crawl of your site with Screaming Frog or a similar tool, or use the internal links report in Search Console. Filter for pages on your triage list. If a page has zero or one internal links pointing to it, add links from topically related pages that are already indexed.

This is especially common on:

• Recently published pages that have not been linked from any existing content
• Pagination pages beyond page two
• Filtered or faceted URLs on e-commerce sites
• Programmatically generated pages published in bulk

Step 4: Check Page Speed and Core Web Vitals

A page that loads slowly or has poor Core Web Vitals scores is not automatically excluded from the index, but severe rendering problems can prevent Googlebot from fully processing the page. Use URL Inspection's Live URL test to confirm the rendered HTML includes your main content.

If the rendered source is missing large sections of your content, the page likely relies on client-side JavaScript rendering that Googlebot's render queue has not processed. Google does render JavaScript, but there is a delay, and pages relying on JavaScript-heavy frameworks may show incomplete HTML on initial fetch.

Step 5: Check Crawl Frequency vs. Page Update Frequency

Pages that have not changed since they were first crawled sometimes fall into a low-priority recrawl queue. If you update the page with new, substantive content and then use the Request Indexing button in URL Inspection, Google will recrawl it sooner.

The Request Indexing button has a quota: Google limits the number of requests per property per day. Use it on your highest-priority pages first. Per Google's documentation on the URL Inspection tool, the request triggers a crawl, not guaranteed indexing.

Step 6: Look for Crawl Budget Signals at Scale

If you have hundreds or thousands of URLs in the Crawled - currently not indexed status, the issue may be systemic rather than per-page. This often affects:

• Sites with large numbers of near-duplicate pages (filtered category pages, paginated archives, parameter URLs)
• Sites that recently published a large batch of pages at once
• Sites with significant amounts of non-indexed low-quality content that affects how crawl budget is allocated across the whole domain

The guide to crawled currently not indexed on large sites covers these patterns in more depth. At scale, the fix is typically to consolidate thin pages, block parameter URLs with robots.txt or noindex, and reduce the total number of URLs Google needs to evaluate before getting to your important pages.

Step 7: Request Indexing After Making Changes

Once you have made a substantive change to a page (added content, improved internal links, fixed a canonical issue), use URL Inspection to Request Indexing. This tells Google there is something new to fetch.

Do not use Request Indexing as a first step without making changes. If the page had a reason to be excluded before your request, it will likely be excluded again after the crawl.

Step 8: Wait and Re-check

After requesting indexing or making changes, check the Page Indexing report again after 10 to 14 days. The report does not update in real time. The data in Search Console reflects the crawl date shown in URL Inspection, not the moment you made changes.

If a page remains in Crawled - currently not indexed after two recrawl cycles with no apparent content or link issue, it is worth asking whether the page is genuinely useful to a person who would search for it. Pages that exist for internal reasons (tracking, redirects, staging artifacts) rather than to answer a search query are often correctly excluded.

Tracking Progress

Keep the CSV export from step one. After working through the checklist and requesting indexing on your priority pages, run a fresh export from the Page Indexing report in two to three weeks and compare. The count of URLs in the Crawled - currently not indexed status should decrease as fixes take effect.

If a URL moves out of this status and into Indexed, your fix worked. If it moves into a different exclusion status (Duplicate without user-selected canonical, for example), you have a new and more specific problem to solve.

---

Frequently Asked Questions

How long does it take for a "Crawled currently not indexed" page to get indexed after I fix it? After you request indexing through URL Inspection, the initial recrawl usually happens within a few days. Whether the page gets indexed after that crawl depends on what Google finds. If the content issue is resolved, most pages move to indexed status within two to three weeks. Some pages take longer, and some never index if Google continues to judge the content as low-value.

Does requesting indexing in Search Console guarantee the page will be indexed? No. According to Google's documentation, requesting indexing triggers a crawl, not an indexing decision. The indexing decision is made after Googlebot evaluates the page. A request on a page with thin content or no internal links will usually result in another exclusion.

Can I see which specific URLs are in "Crawled currently not indexed" status and filter them in bulk? Yes. In the Page Indexing report, click on the status row to filter. Then use the export button to download the full list as a CSV. The UI shows a sample, but the export is more complete. For properties with thousands of URLs, the export is the only practical way to work through the list systematically.

Why do some pages get indexed immediately while similar pages sit in this status for months? Google's indexing is not uniform across all pages on a site. Pages with strong internal links from already-indexed pages, with unique content, and on domains with higher crawl priority tend to index faster. Pages on domains with many previously excluded pages may face a higher bar because Google allocates crawl and indexing resources based on its assessment of overall site quality.

Should I use noindex on pages stuck in this status to clean them up? Only if the page has no search value and you do not want it indexed. Adding noindex tells Google the page should be excluded, which moves it into the Excluded by noindex tag status and removes it from the Crawled - currently not indexed count. This is appropriate for pages that exist for operational reasons (thank-you pages, internal tools) but should not be used to mask thin content problems on pages you actually want to rank.