How to Fix Crawled Currently Not Indexed Pages in Google
You open the Pages report in Google Search Console and find 37 URLs sitting under "Crawled, currently not indexed." Google visited them, read them, and decided not to put them in search results.

You open the Pages report in Google Search Console and find 37 URLs sitting under "Crawled, currently not indexed." Google visited them, read them, and decided not to put them in search results. There is no error message, no broken link to fix, and the Request Indexing button seems to do nothing useful. On a site with 60 pages, that is more than half of your work invisible.
This status confuses beginners because it looks technical, so they go hunting for a technical fix. Usually the cause is closer to an editorial verdict. Google has a limited appetite for any given site, and on a small or young site it saves that appetite for pages it thinks are worth showing. The good news is that you can change its mind, and the process is mostly about deciding which pages deserve to exist.
What the status actually tells you
Search Console separates two situations that look similar. "Discovered, currently not indexed" means Google knows the URL exists but has not fetched it yet. That one is often about crawl scheduling or a slow server. "Crawled, currently not indexed" is different: the page was downloaded and rendered, and Google chose to leave it out.
Google rarely spells out why. From the sites I have worked on, the reasons fall into a handful of buckets:
- The page is thin, meaning it has little text or says what another page already says.
- The page is very similar to another URL on the same site, such as a tag archive that lists the same three posts as a category archive.
- Nothing links to it except the sitemap, so Google sees no sign that you consider it important.
- The site is new and has few external signals, so Google is cautious with everything.
- The page is fine, and Google simply has not got round to reconsidering it. Some URLs move out of this bucket on their own within four to eight weeks.
Before you change anything, click into the report and export the list. Then sort the URLs by type. In my experience a surprising number turn out to be pagination pages, tag archives, attachment pages from WordPress, or URLs with tracking parameters. Those are not problems to solve. They are pages you probably did not want indexed in the first place.
Why pressing Request Indexing is the wrong first move
The common advice on forums is to inspect each URL and hit Request Indexing, then wait. I think that is close to useless for this particular status, and it wastes your daily quota of roughly ten to twelve requests.
Requesting indexing asks Google to crawl the page again. But Google already crawled it. It saw the content and made a call. Sending the same page back for a second look, unchanged, is like resubmitting a job application without editing it. Sometimes it works, because the decision was borderline. Mostly the URL slides back into the same report a week later.
Request Indexing is worth using after you have changed something meaningful on the page. Then you are asking for a fresh judgment on new evidence, which is the only situation where the button earns its place.
A fix order that works on small sites
Work through the exported list in this order. Each step reduces the pile, and the later steps only make sense once the earlier ones are done.
- Remove the pages you never wanted indexed. Tag archives with one or two posts, attachment pages, search result pages, and old test pages should get a
noindexmeta tag or be removed entirely. If a URL has a better equivalent, redirect it. Our guide to setting up 301 redirects covers how to do that without losing links. - Merge near duplicates. If you have three short posts on the same topic, for example "choosing a domain," "picking a domain name," and "domain tips," combine them into one longer article and redirect the other two. This step alone often clears a third of the list.
- Check the sitemap matches reality. Your XML sitemap should list only pages you want indexed. If it still includes the tag archives you just noindexed, you are sending Google mixed signals. The steps in creating an XML sitemap for a small website show what belongs in it.
- Link to the remaining pages from pages that already rank. Find your three or four best performing posts in the Performance report and add a natural, contextual link from each to a page stuck in the report. A link from inside body text carries far more weight than a footer link. The approach in planning internal links on a small website fits this step well.
- Improve the pages that are genuinely weak. Add the answer the visitor came for, a worked example, a screenshot, a price, a number. A 300 word page that restates its title three times will stay out of the index no matter how many links point to it.
- Only now, request indexing for the pages you changed, a few per day, and note the date in a spreadsheet.
When the problem is the whole site, not single pages
Sometimes the report is not a list of a few weak URLs. It is nearly everything. On a three month old site with 40 posts and 30 of them excluded, individual page fixes help less than you would hope, because Google is judging the site overall.
In that case, the most effective thing I have seen is cutting. One client had 120 short articles written quickly at launch. We deleted or merged about 50, kept 70, and spent two weeks making those 70 better. Within roughly six weeks, indexed pages went from 31 to 64. Fewer pages, more of them in search. It felt backwards at the time.
Speed matters a little here too. If your server takes two or three seconds to respond, Google crawls less, and pages get reconsidered less often. That is not usually the reason a page is excluded, but a slow shared host makes every other fix take longer to show. Checking time to first byte in PageSpeed Insights takes thirty seconds and is worth doing once.
How long recovery takes and how to track it
Expect changes to show up over two to six weeks, not days. Search Console's Pages report updates with a lag, and the chart can look flat for a fortnight before moving all at once.
Keep a simple sheet with four columns: URL, what you changed, the date, and the status two weeks later. It sounds tedious, but after a month you will see which fixes worked on your site specifically. On some sites internal links move the needle most. On others, merging content does. Your own data beats any general rule, including mine.
If a page is still excluded after two rounds of real improvement and eight weeks of waiting, ask whether it needs to exist as a separate page at all. Folding it into a stronger article is often the honest answer.
FAQ
Is "Crawled, currently not indexed" a penalty?
No. It is a quality and priority decision, not a manual action. Manual actions appear in a separate report in Search Console with an explanation.
How many pages in this report is normal?
Some is normal on every site. If it is mostly pagination, tags and parameter URLs, ignore them. If it includes your main articles, act.
Will adding more words get a page indexed?
Not by itself. Extra words that repeat the same point do nothing. Adding information a visitor actually needs is what changes the outcome.
Should I delete pages that never get indexed?
If a page has no traffic, no backlinks and no better purpose after improvement, merging it into a related article and redirecting the old URL is usually the better move.
More in SEO
SEO
How to Write a robots.txt File for a Small Website
Someone on a forum tells you your site needs a robots.txt file, so you paste in a block of rules you found, upload it, and move...
SEO
How to Set Up 301 Redirects When You Change a URL
You tidy up your site. A page called /services-page-2 becomes /web-design , an old blog post gets a cleaner address, and a...
SEO
How to Write SEO Friendly URLs for a Small Website
You publish a new page, glance at the address bar and see something like /index.php?p=4823 or...