Crawled – Currently Not Indexed: What It Means and How to Fix It

You log into Google Search Console, pull up the Indexing report, and there it is. A status you have probably seen before and quietly worried about:

crawled currently not indexed warning

If you have pages sitting in this bucket, you are not alone. It is one of the most common and most misunderstood status messages in Google Search Console. Business owners see it and assume something is technically broken. Sometimes they are right. Often, the real issue is something else entirely.

This status is Google’s way of telling you it visited the page, looked at it, and decided not to include it in search results. The page was crawled. Google just chose not to index it. That decision, more often than not, is a signal worth paying attention to rather than dismissing.

What is Google’s Index? The index is a massive database storing copies of webpages [Your Index]. If a page is in the index, it can appear in search results [Your Index]. If it is not indexed, it is invisible to searchers [Your Index].

In this article, I will explain exactly what this status means, walk through the most common reasons it happens, and give you a clear set of actions to take (whether you manage your own WordPress site or work with a developer).

What Google Search Console Is Actually Telling You

Google’s indexing process has two distinct stages, and understanding the difference between them is the foundation of diagnosing this problem correctly.

StageWhat It Means
CrawlingGooglebot visits the URL and downloads the page content. Think of it as Google knocking on the door, walking in, and reading what is on the walls.
IndexingGoogle processes the content it found and decides whether to add the page to its search index. This is the database it uses to serve results to searchers.

“Crawled — currently not indexed” means Google completed stage one but declined stage two. The door was open, Googlebot walked in and read the page. It just decided not to put it in the index. Ultimately, the page will NOT show in search results).

It helps to see this status in context alongside the other messages you might encounter:

GSC StatusWhat It Actually Means
Crawled — currently not indexedGoogle visited it, read it, and decided not to index it. It is worth investigating why
Discovered — currently not indexedGoogle knows the URL exists but has not visited it yet. It is often a crawl budget or priority issue
Excluded by noindex tagA directive on the page is explicitly telling Google not to index it
Duplicate without canonicalGoogle found multiple versions of this content and is not sure which one to index
Not found (404)The page does not exist or returned an error when Googlebot tried to visit it

Not all GSC exclusion statuses mean the same thing or have the same fix. “Crawled — currently not indexed” is a quality judgment by Google, not a pure technical failure. That distinction matters when you are deciding where to spend your time.

The Most Common Reasons Google Skips a Page

Google does not publish a detailed explanation for why any individual page was left out of the index. What I have seen across years of SEO audits and WordPress site work is that the causes fall into a consistent set of patterns. Most of them are fixable once you identify which one you are dealing with.

CauseCause
What You See in GSC
Fix Difficulty
Thin or low-quality contentPages with very low word count or no substantive informationMedium: requires content work
Duplicate or near-duplicate contentMultiple pages with similar or identical copyMedium: canonical tags or consolidation
Poor internal linkingPages with few or no internal links pointing to themLow: add relevant internal links
Crawl budget constraintsLarge sites where lower-priority pages get deprioritizedLow-Medium: improve site architecture
Soft 404 behaviorPage loads but appears empty or near-empty to GoogleLow: fix content or redirect
Accidental noindex tagPage has a noindex directive added unintentionallyLow: remove the tag
Blocked in robots.txtCrawl access restricted unintentionallyLow: update robots.txt
Rendering or speed issuesPage loads too slowly or content is hidden behind JavaScriptMedium: performance or rendering fix

Let me walk through each of these in detail.

1. Thin or Low-Quality Content

This is the most common cause, and often the hardest for business owners to hear. If a page has very little content (a few sentences, a short product description with no supporting detail, a contact form with a paragraph of generic text), Google may simply decide it does not add enough value to include in its index.

Google is increasingly capable of evaluating whether a page genuinely answers a question a searcher might ask. Pages that exist mostly as placeholders, that say nothing a competitor’s page does not already say, or that were written to fill a URL rather than to help a reader are frequently excluded from the index.

The types of pages I see flagged most often for this reason:

  • Service pages with a single generic paragraph of description
  • Location pages built by swapping one city name for another with no unique content added
  • Blog posts under 300 words that address nothing specific
  • Tag and category archive pages with no content above the post list

Thin content is not just a quantity problem. A short page written by someone with genuine expertise can outperform a long page that says nothing new. Google is evaluating whether the page demonstrates real knowledge, not just whether it hits a word count. When I see this status on a content page, the first question I ask is: does this page tell me anything I could not find on twenty other sites?

2. Duplicate or Near-Duplicate Content

Google will not index multiple versions of the same content. If your site has pages that are substantially similar to each other, or to pages on other websites, Google will typically pick one version to index and exclude the rest.

On WordPress sites, this shows up more often than most owners realize:

  • Multiple service pages targeting the same service with nearly identical copy
  • Location pages built from a template where only the city name changes
  • Product descriptions copied from a manufacturer or supplier
  • Blog content that has been syndicated to or from other sites
  • WWW and non-WWW versions of the site both accessible without a proper redirect in place

Duplicate content issues compound over time. Each near-duplicate page you add dilutes the signal strength of all the others. The fix is usually consolidation. Merge similar pages into one stronger page, or add canonical tags that tell Google explicitly which version you want indexed. Both approaches are better than leaving the situation as-is.

3. Poor Internal Linking

Google discovers and evaluates pages in part based on how well they are connected to the rest of your site. A page that has no internal links pointing to it, sometimes called an orphan page, is harder for Google to contextualize and is frequently deprioritized for indexing.

Internal links are votes of relevance within your own site. When your homepage, your main service pages, and your blog posts link to a specific page, you signal to Google that the page matters. When nothing links to it, the opposite is communicated.

  • Check whether your not-indexed pages have any internal links pointing to them at all
  • Add contextual links from relevant, already-indexed pages to the problem pages
  • Make sure your XML sitemap includes ONLY the pages you want indexed
  • Review your navigation. Important pages should be reachable within two or three clicks from the homepage.

4. Crawl Budget Constraints

Google allocates a limited amount of crawl resources to every website. On smaller sites, the kind most small businesses run, crawl budget is rarely a significant issue. But if your WordPress site has grown over the years, accumulated a large number of pages, or generates many URL variations through plugins, filters, or query parameters, Google may not crawl every page on every visit.

Pages that are hard to reach, poorly linked, or perceived as low priority may get crawled infrequently. They may stay in the crawled-not-indexed state for extended periods as a result.

  • Reduce the number of low-value URLs your site generates. Disable tag and author archive pages if they add no meaningful content
  • Block parameter-based URLs in robots.txt if they produce duplicate or thin content
  • Submit your XML sitemap in Google Search Console and keep it current
  • Strengthen internal linking to the pages you most want indexed to signal their priority

5. Soft 404 Behavior

A soft 404 is a page that returns a 200 OK status code. It technically loads but appears empty, broken, or nearly contentless to Google. This happens on WordPress sites more often than most owners expect.

Common causes include:

  • A page that was created but never had content added to it
  • A WooCommerce product page where the product was removed but the URL still loads
  • A membership or gated page that shows only a login prompt to Googlebot
  • A page built with a page builder that renders blank when JavaScript is not executed

The fix is either to add substantial content to the page or to redirect the URL to a relevant page that does have content. Leaving soft 404 pages unaddressed trains Google to deprioritize those URLs over time.

6. Accidental Noindex Tags

A noindex directive tells Google explicitly not to include a page in search results. Google honors it. The problem is that these tags get added accidentally on WordPress sites unexpectedly.

  • A developer set the site to “Discourage search engines” in WordPress Settings during a build or redesign and forgot to uncheck it after launch. This adds a noindex to every single page on the site
  • A Yoast SEO or Rank Math setting was configured to noindex a post type, category, or individual page during setup and was never revisited
  • A page was intentionally noindexed during a redesign and never re-enabled after going live

To check: in Google Search Console, click on a specific not-indexed URL and look at the Page Indexability section. If the page is excluded due to a noindex tag, it will say so. You can also use the URL Inspection tool to view the live rendered version and look for the tag directly.

7. Robots.txt Blocking

Your robots.txt file tells search engine crawlers which parts of your site they are and are not allowed to visit. If a page or directory is blocked in robots.txt, Google cannot crawl it. It will not appear in the crawled-not-indexed bucket at all, since it was never crawled. But it is worth checking, especially if you are seeing multiple exclusion statuses across your site.

Check your robots.txt file at yourdomain.com/robots.txt and look for any Disallow rules that might be unintentionally blocking pages you want indexed. Some security and caching plugins add robots.txt rules that are broader than intended.

A page blocked by robots.txt will show as “Blocked by robots.txt” in GSC (not “Crawled — currently not indexed”). If you are only seeing the crawled-not-indexed status, robots.txt is less likely to be the cause. But if you are seeing both statuses, your crawl access rules are worth a close look.

8. Page Speed and Rendering Issues

Google’s crawler has limited patience for slow-loading pages. A page that takes too long to respond or fails to render its content properly, (particularly when content is generated by JavaScript that Googlebot cannot execute) Google may crawl the URL but fail to read the actual content, resulting in a not-indexed outcome.

On WordPress, this most commonly happens with:

  • Pages built heavily with JavaScript-dependent page builders where content is not in the raw HTML
  • Sites with server response times consistently above two seconds
  • Pages that load multiple heavy third-party scripts that block rendering

Use the URL Inspection tool in Search Console and click “Test Live URL” to see what Googlebot actually renders when it visits the page. If the rendered version looks empty or incomplete, rendering is likely a contributing factor.

How to Diagnose Which Cause Applies to Your Site

Before making any changes, identify the actual cause. Applying fixes at random wastes time and occasionally makes things worse. Here is the diagnostic sequence I use when working through this with clients.

Step 1: Pull the Full List of Not-Indexed Pages

  1. Log into Google Search Console
  2. Go to Indexing → Pages in the left sidebar
  3. Scroll to the “Why pages aren’t indexed” section
  4. Click “Crawled — currently not indexed” to see the full affected URL list
  5. Export the list using the Export button in the top right

Start by asking: are these pages you actually want indexed? Thank-you pages, admin utility pages, and filtered archive URLs often end up here and should not be indexed. Flag those and set them aside. You can explicitly noindex them later to clean up the report.

Step 2: Inspect Each Important Page

Use the URL Inspection tool in Search Console to examine the pages that matter. For each one, check:

  • Is there a noindex tag present?
  • What does the rendered page look like? Is the content visible or blank?
  • When was the page last crawled?
  • Is the page referenced in your sitemap?

Step 3: Audit the Content on Pages That Pass Technical Checks

For pages that look fine technically (no noindex tag, renders correctly, not blocked), the issue is almost always content. Ask honestly:

  • Is there enough substantive content on this page to genuinely help a reader?
  • Is the content substantially similar to another page on the site?
  • Does the page have internal links pointing to it from other indexed pages?
  • Does the content reflect real expertise and specific knowledge, or is it generic?
When I audit sites with large numbers of crawled-not-indexed pages, I segment them into groups before doing anything else: thin content pages, near-duplicate pages, orphan pages, and technical issues. Each group has a different fix. Treating them all the same leads to partial solutions that leave most of the problem untouched.

How to Fix It

Once you have identified the cause, the fix is usually clear. Here is what I recommend for each scenario.

If the Cause Is Thin Content

  • Expand the page with substantive, specific content that answers a real question a visitor might have
  • Add detail that only your business could provide such as specific outcomes, real process descriptions, FAQs based on actual client questions
  • If the page genuinely cannot be expanded into something useful, add a noindex tag intentionally so Google stops trying to index it and the page stops dragging down your overall site quality signals

If the Cause Is Duplicate Content

  • Identify which version of the page is the strongest and most complete
  • Add a canonical tag to all duplicate versions pointing to the preferred URL
  • Consider consolidating near-duplicate pages into a single stronger page and redirecting the others to it
  • For location pages built from templates, add genuinely unique content to each page such as specific local details, local examples, or service specifics relevant to that market

If the Cause Is Poor Internal Linking

  • Find two or three already-indexed pages on your site that are topically related to the not-indexed page
  • Add a contextual link from those pages to the problem page using descriptive anchor text
  • Confirm the page is included in your XML sitemap
  • Consider whether the page deserves a spot in your main navigation or a prominent in-content link from a high-traffic page

If the Cause Is an Accidental Noindex Tag

  • In WordPress, go to Settings → Reading and confirm “Discourage search engines” is unchecked
  • In Yoast SEO, check the page’s meta robots setting under the Advanced tab in the post editor
  • In Rank Math, check the Advanced tab for the robots meta setting on the affected page
  • After removing the noindex tag, use URL Inspection in Search Console to request indexing

If the Cause Is Rendering or Speed Issues

  • Use the URL Inspection tool to view the rendered page as Googlebot sees it. Compare it to how the page looks in your browser.
  • If content is missing in the rendered view, the page likely relies on JavaScript that Googlebot cannot execute. Key content should be in the server-rendered HTML, not loaded dynamically after the fact.
  • Run the page through Google PageSpeed Insights and address the highest-impact performance issues
  • Review your hosting environment. Underpowered shared hosting is a common culprit for slow server response times on WordPress sites.

After making any fix, do not wait passively for Google to re-crawl. Use the URL Inspection tool in Search Console and click “Request Indexing” for each important page you have updated. It does not guarantee immediate indexing, but it signals to Google that the page has changed and is worth a fresh look.

The Indexing and AI Visibility Connection

If you have read my previous article on first-hand experience content and SEO, you already know that Google and AI search systems have become increasingly selective about what they surface. The crawled-not-indexed problem is the technical face of the same underlying issue.

A page that Google declines to index will not appear in traditional search results. What is less obvious is the secondary consequence: pages Google does not trust enough to index are almost certainly invisible to AI systems as well. ChatGPT, Perplexity, and Google’s AI Overviews draw from the indexed web. Pages outside the index are not available to be cited when someone asks an AI tool a question your business could answer.

This means fixing your indexing problems is not just a rankings task. Every page you successfully get into the index (with real, substantive content behind it) becomes eligible to earn AI citations. Getting pages indexed is the floor. Everything else in SEO and AI visibility is built on top of it.

Crawled Not Indexed — Diagnostic Checklist

Use this when you find pages in the “Crawled — currently not indexed” bucket in Google Search Console.

  • Export the full list of not-indexed URLs from GSC → Indexing → Pages
  • Separate pages you actually want indexed from those that can be safely noindexed or ignored
  • Run each important page through the URL Inspection tool. Check for noindex tags and rendering issues.
  • Confirm Settings → Reading in WordPress does not have “Discourage search engines” checked
  • Check Yoast SEO for any post-type-level or page-level noindex settings
  • Review the page content. Is there enough substantive, specific content to justify indexing?
  • Check for near-duplicate content. Is this page saying the same thing as another page on the site?
  • Identify internal links pointing to this page. If none exist, add at least two from related indexed pages.
  • Confirm the page is included in your XML sitemap
  • After fixing, use URL Inspection → Request Indexing to prompt Google to re-crawl
  • Monitor the page’s status in GSC over the following two to four weeks

When to Handle It Yourself vs. When to Call a Developer

Many of these fixes are accessible to any WordPress site owner who is comfortable in the admin dashboard. Some situations genuinely need deeper technical experience.

Handle It Yourself If…Call a Developer If…
The issue is a noindex tag you can remove in Yoast or Rank Math settingsThe site-wide “Discourage search engines” setting was left on after launch. This affects every page.
The pages need more content and you can write itRendering issues suggest JavaScript is preventing Google from reading page content
Internal links are missing and you can add them in the WordPress editorDuplicate content issues are widespread and require canonical tag implementation across many pages
A single page needs to be redirected to a better URLCrawl budget issues suggest deeper site architecture problems
Your sitemap needs to be updated or resubmitted in GSCGSC shows hundreds of not-indexed pages and the pattern is not immediately clear

If you are dealing with a large number of not-indexed pages, a consistent pattern across your site, or any of the more technical scenarios in that right column, a WordPress-focused SEO audit is the most efficient path to a real diagnosis. The team at VegasGeek has worked through crawled-not-indexed issues on sites ranging from small local businesses to large-scale WordPress installations. The fastest resolution almost always starts with a clear picture of what is actually happening across the full site before touching anything.

The Bottom Line

“Crawled — currently not indexed” is not a crisis, but it is not something to sit on either. It is Google telling you, in plain terms, that it visited your page and decided it was not worth including in search results. That decision is almost always reversible, but only once you understand why it was made.

The most common causes are not mysterious. They are content that is too thin, pages that are too similar to each other, pages that nothing on your site links to, or the occasional accidental noindex tag left over from a development cycle. Each of these has a clear fix.

What matters is approaching the diagnosis systematically. Export the list, inspect the important pages, identify the cause, apply the right fix, then request re-indexing and give Google a few weeks to catch up.

A well-indexed site is the foundation everything else in SEO and AI visibility is built on. You cannot rank for what Google will not index, and you cannot earn AI citations for pages that are outside the index. Getting this right is not optional, it is where everything else starts.

Not sure where to start, view our SEO Audit services for business owners.

Schedule a call today to discuss getting more website visibility.