FWIW you can open (once) https://google.com/ncr
It will set an NCR (no-country redirect) cookie.
There are also extensions that might help in case you've set the browser to remove cookies on exit.

I used https://google.com/ncr when chrome wasn't released yet years ago in Firefox 4. You could try the "Steps to reproduce the problem" and see that it doesn't help.
Google should decide if its Chrome is something like Windows (requiring plugins, extensions, patches, hacks, chance, pray, good weather, etc) to do its job or it's like MacOS doing what it's supposed to do out of the box. I'm not gonna install a plugin to stop Chrome's smart location detector, If that's the resolution of this thread I'll use stand alone react dev tools for Safari and close Chrome forever.

Able to reproduce the issue on reported chrome version 65.0.3325.181 and on the latest canary 67.0.3395.0 using Windows 10, Ubuntu 14.04 and Mac 10.13.1.

As similar behaviour is observed from M60(60.0.3072.0) considering it as Non-regression and marking it as Untriaged.

Tentatively adding component "Internals>Permissions>SearchEngineGeolocation", please change if this isn't apt.

Note: Considering the feature of editing/changing "{google:baseurl}" in chrome://settings/searchEngines as an issue for this report.

Thanks!

So in summary, this is a feature request to allow users to set the Google region they're currently in. There is probably a lot of history here. Applying some likely labels, and +cc pkasting who might know more.

To be precise, it's not about "allowing users to set the google region they're currently in." unless it's a technical term known for google guys, it's just about "I may be in Netherlands, but I'm not comfortable with dutch language as much as I am with English, so it'll be super annoying that each time I type something in omnibar and hit enter, it'll open my search result in `google.nl` and there's no way I can make it open `google.com` instead. I AM currently in Netherlands, but I don't want to use `google.nl` I wanna use `google.com`"

#6: As a work-around, can you just manually change the default search engine as folllows?

1) Go to chrome://settings/searchEngines
2) Click "add"
3) Fill in name, keywoard and URL (use  for the URL https://www.google.com/search?q=%s)

See also attached screencast. Does that still get overriden by your location?

Deleted: out.mp4 602 KB

	out.mp4 602 KB View Download

What if Google changes "q=" to "query=" next month and updates its {google:baseUrl} and I'm not a technical user?
This is the original url:
`{google:baseURL}search?q=%s&{google:RLZ}{google:originalQueryForSuggestion}{google:assistedQueryStats}{google:searchFieldtrialParameter}{google:iOSSearchLanguage}{google:searchClient}{google:sourceId}{google:contextualSearchVersion}ie={inputEncoding}`
To be honest I'm not comfortable replacing it with `https://www.google.com/search?q=%s`
Just search this issue in internet and see how many people feel the same. There are lots of unresolved threads about this issue.
From a software developer perspective, the current state is alright, but I'm sure from a UX designer perspective it's not alright and I'm talking about ux here. In past years it has always been annoying for me. Every few months I should deal with it: whenever I install a new OS, whenever I install an extension related to search engines, whenever a chrome update breaks something and resets search engines, ... and each time I feel bad I can't fix it once for ever. If I could set a setting 5 years ago and that setting was synced in my account my life would be easier, believe me, sun would shine brighter if that setting was synced in my account and I didn't have to deal with this annoying smart region detection every few months.

> What if Google changes "q=" to "query=" next month and updates its {google:baseUrl} and I'm not a technical user?

This is very unlikely to happen, but sure it is a possibility that.

> Just search this issue in internet and see how many people feel the same.

I am just trying to help. Not arguing that this is not an issue.

> To be honest I'm not comfortable replacing it with `https://www.google.com/search?q=%s`

If anything, the proposed URLs seems more device agnostic (like no sourceId), and seems to pass less info to the search servers. But I understand, if you don't feel like changing it.

Work that's currently being implemented is eventually going to send everyone through google.com no matter where they are, at which point this will become moot.

I can't guarantee what language the results will appear in when on google.com in the Netherlands (or any other combination).  Google may very well show results in Dutch by default.  If bad things are happening there, changing the configured languages list in the browser may help, since those are sent to the server to tell it what it's allowed to send back.  That would probably be a good move _today_ -- it might make the behavior on google.nl be "English by default", at which point there's no real need to change things.

->WontFix not because there's no issue but because this is being addressed in a different way.

If it all uses google.com I guess it'll respect the google language settings and google.com/ncr will work so it should solve the problem. Thanks. Different domains for the same site in different languages never looked like a wise decision to me, I'm glad Google is gonna use same domain.

For reference, the change to make Chrome route everyone with Google as their default search engine through google.com as opposed to be country-specific domains is being tracked in bug 825255.  Apologies that that bug is only accessible to Google employees.