Crawled, currently not indexed: why it happens
·4 min read
"Crawled, currently not indexed" is a Search Console status for pages Googlebot fetched and then chose to leave out of the index. Google read the page and decided it was not worth storing yet, usually because the content is thin, duplicates another URL, looks like an empty or error page, or renders without its main content. Nothing is technically blocking it. Fix the page itself, or merge it into a stronger one, and only then ask Google to look again.
What does crawled, currently not indexed mean?
It means Google downloaded the page, evaluated it and passed for now. The status sits under Indexing > Pages in Search Console. Google's help says the page "may or may not be indexed in the future" and that there is "no need to resubmit this URL for crawling."
That last part matters. Resubmitting an unchanged page asks Google for the same verdict twice. When Google has not fetched the URL at all, that is a crawl problem, covered in discovered, currently not indexed.
If a whole site is missing from Google rather than a set of pages, start with why your website is not showing up on Google.
Why a page gets crawled but not indexed
Google judged the page as adding little to its index. Four causes cover most cases.
| Cause | What it looks like | What to change |
|---|---|---|
| Thin content | Tag archives with one post, empty category pages, 80-word product pages | Add real content or noindex and drop from the sitemap |
| Duplicate content | Near-identical location pages, printer versions, the same product under three paths | Merge into one URL and redirect or canonicalize the rest |
| Soft 404 signals | "No results found", "out of stock" shells, expired listings returning 200 | Return 404 or 410, or put real content on the page |
| Rendering problems | Body text loads by JavaScript and the HTML Google stores is a skeleton | Server-render the main content |
A site that generates a page for every city, tag or filter combination gives Google thousands of URLs that say the same thing, and Google keeps a few.
Soft 404s have their own row, but borderline pages often land here. A search page with no results, or a listing marked "sold", reads like an error page with a 200 status.
Rendering problems hide well because the page looks fine in your browser. Use URL Inspection, run a live test and open View tested page to see the HTML and screenshot Google got. If the copy is missing there, read our guide to JavaScript SEO and compare your rendered source and raw HTML.
How to fix crawled currently not indexed
Group the URLs first, then work from the cheapest explanation to the most expensive.
- Export the example URLs from the status and sort them by path.
- Drop patterns you never wanted indexed, such as internal search, tag pages and parameters.
- Inspect two or three URLs per remaining pattern and check the tested page for missing content.
- Check for conflicting signals, such as a canonical pointing elsewhere.
- Compare each page with the URL on your site that covers the same topic best.
- Improve, merge or remove what is left.
Step 5 decides most cases. If two pages target the same query, Google indexes one. Fold the useful parts of the weaker page into the stronger one and 301 the weaker URL. A page with no rival on your site usually needs content a searcher cannot get from the snippet, such as specs, prices or original photos.
When to ignore crawled, currently not indexed
Leave it alone when the URLs are pages you never needed in search. Paginated archives, feed URLs, filter combinations and thank-you pages often sit here, and that costs you nothing.
Give new pages time too. A post published last week can move to indexed without any change. I'd wait two to four weeks before touching a fresh, solid article.
Act when the URLs are product pages, service pages or your best articles. A rising count of those is a content problem worth fixing now.
How to request indexing after you improve a page
Request indexing only after the page has materially changed. Open URL Inspection, run a live test to confirm the new version loads and is indexable, then click Request indexing.
Google's recrawl docs set expectations. There is a quota for individual URL submissions, asking again for the same URL does not speed anything up, and a request does not guarantee indexing "instantly or even at all." Crawling can take a few days to a few weeks. For many changed URLs, update their lastmod in your sitemap instead of submitting each one.
If you fixed a whole pattern, click Validate fix on the status instead. Google's help says validation typically takes up to about two weeks and sometimes much longer.
Check if a page can be indexed
Before you rewrite a page, rule out signals that keep it out regardless of quality. Our Indexing & Canonical Checker reads one URL and reports its HTTP status and any redirect loop, the robots.txt rule that applies to Googlebot, a noindex in meta robots or the X-Robots-Tag header, and the canonical tag. It fetches the canonical target and flags one that errors, redirects, carries noindex or chains to another URL. Each finding names the tag or header to change, and a run costs 8 credits.
A canonical pointing at another page is the result to catch, since Google may then treat your page as the duplicate. A clean report means the problem is the content.
The checker reads the HTML your server returns without running JavaScript, so it will not show content missing after rendering. It cannot confirm whether Google has indexed a URL or judge content quality.