WordPress Cache Protection

WordPress Cache Protection Protects WordPress page cache from fragmentation by tracking parameters and bot abuse. Install What it does Hooks at plugin load and runs before WordPress queries posts. Two modes for handling cache-busting query params: - Redirect — 301 → clean URL. Varnish caches the 301, so subsequent dirty hits cost no PHP. Used for params that on-site JS doesn't read from window.location (default: srsltid, fbclid). - Strip — internal rewrite of $GET / REQUESTURI. Browser URL stays dirty so client-side analytics/ads scripts can still read attribution from window.location; the application sees clean. Used for default: gclid, msclkid, kx, gbraid, gadsource, gadcampaignid, utm, hsa, hsmi, hsenc, hstc, hssc, hsfp. Also strips Pantheon's =PANTHEONSTRIPPED leftovers. Augments robots.txt with bot-throttling rules for known abuse patterns. Search protection Per-IP rate-limit + page-cache kill on search responses. Every search query is unique, so the page cache can never help; meanwhile bots blast random queries to fragment cache and stress the DB. - Two flood windows: burst (default 5/10s) + sustained (default 30/60s). Either limit triggers 429. - Cache-Control: pr