Example: just because I am accessing a Google site from an IP geolocated in Japan does not mean I want content localized in Japanese. Especially if my browser is already telling the web server I want it in English. Which it is.
@trysdyn yup. It really speaks volumes to the imperialist mindset of tech companies assuming the world is divided cleanly by state borders with singular "native" languages.
@shaderphantom Google needs to die.
This is particularly silly because Chrome itself even handles the Google Translate integration by observing a combination of Content-Language and the lang attribute of the HTML tag. So some parts of Google seem to recognize this standard, while the search indexer uses fucking content heuristics and separate IPs to detect content language, and totally ignores the standard headers and html features.