You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am noticing when calling SEOstats\Google::getSerps('search_term', 10);, the search results are (very slightly) different when performed from Melbourne, Australia (on my local computer) versus Sydney, Australia.
General information on this phenomenon is available here:
Other than using a proxy (such as Squid) by configuring CURLOPT_PROXY and CURLOPT_PROXYUSERPWD or originating my requests from Melbourne, Australia - is there any way to solve this?
The second article link provided above seems to indicate that adding &near=cityname to the query string request might help to return the results expected for your local state/city.
The text was updated successfully, but these errors were encountered:
jamesspittal
changed the title
SEOstats\Google::getSerps('search_term', 10) slightly different when searching from "Sydney, Melbourne" versus "Melbourne, Australia"
SEOstats\Google::getSerps('search_term', 10) slightly different when searching from "Sydney, Australia" versus "Melbourne, Australia"
Dec 4, 2016
Tested appending near=Melbourne to the request and the results did change slightly, but they are still not consistent with what I'm seeing when searching from a clean browser request (no cookies, no history, logged out, incognito, etc.).
I am noticing when calling
SEOstats\Google::getSerps('search_term', 10);
, the search results are (very slightly) different when performed fromMelbourne, Australia
(on my local computer) versusSydney, Australia
.General information on this phenomenon is available here:
https://gofishdigital.com/google-results-change-location/
http://searchengineland.com/localize-google-search-results-239768
Other than using a proxy (such as Squid) by configuring
CURLOPT_PROXY
andCURLOPT_PROXYUSERPWD
or originating my requests fromMelbourne, Australia
- is there any way to solve this?The second article link provided above seems to indicate that adding
&near=cityname
to the query string request might help to return the results expected for your local state/city.The text was updated successfully, but these errors were encountered: