<?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>Divine Write Copywriting Blog &#187; Usability</title>
	<atom:link href="http://www.divinewrite.com/blog/category/usability/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.divinewrite.com/blog</link>
	<description>All things copywriting - and quite a bit about SEO</description>
	<lastBuildDate>Thu, 27 May 2010 02:58:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Facebook did WHAT?!</title>
		<link>http://www.divinewrite.com/blog/copywriting/facebook-did-what/</link>
		<comments>http://www.divinewrite.com/blog/copywriting/facebook-did-what/#comments</comments>
		<pubDate>Tue, 25 Nov 2008 01:09:05 +0000</pubDate>
		<dc:creator>Glenn (Owner)</dc:creator>
				<category><![CDATA[Copywriting]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[Headlines]]></category>
		<category><![CDATA[Readability]]></category>
		<category><![CDATA[Social Media]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[Web Copy]]></category>

		<guid isPermaLink="false">http://www.divinewrite.com/blog/2008/11/25/facebook-did-what/</guid>
		<description><![CDATA[Today’s ‘Marketing Pilgrim’ announced:
Facebook Note Removes British Juror from Trial

WHO removed her?! Unless Facebook has really extended its reach recently, I’m pretty sure IT didn’t remove the juror. I think it’s far more likely a judge did that! 
The problem with this headline is that it’s written in the active voice but has no ‘Actor’. [...]]]></description>
			<content:encoded><![CDATA[<p>Today’s ‘Marketing Pilgrim’ announced:</p>
<blockquote><p><a href="http://www.marketingpilgrim.com/2008/11/facebook-note-removes-british-juror-from-trial.html" target="_blank">Facebook Note Removes British Juror from Trial</a>
</p></blockquote>
<p>WHO removed her?! Unless Facebook has really extended its reach recently, I’m pretty sure IT didn’t remove the juror. I think it’s far more likely a judge did that! </p>
<p>The problem with this headline is that it’s written in the active voice but has no ‘Actor’. The Actor is the person or thing that actually does something. Clearly that’s the judge, here, not the Facebook note.</p>
<p>So <b>how does a copywriter make such a fundamental error?</b> Probably because of a <b>conflict between a grammar rule and a usability rule</b>. The rules?</p>
<ol>
<li>Grammar rule: Headlines should be active</li>
<li>Usability rule: Make the first two words count</li>
</ol>
<h3>So why the conflict?</h3>
<p>Let me explain. The conventional grammarian wisdom says that headlines should be in the form:</p>
<blockquote><p>Actor does X to Object</p></blockquote>
<p>Now in the Facebook story, the Actor is clearly the judge and the Object is clearly the juror. Facebook didn’t DO nothin’! (Kinda ironic, huh?) </p>
<p>But if we followed this rule, we’d end up with:</p>
<blockquote><p>“Judge Removes British Juror from Trial for Posting Facebook Note”<br />
or<br />
“Judge Removes Juror from Trial Because of Facebook Note.”
</p></blockquote>
<p>Too long, right? </p>
<p>What’s more, what would online visitors see if they were just <a href="http://www.useit.com/alertbox/reading_pattern.html" target="_blank">scanning with the typical F-pattern</a>? Probably just:</p>
<blockquote><p>“Judge Removes”<br />
or<br />
“Judge Removes British”<br />
or<br />
“Judge Removes Juror”
</p></blockquote>
<p>In a legal publication that’d be fine, but in ‘Marketing Pilgrim’, the key subject is Facebook. And in the Active voice construction above, Facebook is shunted right to the end.</p>
<p>As you can see, the copywriter (or copy-editor) is in a bit of a bind.</p>
<p>Their solution? Simply bung Facebook in at the start of the sentence, in place of the Actor, and hope everyone understands what you mean! In order to avoid breaking a usability rule, they’ve broken a grammar rule, making their headline a muddy mess.</p>
<p>Now don&#8217;t get me wrong. I’m not suggesting that grammar’s more important than usability. To the contrary. I believe the only solution WAS to break a grammar rule. Just not the one they broke.</p>
<p>I think the headline should have read something like this. </p>
<blockquote><p>“Facebook Juror Removed from Trial”</p></blockquote>
<p>Yes, I know it’s passive (Object has X done to it), and worse yet, there’s no Actor, but at least it gets the eye-candy up front, and it’s direct and easy to understand.</p>
<p>The reality is that sometimes, passive headlines just work better. Especially online. If you don’t believe me, perhaps you’ll believe leading web usability specialist, Jakob Nielsen:</p>
<blockquote><p>“Selecting the first 2 words for your page titles is probably the highest-impact ROI-boosting design decision you make in a Web project. Front-loading important keywords trumps most other design considerations.” (<a href="http://www.useit.com/alertbox/passive-voice.html">Passive Voice Is Redeemed For Web Headings</a>)
</p></blockquote>
<h3>Wrap up</h3>
<p>The truth is, most readers probably COULD understand the Facebook headline in its current form… if they tried hard enough. But headlines are like ads; if they make the audience work, they usually fail.</p>
<p>The moral to this story? If you’re going to break a rule, break the right one. The one that’ll simply offend a few prescriptive grammarians, not the one that’ll stop readers from clicking through.</p>
<p>Happy copywriting!</p>
<p>PS. <b>What do you think the headline SHOULD have been? Please comment</b> your suggestions.</p>
<p><a href="http://www.divinewrite.com/blog/copywriting/facebook-did-what/#comments">Comment on this post</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.divinewrite.com/blog/copywriting/facebook-did-what/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Google is right to penalize sites that over-optimize internal links</title>
		<link>http://www.divinewrite.com/blog/copywriting/web-copy/google-is-right-to-penalize-sites-that-over-optimize-internal-links/</link>
		<comments>http://www.divinewrite.com/blog/copywriting/web-copy/google-is-right-to-penalize-sites-that-over-optimize-internal-links/#comments</comments>
		<pubDate>Fri, 21 Nov 2008 03:29:36 +0000</pubDate>
		<dc:creator>Glenn (Owner)</dc:creator>
				<category><![CDATA[Audience]]></category>
		<category><![CDATA[Keyword Density]]></category>
		<category><![CDATA[Linking]]></category>
		<category><![CDATA[Readability]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[SEO Copy]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[Web Copy]]></category>

		<guid isPermaLink="false">http://www.divinewrite.com/blog/2008/11/21/google-is-right-to-penalize-sites-that-over-optimize-internal-links/</guid>
		<description><![CDATA[In today’s blog post at Search Engine Journal, Ann Smarty reveals results indicating that Google penalizes sites with over-optimized internal links. 
Specifically, she examined the effect of linking to the Home page using keyword rich anchor text. These results are very instructive (thanks Ann!), and they make a lot of sense. Google is right to [...]]]></description>
			<content:encoded><![CDATA[<p>In today’s blog post at Search Engine Journal, Ann Smarty reveals results indicating that <a href="http://www.searchenginejournal.com/keyword-rich-internal-anchor-text-how-much-is-too-much/8036/" target="_blank">Google penalizes sites with over-optimized internal links</a>. </p>
<p>Specifically, she examined the effect of linking to the Home page using keyword rich anchor text. These results are very instructive (thanks Ann!), and they make a lot of sense. Google is right to penalize sites with over-optimized internal links. Here’s why…</p>
<p>When a visitor first arrives at your site, one of the first things they’re gonna try and do is find the Home page. (Jakob Nielsen: <a href="http://www.useit.com/alertbox/20020512.html" target="_blank">Top Ten Guidelines for Homepage Usability</a>) And when they do, they’ll look for a link, menu or button that says “Home” (or they look for a logo at the top left of the page). They won’t look for a link that says, “Computer Spare Parts Home” or “SEO Copywriter Home” or “Red Tennis Shoes Home.” </p>
<p>So by optimizing links to your Home page, you’re certainly not improving usability. Your optimization is purely an SEO tactic with no visitor benefit. (Indeed, if you replace all straight “Home” links with optimized links, you’d be actively undermining usability.)</p>
<p>Why should this affect your ranking? Simple. Google wants quality, helpful sites in its SERPs. If you make your site less usable, that’s not gonna reflect well on Google, so it makes perfect sense that your ranking will drop as a result.</p>
<p>I hate to say it (well… err… no, actually, I don’t ;-)), but Ann’s results reinforce what good SEO copywriters have been saying for years: “never sacrifice readability for searchability.” It’s also what Google’s been saying all along.</p>
<p>And, although Ann’s results relate to Home page links only, the usability message (and maybe even the penalty) applies to all links. Don’t over-optimize them. Here’s just a few reasons why:</p>
<ol>
<li>79% of users scan; only 16% read word-by-word. (Nielsen: <a href="http://www.useit.com/alertbox/9710a.html" target="_blank">How Users Read on the Web</a>)
</li>
<li>People look for links when scanning a page. (Nielsen: <a href="http://www.useit.com/alertbox/9710a.html" target="_blank">How Users Read on the Web</a>)
</li>
<li>Concise copy is 58% more usable, and scannable copy is 47% more usable. (Nielsen: <a href="http://www.useit.com/papers/webwriting/writing.html" target="_blank">Concise, SCANNABLE, and Objective: How to Write for the Web</a>). Over-optimizing links makes them both less concise and less scannable.
</li>
<li>Low-literacy visitors don’t scan effectively. They tend to read word-for-word. And if the text gets to dense, they look for the next link, often skipping important info in the process. If that link is also dense, they’re more likely to skip it too, resulting in more info skipped. (Nielsen: <a href="http://www.useit.com/alertbox/20050314.html" target="_blank">Lower-Literacy Users</a>)
</li>
<li>The first two words of scannable items, like links, are vital, because they’re often all the visitor sees. They should be words that carry the most information. (Nielson: <a href="http://www.useit.com/alertbox/passive-voice.html" target="_blank">Passive Voice Is Redeemed For Web Headings</a>, <a href="http://www.useit.com/alertbox/print-vs-online-content.html" target="_blank">Writing Style for Print vs. Web</a> and <a href="http://www.useit.com/alertbox/designmistakes.html" target="_blank">Top Ten Web Design Mistakes of 2005</a>) And that generally won’t be your keywords. In most cases, the visitor is already on a page related to your keywords. Starting a link with those same keywords really only tells visitors that the destination page is related to the current page. It doesn’t tell them anything notable about the destination page, so they can decide whether they want to read it. Knowing that it’s related to the current page isn’t enough.
</li>
<li>People love clicking on links; it’s the Internet’s most used feature. (Harald Weinreich, Hartmut Obendorf, Eelco Herder, and Matthias Mayer: <a href="http://portal.acm.org/citation.cfm?doid=1326561.1326566" target="_blank">Not Quite the Average: An Empirical Study of Web Use</a>) So you want to make it easy for them to do what they like, and to find what they’re looking for when they do it.</li>
</ol>
<p>Maybe Google is already taking all of these usability issues into account, maybe it’s not. One thing’s certain though: your visitors sure are!</p>
<p><a href="http://www.divinewrite.com/blog/copywriting/web-copy/google-is-right-to-penalize-sites-that-over-optimize-internal-links/#comments">Comment on this post</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.divinewrite.com/blog/copywriting/web-copy/google-is-right-to-penalize-sites-that-over-optimize-internal-links/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
