'Crawled - currently not indexed': what it means and how to fix it

This status matters more than it used to. AI answers cite what's been crawled, and they lean toward pages that are kept current. A page that is crawled but not indexed can't rank in Google, and it can't be cited in AI Overviews either. FreshlyCited helps Google discover and index the pages, posts and backlinks you publish or update sooner, so they become eligible for Google Search, AI Overviews and AI Mode, then re-checks and shows you what Google has indexed. This guide explains what the status means per Google's documentation, when to ignore it, the common causes, and a step-by-step way to fix it and confirm the result.

What 'Crawled - currently not indexed' means

"Crawled - currently not indexed" is a reason in the Search Console Page indexing report that says Google crawled the URL but chose not to index it. Google's Page indexing report documentation describes it plainly: "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."

Three things follow from that wording:

1. Google reached the page. Robots.txt, server errors and noindex are not the issue here, because those produce different statuses.
2. Google processed what it found. The decision was made after the crawl, which points to the page itself or how it fits into your site.
3. The decision isn't final. Google re-evaluates over time. A page can move into the index later without any action, and an improved page has a better chance.

If no pages from your site appear in Google at all, this status isn't the place to start; work through why a website isn't showing up on Google first.

It helps to remember how Google describes its own pipeline. In How Google Search works, Google lists three stages (crawling, indexing and serving) and says it doesn't guarantee it will crawl, index or serve any page, even one that follows its guidelines. "Crawled - currently not indexed" is the point where a page passed the first stage and stalled at the second.

If you're seeing a different status, such as "Discovered - currently not indexed", the problem is earlier in the pipeline. See discovered - currently not indexed for that case, or all page indexing statuses for the full list.

Is it a problem? When to leave it alone

"Crawled - currently not indexed" is only a problem when it affects pages you want to rank or be cited. On many sites a large share of URLs in this bucket are pages nobody needs in search.

Leave it alone when the affected URLs are:

• Paginated archive pages, tag pages or internal search results
• Parameter variants (sort orders, filters, tracking parameters)
• Feeds, print versions, or attachment pages
• Old, thin pages you were planning to remove or merge anyway

Treat it as a problem when it affects:

• New articles, landing pages or product pages you've just published
• Updated pages that dropped out of the index after a change
• A large share of one template (every product page, every location page)
• Pages that earn backlinks or that you are paying to promote

A quick way to triage: export the example URLs from the report and sort them by template or folder. Google notes that the example list is capped at 1,000 URLs and isn't guaranteed to show every URL with a given status, so treat it as a sample. If the bucket is mostly low-value URLs, the right fix may be to stop generating them, not to get them indexed.

Common causes: thin, duplicate or low-value content

The most common reason Google crawls a page and declines to index it is that the page adds little that isn't already in the index. Google indexes selectively, and a page has to earn its place.

Two checks catch most of these. First, open URL Inspection and compare the user-declared canonical with the Google-selected canonical; if Google picked a different URL, it considers your page a duplicate (see duplicate without user-selected canonical and alternate page with proper canonical tag for those statuses). Second, use Test live URL and view the rendered page to make sure the main content actually appears in what Googlebot sees.

AI-assisted content isn't a problem by itself, but pages produced at scale with little added value are what Google's spam policies call scaled content abuse: "many pages are generated for the primary purpose of manipulating search rankings and not helping users." If a whole batch of generated pages lands in this status, that is a signal about the batch, not about each URL.

Weak internal linking and orphan pages

Weak internal linking makes a page look unimportant. A page that is only reachable from a sitemap, or buried five clicks deep, sends Google a weak signal that you care about it.

Look for these patterns:

• Orphan pages: in the sitemap but not linked from any other page on your site.
• Deep pages: only reachable through long chains of pagination.
• Nofollowed or script-only links: links Google can't follow as normal <a href> links.
• No contextual links: the page appears only in navigation or footer lists, never in body copy on related pages.

The fix is straightforward. Link to the page from two or three relevant pages that Google already crawls often, such as your homepage, a hub page or popular articles, using descriptive anchor text. External links help in the same way. A link from a relevant page that Google already has indexed can tell Google the page is worth keeping; see how backlinks help indexing for how that works and its limits.

Site-wide quality signals

Sometimes the cause is not the page but the site around it. If a large share of a site is thin, duplicated or unhelpful, new pages from that site can land in the same bucket. Google's How Search works guide lists "The quality of the content on page is low" among common indexing issues and says "Indexing isn't guaranteed; not every page that Google processes will be indexed."

Signs you're dealing with a site-level issue:

• The status affects new pages across many templates, not just one.
• Well-written new pages sit in this bucket as long as weak ones do.
• The number of indexed pages has been flat or falling while you keep publishing.

Google's guidance on creating helpful, reliable, people-first content is the reference here. In practice, the work is pruning and consolidating: remove or noindex pages that serve no one, merge overlapping posts into one stronger page, and put your effort into fewer, better pages. This is slow, and you won't see a change in days. It is still the fix that actually moves the number.

How to fix it, step by step

Fixing "Crawled - currently not indexed" means changing what Google found, then asking it to look again. Work through this checklist in order.

Diagnosis checklist

• Is this a page you actually want indexed? If not, stop here.
• Does URL Inspection show the page as crawlable and indexable (no noindex, allowed by robots.txt, 200 status)?
• Does the rendered HTML include the full main content?
• Does the Google-selected canonical match your declared canonical?
• Is there another page on your site (or elsewhere) covering the same thing better?
• Is the page linked from relevant, frequently crawled pages?
• Does the page add something that the pages already ranking don't?

Fixes

1. Decide keep, merge or remove. If the page duplicates another, merge it and 301-redirect, or canonicalize. If it serves no search purpose, noindex or remove it.
2. Make the content substantially better. Add original information, examples, data you collected, clearer answers and a structure that matches the query. Cosmetic edits don't count.
3. Fix rendering. Make sure the main content is in the initial HTML or renders reliably for Googlebot.
4. Strengthen internal links. Add contextual links from two or three related, well-crawled pages.
5. Update your sitemap. Keep the URL in your XML sitemap and set <lastmod> to the real date of the change.
6. Prompt a re-crawl once the page has actually changed (next section).
7. Re-check after a few days, then again a week or two later.

• Don't click Request indexing again and again without changing the page. Google says repeated requests for the same URL "won't get it crawled any faster" (Ask Google to recrawl your URLs), and a recrawl of the same page usually brings the same decision.
• Don't bump the published or modified date without a real change. Google's helpful content guidance lists it as a warning sign: "Are you changing the date of pages to make them seem fresh when the content has not substantially changed?"
• Don't use Google's Indexing API for ordinary pages. It is documented only for job posting and livestream pages.
• Don't mass-buy low-quality links to force the issue. Indexing won't rescue a page Google doesn't value, and spammy links can cause their own problems.

Getting Google to re-crawl after the fix

After a meaningful change, ask Google to crawl the page again so it evaluates the new version. For a handful of pages you own, the URL Inspection tool is the direct route. For every route and what to expect from each, see how to get Google to crawl your site.

1. Open Search Console, paste the URL into the inspection bar and run Test live URL to confirm the fixed version is what Googlebot will see.
2. Click Request indexing. You must be an owner or full user of the property, and there is a daily quota for individual URLs.
3. For many pages, resubmit your sitemap with accurate lastmod values instead of requesting each URL.
4. If you fixed a pattern across a template, use Validate fix in the Page indexing report. Google says validation "typically takes up to about two weeks, but in some cases can take much longer."

Google is clear that crawling "can take anywhere from a few days to a few weeks." A request is a request; Google still decides whether to index. When you have more URLs than the quota covers, or you're working across many client sites, a push service can ask Google to look at the batch. FreshlyCited, for example, checks each URL first and can push the fixed page to Google only if Google still can't see it, so you don't spend on pages that are already in.

Checking whether the page is now indexed

Confirm the result instead of assuming it. A fixed page that is still "Crawled - currently not indexed" after several weeks needs another look at the causes above, not another request.

Ways to check:

• URL Inspection: shows whether the URL is on Google, the last crawl date and the selected canonical. This is the most reliable view for a single page you own.
• Page indexing report: watch the count for this reason fall over time. The report updates more slowly than URL Inspection.
• site: or exact-URL search: a quick look only. Google's documentation says site: results are "not always exhaustive," so a missing result doesn't prove the page isn't indexed.
• A bulk index checker: for many URLs, or pages on sites you don't own, a checker records which URLs Google returns and lets you re-check on a schedule.

Getting indexed is also the first gate for AI search. Google says a page must be indexed and eligible to show with a snippet to appear as a supporting link in AI Overviews or AI Mode (AI features and your website), which is why unindexed pages can't appear in AI Overviews. Indexing doesn't guarantee a citation; quality, authority and relevance still decide that. It does make the page eligible.

For the wider picture of crawling, indexing and how long each takes, read the Google indexing guide.

If you want to see which of your pages Google has and which it doesn't, without checking them one by one: Check your own links free. FreshlyCited checks what Google sees, pushes only what it can't, and re-checks so you know whether the fix worked.