"Crawled - currently not indexed" means Googlebot fetched your page and then decided not to add it to Google's index. It is not an error: nothing blocked the page. Google looked at it and judged it not worth indexing yet, usually because it's thin, too similar to other pages, or treated as unimportant within your site.
To fix it, change that judgment. Group the affected URLs to find the pattern, rule out rendering and canonical problems, then make the pages genuinely better or merge them, link to them from your strongest pages, and request indexing once. Clicking "Request indexing" without changing the page rarely sticks.
Key takeaways
- Google's own definition: the page was crawled but not indexed, and there is no need to resubmit it. Resubmitting an unchanged page doesn't fix anything.
- The usual causes are quality and duplication (thin, templated or near-identical pages), not technical blocks.
- Fix patterns, not URLs. Export the list from Indexing → Pages, group it by folder or template, and fix the template.
- "Discovered - currently not indexed" is a different problem: Google hasn't crawled the page yet, usually because of crawl capacity or weak internal links.
- After fixing, click Validate fix. Google says validation typically takes up to about two weeks, sometimes longer.
What "Crawled - currently not indexed" means
Google's Page indexing report documentation describes it as a page that "was crawled by Google but not indexed", and adds that there is no need to resubmit the URL. Indexing is a separate decision from crawling: Google can fetch a page perfectly and still decide the index doesn't need it.
It helps to know the statuses it gets confused with:
| Status in Search Console | What happened | What it usually means |
|---|---|---|
| Crawled - currently not indexed | Google fetched the page and chose not to index it | Quality, duplication or low importance |
| Discovered - currently not indexed | Google knows the URL but hasn't fetched it | Crawl capacity, weak internal links, too many URLs |
| Duplicate, Google chose different canonical than user | Google indexed another URL instead | Your canonical tag lost to other signals |
| Duplicate without user-selected canonical | Near-copies with no canonical | Add a canonical or consolidate |
| Excluded by 'noindex' tag | You told Google not to index it | Remove the tag if the page should rank |
| Blocked by robots.txt | Google wasn't allowed to fetch it | Change robots.txt if the page should rank |
| Soft 404 | The page returned 200 but looked empty or missing | Return a real 404, or add real content |
First, decide whether it's a problem at all
Every site has URLs in this bucket that should stay there. Leave these alone:
- RSS feeds,
?replytocom=comment URLs, print versions and other technical variants. - Paginated archives (
/page/7/), tag pages and thin category pages you never meant to rank. - Old URLs that now redirect or 404 and haven't been recrawled yet.
- URLs with tracking or sort parameters that duplicate a canonical page.
It becomes a problem when the list includes pages you want traffic from: blog posts, product pages, service pages, location pages, docs. If a whole template is in there (say, half your blog), that's a site-level quality signal worth fixing quickly.
How to fix it: the six-step checklist
Work through the steps in order. Tick them off as you go; your progress is saved in your browser.
Interactive checklist
Fix "Crawled - currently not indexed"
0/17
1. Export and group the URLs
0/32. Rule out technical causes
0/43. Make the page worth indexing
0/44. Show Google the page matters
0/35. Ask Google to look again
0/16. Validate and monitor
0/2Your progress is saved in this browser, so you can come back to it later.
Step 1: Export the list and look for the pattern
The export from Indexing → Pages includes a "Last crawled" date for each URL. Sort by folder and you'll usually see one of three patterns:
- One template dominates (all tag pages, all location pages, all integration pages). The template produces pages Google sees as thin or interchangeable.
- Recent posts are stuck. New content on a site Google doesn't yet trust much often sits here for a while before being indexed.
- Random older posts. Pages that were indexed before and dropped out usually lost to a better page, often one of your own.
Step 2: Rule out the technical causes
Technical causes are less common for this status (a blocked page would show a different reason), but they're quick to rule out. In URL Inspection, run a live test and open the rendered HTML. If your main text isn't there (common with JavaScript frameworks, tabs and "load more" buttons), Google is judging an almost empty page. Our technical SEO for SaaS guide covers server-side rendering for JavaScript sites.
Then compare canonicals. If the Google-selected canonical is a different URL, Google sees your page as a duplicate of that one. Either make the pages clearly different or consolidate them.
Step 3: Make the page worth a place in the index
This is the step that fixes most cases. Google doesn't index everything it crawls; it indexes pages that add something. Open the top results for the page's main query and be honest about the comparison. Pages that typically end up here:
- Thin pages: 300 words that restate what every other result says.
- Near-duplicates: five posts on slight variations of one topic, or location pages that differ only by city name. That is also keyword cannibalization.
- Templated stubs: programmatic pages where only one variable changes. Our programmatic SEO guide shows how to give each page real, unique data.
- Off-topic pages: content far from what the rest of the site is about, which Google has little reason to trust. Building topical authority around a few themes helps here.
The fix is substance: original examples, numbers, screenshots, step-by-step instructions, a clear answer in the first paragraph, and the details competing pages skip. If two of your pages compete, merge them into one and 301-redirect the weaker URL. If a page has no search purpose, noindex it or delete it; fewer weak pages makes the rest of the site look stronger.
Step 4: Link to the page from pages Google already values
Internal links are how Google judges importance within your site. A post linked only from a paginated archive looks unimportant. Add contextual links from two to five related pages that are indexed and get traffic, and make sure a hub or category page links to it. Our guide on finding internal links to a page shows how to check what links there today.
If you publish a lot of content, this is the step that slips. Outrank, for example, adds internal links from each new article to related posts on your site, but older pages still need links pointing to the new ones, so review your hub pages every month.
Steps 5 and 6: Request indexing, then validate
Once the improved page is live, run URL Inspection → Request indexing once. There's a daily quota and repeated requests for the same unchanged page don't help. Google's Indexing API is not a shortcut either: it's only supported for job postings and livestream video pages.
Then click Validate fix on the issue in the Pages report. Google says validation typically takes up to about two weeks and can take longer. Check the export again after four to six weeks and compare counts per folder.
"Discovered - currently not indexed" is a different fix
"Discovered - currently not indexed" means Google found the URL (through a link or sitemap) but hasn't crawled it yet. Google's documentation says this typically happens when crawling the URL was expected to overload the site, so the crawl was rescheduled. The fixes are about crawling, not content:
- Check Settings → Crawl stats for slow response times or server errors; a slow server gets crawled less.
- Cut URL waste: faceted filters, parameters and endless calendar pages that soak up crawl attention.
- Link to the important pages from strong, indexed pages, and keep them in the sitemap.
On large sites, also read Google's guidance on crawl budget, which is aimed at sites with roughly a million pages or more, or tens of thousands of pages that change daily.
"Indexed but not ranking" and other related statuses
If a page is indexed but not ranking, indexing isn't the issue. Check the queries it gets in Performance → Pages → [the page] → Queries. No impressions at all usually means weak relevance or a stronger page on your own site for the same query; impressions at position 30 to 60 mean it's in the running but outclassed. Both are content and links problems; start with a website audit.
"Non-indexable pages" is crawler language (Screaming Frog, Ahrefs, Semrush) for URLs that can't be indexed by design: they return a non-200 code, carry a noindex tag, canonicalize to another URL, or are blocked by robots.txt. Filter your crawl by "Non-Indexable" and check the reason column; anything you want ranked shouldn't be there.
"Cannot be crawled" or "Blocked due to access forbidden (403)" means a server, firewall or CDN rule is refusing Googlebot. Check your security plugin or CDN bot settings before anything else. The technical SEO audit checklist walks through crawl and server checks.
Why Ahrefs shows "no crawled pages"
If Ahrefs Site Audit or Site Explorer reports no crawled pages for your site, it's an Ahrefs crawling problem, not a Google one, though the causes overlap. Ahrefs' help center lists the usual reasons:
- Wrong domain version. You started the project on
www.but the site runs on the bare domain (or the reverse), and the crawler stops at the redirect. Start the audit on the exact version that loads in your browser. - JavaScript-built site. Turn on "Execute JavaScript" in the crawl settings.
- AhrefsBot or AhrefsSiteAudit blocked in robots.txt, or by a firewall, CDN or security plugin (Cloudflare, Sucuri, ModSecurity) returning 403 or 406 errors.
- A brand-new domain. Ahrefs suggests giving its crawler one to two weeks to find a new site.
The same blocks can affect Googlebot if your firewall is aggressive, so after fixing Ahrefs, confirm in Search Console's URL Inspection that Google gets a 200 too.
FAQ
What does "Crawled - currently not indexed" mean?
It means Googlebot fetched the page but Google decided not to add it to the index for now. Nothing technical blocked it. Google usually leaves pages here when they're thin, very similar to other pages, or appear unimportant within the site. The page may be indexed later, especially if it improves or gains internal links.
How do I fix "Crawled - currently not indexed"?
Group the affected URLs to find the pattern, confirm the content appears in the rendered HTML and the canonical is correct, then improve or merge the pages so each adds something unique. Link to them from strong, indexed pages, request indexing once, and click Validate fix in Search Console.
How long does it take for Google to index a page after fixing it?
There's no fixed time. Pages can be indexed within days of a substantial improvement, or take several weeks. Google says validation in the Page indexing report typically takes up to about two weeks but can take longer. If a page stays excluded after six to eight weeks, the change probably wasn't substantial enough.
Is "Crawled - currently not indexed" bad for SEO?
Not on its own. Every site has URLs here that shouldn't be indexed, like feeds and parameter variants. It matters when it includes pages you want traffic from, and especially when a large share of a template, such as your blog, is excluded, because that suggests Google sees that content as low value.
What is the difference between crawled and discovered not indexed?
"Crawled - currently not indexed" means Google fetched the page and chose not to index it, which is mostly a content or duplication issue. "Discovered - currently not indexed" means Google knows the URL but hasn't fetched it yet, which is mostly about crawl capacity, server speed or weak internal links.
