How to Fix Crawled – Currently Not Indexed in WordPress

WordPress-specific causes of the crawled - currently not indexed status and the exact settings, plugins, and fixes that resolve it.

If Google Search Console shows “Crawled – currently not indexed” for your WordPress posts, the cause is usually hiding in your WordPress setup itself: plugin-generated archive bloat, theme quirks, or settings that quietly undermine how Google evaluates your content. This guide covers the WordPress-specific causes and the exact settings that fix them.

Why WordPress Sites Hit This Status So Often

WordPress multiplies URLs by design. Every post spawns tag pages, category archives, date archives, author pages, attachment pages, and paginated versions of all of the above. On a young blog with 20 real articles, Google may find 200 URLs – and 180 of them are near-empty shells. When most of what Google crawls on your domain is thin, it grows reluctant to index anything, including your genuine content. The fixes below cut the bloat and concentrate Google’s attention on your actual posts.

Fix 1: Noindex the Junk Archives

In Yoast SEO (Settings → Content types and Taxonomies) or Rank Math (Titles & Meta), switch these to noindex unless you have a deliberate reason otherwise:

  • Tag archives – almost always thin duplicates of category content
  • Date archives – no search value on any blog
  • Author archives – on a single-author blog this duplicates your homepage
  • Format archives and attachment pages – Rank Math and Yoast can redirect attachment URLs to the file or parent post; enable that option

This one change often halves the number of low-value URLs Google wastes crawls on.

Fix 2: Clean Your Sitemap

Open yourdomain.com/sitemap_index.xml and look at what you are actually feeding Google. If tag, author, or date sitemaps are listed, disable those in your SEO plugin’s sitemap settings so the file contains only posts, pages, and any category archives you genuinely curate. A sitemap full of noindexed or thin URLs sends mixed signals that slow evaluation of everything else.

Fix 3: Check for Stray Noindex and Canonical Problems

WordPress-specific traps to rule out in two minutes:

  • Settings → Reading: “Discourage search engines” must be unchecked – hosts sometimes leave it on after staging.
  • In the post editor, check the SEO plugin sidebar: the post must be set to index, and the canonical field should be empty or point to the post itself.
  • If you migrated from staging or changed domains, search your database or theme header for a hard-coded noindex meta tag.
  • Paginated comment pages (Settings → Discussion → break comments into pages) create duplicate URLs – turn this off on most blogs.

Fix 4: Strengthen Internal Linking – the WordPress Way

Orphaned posts are endemic on WordPress because themes bury older content. Practical fixes: add a “related posts” section (Rank Math and many themes include one), maintain a handful of hub pages linking to your best posts by topic, and edit two or three older relevant posts to link to each new article the day you publish it. Internal links from indexed pages are the strongest nudge you can give a stuck URL.

Fix 5: Improve the Content Itself

WordPress mechanics aside, the core rule from our general guide still applies: Google shelves pages that add nothing to the index. Expand thin posts to cover the topic fully, merge posts competing for the same keyword and 301-redirect the loser (Rank Math’s redirection module makes this easy), and delete placeholder content entirely.

Fix 6: Speed and Rendering Checks

Two WordPress-specific gotchas. First, aggressive optimization plugins that defer or minify JavaScript can occasionally break rendering for Googlebot – use URL Inspection’s “View crawled page” to confirm your content appears in the rendered HTML. Second, slow shared hosting throttles crawl rate; caching via LiteSpeed Cache or WP Rocket and compressed images bring most blogs under the two-second mark that keeps Googlebot coming back.

Fix 7: Resave, Then Request Indexing Once

After improvements: update the post (which refreshes its sitemap timestamp), then open Google Search Console → URL Inspection, paste the post URL, and click Request Indexing one time. Re-evaluation typically takes days to a few weeks on newer sites. Meanwhile, keep publishing – consistent output raises sitewide trust faster than anything else.

FAQ

Which WordPress plugin fixes “crawled – currently not indexed”?

No plugin fixes it directly. Yoast or Rank Math give you the controls – noindexing archives, cleaning sitemaps, redirects – but the fix is how you configure them plus content quality.

Should category pages be indexed on a WordPress blog?

Index categories only if you curate them like real landing pages with intros and organized content. Otherwise noindex them along with tags.

Do attachment pages cause indexing problems?

They can. WordPress creates a page for every uploaded image; hundreds of near-empty attachment URLs look like thin content at scale. Enable the redirect-attachments option in your SEO plugin.

Will changing my theme help indexing?

Only if your current theme hides content behind heavy JavaScript or loads painfully slowly. Check the rendered HTML in URL Inspection before blaming the theme.

How many of my posts should I expect to be indexed?

On an established, well-configured blog: close to all genuine posts. On a domain under six months old, partial coverage is normal and improves as trust accumulates.

The underlying causes apply to every platform – see the seven general fixes for the content-quality side. Slow sites also index worse, so it is worth checking why your WordPress site is slow.

Final Thoughts

On WordPress, “crawled – currently not indexed” is usually a signal-to-noise problem: Google is drowning in auto-generated archive URLs and rationing its attention. Noindex the junk, feed Google a clean sitemap, interlink your real content, and make each post worth storing. Configure it once, and WordPress works for your indexing instead of against it.

Related Reading