"Crawled – Currently Not Indexed": What It Means and What We Did on a New Site

"Crawled – currently not indexed" means Googlebot fetched your page but decided not to add it to the index, at least for now. On a new site it is usually a quality, duplication or priority question, not a technical error, and it often changes on its own. Below is Google's definition, a diagnostic order that works, and the real Search Console timeline of satelo.io in its first two weeks.

Published: 2026-10-16 · 8 min read · Satelo

What "Crawled – currently not indexed" actually means

Google's Page indexing report documentation describes the status briefly: "The page was crawled by Google but not indexed." It adds that the page "may or may not be indexed in the future" and that there is no need to resubmit the URL for crawling.

Three things follow from that wording:

• Google could reach the page. Robots.txt did not block it, the server answered, and the HTML was downloaded. So this is not a crawlability bug in the usual sense.
• Google chose not to index it. The decision happened after crawling, which points to content, duplication or overall site signals.
• It is not a penalty. The status is not a manual action, and the same help page says plainly: "Don't expect every URL on your site to be indexed."

The same page also sets expectations for new sites: "It can take a week or so for Google to start crawling and indexing a new page or site." If your domain is a few days old, panic is premature.

Crawled vs. Discovered – currently not indexed

These two statuses look alike but sit at different stages of the pipeline. Mixing them up leads to the wrong fix.

All definitions are paraphrased or quoted from the Page indexing report help page.

Why Google crawls a page and still skips it

Google does not publish a per-URL reason, so treat the list below as the usual suspects to rule out, not as a confirmed diagnosis.

• Thin or near-duplicate content. Tag pages, empty category archives, auto-generated profiles and pages that say what ten other pages already say. Google's helpful content guidance asks: "Does the content provide original information, reporting, research, or analysis?"
• Canonical confusion. If a page's rel="canonical" points to a different URL, you are telling Google that other URL is the real one. Google calls the tag "a strong signal", not a command, in its duplicate URL guide, and it also recommends absolute URLs and a self-referencing canonical on the main version.
• Weak internal linking. A post reachable only through page 7 of a blog archive or a footer looks unimportant. The same canonical guide advises linking internally to the URL you want treated as canonical.
• Few external signals. A brand-new domain with no mentions anywhere gives Google little reason to prioritize it. This is the slowest factor to change and the one you control least.
• Site-wide quality signals. Hundreds of low-value URLs can make the whole site look less worth indexing. This is a common hypothesis among SEOs; Google's own docs speak about helpful content in general rather than giving a threshold.

A diagnostic order that saves time

Go from cheapest check to most expensive. Most issues on small sites show up in the first four steps.

1. Open URL Inspection for the exact URL. Check "Page indexing", the user-declared canonical and the Google-selected canonical. If they differ, you have a canonical problem, not a quality problem.
2. Run "Test live URL". Look at the rendered HTML. Is the main text actually there, or does it appear only after JavaScript that failed?
3. Look for an accidental noindex. Check the meta robots tag and the X-Robots-Tag header. Note that Google can only see noindex on a page it is allowed to crawl; a page blocked by robots.txt never shows its noindex, per Google's noindex documentation.
4. Check robots.txt for rules that block CSS, JS or whole sections. Google's robots.txt introduction explains that robots.txt controls crawling, not indexing.
5. Compare the page with its closest sibling. If two of your URLs answer the same query, merge them or make one clearly different.
6. Count internal links to the page. Is it linked from the homepage, a hub page or related articles, or only from the sitemap?
7. Check speed and server errors. Slow or flaky responses mostly cause "Discovered" rather than "Crawled", but it is worth ruling out. Our Core Web Vitals guide for small sites covers the basics.

Our own case: satelo.io in its first two weeks

Satelo launched in early October 2026, which makes it a clean example of a new domain with no history. Everything below comes from our Google Search Console account. We report what we did and what the report showed on given dates. We cannot prove which step caused which change, and we will not pretend we can.

The timeline

The 137 not-indexed URLs on October 16 broke down like this:

So on October 16 the "Crawled – currently not indexed" bucket was not among the reasons listed. Most of the "not indexed" total was our own choice, which is exactly why you should read the reasons, not the headline number.

What we did between those dates

• Submitted an XML sitemap with 96 URLs, plus a second sitemap for another section of the site.
• Fixed a wrong canonical. Our tool page /check/ declared its canonical as /check/index.php, a URL nobody should ever see. A server rewrite rule was treating "index.php" as a domain name. We fixed the rule and the canonical now points to https://satelo.io/check/.
• Linked the blog from the homepage. Before, blog posts were reachable mainly from the footer. We added a block of links from the homepage to articles and guides.
• Requested indexing manually in URL Inspection for a handful of key URLs: the homepage, the tool, the blog index and our strongest articles.
• Noindexed thin bulk pages. We generate profile pages for many sites automatically. Most of them carry little unique text, so we marked them noindex rather than ask Google to judge hundreds of near-identical pages.
• Pinged IndexNow on every deploy. IndexNow notifies participating engines such as Bing and Yandex. Google is not among the endpoints listed in the IndexNow FAQ, so this step does not explain anything in our Google numbers.

What we can and cannot conclude

We can say the index grew from 2 to 97 pages in a week while we did the steps above. We cannot say which step mattered most. Some of that growth may simply be Google getting around to a new domain, which its own help page says can take "a week or so". If you read a case study that claims "do X and your pages get indexed in 48 hours", ask what else changed at the same time.

When requesting indexing is useless

The "Request indexing" button is useful once, after a real change. It is not a lever you can pull until it works. Google's recrawl documentation says there is a quota for individual URLs and that "requesting a recrawl multiple times for the same URL won't get it crawled any faster." It also says crawling "can take anywhere from a few days to a few weeks."

Skip the request when:

• You changed nothing since the last crawl. Google already saw that version and passed on it.
• The page is a near-duplicate. Fix the duplication first.
• You have dozens of URLs. Submit or update a sitemap instead; Google recommends sitemaps for large numbers of URLs, while noting in its sitemap guide that a sitemap "is merely a hint".

Should you noindex thin pages?

Often, yes. A noindexed page is your decision, visible as such in the report. A crawled-but-skipped page is Google's decision, and you do not learn why. If a group of pages exists for users (filters, internal search results, auto-generated profiles) but has little unique text, noindex is the honest label. Keep them crawlable so Google can see the tag, and keep them out of your sitemap.

Do not noindex pages just to "push" others into the index. There is no documented mechanism for that. The benefit is clarity: your sitemap and internal links then point only at pages you actually want judged.

A checklist for a new site, in order

1. Confirm the property in Search Console and submit one clean sitemap with only indexable, canonical URLs.
2. Inspect your five most important URLs. Fix any canonical mismatch first.
3. Link those pages from the homepage and from each other.
4. Merge or rewrite pages that duplicate each other. Noindex helper pages that exist for users only.
5. Request indexing once per key URL, after the fixes, not before.
6. Earn a few real mentions on other sites. Our guide to getting your first mentions and the article on link building for new websites list realistic sources.
7. Wait a week, then read the Pages report by reason, not by total.

What to do next

If Google crawled your pages, it can reach your site. The next question is whether the rest of the web knows you exist. Satelo's free check shows whether Common Crawl and the Tranco list already see your domain and how fast it loads, built mostly from open data, so you can tell a crawler-reach problem from a "nobody links here yet" problem in one run. When you are ready for your first outside mentions, the Satelo exchange places labeled partner articles about your site on sites of a similar level; it is a public beta with a small network, so treat it as one source of mentions among several.

FAQ

Is "Crawled – currently not indexed" a penalty?

No. It is a normal status in the Page indexing report, not a manual action. Google says the page may or may not be indexed in the future and that not every URL on a site should be expected in the index.

How long does it take for a crawled page to get indexed?

Google gives no fixed time. Its help pages say a new site can take a week or so to start being indexed and that crawling can take from a few days to a few weeks. Some pages are never indexed.

Should I click "Request indexing" again and again?

No. Google says repeated recrawl requests for the same URL won't make it faster, and there is a quota. Request once after you have actually improved the page or fixed its canonical.

What is the difference between crawled and discovered – currently not indexed?

Discovered means Google knows the URL but has not fetched it yet. Crawled means Google fetched the page and decided not to index it for now. The first points to crawling priority and server capacity, the second to content and duplication.

Why is my website not indexed by Google at all?

On a brand-new domain, usually because Google has not got to it yet. Check that the site is verified in Search Console, a sitemap is submitted, robots.txt doesn't block important sections, and no page carries an accidental noindex.

How do I get my blog posts indexed faster?

Link new posts from your homepage and related articles, keep them in an up-to-date sitemap, avoid publishing near-duplicates, and request indexing once for the most important ones. Mentions on other sites help Google discover you, but nothing guarantees indexing.

Read next

"Discovered – Currently Not Indexed": Why Google Hasn't Crawled Your Pages YetWhat "Discovered – currently not indexed" means in Search Console, why it is usually about priority on small sites, and what to fix first, step by step.

How Long Does It Take a New Website to Rank? Sandbox, Data and a Real TimelineHow long a new website takes to rank on Google: what Ahrefs data shows, what Google says about the sandbox, a realistic timeline and what to do while you wait.

How to Speed Up Indexing in Yandex (and Bing) with IndexNowHow to speed up indexing in Yandex and Bing: set up IndexNow on WordPress or a static site, use Yandex page recrawl, fix sitemaps and link new pages properly.

Anchor text for SEO: types, official rules, and how to pick itAnchor text SEO without myths: anchor types, what Google and Yandex actually say, why exact-match anchors look like link schemes, and how to check your own.