You missed answering the question "What's the best way to do this?". You explained how not to do it.
My suggestion would be to have unique URLs for each of your IP targeted iterations of your site and redirect the user based on their IP. If appropriate, offer a way for the user to get to the other iterations as IP geo-targeting is not aways very accurate.
Apache can do it if you have a set IP. But you would probably have to use a server-side language (ie. PHP) to take the IP from the request, check it against a geo lookup server and then do then have the server-side language do the redirect.
Thanks, I have an list of IP ranges from a country, and achieving in Apache would be more suitable for me. But I don't see how to preform the redirect? - I can block a range of IP's, or blanket redirect when a specific URL is requested, but can see how to be selective on Geo location using .htaccess.??? Confused! :)
Aha! - Thinking around the issue, I could perfom a blanket redirect using .htaccess, to a php page which filters (server side) , to the page/s I wish to serve to people in different contries. This way, I don't think I will be classed as cloaking, as the IP that googlebot has comefrom will indeed see the correct contenc. Does this make sense? - Now I just need to work out how to do the GeoLocate in a php page! - Any tips? :)
For people who are still expressing their reservations, what Matt is basically saying is don't try to serve content to the Googlebot which is different from what regular users are getting.
That's cloaking, unless I got it all terribly wrong ...
Just a question, perhaps a bit off-topic:
From a SEO point of view, what is better, to use JavaScript for Geo-redirection or do the redirect on the server?
oh, matt! I am ready to cry. Most googlebots use IPs located in Mountain View CA. Thus GOOG pollutes its index of any website that tries to improve user experience via geo-context IP Delivery. These all will present as sites 'about' CA.
The pollution also affects adsense, which will display ads for SFO on geo-sensitive sites. This likely loses GOOG $. One must special-case and risk penalty, or rework site 2 b text tree. its been that way for years!
Does GoogleBot scan from differing country IP addresses other than the US? If not, surely only the US version of your example site would get indexed. How would you index the other country's versions?
Hay Matt,
You missed answering the question "What's the best way to do this?". You explained how not to do it.
My suggestion would be to have unique URLs for each of your IP targeted iterations of your site and redirect the user based on their IP. If appropriate, offer a way for the user to get to the other iterations as IP geo-targeting is not aways very accurate.
mountainash 2 years ago
How do you actually redirect the user based on IP (using Apache). Using a .htaccess file and re-write? - or redirect?
MegaLoMonkey 2 years ago
Apache can do it if you have a set IP. But you would probably have to use a server-side language (ie. PHP) to take the IP from the request, check it against a geo lookup server and then do then have the server-side language do the redirect.
mountainash 2 years ago
Thanks, I have an list of IP ranges from a country, and achieving in Apache would be more suitable for me. But I don't see how to preform the redirect? - I can block a range of IP's, or blanket redirect when a specific URL is requested, but can see how to be selective on Geo location using .htaccess.??? Confused! :)
MegaLoMonkey 2 years ago
Aha! - Thinking around the issue, I could perfom a blanket redirect using .htaccess, to a php page which filters (server side) , to the page/s I wish to serve to people in different contries. This way, I don't think I will be classed as cloaking, as the IP that googlebot has comefrom will indeed see the correct contenc. Does this make sense? - Now I just need to work out how to do the GeoLocate in a php page! - Any tips? :)
MegaLoMonkey 2 years ago
From the minute of 1.30, it's a very clear example between IP delivery and Cloaking.
What I've learned between cloaking, Geography or IP base delivery.
IP delivery is based on delivery content which based on IP content address.
Cloaking is showing different content to users than showing to googlebot. Cloaking is a type of IP delivery but not IP delivery is cloaking.
A type of IP delivery which is not cloaking is showing;
1. different content
2. different users
3. different countries.
MichaelDadona 2 years ago
our site is only available from US and Uk ip.
and we show under construction page to Asian IP so would google penalize our website
takeallfree 2 years ago
I'd block googlebot from viewing it using robots.txt...
Andbac 2 years ago
Thank you for the clarification.
For people who are still expressing their reservations, what Matt is basically saying is don't try to serve content to the Googlebot which is different from what regular users are getting.
That's cloaking, unless I got it all terribly wrong ...
Just a question, perhaps a bit off-topic:
From a SEO point of view, what is better, to use JavaScript for Geo-redirection or do the redirect on the server?
RafaelMinuesa 2 years ago 2
thanks Matt, very helpful :)
AzizNatour 2 years ago
oh, matt! I am ready to cry. Most googlebots use IPs located in Mountain View CA. Thus GOOG pollutes its index of any website that tries to improve user experience via geo-context IP Delivery. These all will present as sites 'about' CA.
The pollution also affects adsense, which will display ads for SFO on geo-sensitive sites. This likely loses GOOG $. One must special-case and risk penalty, or rework site 2 b text tree. its been that way for years!
manfmnantucket 2 years ago
Does GoogleBot scan from differing country IP addresses other than the US? If not, surely only the US version of your example site would get indexed. How would you index the other country's versions?
devji79 2 years ago 11
all google bots are using a US IP address.
finalwebsites 2 years ago