In short if your location has a different default language setting than what you are sending, what you are sending is probably what you really prefer.
...or because your browser defaults to sending en-US even though you're using a Danish-localized browser on a Danish operating system, as described by the parent comment.
It is however not what I experience when I look at my Danish localized firefox because it sends da-DK by default, and my english browser sends en-Us, because I took the effort to make it so, because I don't much like the Danish language for UI.
I admit this is just a quick look over of the different language browsers I have on my system. What do the different language browsers on your system do that you feel so confident in telling me to pay more attention to the parent comment?
Indicating that "the user's actual language" and "en-US" are different. Yes, I extrapolated this to both the browser and the operating system having a different language, maybe it was just one or the other.
> What do the different language browsers on your system
From the parent comment:
> Google has been doing this for almost 20 years. [...] The rationale (which I still don't agree with) was [...]
I don't have any 20 years old browsers to test with, I'm afraid.
Thank you so very much for this tip! I don't use cookies and live in a non-English country so I've been clicking that yellow "change to English results" button for at least half a decade now, numerous times a day, every day. Switching to en-GB indeed makes Google respect my language choice.
Not kidding, you've just saved me thousands and thousands of clicks and small annoyances.
I'm surprised browsers haven't addressed this yet, by adding an extra header stating if the locale is in the default setting or if the user has explicitly configured it.
Default settings need to be treated as the lack of a choice rather than an explicit choice for the default. So much software doesn’t make this distinction apparent and makes peoples’, usually users’, lives difficult.
If “agree to send me promotional email” is the default (and is gross but that’s not really the point here) you’re missing out on good data knowing who explicitly chose it. If the new version of a software has a setting with a new default but you can’t change it on upgrade because you don’t what users explicitly chose then you wind up with this weird case where version Y fresh and version Y from X behave differently. Maddening for debugging and support.
To make matters worse, Google uses ccTLDs for everywhere except the US. google.us just redirects to google.com, and google.com uses your IP to figure out your country, so you can't even use the domain as a workaround.
Given Google's wanton dropping support for RFC-compliant HTTPS in the name of changing times, certainly they should be open to changing this policy with the appropriate data.
The results you get are very much dependant on where you are visiting from. I can set my everything to Japanese, both in my browser, OS and my Google user account and search via google.co.jp - but if I am not in Japan, results will be skewed away from Japanese websites.
For example: The other day I wanted to find the lyrics for the Japanese version of a song, so I typed "[song name] 歌詞" and because Google knows that 歌詞 means lyrics, and it can see I'm in Europe, my top result was an English lyric site, with the original version of the lyrics and no mention of the Japanese word from my search term. Technically, that is really impressive, but kinda useless.
On top of that, it can sometimes be impossible to visit help or product pages if you happen to be in the wrong country.
Sounds like a potential workaround is to set your language to another flavour of English like "en-CA" or "en-GB".
Browser set to en-au? "Oh, I'm sorry, you can't use this feature yet because it's not in your region." for years after launch.
I never completely agreed with the rationale for using location, but 15-20 years ago I at least found it understandable...Internet Cafes and borrowing your host's desktop computer were more common scenarios then. Today they're rare enough that I can't understand why anyone would accommodate those scenarios over the scenario of someone traveling with their own device.
Which browsers? I'm using Chrome and it definitely does not do that. Should be easy to find out that with user agent.
The rationale (which I still don't agree with) was that many browsers would send "en-US" by default, and so it wasn't a reliable indication of the user's actual language. If you set your Accept-Language to anything else, then Google would pay attention to it, but en-US was treated as if it wasn't set at all.