"Crawled - currently not indexed" is not a bug. It's a decision. Google fetched the URL and stored the response. Then the indexing pipeline looked at the page and chose not to add it to the searchable index.

Three steps matter here. Crawling is fetching a page. Indexing is storing and understanding it. Serving is returning it in results. A page can pass step one and stall at step two for months. The fix is usually content or duplication, not crawl budget.

This guide covers the gap between those steps, the mistakes that send teams the wrong way, and how to check your own site in Google Search Console.

Crawling, indexing and serving are three separate stages with three separate failures

Mixing them up is why people chase the wrong fix.

Crawling means a bot requests a URL and receives the HTTP response. Indexing means the search engine parses that response, renders it if needed, and decides whether to store it. Serving means the engine picks that stored page for a query and shows it to a user.

Rendering sits between crawling and indexing. It means running the page's JavaScript so the final content is visible. Google describes this pipeline in its Search Essentials documentation and on the "How Search works" page. It does not publish ranking weights or the exact index-selection rules.

Each stage has its own diagnostics. A noindex tag stops indexing, not crawling. A robots.txt rule stops crawling, and therefore blocks indexing too. A slow server slows crawling. A thin page gets crawled and then skipped.

Search Console status labels tell you which stage a page reached

The Page indexing report groups URLs by status. Read the label before you touch anything.

"Discovered - currently not indexed" means Google knows the URL exists but has not fetched it yet. "Crawled - currently not indexed" means the fetch happened and the page was not stored. "Excluded by noindex tag" means the page was crawled and deliberately kept out.

Google's own documentation on page indexing statuses lists these definitions. The report updates on a delay, so a fix made today may not show for days or weeks.

Status labelWhat it meansTypical next check
Discovered - currently not indexedURL known, not yet fetchedInternal links, sitemap, server response time
Crawled - currently not indexedFetched, not stored in indexContent quality, duplication, rendered HTML
Duplicate, Google chose different canonicalStored, but another URL is preferredCanonical tags, internal linking, near-duplicate pages
Excluded by noindex tagCrawled, deliberately kept outConfirm the tag is intentional
Blocked by robots.txtNot fetched at allRobots rules, then re-crawl
Soft 404Fetched, looks like an error pagePage content, HTTP status, empty states

The table is a starting map, not a diagnosis. Two pages with the same label can have different causes.

Blaming crawl budget is the most common wrong turn

Crawl budget is the number of URLs a search engine will fetch on your site in a given period. For most small sites, it is not the bottleneck.

Google's crawl budget documentation says the concept mainly matters for large sites with thousands of URLs, or sites where content changes fast. If your site has 200 pages and a clean sitemap, the crawler can fetch all of them. The problem is what it finds when it arrives.

Two more misconceptions waste time. First, "crawled" is not progress. It's a checkpoint. A page can be crawled every week and still never be indexed if the engine judges it low value or duplicate. Second, indexing cannot be forced. There is no button that makes it happen. The URL Inspection tool's "Request indexing" asks Google to look again. It does not promise a place in the index.

Start the quality-gap check with the rendered page, not the source

The source can look fine while the rendered version is thin or broken.

Use the URL Inspection tool's "Test live URL" and open the rendered HTML. Compare it with what you see in the browser. If the main content is missing or delayed, rendering is the issue.

Then run a duplication check. Search for a distinctive sentence from the page in quotation marks. If near-identical pages exist, the engine may pick one and skip the rest.

Finally, ask whether the page answers a distinct question. A page that repeats a category description or lists products without unique detail has little reason to be stored separately. This is the quality gap: not "bad content", but content that adds nothing the index does not already have.

Check rendering before you rewrite any copy

Rendering failures look like content failures from the outside. Both produce a page that gets crawled and skipped.

Open the URL Inspection report and compare the "Crawled page" screenshot with the live page. If the screenshot is blank or shows a loading state, the crawler did not see your content.

Check whether the main content depends on JavaScript that runs after load. Google can render JavaScript, but rendering uses resources and can be delayed. Server-side rendering or static HTML avoids the queue.

Also check the HTTP status. A page that returns 200 but shows an error message can be treated as a soft 404. Google's documentation explains how soft 404s are detected.

Only after those checks should you edit the copy. Editing content when the real problem is rendering wastes a cycle.

Work the quality-gap checklist in order and answer each item yes or no

A yes-or-no list is easier to hand to a team than a paragraph of advice.

  • Does the page have a unique title and meta description that match its content?
  • Does the main content answer one clear question or serve one clear task?
  • Is there a paragraph or section that appears on other pages of the site?
  • Are there internal links from relevant pages to this one, using descriptive anchor text?
  • Does the page load its main content without waiting on JavaScript?
  • Is the page included in the XML sitemap, and does the sitemap list only indexable URLs?
  • Does the page return HTTP 200 and show real content, not an empty state?
  • Is the page intentionally low value, such as a tag archive or a filter view?

If the last item is yes, leaving the page unindexed may be correct. Not every URL deserves a place in the index. A small site with 40 strong pages often ranks better than one with 400 thin pages.

Sitemap rules come from sitemaps.org, the joint protocol specification. It states that a sitemap is a hint, not a promise of indexing.

Set realistic timelines and stop refreshing the report

There is no public figure for how long reindexing takes. Google's documentation does not promise a timeline, and results vary by site size and crawl frequency.

What you can control is the signal. After a fix, request indexing once, then leave the page alone. Repeated requests do not speed up the queue.

Watch the Page indexing report over the following weeks. If the status changes from "Crawled - currently not indexed" to "Indexed", the fix worked. If it stays, revisit the quality-gap checklist.

For a new site, expect crawl activity to grow over the first weeks. That is normal discovery behaviour, not a penalty. Google has publicly said it does not apply a "sandbox" filter to new sites.

Key Facts at a Glance

  • Crawling fetches a page; indexing stores and understands it; serving returns it in results.
  • "Crawled - currently not indexed" means the fetch happened and the page was not stored.
  • Crawl budget mainly matters for large or fast-changing sites, per Google's crawl budget documentation.
  • Rendering sits between crawling and indexing; a blank rendered screenshot points to a rendering problem.
  • The Request indexing feature asks for a re-check; it does not ensure inclusion.
  • Some low-value pages should stay out of the index on purpose.

Frequently asked questions

What does "Crawled - currently not indexed" mean?

Google fetched the URL and received a response, but chose not to add the page to its searchable index. The usual causes are thin or duplicate content, a rendering problem, or a page that adds nothing the index does not already have.

How long until Google indexes a fixed page?

There is no public figure. Google does not promise a timeline, and it varies by site. Request indexing once after the fix, then watch the Page indexing report over the following weeks.

Is crawl budget why my small site is not indexed?

Usually not. Google's crawl budget documentation says the concept mainly matters for large sites or sites with fast-changing content. For a small site with a clean sitemap, the issue is normally page quality or duplication.

How do I force Google to index a page?

You cannot force it. You can request indexing in URL Inspection, which asks Google to look again. Inclusion still depends on the engine's judgement of the page.

Does "crawled not indexed" hurt rankings?

The page itself will not appear in results, so it cannot rank. It does not directly penalise other pages. A pattern of many skipped pages can be a signal that the site has too many low-value URLs.