---
title: "Crawled, Currently Not Indexed: Fixes for a WordPress Blog"
url: https://hostmy.blog/crawled-currently-not-indexed-wordpress/
date: 2026-10-27
modified: 2026-11-05
lang: en
author: "Aditya Sharma"
description: "What Crawled, currently not indexed means, what Google says about it, and the checks to run on a WordPress blog, sorted by the kind of URL involved."
categories:
  - "WordPress"
image: https://hostmy.blog/wp-content/uploads/2026/10/hmb-card-2619-1024x538.jpg
word_count: 1335
---

# Crawled, Currently Not Indexed: Fixes for a WordPress Blog

Crawled, currently not indexed is a status in Search Console that worries people more than it should. It means Google fetched a page and chose not to add it to its index, at least for now. It is not an error, and it does not mean something on your site is broken. It does mean Google was not convinced the page was worth keeping.

This post is about what to do with crawled currently not indexed URLs on a WordPress blog. It is honest about what is known and what is not. Google's own explanation of this status is short, and a lot of advice about it claims more certainty than the evidence allows.

## What Google actually says

Google's Page indexing report help defines the two statuses that get confused. For Crawled, currently not indexed, the definition is that the page was crawled by Google but not indexed. Google adds that it may or may not be indexed in the future, and that there is no need to resubmit the URL for crawling. For Discovered, currently not indexed, the definition is that the page was found by Google but not crawled yet. Google says it wanted to crawl the URL but expected that crawling would overload the site, so it rescheduled the crawl. Both come from Google's [Page indexing report documentation](https://support.google.com/webmasters/answer/7440203).

| Status | Google's definition | What it tells you |
| ------ | ------------------- | ----------------- |
| Crawled, currently not indexed | Fetched, and not added to the index | Google looked and was not persuaded, for now |
| Discovered, currently not indexed | Found, but not fetched yet | Google knows the URL and has put the visit off |

That page gives no list of reasons for the first status and no steps to fix it. So everything below is the set of checks we run, not a list from Google. Treat each one as a reasonable thing to rule out, not as a known cause.

## Start with the question: do you want this page indexed?

Most URLs in this report are pages you do not need in the index. A WordPress site generates many of them without being asked, and Google declining some is the system working. Open the report, click the reason, and sort the list by what kind of URL each one is before you do anything.

| URL type | Do you want it indexed? | What to do |
| -------- | ----------------------- | ---------- |
| A post or page you wrote on purpose | Yes | Improve it, link to it, and wait |
| A thin post that adds little | Probably not | Improve it, merge it into another, or remove it |
| Tag pages | Often no | Decide whether each adds anything, and leave the rest out of the sitemap |
| Category pages | Sometimes | Keep the ones with real descriptions and structure |
| Author archives | Rarely, on a small blog | They often repeat your posts list |
| Attachment pages | No | They hold an image and little else |
| Search results and parameter URLs | No | They are endless, and should not be in the sitemap |
| Paginated archive pages | Rarely | They are navigation, not content |

If most of the list is the bottom five rows, nothing is wrong. Close the report and put the effort into the first two rows, which are the ones that matter. The sitemap side of this is covered in [WordPress sitemap: where it is and how to fix it](/wordpress-sitemap/).

## For a page you do want indexed

Work down these checks in order. They are cheap, and they rule out the faults that are in your control.

`1. Is the main text in the HTML, not added afterwards by a script?
2. Does the page say something no other page on the site already says?
3. Is it linked from other relevant pages on the site?
4. Is it in the sitemap, and does it return a plain 200?
5. Is there a noindex tag or header, or a canonical that points somewhere else?
6. Is it fast enough to load without a long wait?`

The first check is the same one used in [finding every page an AI cannot parse](/find-pages-ai-cannot-parse/): fetch the page without scripts, and look for a sentence from the body. The fifth is the pair of curl commands in [how to rank in AI Overviews](/rank-in-ai-overviews-wordpress/), because the same tags that limit a snippet can stop indexing.

The third check is the one most blogs fail. A page that nothing links to gives Google little reason to value it. To find which posts link to a page, search your content for its address.

`wp db query "SELECT ID, post_title FROM wp_posts WHERE post_status='publish' AND post_content LIKE '%/your-page-slug/%'"`

That assumes the default table prefix, wp_, so change it if yours differs. If the result is empty, no post links to the page. Add links from posts that are genuinely related, in sentences where the link helps the reader, and not in a block at the bottom.

## Thin and overlapping posts

The most common honest answer to this status is that the page is close to another page on the same site. Two posts on the same question compete with each other, and Google may index one and decline the other. If you have several, the choice is to improve one so it is clearly the better answer, merge them, or remove the weaker one and redirect it.

That is a content decision and a redirect decision together. [Content pruning for AI: what to delete, redirect or refresh](/content-pruning-for-ai/) sets out how to choose. [Finding your stale posts with a script](/find-stale-posts/) shows how to find the ones that have aged. When you do redirect, use a permanent one and point it at the page that best replaces the old one, as in [WordPress redirect plugin or server rule](/wordpress-redirect-plugin-or-server-rule/).

## What Discovered, currently not indexed adds

The second status is about capacity and priority, not about the page. Google found the URL and has not fetched it yet. In our experience, a long list here on a small blog often means a lot of low-value URLs have been discovered, such as parameters and archives. Google is spending its visits elsewhere instead. The remedy is to stop producing the junk URLs and to make sure the sitemap lists only pages you want. If the list is full of pages you do want, check that the server answers quickly and does not error under load. [What a real WordPress uptime problem looks like from the logs](/wordpress-downtime/) shows how to read that.

## What not to do

Do not resubmit a URL over and over. Google says there is no need to resubmit a Crawled, currently not indexed URL for crawling, and repeating the request adds nothing. Do not edit a page by shuffling words to look new. And do not expect a fixed timeline, because Google gives none. Judge by whether the page has genuinely changed, and look again after Google has had time to revisit it.

Also resist the pull to chase every URL in the list. A blog with fifty posts you care about and two hundred generated URLs should spend its time on the fifty.

## A simple routine

`1. Open the Page indexing report once a month.
2. Sort the not-indexed URLs by type.
3. Ignore the types you never wanted indexed, and keep them out of the sitemap.
4. For each post you wanted, run the six checks above.
5. Improve, merge or redirect, then leave it for a few weeks.`

This takes less than half an hour a month, and it is the same habit as the monthly review in [what to actually monitor on a WordPress site](/wordpress-monitoring/).

Last checked against Google's Page indexing report documentation in October 2026. Google can change how it describes these statuses.

## Where Host My Blog fits

A rise in this report is the kind of slow change nobody notices until traffic has already moved. That is the pattern in [what breaks on a WordPress site when nobody is watching](/what-breaks-when-nobody-is-watching/). On the blogs we look after, we watch for it as part of the monthly review. If you would like someone else to read the report and tell you in plain English what matters, [our care for bloggers](/for-bloggers/) covers it.

If you sorted your not-indexed list by type tonight, how much of it would be pages you actually wanted?