BigTech CompaniesCybersecurityNewswireTechnology

Google Flags WordPress Plugins for Security Issues

▼ Summary

– Google’s crawl team is filing bug reports against WordPress plugins that create wasteful URL parameters, with WooCommerce being a notable example that quickly fixed the issue.
– Action parameters and faceted navigation together accounted for about 75% of all crawl issues Google flagged in its 2025 year-end report.
– These problematic parameters, often injected by CMS plugins, create duplicate or infinite URLs that waste Googlebot’s crawl budget and strain servers.
– The responsibility for managing this crawl waste ultimately falls on website owners, even when the problem originates from a plugin they use.
– Google recommends using robots.txt to block parameter URLs proactively and views its direct outreach to plugin developers as a way to reduce the problem at its source.

Google’s web crawlers are now actively reporting problematic WordPress plugins that create significant inefficiencies, directly impacting a site’s ability to be indexed effectively. This development was detailed by Google Analyst Gary Illyes, who explained that his team has begun filing bug reports against plugins identified as major sources of crawl budget waste. The initiative highlights a growing focus on technical SEO issues that originate not from website owners, but from the tools they rely on.

During a recent industry podcast, Illyes reviewed Google’s internal year-end crawl issue report. The data revealed that action parameters, often injected by CMS plugins, accounted for roughly 25% of all crawl problems identified. These parameters, which add strings like `?addtocart=true` to URLs, create the illusion of new pages, causing Googlebot to waste valuable resources indexing duplicate or low-value content. Only faceted navigation posed a larger issue, making up about 50% of reported problems. Combined, these two categories represent the overwhelming majority of crawl inefficiencies Google encounters.

A prime example involved the popular WooCommerce plugin. Google’s team filed a bug report after identifying its add-to-cart URL parameters as a top contributor to crawl waste at scale. The developers at WooCommerce responded promptly and shipped a fix, a move Illyes praised. However, not all developers have been as cooperative. Issues filed against other plugins, including a commercial calendar tool that generates infinite URL paths, have gone unaddressed despite direct outreach from Google.

This situation creates a complex challenge for website managers. The crawl waste is frequently baked into the plugin layer, meaning site owners can inherit serious technical SEO problems through no direct fault of their own. Yet, the responsibility for managing these issues ultimately falls on them. Illyes emphasized that Googlebot often cannot determine a URL’s usefulness without first crawling a substantial portion of it, which means server strain and indexing delays can occur before the problem is even noticed.

The core issue is one Google has warned about for some time, leading to updated official documentation on faceted navigation and URL parameter handling. Despite these guidelines, the persistence of these problems in annual reports indicates that warnings alone are insufficient. Google consistently recommends using robots.txt to block problematic parameter URLs proactively, as this is more effective than reacting to symptoms like server overload or poor indexing.

Looking forward, Google’s direct engagement with open-source plugin developers could help reduce crawl waste at its source. By addressing these inefficiencies within the code of widely used tools, the overall health of the web ecosystem improves. This proactive approach signals a shift toward treating widespread technical SEO flaws as software bugs, potentially leading to more systemic solutions for site owners everywhere.

(Source: Search Engine Journal)

Topics

crawl budget 95% url parameters 93% wordpress plugins 90% google crawl team 88% woocommerce fix 85% faceted navigation 82% plugin developer responsiveness 80% crawl issues report 78% open source repositories 75% server strain 72%