WordPress powers a massive chunk of the web—around 43% of all websites as of early 2026, depending on whose stats you trust (W3Techs pegs it at about 42.8%, others nudge it higher). That’s hundreds of millions of sites, many running e-commerce with WooCommerce or heavy filtering features.

But here’s the kicker: Google is quietly filing bug reports directly against WordPress plugins that create massive crawl waste. This isn’t some vague warning from a blog post. It came straight from Gary Illyes on Google’s Search Off the Record podcast, breaking down their 2025 year-end crawl report.

Faceted navigation (also called faceted search or filtering) tops the list at roughly 50% of the crawl issues Google’s team sees. Action parameters clock in at about 25%. Together, they account for around 75% of the problems—think endless URL variations that trap Googlebot in low-value loops.

What Faceted Navigation Actually Is (and Why Users Love It)

Faceted navigation lets visitors slice and dice large sets of content or products using multiple filters at once. It’s a killer UX feature, especially on e-commerce.

Picture this: Someone lands on your “Shoes” category page. They click “Brand: Nike,” “Color: Black,” and “Size: 10.” Boom—the page updates instantly to show only matching items. Faster finds, happier shoppers, higher conversions. Who wouldn’t want that?

WordPress doesn’t ship this out of the box. You add it via plugins like WP Grid Builder (which smartly indexes facets in a custom table for speed), FacetWP, or others built for WooCommerce and custom post types/taxonomies.

Great for humans. Not always great for crawlers.

The SEO Dark Side: Duplicate Content, Crawl Traps, and Wasted Budget

Every filter combo often spits out a unique URL—like /shoes/?brand=nike&color=black&size=10. Stack a few more attributes, and one category page balloons into thousands (or millions) of near-identical pages.

Search engines see:

• Duplicate content everywhere—confusing which version is the “real” one.
• Crawl budget drain—Googlebot burns resources chasing low-value URLs instead of your money pages.
• Diluted link equity—authority spreads thin across endless variants instead of concentrating on canonical category pages.

Result? Slower indexing of important content, potential ranking drops, and servers sweating under bot traffic.

How Plugins Quietly Create “Infinite Websites”

Many plugins append parameters or generate dynamic paths for features like filtering, sorting, add-to-cart, wishlists, calendars, or personalization.

Gary Illyes highlighted a classic: WooCommerce’s add-to-cart parameters. Add one (?add_to_cart=123), and your URL space doubles. Stack another, triple it. These create unique-looking URLs with basically the same content.

Google’s crawl team spotted the pattern at scale, filed a bug report directly with WooCommerce—and the team fixed it fast. One upstream tweak helped thousands of sites overnight.

Not every case ends that cleanly. Some plugins (especially commercial ones without public trackers) generate truly infinite spaces—like calendar tools creating bogus URLs for every date combo on every path. Outreach fails, the traps stay, and crawl waste continues.

Why can’t Google just ignore them? Illyes explained: Googlebot can’t know a URL space is worthless without crawling enough samples to spot the redundancy. That discovery phase eats budget first. Proactive blocks (robots.txt, noindex, canonicals) are still the best defense.

Action Parameters: The Sneaky Cousin

In SEO lingo, “action parameters” mean URL queries that trigger actions rather than show unique content—like ?add_to_cart=true, ?action=logout, or sorting params. They don’t change the page meaningfully but create fresh URLs.

Same problems: crawl explosion, waste.

(Developer note: In core WordPress, “action parameters” also refer to args passed via do_action() hooks—but here we’re talking the URL/SEO side.)

What This Means for WordPress Site Owners in 2026

The shift is real: Crawl health is increasingly upstream—tied to plugin choices more than manual tweaks. As WordPress gets more modular with plugins for everything, “plugin hygiene” becomes core technical SEO.

Best practices haven’t changed much, but they’re more urgent:

• Use canonical tags to point filter pages back to the main category.
• Noindex low-value filtered pages.
• Block problematic patterns in robots.txt (e.g., disallow /shoes/?sort= or similar).
• Choose plugins that handle faceted nav smartly (AJAX loading, no URL changes for filters when possible, or built-in SEO controls).
• Monitor crawl stats in Google Search Console—watch for spikes in discovered URLs.
• On VPS hosts like Bluehost, you get root access for deeper log dives and file control.

Google filing bugs against plugins signals shared responsibility: developers, platforms, and owners all play a role in preventing structural crawl waste.

No big announcement. No algorithm hit tied to it. But the message is clear: Clean up those faceted URLs and action params before Googlebot does it for you—inefficiently.

Your site’s growth depends on healthy discovery. Don’t let plugins turn your WordPress install into an accidental crawl trap.

If you’re running WooCommerce or heavy filters, double-check your setup. A quick audit now beats a budget crisis later.

Auditing for “plugin hygiene” in the context of crawl budget waste—especially from faceted navigation and action parameters—isn’t a one-click dashboard feature in WordPress. It’s a deliberate, multi-tool process that combines observation, crawling, log analysis, and proactive blocking. The goal? Spot which plugins are quietly multiplying low-value URLs before Googlebot wastes too much time on them.

Google doesn’t publish a formal “plugin hygiene checklist,” but Gary Illyes’ comments on the Search Off the Record podcast highlight the pattern: problems often stem from repeatable behaviors in popular plugins (filtering, e-commerce add-ons, calendars, personalization layers). Site owners end up doing the detective work themselves.

Here’s a practical, step-by-step audit approach that WordPress tech folks use in 2026 to stay ahead of crawl traps.

1. Start with Google Search Console (GSC) – Your Free First Line of Defense
   GSC gives the clearest real-world view of what Googlebot is actually doing on your site.

• Go to Settings > Crawl stats (or the older Crawl Stats report if still available) to see crawl requests per day, file types, and response codes.
• Look for spikes in “Discovered – currently not indexed” or high crawl volume on URLs with ? parameters.
• In Coverage > Excluded, check for categories like “Crawled – currently not indexed,” “Duplicate without user-selected canonical,” or “Soft 404.”
• Use the URL Inspection tool on suspect filtered pages (e.g., /category/?brand=nike&color=black). See if Google says “URL is on Google” or flags duplicates.
• Run a quick site:yourdomain.com/? search in Google to see how many parameterized URLs are indexed. If the results explode with filter combos, you’ve got bloat.

If GSC shows faceted/action params eating crawl resources (e.g., thousands of ?filter= or ?sort= URLs crawled recently), proceed to deeper tools.

2. Crawl Your Own Site Like Googlebot Does
   Use a desktop crawler to simulate bot behavior and uncover hidden URL generation.

• Screaming Frog SEO Spider (free up to 500 URLs, paid for bigger sites) or Sitebulb – Crawl your site and filter URLs by:
• Containing ? (query parameters)
• Patterns like ?add_to_cart=, ?action=, ?sort=, ?filter_, ?page=, ?min_price=
• Facet-specific params from your plugins (e.g., FacetWP uses ?fwp_, WP Grid Builder might use custom ones)
• Export the list and sort by count. If one plugin generates 10,000+ similar URLs, that’s your culprit.
• Check for status codes (200s on thin/duplicate pages = waste) and title/description duplication.

Pro tip: Crawl with JavaScript rendering enabled if your faceted nav is AJAX-heavy—some plugins change URLs only after JS loads.

3. Dive into Server Logs (The Gold Standard for Behavior)
   Server logs reveal exactly what Googlebot requests and how much time it spends.

• On shared hosting: Download access logs via cPanel/File Manager.
• On VPS (Bluehost, etc.): Use root access for full Apache/Nginx logs.
• Filter for User-Agent: Googlebot
• Look for patterns: Repeated requests to /category/?brand=...&color=...&size=... combinations.
• Tools like Log Analyzer (free), GoAccess, or paid ones like Screaming Frog Log File Analyser help visualize bot paths and waste.
• Calculate rough waste: If Googlebot hits 50k+ param URLs in a month on a 5k-page site, hygiene is poor.

3. Inventory & Test Your Plugins Directly
   Manual check for the usual suspects.

• List all active plugins, especially:
• Faceted nav/filtering: FacetWP, WP Grid Builder, Search & Filter Pro, YITH WooCommerce Ajax Product Filter, etc.
• E-commerce extras: WooCommerce add-ons for sorting, wishlists, quick view.
• Others: Calendars (The Events Calendar), personalization (e.g., dynamic content plugins).
• Test behavior:
• Apply filters/sorts/actions on frontend.
• Watch URL changes (or lack thereof if AJAX-only).
• Check plugin settings for SEO options: canonical enforcement, noindex toggles, param exclusion.
• Update everything—many issues (like the WooCommerce add-to-cart stack) get fixed in core/plugin updates.

3. Implement & Monitor Fixes (Hygiene Maintenance)
   Once you identify bad actors:

• Configure canonicals to point back to the base page.
• Add noindex meta on low-value variants (via plugin or Yoast/Rank Math).
• Block patterns in robots.txt (e.g., Disallow: /?filter=, Disallow: /?add_to_cart=).
• Switch to AJAX faceted nav if possible (no URL change = no new crawl).
• Use SEO plugins like All in One SEO or Rank Math crawl cleanup features to auto-block common junk params.

Re-crawl in GSC after fixes, watch Crawl Stats for drops in wasteful requests.

Bottom Line for WordPress Builders
Plugin hygiene auditing is iterative: monthly GSC checks + quarterly full crawls/logs for most sites. On larger e-commerce or directory sites, it’s weekly. The payoff? Faster indexing of real content, better rankings, and fewer surprises when Google quietly files the next bug report upstream.

It’s not glamorous, but in a plugin-powered ecosystem, this is the new baseline for technical SEO ownership. Spot the traps early, and your site stays lean and crawl-efficient.