The Coke Vs. Pepsi Challenge: Who Redirects Better?
Both Coca-Cola and Pepsico have seen fit to set up redirects on their homepage URLs—a very common practice among commercial websites. Classically, search optimization experts have advised clients that if their sites perform redirects on pages, they should use only server-side redirection, and it should ideally be a 301 redirect in order to ensure that the search engine can index and rank the destination page properly. However, Google is now handling some non-server-side redirects better than search engines once did—should people worry about 301-ing as much? Using these two big-brand competitors, let’s look at how they’ve set up their redirection to see what’s working and what’s not.
A "redirect" in the online world is a programming instruction delivered to a system which requests an internet resource, such as a web page or image, and the instruction tells the requesting system to "go elsewhere." For instance, if a web page has moved, a redirect could tell a browser that’s requesting that page that the page has been moved temporarily or permanently to a different URL.
A server-side redirect is where the web server replies back to a request, and the response includes the redirection directives in the "http response header." This header is a bit of code that’s invisible to users, and tells the requesting system how to interpret and display the resource—including things such as what language it’s in, what character set to use, compression encoding method, etc.
A few different status code numbers are returned as part of this response. A "200" response means "the request has succeeded," and is the usual response code when a web page is requested and returned in a straightforward manner. A "301" status means the resource has moved permanently, and the header includes a "location" with a new URI (uniform resource identifier) pointing to the new place to retrieve the resource (check out the great illustration on the Power of 301 Redirects from a few days ago). A "302" status means the resource has moved temporarily, and this header message is returned along with the temporary location URI.
You’ll notice that the Coca-Cola Company web site, TheCoca-ColaCompany.com, (geared towards investor relations, publicity releases, and hiring info) is showing up 2nd with nice info in the second search results listing slot (the indented listing is not counted as a true "second" listing in the rankings, but that’s a different story). You can see that it has a great TITLE on the link: "The Coca-Cola Company: Soft Drinks, Energy Drinks, Sports Drinks…". And, the descriptive text below that link is good, too: "Welcome to the official web site of the Coca-Cola Company. You’ve come to the right…".
Yet, oddly, the Coca-Cola marketing site in the top results listing shows only a short link TITLE of the name, and no descriptive text.
The reason is that when Google requests the home page at "www.coca-cola.com", their server is returning a 200 status code, along with some very brief HTML code:
<!DOCTYPE html PUBLIC"-//W3C//DTDXHTML1.0Transitional//EN"
<meta http-equiv="pragma" content="no-cache">
<meta http-equiv="cache-control" content="no-cache">
<meta http-equiv="expires" content="0">
Notice how the HTML returned for the Coke homepage has absolutely nothing between their <BODY> tags! You can also see that there’s no META Description tag—which is the reason why the listing displays no descriptive text below the link in Google’s search engine results pages.
- No on-page keywords other than "Coca-Cola" in the TITLE, are associated with the homepage URL, so some signal potential is being lost. For instance, when you click on the URL, you can see on the final destination page that they list out a menu of languages for Coca-Cola sites. But, do a search for "coca cola en espanol" and this homepage doesn’t come up to the top of the SERP as relevant, nor are any of the natural search results links on the first page of Google results pointing to any of those official Coca-Cola company web sites at the moment.
- PageRank doesn’t transfer to Coca-Cola’s final destination homepage. When you go to "http://www.coca-cola.com/glp/e/index-e.html", the Google toolbar shows zero PageRank! All that link-juice potential is focused on a page containing no real content and no links to their other content pages, so the PR value isn’t being fully exploited or transmitted to the page where it needs to be applied.
Well, perhaps Coca-Cola can afford to get away with this indifference to even basic SEO techniques. So many people link to the site and its sub-pages that some of the other pages still have some strong PageRank. Heck, Coca-Cola’s leading everyone in world-wide name-brand recognition, so they don’t even have to work very hard at some of their marketing stuff. But, if you do click through to the English -> United States page for the site, you’ll see that they have an online store. So, if they optimized a trifle better they could be getting a lot more traffic and associated sales with that store. The bad homepage redirection is preventing the store and other site pages from having as much PageRank as they could.
Now let’s look at what Pepsi is doing.
When you do a search for "Pepsi" in Google, you’ll see their marketing web site, www.pepsi.com, listed first:
In contrast to Coca-Cola’s search result listing, Pepsi’s is displaying a very brief description under the linked TITLE: "Pepsi’s official web site." They also have four "site links" listed under their first listing. Once you click through to "www.pepsi.com", you’ll notice that the page redirects to "http://www.pepsi.com/home.php".
Also, the TITLE tags of the page contain a different text than what Google is displaying in the SERP:
<title>Pepsi USA Flash Check</title>
There’s absolutely no META Description within that initial page code—no text in the page that says "Pepsi’s official web site." Here’s a telling thing about Google’s functionality. If you look in the HTML code of the page that Pepsi’s site redirects the homepage URL to, you’ll see that it’s TITLE contains the actual text that’s being used in the Google SERP:
So, Google has taken the TITLE from the page at "home.php", and associated it with their homepage at www.pepsi.com, exactly as they would if Pepsi had set up a 301 redirect over to home.php!
There’s still not any META Description on that final destination page for Pepsi, but Google’s apparently pulling the descriptive snippet displayed under the link in the SERP from Pepsi’s description text found in DMOZ directory.
Interestingly enough, Google also handles META refreshes fairly fluidly, but that method of redirection should also be avoided in application design for the same reasons outlined above. Google engineers have mentioned to me that Google may apply treatment to Meta refreshes similar to 301 redirects, but this is partly conditional on the time delay coded with the refresh—too much delay, and they would choose not to treat it like a server-side redirect, apparently.
A lot of developers will set up redirects on homepages to accomplish various things with load balancing and handling of application parameters, but it’s really not necessary. I see lots of WebSphere Commerce sites set up in this way, for instance, but even IBM has advised against using non-server-side redirection.
Just because your site and homepage are getting crawled doesn’t mean you should ignore how your application may be redirecting users. If someone passes to your domain name, watch to see if the browser automatically changes the URL before delivering up the homepage. If it does, you have a redirect, and you should then check the redirect to see what it’s doing. You can do this by typing your domain name into a HTTP header "sniffer" or "checker", such as this one. I recommend checking to also see the raw HTML returned by the application as well as the header response. If it returns a 200 status code and the URL is redirecting in your browser, you’ve got a non-server-side redirect going on which is less-optimal. Unless you have so much brand-name recognition like a Coke or Pepsi, you can’t afford to be using less-than-optimal redirection methods.
Opinions expressed in this article are those of the guest author and not necessarily Search Engine Land. Staff authors are listed here.