Store state in the browsers url is great advice. Just like you try to build (web) components (in any of those web frameworks) in the most stateless fashion (using @Input() decorators or any other way to send state down into a component), using the URL to store this information might be a good choice.

The only downside I see myself is autocompletion of urls with the appended state information when trying to browse the webpage, e.g. instead of going to example.com/posts the browser autocompletes example.com/posts?filters=a+b+c&category=foo&brand=bar. I then have to delete all of those parameters to get rid of these filters.