When WordPress Plugins Break the Crawl And Why Google Is Filing Bugs

Earlier today, Search Engine Journal published a fascinating piece: Google’s crawl team is now filing bugs directly against WordPress plugins that waste crawl budget at scale. One of those bugs was filed against WooCommerce. Google flagged its add‑to‑cart URL parameters as a major source of crawl waste. WooCommerce acknowledged the issue and shipped a fix quickly.

Other plugins? Not so much.

Google also mentioned an unnamed commercial calendar plugin that generates effectively infinite URLs. That developer hasn’t responded. And if you’ve ever worked close to crawling infrastructure, that detail should immediately make you uneasy.

Because I’ve seen this movie before.

A Real‑World Crawl Gone Wrong

Years ago, I was tasked with building a custom search engine, crawler, and index for a large organization with hundreds of websites spread across many sub‑organizations and partner groups.

The goal was ambitious:

• Crawl hundreds of independent websites
• Normalize wildly inconsistent URL structures
• Index everything into AWS CloudSearch
• Expose it through a clean, custom front‑end search interface

I used Apache Nutch as the crawler, configured it to pull from an API that defined which sites were allowed to be indexed, and built tooling to manage that list. A cron job kicked off crawls multiple times per week, pushing updates into the search index automatically.

It was a cool system.

It was also a masterclass in just how messy crawling the open web really is.

Crawling the Internet Is Harder Than It Looks

If you’ve never built a crawler, it’s easy to underestimate the problem.

Not all websites:

• Follow predictable URL patterns
• Use canonical URLs correctly
• Change URLs when content changes
• Or even change URLs at all between pages

Old CMS platforms, custom legacy systems, and poorly written plugins all introduce edge cases. A crawler has to make decisions constantly:

• Is this a new page?
• Is this the same page with different parameters?
• Is this infinite?

And sometimes, you only discover the answer after it’s too late.

The Calendar Plugin That Ate the Crawl

One night, I let the crawler run unattended.

When I came back the next morning, it had barely made progress through one particular site. The crawler wasn’t stuck — it was busy.

The culprit?

An events calendar plugin.

The plugin was generating URLs for:

• Every month
• Every year
• Every day

Indefinitely.

Past, future, it didn’t matter. URLs like:

/events/december/2035
/events/january/2042

From a crawler’s perspective, this looked like an infinite website.

The crawler never reached the rest of the site because it kept discovering “new” event archive pages. Perfectly valid URLs. Perfectly crawlable. Completely useless.

Sound familiar?

Google Is Fighting the Same Battle

According to Google’s own internal crawl reports:

• Faceted navigation caused ~50% of crawl issues in 2025
• Action parameters caused ~25%

Together, that’s three‑quarters of all crawl problems Google flagged.

Many of these issues aren’t created intentionally by site owners. They’re injected by plugins — especially ecommerce and calendar plugins — that generate endless combinations of URLs.

Google’s crawl team identified WooCommerce’s add‑to‑cart parameters as one of the worst offenders. Each parameter made URLs appear unique, multiplying crawlable pages and wasting crawl budget.

WooCommerce fixed it.

But Google also referenced a commercial calendar plugin that generates infinite URL paths — and that developer hasn’t responded.

As someone who’s watched a crawler get swallowed whole by a calendar, I can confidently say:

This is not a theoretical problem.

Why This Hurts Your SEO (Even If It’s Not Your Fault)

Googlebot can’t know a URL space is useless until it crawls it.

By the time Google realizes:

• Your event archives go on forever
• Your add‑to‑cart parameters don’t represent unique content
• Your calendar generates infinite future months

The damage is already happening.

Crawl budget is finite.

If Google is spending it crawling junk URLs, it’s not crawling:

• New blog posts
• Updated service pages
• Product changes

And yes — this can absolutely be why your pages aren’t getting indexed.

How Calendar Plugins Should Work

Your calendar plugin should never expose infinite URLs to crawlers.

A sane approach looks more like this:

• Show a limited window of time
• Example: 3 months in the past, 6 months in the future
• Block or noindex anything outside that range

There is almost never SEO value in exposing /events/december/2035 to Google.

If users can’t reasonably navigate to it, crawlers shouldn’t either.

What You Should Do Right Now

1. Update WooCommerce

   • If you’re running WooCommerce, make sure you’re on the latest version

2. Audit your plugins

   • Especially calendar, filtering, and ecommerce plugins

3. Check for infinite URL paths

   • Look for parameters or date‑based archives that never end

4. Use robots.txt proactively

   • Blocking problematic parameters early is far better than reacting later

Final Thought

Google filing bugs against WordPress plugins should be a wake‑up call.

Your crawl issues might not be your fault — but they are your responsibility.

If your site is struggling to get pages indexed, the problem may not be your content.

It might be your plugins quietly giving Google a headache.

If you’re not sure, that’s exactly the kind of thing we help uncover at Arcane Web Design.