<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Umpf blog &#187; Nike</title>
	<atom:link href="http://www.umpf.co.uk/blog/tag/nike/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.umpf.co.uk</link>
	<description>It's like PR, but with a bit more Umpf.</description>
	<lastBuildDate>Sat, 04 Feb 2012 13:34:07 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>http://You.re/SoVain</title>
		<link>http://www.umpf.co.uk/blog/pr/httpyou-resovain/</link>
		<comments>http://www.umpf.co.uk/blog/pr/httpyou-resovain/#comments</comments>
		<pubDate>Wed, 24 Feb 2010 22:28:42 +0000</pubDate>
		<dc:creator>Adrian Johnson</dc:creator>
				<category><![CDATA[PR]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[Nike]]></category>
		<category><![CDATA[social media]]></category>
		<category><![CDATA[Twitter]]></category>
		<category><![CDATA[vanity URL]]></category>

		<guid isPermaLink="false">http://www.umpf.co.uk/?p=576</guid>
		<description><![CDATA[The Umpf blog has been a bit neglected of late (setting up a new agency can be time consuming) and I’ve been meaning to write something interesting for a while. So just when I was looking for an excuse, Nike served one up.  Swoosh.
This week, their football Tweets @NikeFootball (5,000+ Followers) started using a bit.ly [...]]]></description>
			<content:encoded><![CDATA[<p><a rel="attachment wp-att-581" href="http://www.umpf.co.uk/blog/pr/httpyou-resovain/attachment/nike/"><img class="size-full wp-image-581 alignright" title="NIKE" src="http://www.umpf.co.uk/wp-content/uploads/2010/02/NIKE.jpg" alt="NIKE" width="249" height="307" /></a>The Umpf blog has been a bit neglected of late (setting up a new agency can be time consuming) and I’ve been meaning to write something interesting for a while. So just when I was looking for an excuse, Nike served one up.  Swoosh.</p>
<p>This week, their football Tweets <a href="http://twitter.com/nikefootball" target="_blank">@NikeFootball</a> (5,000+ Followers) started using a bit.ly vanity URL <a href="http://bit.ly/writehistorylive" target="_blank">http://bit.ly/writehistorylive</a>.  As you’ll see it takes you to an app on their Facebook Fan page (almost a third of a million fans).</p>
<p>If you’re new to URL shorteners such as bit.ly and is.gd (and there are <a href="http://code.google.com/p/shortenurl/wiki/URLShorteningServices" target="_blank">hundreds</a> of services out there), they take a long URL like <a href="http://www.facebook.com/nikefootball?v=app_10442206389&amp;ref=ts" target="_blank">http://www.facebook.com/nikefootball?v=app_10442206389&amp;ref=ts</a> (which eats up 61 of your 140-chracter Tweet) and shortens it to something like <a href="http://bit.ly/9HQmpy" target="_blank">http://bit.ly/9HQmpy</a> (20 characters). Both direct users to exactly the same place.</p>
<p>So rather than use a short bit.ly link, typically http://bit.ly/ [and then a randomly allocated  set of six alphanumeric characters with letters in upper and lower case], Nike has gone for a vanity title ‘writehistorylive’ to increase social media campaign recognition.</p>
<p>At the time of writing they’d had more than 6,500 clicks on their bit.ly vanity URL.  But see what happens when you click <a href="http://bit.ly/Writehistorylive" target="_blank">http://bit.ly/Writehistorylive</a> or <a href="http://bit.ly/WriteHistoryLive" target="_blank">http://bit.ly/WriteHistoryLive</a>.  The URL is subtly different – you probably wouldn’t even notice if it wasn’t pointed out – but the end result is, of course, not a Nike-endorsed site.  And imagine if there was some darker skulduggery eg <a href="http://bit.ly/writehistoryLive" target="_blank">http://bit.ly/writehistoryLive</a>.</p>
<p>We’ve been advising clients recently on shortened vanity URLs.  One of our recommendations is, if you’re going to use a shortened vanity URL – as opposed to the shortened URL you’re allocated – ensure you secure any obvious alternative spellings, and the basic variations on capital letters.</p>
<p>Clearly, in Nike’s case there are millions of permutations in the use of upper and lower case with a long phrase such as writehistorylive (wRiTEhistorylive, WRITEhistoryliveE, etc etc ), but at least go for the basics: ALLCAPS, CapOnEachNewWord, alllowercase, Capfirstletter.</p>
<p>Of course, the counter argument is that the vanity shortened URL is typically only ever a social media link, so the reader will click straight through and, hence, there’s no need to worry.  But if a phrase is central to a campaign – as I would argue writehistorylive is (why create it in the first place?) – then there’s a credible argument to say the URL could be passed on verbally.</p>
<p>It’s probably only a matter of time before we see an intellectual property court case sparked by a shortened vanity URL.</p>
<p><em>NB: Neither bit.ly, is.gd, Nike (clearly!) nor Adidas are clients of Umpf and all example shortened vanity URLs have been created to demonstrate a point rather than to pass off a brand or marketing campaign.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.umpf.co.uk/blog/pr/httpyou-resovain/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

