No query strings here either from
The article discusses the author's decision to ban query strings on their website, inspired by Chris Morgan's similar approach. The author allows only a specific query string format for cache-busting purposes while rejecting others that may include tracking parameters. The rationale behind using a 403 Forbidden status code for rejected requests is also explained.
- ▪The author has implemented a ban on query strings to prevent unwanted tracking parameters in URLs.
- ▪Only the query string format ?v=<digits> is allowed for cache-busting purposes.
- ▪Requests with any other query strings result in a 403 Forbidden response, accompanied by an explanatory message.
Opening excerpt (first ~120 words) tap to expand
No query strings here either May 19, 2026 by Timo Furrer A couple of weeks ago, Chris Morgan published I've banned query strings. I read it, liked it and then did roughly the same thing on my own site - with two deliberate differences. Chris's opening sums up the motivation better than I could: I don't like people adding tracking stuff to URLs. Still less do I like people adding tracking stuff to my URLs. [...] UTM parameters are for me to use, not you. Leave my URLs alone. From chrismorgan.info/no-query-strings The premise is the same here. A ?utm_source=... or ?ref=... tacked onto one of my URLs by some intermediary is, at best, noise I never asked for and at worst a tracker the referrer is using to nudge my visitor's behaviour into a funnel.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Furrer.
Discussion
0 commentsMore from Furrer
