Google urls not completely cleaned

[Neustradamus]

Dear @ClearURLs team, @KevinRoebert,

It is new, do a test search and you will have:

• https://www.google.com/search?q=test&sca_esv=XXXXXXXXX

You can see:

• sca_esv

Can you remove it?

Thanks in advance.

Linked to:

• https://gitlab.com/ClearURLs/rules/-/issues/283

[Neustradamus]

In more, with Firefox, there is "oe=utf-8" in more:

• https://www.google.com/search?q=test&oe=utf-8

[kowith337]

I feels like they've changed parameters for avoision, I've seen more parameters are changed away, include track screen width/heigh of browser, but I mostly rely to randomization (use alternative, such as SearXNG, Whoogle, include use Farside, SearX neocities for redirect random instances), so I can't remember which parameters were changed to.

[FuccDucc]

I can see such parameters at the end of URL (not cleaned by ClearURLs plugin as of today): &sca_upv (i dont know why for you it was _esv instead of _upv, maybe local or Google alghoritm dependent)

But there are some catches to it.. it will happen if you:

1. search directly from the Google.com search field (cleanly)
2. search once directly in URL bar (with Chrome/browser set to Google as default search engine), and then change your search term from there on in Google's search field that contains your initial search term

^ On first try from URL bar, the URL will be properly cleaned by ClearURL. But when you modify the search term, it will fail to properly clean it, and the "sca" parameters will be added, to track you.

So this means the new tracking parameter has to do with Google site's search field. At present, ClearURLs plugin is only still successful to clean tracking elements out of Chrome/Browser Search Engine omnibox typed searches. Unless the user changes their search term using the Google.com website once afterwards.

@KevinRoebert @Neustradamus