Crawled, Currently Not Indexed: How to Fix It
Crawled, currently not indexed means Googlebot fetched your page without any trouble and then decided not to add it to the index, at least for now. Nothing technical blocked it: robots.txt allowed the crawl, there was no noindex, and the server answered. The decision was about the page itself and how it fits into your site. In most cases the page is thin, too similar to another page, weakly linked, or shows Google something different from what visitors see. This guide explains how to tell which of those applies, how to check what Google actually rendered, how to improve or merge the pages worth keeping, and how to prune the ones that are not, so that your stronger pages are indexed and stay indexed.
What the status means
In the Page indexing report, Search Console shows this reason as Crawled - currently not indexed. Google's own description is short: the page was crawled by Google but not indexed, it may or may not be indexed in the future, and there is no need to resubmit the URL for crawling.
Read that carefully and three things follow:
- The crawl worked. Robots.txt,
noindex, login walls and server errors each have their own statuses. If one of those were the problem, the page would be listed under a different reason. - The decision is not final. Google revisits pages, and a page can move in or out of the index as its content, links and the rest of your site change.
- Resubmitting alone does nothing. Google has already seen the page. Asking again without changing anything gives it no new reason to decide differently.
This is a quality and priority decision. Google does not index every page it can reach. It indexes the pages it expects to be useful in search results, and a site with many weak or repetitive pages will see more of them held back. Pages can also move here after being indexed, which often shows up as a slow fall in indexed counts after a site adds a large batch of similar pages.
/feed/, comment reply links such as ?replytocom=, image attachment pages and old paginated archives are not meant to rank, so ignore them while you work on the pages that matter.The usual causes
Export the list and sort it by template or folder. You will usually find that most entries share one or two page types, which points straight at the cause.
| Cause | Typical pages | What to check |
|---|---|---|
| Thin content | Tag pages, empty categories, short posts, stub product pages | Word count and whether the page answers anything on its own |
| Near-duplicates | Location pages with the town name swapped, product variants, copied manufacturer text | Search for a distinctive sentence in quotes |
| Weak internal links | Pages reachable only from the sitemap or deep in pagination | Click depth and number of internal links in |
| Rendering gap | Pages whose main content loads with JavaScript | The rendered HTML in URL Inspection |
| Wrong content shown to Googlebot | Pages behind a cookie wall, geo redirect or soft error message | The screenshot in a live test |
| Overlap with a stronger page | Two posts targeting the same search | Which page ranks, and whether they cover the same ground |
| Young site or new page | Fresh posts on a site with few links | Whether the page is days or months old |
Thin and duplicate content are by far the most common. The thin content guide and the duplicate content guide go deeper on each. If two of your own pages chase the same search, see the cannibalisation guide.
How to diagnose a listed page
See what Google rendered
Paste the URL into URL Inspection and click Test live URL, then View tested page. Look at the HTML tab and the screenshot. If your main text, product details or article body are missing from the rendered HTML, Google is judging an empty shell. The same applies if the screenshot shows a cookie consent wall covering the page, a country selector, or a message such as no products found.
You can compare the raw HTML your server sends with what visitors see:
curl -s -A "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" \
https://example.com/services/boiler-repair/ | grep -c '<p>'A count close to zero on a page that has many paragraphs in the browser means the content arrives through JavaScript. Google can render JavaScript, but it adds delay and risk. The JavaScript-only content guide explains how to move key content into the server HTML.
Confirm Google really crawled it
Do not guess from Search Console dates alone. Check your server access logs for Googlebot requests to the URL:
grep "Googlebot" /var/log/nginx/access.log | grep "/services/boiler-repair/" | tail -5On Plesk the logs for a domain are under /var/www/vhosts/example.com/logs/. Anyone can fake the Googlebot user agent, so confirm a hit with a reverse DNS lookup on the IP address. A genuine request resolves to a host ending in googlebot.com or google.com:
host 66.249.66.1
# 1.66.249.66.in-addr.arpa domain name pointer crawl-66-249-66-1.googlebot.com.Check for duplicates
Copy a distinctive sentence from the page, not a generic one, and search Google for it inside quotation marks. If another page on your site or another site shows the same text, that copy is competing with yours. Our site audit also flags pages with near-identical titles and body text across your site.
Measure internal links
Run a crawl and note how many internal links point to each listed page and how many clicks it sits from the home page. Pages found only through the sitemap, with no links from other pages, are a strong signal of low importance. The orphan pages guide shows how to find and link them.
What makes a page worth indexing
Google's guidance on helpful content is the best yardstick. A page earns its place when it gives a searcher something they cannot get from your other pages or from the pages already ranking. In practice that means:
- A clear purpose. One topic, one main question, a title and heading that say what it is.
- Original substance. Your own explanation, prices, steps, measurements, examples, photographs or data, not a reworded version of what is already out there.
- Enough depth to finish the job. There is no minimum word count, but a page that leaves the reader needing to search again is unlikely to be chosen.
- Evidence of experience. Who wrote it, why they know, and specific details that only someone who has done the work would include.
- A place in the site. Links in from related pages, and links out to the next useful step.
For local service businesses, the classic trap is dozens of town pages with the same text. Each one either needs real local detail, or the set should be merged into one service area page. The service area guide covers how to structure that.
Platform notes
WordPress
Tag archives, author archives for single-author blogs, date archives and media attachment pages are the usual residents. In Yoast SEO or Rank Math you can set these archive types to noindex, and Yoast can redirect attachment URLs to the file. Thin category pages can be improved by adding an introduction that explains what the category covers.
Shopify
Collections with one or two products, products with only the manufacturer's description, and blog tag pages such as /blogs/news/tagged/ often land here. Write your own product descriptions and give collections a short introduction above the grid.
JavaScript frameworks
In React, Vue or Angular apps that render in the browser, the first HTML can be nearly empty. Use server-side rendering or static generation for pages you want indexed. In Next.js, make sure the content is fetched on the server, not in a useEffect hook, so it is in the HTML response.
A worked example
A heating engineer's site has 300 location pages, one per town, each with the same 400 words and the town name swapped. Search Console lists 262 of them as crawled, currently not indexed. A crawl shows each page has only one internal link, from a long list in the footer.
The owner picks the 20 towns where most jobs come from and rewrites those pages with real detail: recent jobs in the area, typical call-out times, local water hardness and what it does to boilers, and photographs from those jobs. The other 280 pages are merged into one service area page listing every town, and each old URL gets a 301 redirect to it. The 20 rewritten pages are linked from the service area page and from relevant blog posts.
After requesting indexing for the 20 pages once, 17 are indexed within four weeks. The service area page is indexed too, and starts appearing for broader searches that none of the thin pages ever reached.
The fix, step by step
Step 1
Export and group the affected URLs
In Search Console open Indexing, then Pages, click Crawled - currently not indexed and export the list. Group the URLs by template or folder, such as tags, products, locations or posts. Set aside feeds, attachment pages and comment reply URLs, which need no action. Note which group is largest, because fixing one template usually helps hundreds of pages at once. Keep the export so you can compare counts later and confirm the trend is falling.
Step 2
Check what Google rendered
Pick two or three URLs from the largest group and run a live test in URL Inspection. Open View tested page and read the HTML tab and the screenshot. Confirm the main content is present in the rendered HTML, and that no cookie wall, country selector or error message covers the page. If content is missing, move it into the server HTML before anything else, then run the live test again to confirm it now appears.
Step 3
Confirm the crawl in your server logs
Search your access logs for Googlebot requests to a sample of listed URLs, for example with grep Googlebot access.log | grep /page/. Note the date and the status code returned. Run host on the requesting IP address and check it resolves to a googlebot.com or google.com host. A genuine 200 response confirms Google saw the page and that the decision was about its content and links, not a failed crawl.
Step 4
Look for duplicates and overlap
Copy a distinctive sentence from each sample page and search for it in quotation marks. Note any other page, on your site or elsewhere, carrying the same text. Run a crawl and list pages with near-identical titles or body text. Where two of your pages cover the same topic, decide which one is stronger. Merge the weaker page into it and add a 301 redirect, then confirm the redirect with curl -I.
Step 5
Improve the pages worth keeping
For each page you want indexed, add substance that no other page offers: your own explanation, prices, steps, examples, photographs, local detail or data, and answers to the questions people ask about the topic. Rewrite copied manufacturer or template text in your own words. Make the title and main heading state clearly what the page covers. Read it as a stranger would and confirm it answers the question fully without sending them elsewhere.
Step 6
Strengthen internal links
Link to each improved page from at least two relevant pages that are already indexed, using anchor text that describes the destination. Add hub or category pages that link to related content, and keep important pages within three clicks of the home page. Crawl the site afterwards and confirm each improved page has several internal links pointing to it and is no longer reachable only from the sitemap or a footer list.
Step 7
Prune or noindex low-value URLs
For pages you must keep for visitors but that will never deserve a place in search, such as thin tag archives or filtered views, add noindex or consolidate them into stronger pages. Remove those URLs from the XML sitemap. Delete pages with no value to anyone and let them return 404 or 410, or redirect them to a close match. Confirm the sitemap now lists only pages you want indexed.
Step 8
Request indexing once and monitor
After improving a page, run a live test in URL Inspection to confirm Google sees the new version, then click Request indexing once. Do not repeat the request on the same unchanged URL. Check the Page indexing report weekly for the next four to eight weeks and compare counts against your export. Improved pages should move to indexed gradually; if a group does not, review it again for duplication or weak links.
Edge cases worth knowing
- New pages on young sites can sit here for a few weeks and then be indexed without any change. Give a fresh page time before rewriting it.
- Pages that were indexed and then dropped usually point to a site-wide quality issue or a recent batch of weak pages, not a problem with that one URL.
- Non-HTML files such as feeds, JSON endpoints and some PDFs appear here routinely and need no action.
- Site-wide changes such as a migration or a core update can move many pages here at once. Check the coverage drops guide if the count jumps suddenly.
- Canonical choice. If Google picks another page as the canonical, the URL moves to a duplicate status instead. See alternate page with proper canonical tag.
Keeping it fixed
Check the Page indexing report monthly and watch the trend, not single URLs. A stable or falling count is healthy. A rising count usually means a template is producing pages faster than they earn their place.
Before publishing any new page type, ask whether each page will carry something unique. Build internal links into the publishing routine so every new page is linked from at least two relevant indexed pages on day one. Review old content once a year and merge, improve or remove what no longer pulls its weight. A smaller site of strong pages is crawled more often and indexed more fully than a large site padded with weak ones.
1. What does crawled, currently not indexed mean?
It means Google fetched the page successfully but chose not to add it to the index for now. Nothing technical blocked the crawl, so robots.txt, noindex and server errors are not the cause; those have their own statuses in the Page indexing report. The decision is about the page itself and its place in your site, usually because it is thin, too similar to another page, or weakly linked. Google says the page may or may not be indexed in the future, and resubmitting it unchanged will not help.
2. How long does it take to fix crawled, currently not indexed?
It usually takes two to eight weeks after you improve a page for Google to recrawl it and reconsider. Requesting indexing once through URL Inspection can bring the recrawl forward for important pages. Pages with strong internal links tend to be picked up sooner than pages buried deep in the site. A fresh post on a young site may move into the index within a few weeks with no changes at all, so give new pages time before you start rewriting them.
3. Should I keep clicking request indexing?
No, requesting indexing repeatedly for an unchanged page does not help. Google has already crawled the page and made its decision, so a new request gives it no reason to decide differently. There is also a daily limit on requests, which is better spent on pages you have genuinely improved. Make a real change first, such as adding original content, merging a duplicate or adding internal links, run a live test to confirm Google sees the change, and then request indexing once.
4. Is crawled, currently not indexed a penalty?
No, it is not a penalty. A manual action appears in the Manual actions report in Search Console, not in Page indexing. Crawled, currently not indexed is Google's normal judgement that a page is not worth indexing at the moment compared with other pages. That said, a very large share of a site sitting here can point to a site-wide quality problem, such as many near-duplicate pages, which can affect how Google treats the whole site. Improving or pruning the weak pages addresses both.
5. Does word count affect whether a page gets indexed?
Not directly, because Google has no minimum word count for indexing. What matters is whether the page offers something useful that other pages do not. A short page with a precise answer, a price list or a unique tool can be indexed easily, while a long page that repeats what is everywhere else may not be. Thin pages tend to be short, which is why length and indexing often appear linked, but adding filler words to reach a target does not fix the underlying problem.
6. Why are my new blog posts crawled but not indexed?
New posts often sit here because the site is young, has few links, or the posts look similar to content already indexed. Check that each post has a clear, specific topic you have not covered before, and that it adds your own experience or data. Link to it from your home page or blog index and from older related posts. Many new posts on established sites are indexed within days, while on brand new sites a wait of several weeks is common.
7. Should I delete pages that are crawled but not indexed?
Only delete them if they have no value to visitors either. Pages that serve users but will never rank, such as some tag archives, can stay live with noindex. Pages that overlap with stronger pages are better merged, with a 301 redirect to the page that remains, so any links they earned are kept. Pages with no purpose at all can be removed and allowed to return 404 or 410. Pruning weak pages helps Google focus on your stronger content.
Our site audit crawls your site and flags thin pages, near-duplicate titles and text, and pages with few or no internal links, so you can see which pages are likely to be held back.
Open Site Audit Fixes →