Why WooCommerce Category Page Not Indexing: What to Check

Your category pages are live, crawlable (you checked), and sitting in your sitemap. Google has visited your store. Yet when you open Search Console, those pages are missing from the index — or worse, they’re sitting in “Crawled – currently not indexed” limbo for weeks.

This isn’t a patience problem. Something is actively blocking them, or Google has decided they’re not worth indexing. Both are fixable — but only if you check in the right order.

This guide walks through every real cause, starting with the ones that take 30 seconds to fix and often turn out to be the culprit.

Table of Contents

Start Here: The Most Common Cause Takes 30 Seconds to Find

Before touching robots.txt or writing category descriptions, open your SEO plugin settings.

In Yoast SEO: Go to SEO → Search Appearance → Taxonomies. Find “Product Categories.” Check whether “Show in search results?” is toggled to Yes. If it says No, that’s your answer. Every category page has been broadcasting a noindex signal to Googlebot without any visible warning on the front end.

In Rank Math: Navigate to Rank Math SEO → Titles & Meta → Product Categories. Look at the “Robots Meta” field. If No Index is enabled at this level, all category pages are excluded — regardless of individual page settings.

This sounds too simple to be the problem. It happens constantly. One documented audit of a Singapore e-commerce store found 847 product pages noindexed because someone had accidentally toggled a single WooCommerce post type setting in Rank Math’s global configuration. The fix took 30 seconds. The Google recovery took six weeks.

After fixing the taxonomy setting, go to Search Console’s URL Inspection tool, enter one of your affected category URLs, and click “Request Indexing.” Don’t just wait.

Check 1: WordPress’s Own Indexing Blocker

There’s a checkbox inside WordPress core that overrides every SEO plugin setting on your site.

Go to Settings → Reading. Look for “Search Engine Visibility.” If the box labeled “Discourage search engines from indexing this site” is checked, WordPress injects a noindex directive at the server level for every page. No SEO plugin can override it.

This setting exists for development and staging environments. It gets left on after a site migration more often than it should. Uncheck it, save changes, and run the URL Inspection check again before going further.

Check 2: The Noindex Tag on Individual Category Pages

Even if your global taxonomy setting is correct, individual categories can carry their own noindex directives.

Edit the category in WooCommerce → Products → Categories. Scroll to the SEO meta box. In Rank Math, open the Advanced tab and confirm “No Index” is not selected. In Yoast, expand the Advanced panel and check the robots meta setting.

This matters on stores where multiple team members have admin access. A category created for a “coming soon” product range or a seasonal clearance sale may have been manually noindexed and never cleaned up.

Check 3: Robots.txt Is Blocking the Crawl Entirely

A noindex tag tells Google not to index a page. A robots.txt block tells Google not to crawl it at all. These are different problems with different symptoms.

If Googlebot can’t crawl a page, it may never read the noindex tag — which means the page could appear in Search Console as “Discovered – currently not indexed” indefinitely. Worse, the page might stay in the index from an older cached version while Google can’t check whether it’s changed.

Visit yourdomain.com/robots.txt and scan for any Disallow rules that could match your category URL structure. Common patterns that accidentally block WooCommerce category pages:

Disallow: /product-category/ blocks all standard category URLs
Disallow: /shop/ blocks stores using the shop base permalink structure
Overly broad wildcard rules like Disallow: /*?* — intended to block filter parameters but can catch category pagination URLs depending on how filters are implemented

Test a specific category URL using Search Console’s URL Inspection tool. If it returns “Blocked by robots.txt” in the crawl results section, this is the cause.

Check 4: Thin Content — The Invisible Reason Google Skips the Page

This one doesn’t produce any warning in Search Console. There’s no error, no flag, no “excluded by” status. Google simply decides the page doesn’t meet the threshold for indexing and moves on.

WooCommerce category pages are structurally thin by default. They consist of a product grid and a category title — both of which appear across multiple pages, in multiple contexts, in near-identical form. Without a unique category description, relevant heading structure, or any editorial content, Google has no basis to treat the page as something distinct worth showing in search results.

According to a 2026 optimization study published by Woo Sell Services, category pages without descriptive content are among the most commonly “discovered but not indexed” pages in WooCommerce stores. Google confirmed through Search Central documentation that pages must provide clear, unique value to be considered for indexing — a product grid alone does not typically satisfy this threshold.

The fix: Add a category description from WooCommerce → Products → Categories → Description field. This description renders on the category page, typically above or below the product grid depending on your theme. Aim for at least 150-300 words of genuinely useful content — not keyword-stuffed filler. Explain what this category covers, who it’s for, what makes these products distinctive, and what a shopper should consider before buying. That’s the kind of content Google evaluates when deciding whether to index a page.

Check 5: Canonical Tag Pointing to the Wrong URL

Canonical tags tell Google which version of a URL is the “authoritative” one. When a category page carries a canonical tag pointing somewhere else — to the shop page, to a parent category, or to a filtered version — Google will not index that page. It will index the canonical URL instead.

This is one of the harder causes to spot because the page looks perfectly normal in a browser. You only see it in the page source.

Right-click any category page and select View Page Source (Ctrl+U). Search (Ctrl+F) for rel="canonical". The URL inside the canonical tag should match the URL of the page you’re viewing.

Common misconfiguration patterns in WooCommerce:

A caching plugin generating canonical tags incorrectly after a URL structure change
A CDN or reverse proxy serving a cached version with the old canonical URL
An SEO plugin configured to point paginated category pages to page 1 (which creates a different problem — page 2, 3, etc. should be self-canonical, not pointing back to page 1)
Duplicate URLs created by trailing slashes, uppercase/lowercase inconsistency, or the presence/absence of www — all of which can generate canonical conflicts

If you changed your permalink structure at any point and didn’t update canonical settings, this is worth checking closely.

Check 6: Crawl Budget Wasted on Low-Value WooCommerce URLs

For stores with large catalogs, crawl budget matters. Google’s documentation defines crawl budget as having two components: the crawl capacity limit (how fast Googlebot can crawl without overloading the server) and crawl demand (how frequently Google wants to visit content based on its perceived importance and change frequency).

WooCommerce generates a large number of low-value URLs by default. According to ContentGecko’s technical analysis of WooCommerce crawl patterns, a typical store generates thousands of additional URLs from faceted filters, sort parameters, product variations, and pagination — most of which carry no SEO value but consume the crawl budget Google would otherwise spend on category and product pages.

If Googlebot is spending most of its crawl allocation on /product-category/shoes/?orderby=price&paged=3 and checkout flows, it may not get to your actual category pages during each crawl cycle. The result: your category pages show as “Discovered – currently not indexed” because Google knows they exist but hasn’t prioritized crawling them.

Practical fixes:

Block URL parameters via Google Search Console (Settings → Crawl Stats → Legacy parameter handling is no longer available, but robots.txt parameter blocking still works). For the most common WooCommerce filter parameters — ?orderby=, ?min_price=, ?max_price= — add Disallow rules in robots.txt only for the parameter strings you’re certain carry no unique content worth indexing.

Ensure your XML sitemap includes category pages and excludes paginated versions, tag archives, and empty categories. In Yoast SEO: SEO → XML Sitemaps → Taxonomies. In Rank Math: Rank Math → Sitemap → Taxonomy Sitemap → enable Product Categories, disable Product Tags unless those pages have real content.

Improve server response time. Google’s crawl capacity limit scales with how fast your server responds — slow hosting directly limits how many pages Googlebot will crawl per session.

Check 7: Paginated Category Pages and Duplicate Content

When a WooCommerce category contains more products than the per-page limit, it creates paginated URLs: /product-category/shoes/page/2/, /page/3/, and so on.

These paginated pages can create duplicate content problems when handled incorrectly. There’s an open issue in WooCommerce’s GitHub repository (Issue #36175) specifically about unnecessary pagination creating duplicate content across shop and category pages — where paginated versions are accessible but contain near-identical content to page 1.

The correct approach:

Each paginated category page should be self-canonical (its canonical tag should point to itself, not to page 1)
Do not add paginated pages to your XML sitemap — only the root category URL belongs in the sitemap
Consider whether /page/2/ and beyond are worth indexing at all for smaller categories — if a category has 8 products shown 4 per page, noindexing page 2 and keeping page 1 indexed is cleaner

As Woo Sell Services’ 2026 WooCommerce SEO guide notes, showing 24–48 products per page is optimal for most stores. Too few products per page creates unnecessary paginated URLs; too many slows page load speed, which affects Core Web Vitals and indirectly affects indexing priority.

Check 8: Category Page Has No Internal Links Pointing to It

Google discovers pages through crawling. Crawling follows links. If your category page exists but nothing links to it — not the main navigation, not the homepage, not any product page, not the sitemap-initiated crawl — Google may take a long time to find it, and when it does, may deprioritize it based on low link equity.

Check your category page using Google Search Console’s URL Inspection tool. Under “Coverage,” look at whether Google has crawled the page and when. If it shows “Discovered – currently not indexed” with no crawl date, the page may not have sufficient link signals to trigger crawling.

Fix: Ensure every category is linked from at least one of these: the main navigation menu, the shop page, a breadcrumb trail on product pages, or a related categories section. Internal linking is how link equity flows through the site, and it’s how Google decides which pages are important enough to index promptly.

Check 9: Schema Errors Causing Crawl Issues

WooCommerce category pages often carry schema markup, and schema errors can sometimes coincide with indexing problems — not because schema errors directly prevent indexing, but because they signal content quality issues that compound other weak signals.

Open Google Search Console → Enhancements. Check for any schema errors associated with your product category URLs. Common WooCommerce schema problems include:

Missing aggregateRating properties on pages with no product reviews
ItemList schema errors when the product grid structure doesn’t match the markup
BreadcrumbList errors when category hierarchy URLs don’t match actual page structure

Fix these through Search Console’s Rich Results Test, resolve the underlying structural issue, and validate the fix. While schema errors alone rarely cause deindexing, they add up alongside thin content and crawl budget issues on stores where indexing is already marginal.

Check 10: Verify the Fix in Google Search Console

After working through any of these checks, the verification workflow is the same:

Go to Search Console → URL Inspection
Enter the exact category URL
Check the “Coverage” section — status, last crawl date, canonical URL Google selected, and any crawl issues
If you’ve made a fix, click “Request Indexing”
Wait 3–5 days, then re-run the URL Inspection to confirm status has changed

For category pages that were previously excluded due to noindex, the “Excluded by ‘noindex’ tag” status should clear once Googlebot recrawls. This typically happens within a few days of requesting indexing — though on large sites with low crawl budget, it can take longer.

If a URL shows “Indexed, not submitted in sitemap,” your sitemap configuration needs updating even though the page itself is indexing correctly.

The Diagnostic Order That Saves the Most Time

Run these checks in this sequence before doing anything else:

Step 1: Check WordPress Settings → Reading for the “Discourage search engines” checkbox.

Step 2: Check your SEO plugin’s global taxonomy settings for Product Categories.

Step 3: Use Search Console URL Inspection on one specific affected category URL to see exactly how Google is reading it.

Step 4: View page source and search for noindex and rel="canonical" to see what tags are actually rendered.

Step 5: Check robots.txt for any Disallow rules covering category URL patterns.

Step 6: Assess category content quality — is there a unique description, or just a product grid?

Step 7: Check internal links to the category — does anything link to it?

Step 8: Review paginated category URLs for canonical and sitemap configuration.

Most WooCommerce category indexing problems resolve at step 2 or step 4. The stores that get stuck are usually dealing with thin content (step 6), where Google is technically allowed to index the page but has decided not to.

A Word on “Crawled – Currently Not Indexed”

This specific Search Console status is widely misread as a technical error. It isn’t. Google is telling you the page has been crawled but doesn’t meet the quality threshold for inclusion in the index.

For WooCommerce category pages, this almost always comes back to thin content. Google has visited the page, read it, and concluded there wasn’t enough unique, helpful content to justify an index entry. Adding a substantive category description, building internal links to the page, and ensuring the page has crawl priority in your sitemap will resolve most cases — but recovery takes time. Google typically revisits pages flagged this way within a few weeks of improvements being made.

The one thing that doesn’t help: repeatedly submitting the URL for indexing via Search Console without fixing the underlying content issue. Google’s systems will continue to make the same quality assessment until the page itself changes.

Key Takeaways

WooCommerce category pages don’t index for six primary reasons: they carry a noindex tag (set globally or per-page), they’re blocked in robots.txt, they lack unique content, their canonical tags point elsewhere, their crawl budget is being consumed by low-value URLs, or they have too few internal links to signal importance. The majority of cases resolve at the SEO plugin taxonomy settings level. The cases that don’t resolve there are content quality problems — and those require real editorial investment, not technical tricks.

Check in that order, verify each fix in Search Console, and most category pages will be indexed within a few weeks.

WooCommerce Category Page Not Indexing: What to Check