Welcome back to my series on fixing canonical URL issues. In my last post, Fixing un-canonical URLs. Oh joy! Part 3, I discussed how case-insensitivity and having a default index file could negatively affect your URL canonicalization efforts. Today, we’ll talk about query strings and how they can affect your canonicalization efforts. A query string is a grouping of parameters and values at the end of your URLs that looks like “?podID=249&catID=31”. Let’s review the areas where your site can have un-canonical URLs:

1. Protocols (http and https)
2. Domain and subdomain names (sometimes referred to as host names)
3. URL paths
4. File names
5. Case sensitivity (when myPage.html is handled differently than MYPage.HTML)
6. Query strings
7. Combinations of any or all of the above

Let’s say you have a web page that is used as a landing page and you want to track which of your affiliates referred some visitors to your site. You give each of your affiliates the URL to that page, but add a customized query string to the URL that contains the name of that particular affiliate. The landing page, like many web pages, will show the same generic content regardless of the query string in its URL, but may have another section of the page that does change (even if it’s unnoticeable by a visitor or a search engine) depending on the query string. Your landing page tallies (in a database) the number of visits from each affiliate to the landing page. Though the treatment of URLs with query strings may vary from search engine to search engine, they have the ability to cause different content to show while using the same domain and URL path. You should consider query strings in your efforts to rid your site of duplicate content.

In addition to tracking affiliates and referrer sources, query strings are also used by web applications to display dynamic content from different sections of a site using the same page template or layout. In fact, this is the most common use of query strings in URLs. With this scenario, you can see that query strings allow the web page creator to show a variety of content dynamically while maintaining just one file instead of maintaining one static web page file for each set of content he or she wants to show. A good example of this is an ecommerce site.

If you happen to have a web page that shows one set of contents using one URL plus query string and the same set of contents using the same URL but a different query string, you may have an un-canonical URL issue.

To fix this, you probably don’t want to blindly 301-redirect all URLs that have query strings to the same, respective URLs with the query string chopped off for the simple reason that someone or something probably intended for those query strings to do something meaningful.

One pretty rare exception can be encountered when browsing a site that must remember something about you during your time browsing session. Usually, cookies are used to keep track of which visitor has which products in their shopping cart by storing your unique visitor session number. If the visitor’s web browser is set up to not accept cookies or the ecommerce application is not setup to use cookies, the session number may be appended to every URL the visitor uses to browse the store. That URL may look like: http://www.eample.com/store/privacy_policy.aspx?SESSID=233493JJG37272HB. If cookies were being used, the exact same content would show for any page you visit on that site, but the URL would simply not have the “?SESSID=233493JJG37272HB” part at the end.

Because, under normal circumstances, you want to use the query string appropriately in your web pages, one safe method to canonicalize URLs with query strings (that show the same content) is to add a robots meta tag that instructs the search engines to not index the page. This will work as long the same URL without the query string does not have the robots meta tag. Many times, however, there is a low chance that the URL with a query string is even known to the search engines because you would not publish that URL anywhere.

Another way to canonicalize URLs with query strings is to create SEO-friendly versions of these URLs. Creating SEO-friendly URLs would normally take a URL like http://www.eample.com/store/podID=249&catID=31 and turn it into something like http://www.eample.com/store/cellphones/nokia-8851-clam-shell-camera.html. It doesn’t make sense to create SEO-friendly versions of URLs such as http://www.eample.com/?affiliateID=1446545 because changing the affiliate ID in the query string would probably not change the content of the page substantially. There are various ways to create SEO-friendly URLs. Your CMS may already offer this. If you’re not using a CMS that supports this, you may have to resort to creating URL rewrite rules for your website. (The first part of this series has several links to resources about URL rewriting for both Microsoft IIS and Apache web servers.)

As the topic of query strings is the last item in the 7-item list above, my next post will wrap up this series and provide some tips in your efforts to rid your side of un-canonical URLs.

As most of us are aware, Google is the leader in terms of search market share. Regardless of where you look, this is the case. Although Google has held this lead strong for quite some time, it appears that Microsoft is trying to catch up by offering incentive-based programs in hopes of attracting more searchers.

Initiating these types of programs is not a new tactic for Microsoft.  MSN’s Search and Win, Live Search Club, Search and Give, and Live Search Cashback are few of their previous programs.  Their latest program is called SearchPerks.  SearchPerks is essentially a point system where users can earn “tickets” based on the number of searches conducted.

So how does it work?  To begin, a “Perk Counter” must be downloaded. This Perk Counter is designed to track search activity and award “tickets” for the number of searches performed on Microsoft’s Windows Live, MSN or Live Search. (A maximum of 25 tickets can be earned in a day.) One thing to note is that the actual search queries and the websites visited are not tracked.

At the end of the program, searchers have the opportunity to trade in their tickets and redeem prizes. These prizes vary based on the number of points accumulated. By simply participating in the program, the searcher will initially receive 500 tickets.

There are, however, a few drawbacks to the SearchPerks program. First, it requires a Microsoft browser, Internet Explorer 6.0 or higher, and a Windows PC.  Secondly, it may entice searchers to consider Live Search for their immediate searching needs, but will it make this their search engine of choice in the log run?  What will happen when Microsoft stops offering incentives? Lastly, what about those who participate in the program and just type random characters into the query box in an effort to receive more tickets?

Microsoft has acknowledged that SearchPerks is not designed to actually keep searchers searching. Instead, the primary goal of the program is to create awareness about Live Search, to introduce the search engine to new users, and to build loyalty. Overtime, they would of course like to see searcher’s behaviors and perception of Live Search shift in their favor.

My curiosity regarding the program’s limitations with regard to browser compatibility as well as my question about random characters counting as searches still remain. It will be interesting to see how yet another incentive-based program for Microsoft turns out.

A new version of Flash. Internet Explorer 8, Google Chrome, and a brand new Adobe Creative Suite! When it is all going to end?

If you’re like most office-bound professionals, you use the internet all day, for a myriad of tasks. Transferring files, viewing websites, and sharing data are part of our daily workflow, and when technologies don’t sync, it can seriously impact performance. I’m sure we’ve all had it happen; you send a file, but the receiving party can’t open it because they have an older version of the same software!
The issue is compounded when you add more complex programs, like Creative Suite Graphics programs, and also when you add multiple functionalities and programs. Having an outdated Java applet and Flash player 6 on an old version of Internet Explorer is paramount to rendering the site yourself with crayons! There’s no way you can view sites correctly.

Unfortunately, since technology updates usually bring improvements and upgrades, all we can do is embrace them and keep on upgrading. Most software will alert you when an upgrade is ready. I must stress how important it is to stay current with these changes. Setting some time every week to keep your computer up to speed will prevent a snowball effect later on. Or worse still, a computer stuck in 2004!

In contrast, many of us routinely use programs that cost hundreds of dollars that often involve a purchasing/invoicing/approval rigmarole to procure and upgrade.  Systems like MS Office, Quick Books, Creative Suite, are updated every few years, and may cost hundreds of dollars to replace. Adobe, for example, has let only 8 months lapse since CS3 and we are now faced with the launch of CS4.

Understandably, many companies and individuals can’t afford to keep up with this breakneck pace. But you should try to stay current, even if it means purchasing every second upgrade, or sticking to an ‘upgrade every 2 years’ policy. If budget and purchasing is a problem, keep management in the loop about expected updates, or add the anticipated cost into your budget early. Most companies announce upgrades a few months before launch, which may give you time to make the necessary calls and gain approvals. Check Adobe[http://www.adobe.com/aboutadobe/pressroom/], Microsoft[http://www.microsoft.com/en/us/default.aspx], Intuit’s[http://quickbooks.intuit.com/product/accounting-software/upgrade-quickbooks/index.jsp], Press Releases and Blogs periodically to stay informed.

Upgrades are here to stay, and they will doubtlessly keep coming at record speed. Doing your best to add upgrading into your weekly schedule will only benefit you and your workflow in the long run. So go ahead, check for updates!