As indicated in another answer, you can include the region in your geocoding request to offset (not limit) the result.
However, in this particular case, London in the UK is still considered a better result than London in the USA. Therefore, you can further limit the result (vs bias) using GeocoderComponentRestrictions , as described in Geocoding Service Docs
I made a fiddle showing this type of filtering, requiring the results to be in the USA.
You will notice that the result is in London, USA, but if you remove GeocoderComponentRestrictions from the script code, the first result is now in London, despite the shift in the region.
However, itโs important to note that the offset really works. For example, if you now change the region to "ES" and the address "Toledo", the result will be in Spain. If you delete the offset, it will be set to Toledo USA by default.
tl; dr uses region for offset, and GeocoderComponentRestrictions for restriction.
source share