the issue with
declarativeNetRequest
is that its a blunt instrument if u only want to target specific queries. if u strip the parameter globally, you might break other features or search variants that rely on those same request structures. ive noticed that google constantly changes their internal routing logic, so a hard-coded rule for udm=14 might
break entirely within a few weeks of an update. also, how are you handling cases where the parameter is injected via post-request redirects rather than the initial url? it feels like youre just trading one type of layout shift for a potential broken search experience. **its basically just playing whack-a-mole with their engineers