But UI labels should be presented in the profile-selected language rather than the local language.
I guess I've gone off on a tangent a bit.
Instead, every site/service/app is just trying to guess, and often enough guesses wrongly.
Streetnames are usually written in both languages, as are bus-stops, tram-stops, etc.
Google maps always shows me directions and routes in Swedish despite my attempts to make it use Finnish. Can be a bit jarring and distracting, but I've mostly become resigned to it.
Having placenames in the user's selected language is useful for comprehension and remembering. I can't form a mental picture of a route, or a day's destinations, if I can't read or pronounce anything I see. Having the names localized to my language makes that possible, if not ideal.
On the other hand, knowing what the place is written as in its local script (its autonym/endonym) is useful for placefinding. Usually local signage is more reliable in the local script, especially for smaller streets and businesses. Also useful for asking a passerby for directions, if they can't read English (or I can't pronounce the local language well enough, which is the case for most places in the world).
My most recent example is Prime Video. I'm in Portugal at the moment, and it seems like everything on the page is Portuguese. If I go to my profile, once I find it, all menus and labels are also in the local language. At this point, Amazon has been working with me for over 10 years in English. They know me.
That's what I'm saying about the UI - that should not change to the local language, unless the user asks for that language.