Someone have poisend the Google location infos for a VPN I use. So when use VPN, how to tell Google to use different country for results? And I do not want to sign in to Google account. When using VPN with server location in country A, Google give me results for country B that is more than 2000 km away. (Always before, Google gave correct country localization for this VPN, but last month made this change. IP location checkers still say the VPN server activity come from country A not country B.)
Example is if I check Google News, Google give results for country B news but it should be country A news.
I wouldn't mind knowing myself, just to know. I think you might be stuck at whatever VPN location you use though, less they have specific account settings or cookies. Luckily very few sites I use care, and the ones that do- I don't care.
You can try this suggestions (especially no.3): http://www.searchenginejournal.com/how-to-see-google-search-results-for-other-locations/
Thanks for the suggestion. But it does not working. I think someone else who use the same VPN did something that make Google think the VPN server is in that other country.
it's nothing to do with poisoning whatsoever. just check these out: https://www.ivpn.net/knowledgebase/...nected-to-VPN-How-to-disable-geolocation.html https://airvpn.org/topic/12704-goog...ountries-on-certain-airvpn-servers-lu-server/
I do not understand how you know that is not some poisoning. I think maybe a user on that server did something that make Google change its database infos. So now when it sees that server IP addresses, it thinks in different country. Anyway, I want to fix the problem whatever is the cause. Same problem with different browsers. How to disable geolocation on Firefox not helpful. Using /ncr not helpful.
if you believe your vpn service provider's servers are compromised, then you got more important things than that to worry about.
I do not believe the vpn servers are compromised. I think maybe Google associates the server IP address with activity of a user who wanted to be identified as being in a different country.
i still can't see how he manages to do that? what is it you're suggesting, exactly? if you mean like nested chains, then how on earth will google assume that incoming traffic is originating from a country other than that of the last server on the chain?
No. Crude example: I am in Australia. I log in to a Switzerland location vpn server. I go to Google and Google think I am in Switzerland. I check Google news. Google give me Switzerland news. Ian is in Britain and his ISP server is in London area. He log in to same vpn and use same server in Switzerland. He then log in to a Google account from that location, so Google see him in Switzerland. However, he buy some stuffs from companies in Turkey. He email some friends and family in Turkey. He read news and check weather for Turkey. Maybe he also make some settings changes for his geolocation that Google read that put him 'officially' in Turkey for Google purposes. Also, maybe he has mobile phone register in Turkey and his Google account is tie to that mobile phone account. So now I log in to same Switzerland vpn server again. I check Google news. Google give me Turkey news, not Switzerland news! Server not compromised at all. But Google database misdirected!
things don't work the way you describe in geo-location detection. google doesn't monitor your browsing habits and decides whether you're in some certain country. instead it uses several technologies which are described in the articles linked in post #6. your description is valid only in the case when user is signed in to their google account and as long as their browser history and cookies are kept.
Are you by chance using CyberGhost? When I was using CG I had a problem where Google searches came up in different languages even though I was connected to USA servers. Regardless of your service you might want to check what DNS is being used. If the servers are not based in Australia then changing them to ones based in Australia might solve the problem.
apparently it has nothing to do with a kido poisoning the geo-location awareness of some vpn service provider's servers. on the contrary, it's just google's own geo-location verification mechanism is defining some ip addresses or a certain range of ip addresses erroneously.
And why is Google's own geo-location mechanism making error now. Before it was accurate but now is change. How do you know it was not from user poisoning?
maybe this might shed some light on it? https://www.ivpn.net/knowledgebase/114/Why-is-the-location-of-the-server-not-accurate.html