Digg recently released a URL shortener that doesn’t take customers to your website. It wraps your website in a Digg frame instead. This presents a number of challenges.
So what are the challenges?
Analytics gets hit hard. The main victim is the important referral stat. These next-generation URL shorteners obscure where the traffic to your site is coming from. Since the digg.com URL shortener wraps your site in a digg.com frame it is always digg.com that is seen to be requesting your site.
As a result traffic might be coming from Twitter.com, a competitor’s site, an affiliate or even Digg but the referring site will always be credited as Digg.com by many analytic solutions.
In fact, it may appear as if digg.com is driving traffic to your site without the site ever actually being submitted to digg.com. If your social media campaign is using referrals from social sites as a metric then this is a curveball.
Most affiliate terms and conditions prohibit affiliates from wrapping merchant sites in frames. This is done for brand protection reasons, especially to prevent the affiliate from passing off a look-a-like domain as actually being your site.
The frame-based URL shortener may not always display the URL or the full URL of the site being pointed to. For example, an Ow.ly link for bigmouthmedia describes the URL as being http://www.bigmouthmed… and the rest of the address is obscured.
This URL obfuscation means that affiliate tracking codes might be passed around as the short URL is shared. In fact, when the next generation URL shortener is combined with a site like Digg then it is possible a large amount of traffic will be driven to your site in such a way that the affiliate benefits.
It’s worth noting that many forms of affiliate tracking will be immediately visible if the shortener shows any of the “long” URL at all.
The frame style of URL shortener isn’t particularly good news for an SEO campaign either. The best of the first generation of URL shorteners are kind enough to issue a 301 redirect from themselves to the original “long” URL.
If a link from a trusted site to another site counts as a vote from the trusted site to the other then the 301 redirect ensures that as much of that vote passes through the URL shortener and to the intended site as possible. Google requests 301 redirects are used in situations like this.
This is not the case when the URL shortener wraps the target site in a frame. In this scenario the worth of link is not passed through to the target site – it stays with the URL shortener.