(Of course, you'd still expose the option to change this from the inherited default in the browser's preferences)
Most commonly they'll use an English OS for whatever reason and want to browse websites in their local language.
This is why you'll find that a lot of website language detection tends to discount English specifically. I.e. if your Accept-Language is "en" in France they'll probably give you French, but if it's e.g. Japanese in France they might think that's a "real" setting and give you Japanese.
Or, as I'm sure a lot of non-English speaking technical users here can attest to, they like to use an English OS UI on their laptop or phone, but speak the local language and want browsing a local website to just work. Non-technical users do that too, but have no idea how to tweak their Accept-Language independently from their OS language.
Really, do armchair commentators here think that programmers at major websites like Google that have enough data to know how people are likely to switch languages from the default haven't thought of just implementing what's literally the most simple thing you can do, which is to obey Accept-Language?
Basically `en-US`-only Accept-Language seems to be treated as "perhaps default language of a device and user didn't change it, we should not rely on it" and IP-based localization is applied in that case ("in France? ok show French version").
If for historical reasons Accept-Language needs to pass through the OS locale, which is wrong and can't be changed, why not just standardize an optional User-Requested-Language(s) header, that only appears if the user explicitly sets it in the browser?
The current solution is awful and improving it doesn't seem like rocket science but there seems to be zero interest in fixing it. Stuff like this is why closed platforms like Facebook probably have a brighter future than the open web.
And browsers could make the override easily discoverable in preferences (at least on MacOS, app preferences are in a standard place from the user's perspective: File -> Preferences).
Guessing what language a user actually speaks is not straightforward.
It still doesn't make sense to use the same behaviour in Europe, where in my experience the OS language is almost always the preferred language of the user. (Especially on a mobile.)
1) Inertia. The Indian market is largely English-speaking, so many products came to market in English first, and now people are used to it.
2) Colonialism. Using English still marks you as "educated" and "more respectable". So, to not look like a yokel, everybody sets their UI to English. Content, which is more ephemeral, still is successful in Hindi/Urdu.
3) Localization is hard, and often the English localization is better - but content isn't localized, its first language is the native language.
IIRC, most browsers do default to the OS language. It's just not the correct choice in all cases :)
Websites doing weird things is websites trying to be smart and failing on top of that.
I've tried en and en,da, but I almost always get Danish in Denmark and the local language if I travel.
They shouldn't have to fiddle with language settings. That's a tech failure.
You only need "fiddling with language settings" if you want something other than how your operating system is configured.
But yeah, sites should have a way to sticky it once you have a profile and log in etc., but most users aren't going through that path for most sites.