As someone who lives in one of those locations mentioned in the article: split out locale and language into different settings. Because they are not the same th

As someone who lives in one of those locations mentioned in the article: split out locale and language into different settings. Because they are not the same thing. This article explains that nicely. [1] You want your users to be able to change their location (and, therefore, locale) and their language independently. The Accept-Language header could be used as a sentinel for language. Then again, I wouldn't outright rely on geoIP to set the locale which is an umbrella for regional differing variables like timezone, date formatting, currency, VAT / Taxes,... I think it's okay to have your content served, by default, in a language that reflects either the majority of your target audience; or the culture / place you're based in. Changing the locale / language should follow a clear UI pattern e.g. a language switcher & locale switcher in the header; or a clear navigational aid pointing to a context menu. That's how Hetzner works, for instance. Another example is Deliveroo. [1] https://translatepress.com/locale-vs-language/ https://translatepress.com/locale-vs-language/