Crawled, currently not indexed: what it means and what to do

Search Console’s Page indexing report shows every URL Google knows as Indexed or Not indexed, with a reason. “Crawled, currently not indexed” means Googlebot fetched the page and decided not to index it for now.

Google says no action is needed. In practice, it is Google’s judgement: the page did not earn a place. On small sites the causes cluster: thin or near-duplicate content, weak internal links, a template family seen as low value, or a brand new site that has not built trust yet.

1. 1

   Open Page indexing

   Search Console, Indexing, Page indexing. Filter Status to Not indexed. Click Crawled, currently not indexed. You get up to 1,000 example URLs.

2. 2

   Group by template

   Scan slugs. Do you see a pattern: /blog/, /docs/, /changelog/, parameters like ?ref=? Make a quick list of affected templates.

3. 3

   Inspect one URL

   Use URL Inspection on one example. Note Discovery (sitemap or referring page), Last crawl date, and the User-declared vs Google-selected canonical.

4. 4

   Test live URL

   Click Test live URL. Check HTTP response is 200, the rendered HTML has the main content, and no blocked resources hide content.

5. 5

   Check crawling and indexing allowed

   Confirm robots.txt allows crawl and the page has noindex absent. If either blocks, you will see a different status soon. Fix those first.

If the page redirects, the status will be Page with redirect. The target is what gets indexed. Fix internal links and sitemaps that still point to the old URL before you debug content.

• Thin or near-duplicate pages: template-heavy pages with little unique value, or multiple URLs covering the same query.
• Weak internal links: the page sits as an orphan or is only linked from low-traffic pages.
• A low-value family: Google has judged a whole set of pages as low return for crawl and index, for example faceted or generated variants.
• A new site: few signals of quality or demand yet, so Google holds most pages back.

Use the Performance report and the Links report to tell which one fits. You can do this in under thirty minutes for a small site.

1. 1

   Filter to the problem folder

   Open Performance, Pages, add a Page filter like starts with https://yourproduct.com/docs/. Note impressions for indexed pages in the same folder.

2. 2

   Look for cannibalisation

   Switch to Queries. Do indexed pages already rank for the same query as the not indexed pages? Example: two guides both target “import CSV to app”.

3. 3

   Check demand vs supply

   If no page in the folder has any impressions, demand may be weak. If one or two pages get impressions and others do not, the rest may be thin or duplicative.

4. 4

   Compare titles and intents

   Open the affected URLs and look at H1, title, first screen content. Are two pages both about “Pricing for startups”, one a variant of the other?

A thin or duplicate cluster often shows zero impressions across several lookalike URLs, while one canonical-like page gets any visibility. Fix content first, not crawl settings. A family judged low value often shows zero impressions across a whole template like /tags/ or /search/ with many URLs and no clicks for weeks.

1. 1

   Open Links, Internal links

   Find the problem URL. Check the internal links count. If it is zero or in single digits on a small site, that is weak.

2. 2

   Find linking pages

   Click the URL to see the list of internal pages that link to it. Are they low-value pages like archives or footers only?

3. 3

   Check the path from the homepage

   Click through your site. Can you reach the page from the homepage in two to three clicks? If not, it is weakly linked.

Orphan pages rarely get indexed. A pricing add-on at /pricing/add-ons with no links from /pricing or the navbar will struggle, even with a sitemap entry. Fix linking before you rewrite content for these cases.

• Merge overlapping pages. Pick the stronger URL. 301 redirect the weaker ones. Example: merge /blog/how-to-import and /blog/import-csv-to-app into one guide.
• Declare canonicals on legitimate variants. Use rel=canonical from /blog/how-to-import?ref=twitter to /blog/how-to-import.
• Add substance above the fold. Replace boilerplate with specific detail, examples, data, or steps. Aim for one clear query per page.
• Cut tag, author, date and paginated archive pages from indexing. Keep them for users but add noindex if they create near-duplicates.
• Avoid programmatic series that repeat a template with token swaps, like “Best {tool} alternatives” for 200 tools, unless each has real research.

A fixed page reads like a single best answer to one search. Example: /guides/getting-started covers setup end to end, and no other page repeats those steps. One canonical URL. No thin variants compete with it.

1. 1

   Link from high-traffic pages

   Add a descriptive anchor on /pricing, /, and your top /blog/ posts. Example: link “CSV import guide” to /blog/import-csv-to-app.

2. 2

   Add contextual links

   Within related guides, add two to three in-body links that point to the page with relevant anchor text, not “click here”.

3. 3

   Update nav and footer

   If the page is core, add it to the navbar or footer. Keep the label clear, not clever.

4. 4

   Fix orphaning in templates

   Ensure category, product, or feature pages link crosswise. Example: /features/import links to /guides/import and vice versa.

5. 5

   Resubmit the sitemap

   If you change many links or URLs, update your XML sitemap and resubmit in Search Console’s Sitemaps report.

After linking, use URL Inspection’s Test live URL and Request indexing for two or three key pages. That prompts a fresh crawl. It does not guarantee indexing and has a small daily quota per property. Expect a delay before the Page indexing report updates.

• Prune or consolidate. If you have /tags/ with one post per tag, remove thin tag pages from sitemaps, and add noindex to those templates.
• Stop generating trivial variants. Facets like /shirts?color=red&sort=1 for every combination rarely earn indexation. Keep them crawlable only if they help users, and noindex them.
• Create a head page for the topic. Example: replace 20 “How to export for {tool}” stubs with one /guides/export that covers the top tools well, then add subpages only where depth is needed.
• Show unique value on the template. Add data, comparisons, or FAQs that only you can provide. Avoid empty state pages that say “No items yet”.

A fixed family looks smaller but stronger. The remaining pages each target distinct queries and get internal links from hubs like /features/ and /use-cases/. The sitemap lists only these pages, not every filter or tag.

New domains often see Crawled, currently not indexed across many URLs. Google holds back until it sees quality, demand, and a coherent site structure. Do not panic. Build signals in a focused way.

1. 1

   Publish fewer, better pages

   Start with the core: /, /pricing, /features/, and one or two strong guides that answer real searches. Avoid a blog flood of short posts.

2. 2

   Get a handful of real links

   List your site on profiles you control and relevant communities. Link from your GitHub, docs, or a partner’s site where it helps users.

3. 3

   Strengthen internal linking early

   Build a clear hub and spoke. From /features/ link to each feature page and back. From the homepage link to the strongest guide.

4. 4

   Give it time

   Wait one to two weeks after fixes before judging. Use Validate fix in Page indexing to start a re-check. It can take about two weeks.

• Use it after a substantial change. You merged pages, added 500 words of specific, unique help, or fixed internal links and canonicals.
• Use it for a small batch. Two to five key pages, not hundreds. The quota per property is small and the crawl is not guaranteed.
• Skip it for large templates. If 200 /tags/ pages are thin, fix the template and linking. Let the normal crawl pick it up.
• Do not spam it daily. It will not change a quality judgement. Spend the time improving the page or linking to it.

A good use: you overhaul /guides/getting-started, add a video and real steps, link it from /, then Request indexing to force a fresh look. A poor use: you change a comma and hit the button every morning.

1. 1

   Track the index status weekly

   In Page indexing, export the example URLs list before and after fixes. Watch the count of Crawled, currently not indexed go down across the target folders.

2. 2

   Watch impressions on the fixed pages

   In Performance, filter to the fixed URLs. Look for first impressions and queries. Even a handful is a good sign before clicks arrive.

3. 3

   Validate fix where offered

   In the Page indexing reason page, click Validate fix. That triggers a re-check and progress updates. Expect about two weeks for the run.

4. 4

   Revisit the content if nothing moves

   If a page stays not indexed after a month and has no impressions, make it better or merge it. Do not keep near-duplicates alive.

Use URL Inspection on stubborn URLs. Compare the User-declared canonical and the Google-selected canonical. If Google prefers a different URL, align titles, internal links, and canonicals so the right page wins.