Google’s search engine ignores Google Local
A few weeks ago I asked Is localisation affecting your search engine performance? Obviously, moving a site with a .com domain to a UK-based server will solve the problem of getting the google.co.uk UK rankings.
But my colleague Paul Silver wondered if we we could find another way of establishing this blog’s UK provenance. We ended up registering Dangerous Thinking on Google Local, so Google knew that the blog had a real physical UK location.
We sat back and waited to see if Google Search picked up on the Google Local registration. Some six weeks later, it hadn’t, so we’ve concluded Google Search does not reference Google Local.
Whether Google will join up the two services in the future, I don’t know – it seems very logical to. But they don’t appear to work together now.
Edit (20 November 2007): Burrowing back into my RSS feeds (I always read the most up-to-date ones first), I found Google’s answer to search localisation in a post on the Webmaster Central Blog back in August called Server location, cross-linking, and Web 2.0 technology thoughts.
Here we go:
Does location of server matter? I use a .com domain but my content is for customers in the UK.
In our understanding of web content, Google considers both the IP address and the top-level domain (e.g. .com, .co.uk). Because we attempt to serve geographically relevant content, we factor domains that have a regional significance. For example, “.co.uk ” domains are likely very relevant for user queries originating from the UK. In the absence of a significant top-level domain, we often use the web server’s IP address as an added hint in our understanding of content.
So, there we are. IP and top-level domain.


Recent Comments