If you run a WordPress site, there's a good chance one of your plugins is quietly working against you in Google's eyes. Google's own crawl team has started filing bug reports directly against plugins, calling out the ones that flood Googlebot with junk URLs and burn through crawl budget for no reason. This isn't a rumor or a random SEO forum theory. It came straight from Gary Illyes, an analyst at Google, on a recent episode of the Search Off the Record podcast.
The bigger surprise? One of the world's most popular WordPress plugins, WooCommerce, was on that list. If a plugin used by millions of stores can trigger a crawl budget problem, chances are your site is exposed too, whether you sell products, run a blog, or manage a content-heavy site. In this post, we'll break down exactly what Google found, why it matters, and how you can check if your own WordPress site is quietly bleeding crawl budget right now.
What Is Crawl Budget, and Why Should You Care?
Crawl budget is simply the number of pages Googlebot is willing and able to crawl on your site within a given period. It's not unlimited. Google allocates crawl resources based on your site's size, server speed, and how valuable your content has been in the past.
Here's the problem: when crawl budget gets wasted on low-value or duplicate URLs, your genuinely important pages, new blog posts, updated product pages, fresh landing pages, take longer to get discovered and indexed. For small sites, this rarely causes visible damage. But for stores, membership sites, or content-heavy blogs running on WordPress, wasted crawl budget can mean slower indexing and missed ranking opportunities.
Read our detailed guide on how to optimize your crawl budget.
What Google's Crawl Team Actually Found?
According to Illyes, Google's crawl team traced a large share of crawl waste back to specific WordPress plugins generating what are called "action parameters." These are URL additions like ?add-to-cart=123 or ?add-to-wishlist=456 that get appended every time a visitor interacts with a button on your site.
The problem is that each of these parameter combinations looks like a brand-new URL to Googlebot, even though the underlying page content barely changes. Multiply that across thousands of products and visitors, and you end up with an enormous pool of near-duplicate URLs that Google has to crawl, evaluate, and eventually decide are not worth keeping.
Google's internal data reportedly showed that two categories accounted for roughly three-quarters of all crawl waste flagged in the past year:
- Faceted navigation (filters like size, color, price range) - around half of all reported issues
- Action parameters (add-to-cart, wishlist, and similar interaction URLs) - about a quarter of reported issues
Because WordPress powers such a large share of the web, and because plugins like WooCommerce are so widely used, these patterns showed up again and again in Google's crawl reports. That's what pushed the team to go a step further than documentation and warnings, and start filing bug reports directly with plugin developers.
Why WooCommerce Got Singled Out?
When Google's crawl team identified add-to-cart parameters as a major contributor to crawl waste, they filed the issue directly with the WooCommerce team through their public repository. To their credit, WooCommerce responded quickly and shipped a fix.
Not every plugin developer has been as responsive. Google has also flagged other action-parameter plugins where the bug reports are sitting unclaimed, and at least one commercial calendar plugin that generates an endless stream of URL paths, with no response from the developer despite outreach.
That last point is worth sitting with for a moment. If your site relies on a plugin whose developer isn't actively fixing crawl issues, the responsibility to protect your own crawl budget falls back on you.
Is Your WordPress Site at Risk?
You don't need to be running WooCommerce specifically to be affected. Any plugin that generates dynamic URLs based on user actions can create the same problem, including:
- Ecommerce and cart plugins
- Wishlist and comparison plugins
- Event and booking calendar plugins with infinite date-based URLs
- Filter and faceted search plugins
- Some affiliate link and redirect plugins
A quick way to check is through Google Search Console's Crawl Stats report. Look for a large number of requests going to URLs with question marks, repeated parameters, or pages that return thin or duplicate content. If your "Discovered, currently not indexed" count is climbing while your important pages take longer to get crawled, that's a signal worth investigating.
How to Fix Crawl Budget Waste on WordPress?
The good news is that most of these issues are manageable once you know where to look.
- Audit your URL parameters. Check your crawl stats report and identify which plugins are generating parameter-based URLs.
- Use robots.txt proactively. Google has repeatedly recommended blocking known low-value parameter URLs in robots.txt rather than waiting for problems to show up, since Googlebot can't tell a URL space is useless until it has already crawled a large chunk of it.
- Set canonical tags correctly. Most SEO plugins let you point parameter-based or filtered URLs back to the clean, canonical version of the page.
- Keep plugins updated. Developers who are actively maintaining their plugins are more likely to have addressed known crawl issues, as WooCommerce did.
- Clean up your XML sitemap. Make sure it only includes the URLs you actually want indexed, not every auto-generated variation your plugins create.
Where Hosting Fits Into the Picture?
It's worth pointing out that plugin behavior isn't the only factor at play here. Server response time also shapes how efficiently Google crawls your site. A slow or overloaded server means Googlebot backs off and crawls less frequently, which compounds any waste already happening at the plugin level. A fast, well-configured WordPress hosting environment gives your site more breathing room to absorb parameter-heavy crawling without it hurting the pages that actually matter.
Final Thoughts
Google filing bugs directly against WordPress plugins is a sign of how seriously crawl efficiency is being taken right now, and it's a wake-up call for anyone running a WordPress site with dynamic URLs. The fix isn't complicated, but it does require you to actually look at your crawl stats instead of assuming your plugins are behaving. Take twenty minutes this week to check your Search Console report. It could be the difference between your next post getting indexed in hours instead of weeks.
FAQ
What does "crawl budget" mean for a WordPress site?
Crawl budget is the number of pages Googlebot is willing to crawl on your site within a given timeframe. It's influenced by your server speed and how valuable your past content has been. When it's wasted on low-value URLs, your important pages take longer to get discovered.
Why did Google file a bug report against WooCommerce specifically?
Google's crawl team traced a large volume of crawl waste to WooCommerce's add-to-cart URL parameters, which generate near-duplicate URLs for every product interaction. WooCommerce responded quickly and shipped a fix.
How do I know if my WordPress site is wasting crawl budget?
Check the Crawl Stats report in Google Search Console. Look for a high number of requests to URLs with parameters, and watch for a rising count of "Discovered, currently not indexed" pages, which often signals wasted crawl activity.
Can I fix crawl budget issues without waiting on a plugin developer?
Yes. You can block low-value parameter URLs in robots.txt, set correct canonical tags, and clean up your XML sitemap. These steps don't require the plugin developer to release a fix.
Does hosting affect crawl budget?
Yes, indirectly. A slow or overloaded server causes Googlebot to crawl less frequently, which compounds any waste already happening at the plugin level. Faster, more stable hosting gives your site more room to absorb crawl activity without hurting important pages.
Is crawl budget a concern for small WordPress sites too?
It matters less for small sites with a handful of pages, but any site using ecommerce, booking, or filter plugins can generate enough parameter URLs to cause problems, regardless of overall site size.
