On This Page
On This Page
Remove Query Strings
Overview
On the front end, strips the ver= parameter from same-host script and style URLs under wp-content and wp-includes. Other query args stay. Third-party hosts are untouched. Conflicts with Remove Version from Scripts—enable only one.

- Sites optimizing asset URLs for certain proxies or legacy cache rules
- Teams that want all local
ver=markers gone (including theme/plugin) - Anyone replacing a “remove query strings” micro-plugin
Features
Strip local ver=
Keep other args
Same-host only
Use Cases
- Legacy proxy or CDN rulesSites on older cache configurations that struggle with ?ver= can serve leaner local asset URLs.
- Markup cleanup auditsTeams auditing HTML that flags query strings on static assets can remove local ver= without touching third-party URLs.
- Replacing overlapping pluginsConsolidate multiple “remove query string” tools into one PowerSuite toggle and keep Remove Version from Scripts off.
Frequently Asked Questions
What does the Remove Query Strings module do in WP PowerSuite?
It strips the ver= parameter from local CSS and JavaScript URLs on the front end (wp-content and wp-includes). Other query parameters and third-party assets stay.
How do I enable Remove Query Strings in WP PowerSuite?
Enable it in the Modules hub, keep Remove Version from Scripts off, then verify page source and purge caches after asset updates.
Who should use Remove Query Strings?
Sites that need all local ver= markers removed—for legacy cache rules, markup cleanup, or consolidating a micro-plugin—and accept clearing caches after theme/plugin updates.
Does this conflict with Remove Version from Scripts?
Yes. Both rewrite asset URLs. This module strips all local ver= markers; the other only strips the core WordPress version. Use one strategy.
Is Remove Query Strings a free or Pro module in WP PowerSuite?
It is included (free) with WP PowerSuite.

