If you’re not a provider of local search services you may want to skip this one as it’s very inside baseball.
When I see someone blogging about geotargeting it usually refers to making sure that a site provides relevant information for the user’s physical location. However, some sites use a technique called “geotargeting location by IP address” to serve up different content to a user based on where the geotargeting software thinks the user is. The idea is that if the software thinks you’re in Tuscon then it will serve you Tuscon content. For the user it can make them feel like the page or site is tailored specifically to them.
This is all well and good except that I have seen this kind of implementation wreak havoc on site optimization, particularly on local search optimization.
The problem occurs when the geotargeting occurs on a single URL (i.e. the person in Tuscon is on the same page as the person in Fresno except each sees content specific to their location such as “best restaurants in…”). Search engine spiders tend to enter a site from a variety of different IP addresses/locations. So one day Google may think a URL is about Tuscon (because it entered via a Tuscon IP address) and another day it may think the URL is about Fresno (because it entered via a Fresno address). This causes two major issues:
1. Google will rank the page (and probably the entire site) for the last location it identified since each page can only have a single location for any given session. So the site may have content for the entire country but it will likely only rank for one city at a time (usually Mountainview, CA - home of Googlebot’s main IP address).
2. Users who click on a link from a search engine to the site and are not in the last location identified will have a jarring experience (e.g. someone traveling to Tuscon but living in Los Angeles will click on a Tuscon link in Google and might get Los Angeles content).
So if a product manager suggests you do some geotargeting by IP address you may want to make sure he/she thinks through this issue before proceeding. As you can see on Insider Pages, when we implemented geotargeting we did it only in the search box to avoid this issue.
If you are having problems with geotargeting on your site please drop me a email at localseo at localseoguide.com.
12 responses so far ↓
1 Boris // Oct 16, 2007 at 12:12 am
Well, How interesting… I am in Tucson and I practice Geo-Targeting for all my clients. Our work simply involves location, location, and location… Which is Tucson. Since I only work the local market, it always amazes me when I read how difficult SEO can be beyond our business model. That is why I like local so much… It’s simple and straight forward… And much easier to get great results. The downside is we have to work harder on the educational component of our marketing plan. Tucson is quit ready for SEO prime time!
2 Andrew Shotland // Oct 16, 2007 at 8:41 am
Boris I believe the town fathers of Tuscon would be proud of your boosterism.
3 Hawaii SEO // Oct 16, 2007 at 4:15 pm
It depends on how you serve the personalized content. You can serve the personalized content onto the page in an iFrame and Google shouldn’t care. Many people serve personalized content this with ad servers. There are some fairly cheap ad servers out there like AdButler which can detect geo-location and serve a pre-selected message to that segment as well as a different message per referring URL. The more segmented you get, the better it seems to work but the grater the labor requirement to manage. At some point, you might run into diminishing returns.
4 Andrew Shotland // Oct 16, 2007 at 8:06 pm
Hawaii, you’re quite right if you are talking about serving a module of content inside a page. The problem arises when you use geotargeting to set the location for the Title, H1, etc.
5 October ‘07: Best Search/Marketing Posts » Small Business SEM // Oct 31, 2007 at 10:40 pm
[…] Andrew/Local SEO Guide: Geotargeting Location by IP Address = SEO Death […]
6 Lucio Dias ribeiro // Nov 1, 2007 at 7:45 pm
Hi Andrew, beauty of article mate!
I’d suggest target using subpages with a piece of PHP and ASP code to solve the problem.,
Depending on what you want to do a good solution is to use the new tool on webmaster tools “Set geographic target” allowing you to associate a particular geographic location with your site if you are targeting users within that area.
Cheers
Lucio Dias Ribeiro
Marketingeasy(dot)net
7 Yelp SEO Analysis: Part One // Nov 12, 2007 at 6:04 am
[…] More City Links on the Home Page Old Home Page: They used to show links to a couple of cities and then offer a “more cities” option that takes you to a city directory. I am not certain, but I think they may have been using your IP address to show you information for your city on the homepage. For more about why this is a no-no check out Geotargeting Location by IP Address = SEO Death. […]
8 Does Close Enough Really Count? | LocalPoint - Perspectives on the Local Internet // Nov 19, 2007 at 5:01 pm
[…] of the users having to pick/change on first visit, the 80% was a reasonable win. A recent post at http://www.localseoguide.com/geotargeting-location-by-ip-address-seo-death/ (written by one of our faithful readers, which I’m sure will spark more commentary!) has made […]
9 Victoria BC Photographer // Nov 28, 2007 at 11:46 pm
Thats right up there with using Web 2.0 / Javascript to serve up content
But as long as there are bad SEOs, and designer / developers we will all be in business 
10 SEMMYS // Jan 15, 2008 at 10:47 am
[…] Geotargeting Location by IP Address = SEO Death Andrew Shotland, Local SEO Guide | 10/14/07 […]
11 How To Judge The SEMMYS // Jan 15, 2008 at 11:09 am
[…] Geotargeting Location By IP Address = SEO Death […]
12 Understanding Google Maps & Yahoo Local Search » Nominees in Local Search category: 2008 SEMMY Awards | Developing Knowledge about Local Search // Jan 15, 2008 at 11:22 am
[…] Geotargeting Location by IP Address = SEO Death Andrew Shotland, Local SEO Guide | 10/14/07 […]
Leave a Comment