How Does Your Reputation Look In Google?
[This article originally appeared in PRNews' print newsletter.]
By Shabbir Imber Safdar and Jason Alcorn, Virilion Inc.
“Google never forgets…” -Online magazine Slashdot
“…and that includes all your PR mistakes.” -Your humble authors
Half the people using the Internet today will use a search engine to look something up. So the question of what Google means for your reputation is an important one. (By the way, this isn’t another article about search engine optimization, so keep reading.) If someone criticizes you on a blog in Digital Nowheresville, many PR professionals don’t care until it starts climbing up into the first 3 or 4 pages of Google search results.
Many incidents are known only within niche communities but that won’t stop word of the incident from hitting Google, the biggest community out there. What you want to do is be able to measure how these incidents, once resolved, are affecting your product and your core brand. In this article we look at two online PR crises from the last year and show you how the short-term response affected (or didn’t) the perception of the product line and the core brand in the long term.
Although you may not have heard of these crises, they were serious for each of the brands involved.
Dell Vostro Keyboard
Mistake
In early 2008, Dell shipped a small number of laptop models with the lower row of letters (ZXCVBNM) shifted one letter to the right. As a result, most people typing on the keyboard consistently misspelled any word involving those letters. Two separate recalls were issued, the second one occurring when a keyboard supplier re-shipped the now rejected keyboards for assembly a second time.
The initial posting to flickr.com from new Dell Vostro owner Jake Gordon occurred on May 1, 2008 (Day Zero). It was quickly picked up by online news outlets. Within 24 hours, Dell representatives were posting in the comment areas of these news outlets taking responsibility for the problem and promising to fix all affected laptops. Official blog posts from Dell came on day 7, by which time the mea culpa had already been put out to the market. Dell made good on its promises to replace all affected keyboards.
Now, several months later, what is the history of the event seen through the eyes of the Internet’s memory, Google? How did history write the crisis? Is it affecting the online reputation of the Dell Vostro product line, and more importantly, is it affecting the core Dell brand? We looked at the top 20 search results for the incident using the search phrase “dell vostro keyboard problem” to see how balanced the results were. Then we examined search results for laptop line itself using the search phrase “dell vostro” to see how heavily the incident affects perception of the product line. Finally we searched on the core brand with the simple search phrase “dell”, to see how the incident might affect Dell’s reputation going forward.
The chart below visually demonstrates the top 20 search results for the incident, the product line, and the brand. The graph below is a visual representation of Google Search Results. An ‘Acceptable’ box is a Google search result that isn’t related to the problem. A ‘Mitigated’ box is a criticism of the company regarding the incident that includes mitigating comments from Dell to balance out a reader’s opinion. A ‘Hostile’ box (there are none in this example) represents a criticism that either isn’t answered or isn’t answered satisfactorily.
|
Google Search on: |
||||
|
“dell vostro keyboard problem” |
“dell vostro” |
“dell” |
||
|
Google Result # |
1 |
Mitigated |
Acceptable |
Acceptable |
|
Google Result # |
2 |
Mitigated |
Mitigated |
Acceptable |
|
Google Result # |
3 |
Mitigated |
Acceptable |
Acceptable |
|
Google Result # |
4 |
Acceptable |
Acceptable |
Acceptable |
|
Google Result # |
5 |
Mitigated |
Acceptable |
Acceptable |
|
Google Result # |
6 |
Mitigated |
Acceptable |
Acceptable |
|
Google Result # |
7 |
Acceptable |
Acceptable |
Acceptable |
|
Google Result # |
8 |
Mitigated |
Acceptable |
Acceptable |
|
Google Result # |
9 |
Acceptable |
Acceptable |
Acceptable |
|
Google Result # |
10 |
Mitigated |
Acceptable |
Acceptable |
|
Google Result # |
11 |
Acceptable |
Acceptable |
Acceptable |
|
Google Result # |
12 |
Mitigated |
Acceptable |
Acceptable |
|
Google Result # |
13 |
Acceptable |
Acceptable |
Acceptable |
|
Google Result # |
14 |
Mitigated |
Acceptable |
Acceptable |
|
Google Result # |
15 |
Acceptable |
Acceptable |
Acceptable |
|
Google Result # |
16 |
Mitigated |
Acceptable |
Acceptable |
|
Google Result # |
17 |
Mitigated |
Acceptable |
Acceptable |
|
Google Result # |
18 |
Acceptable |
Acceptable |
Acceptable |
|
Google Result # |
19 |
Acceptable |
Acceptable |
Acceptable |
|
Google Result # |
20 |
Acceptable |
Acceptable |
Acceptable |
As you can see from the chart, it’s impossible to suppress the incident, as it’s now indelibly associated with the product line. But as most PR professionals would hope, as you move away from the incident towards the product line and the core brand, the impact of the incident lessens.
What did Dell do right?
The lesson here is that in every search result that mentions the incident, there’s a statement from Dell taking responsibility and promising a fix. For someone considering buying a Dell computer, this is key. Accidents happen, but Dell will stand behind their product and make good when they do.
A note about Google results: Google results are fluid both from data center to data center and over time. As people find the results above more or less interesting, the results in our searches will change. For companies wishing to get rid of unpleasant news in Google searches about them, this is usually a benevolent event. For companies who wish to never see new bad news appear about them, this is a constant threat.
Creative Threatens Hobbyist
Creative makes a line of sound cards for PCs running Windows. A hobbyist (Daniel K) wrote better software to operate the sound cards for systems running Windows Vista, much to the delight of many unhappy sound card owners using Windows. In March of 2008 Creative became uncomfortable that an unlicensed third party was distributing modified versions of their sound card software and threatened him publicly, only to receive significant customer blowback.
The initial posting from Creative Labs VP of Public Relations Phil O’Shaugnessy criticizing the hobbyist appeared on March 28, 2008.
After several days of criticism, Phil or someone acting as a forum moderator actually altered the original posting to soften their criticism of the third party developer. The alteration caused several members of the forum to repost the original. In addition, Wired news and other outlets ran with the story that Creative Labs had intentionally crippled their product for the Windows Vista platform, an accusation that is especially damaging. Most outlets echoed the product owners’ sentiments, namely that it was shameful that an unaffiliated developer could get the Creative product to perform so much better than the manufacturer itself.
After the initial flurry of controversy, Creative never found a way to address user concerns through public relations and stopped making public announcements. You can see the effect that a lack of satisfactory resolution had in the search results for the incident (“creative labs vista driver problem”), for the product itself (“creative labs sound card”), and for the core brand (“creative labs”) as displayed in the chart of Google search results below.
The graph below is a visual representation of Google Search Results. An ‘Acceptable’ box is a Google search result that isn’t related to the problem. A ‘Mitigated’ box is a criticism of the company regarding the incident that includes mitigating comments from Creative Labs to balance out a reader’s opinion. Note that there aren’t any in this example. A ‘Hostile’ box represents a criticism that either isn’t answered or isn’t answered satisfactorily.
|
Google Search On: |
||||
|
“creative labs vista driver problem” |
“creative labs sound card” |
“creative labs” |
||
|
Google
Result # |
1 |
Hostile |
Acceptable |
Acceptable |
|
Google
Result # |
2 |
Acceptable |
Acceptable |
Acceptable |
|
Google
Result # |
3 |
Hostile |
Acceptable |
Acceptable |
|
Google
Result # |
4 |
Acceptable |
Acceptable |
Hostile |
|
Google
Result # |
5 |
Acceptable |
Acceptable |
Acceptable |
|
Google
Result # |
6 |
Hostile |
Acceptable |
Acceptable |
|
Google
Result # |
7 |
Acceptable |
Hostile |
Acceptable |
|
Google
Result # |
8 |
Acceptable |
Acceptable |
Acceptable |
|
Google
Result # |
9 |
Hostile |
Acceptable |
Acceptable |
|
Google
Result # |
10 |
Acceptable |
Acceptable |
Acceptable |
|
Google
Result # |
11 |
Acceptable |
Acceptable |
Acceptable |
|
Google
Result # |
12 |
Hostile |
Acceptable |
Acceptable |
|
Google
Result # |
13 |
Hostile |
Acceptable |
Acceptable |
|
Google
Result # |
14 |
Acceptable |
Acceptable |
Acceptable |
|
Google
Result # |
15 |
Hostile |
Acceptable |
Acceptable |
|
Google
Result # |
16 |
Hostile |
Acceptable |
Acceptable |
|
Google
Result # |
17 |
Acceptable |
Acceptable |
Acceptable |
|
Google
Result # |
18 |
Hostile |
Acceptable |
Acceptable |
|
Google
Result # |
19 |
Acceptable |
Acceptable |
Acceptable |
|
Google
Result # |
20 |
Acceptable |
Acceptable |
Acceptable |
What did Creative Labs do right?
Almost nothing. In this table, "Hostile" boxes represent Google search results that are unfavorable to Creative Labs and have no adequate or balanced response. The column on the right is the worst of all possible outcomes: an outright criticism of the company is the fourth search result for the core brand. For someone considering purchasing any Creative Labs product, this item will give pause.
Creative Labs had all the options in the world available to them, but they chose a combative route to publicly embarrass and thwart someone who had earned the goodwill of their own customer base. He had, in effect, given customers better customer support than Creative had given, and they publicly took that away from their customers.
This graph shows that today, Creative Labs PR people still have a lot of work to do. This incident is tarnishing the reputation of the entire company.
What Can You Learn From This?
The old cliché that “winners write history” should not just be taken as advice for PR professionals working online, but as a commandment. Communicate in the way you want the world to judge your handling of each incident, knowing that your words will be echoed online by dozens of outlets, large and small, and kept online for years to come.
Just as importantly, don’t forget to actually write it down. At some point be willing to go on the record. All the personal emails, telephone calls and good intentions in the world won’t matter if there is nothing written down for pundits to quote – or for Google to make part of Internet history.
Consider:
- Timing: It’s almost always right to respond in some fashion, if only to set the record straight. The more outlandish the accusation, the less you have to worry about engaging your critic directly. If you don’t get something online for people to find, their criticism will stand unanswered forever.
- Tone: It may seem attractive to vent anger at a critic, as in the case of Creative Labs Phil O’Shaugnessy who publicly threatened a developer, but those words will live forever, even if you try to edit or delete them. Take the higher ground. It will look better a year from now.
- Target: You don’t always have to respond directly to all your critics, but consider that their Web sites will be around for a long time. Wouldn’t it be nice if they would incorporate your response into their article or blog post? Again, give them something to write down.
The cost of screwing up an incident in a big way is a very expensive search engine marketing campaign to try to push the unpleasant results out of the top 10 or 20 in Google. While that’s sometimes doable, do yourself a favor and get it right the first time.
Shabbir, Jason,
Enjoyed the post as always. Another interesting issue touched on in the case of Creative is how to take complex issues and distill them down into a response that "works" on the web. While Creative has a problem providing basic support for Vista (which made their response more difficult), they had some legitimate concerns:
1) If they have licensed IP from a third party but are only licensed to use it on certain products, they could have some legal exposure if they permit Daniel_K to enable those features on an unlicensed product. This is particularly important when this information is available on Creative's own forum sites.
2) I believe Creative was unfairly attacked in the forum and Wired article for a common industry practice- using a single configurable "platform" and selling it at different price points based on which features were enabled (or not). It is simply too expensive to produce distinct hardware and software for the "entry level", "mid range", and "premium" versions of a product. (People will have different opinions on whether or not this is "crippling" products or providing more consumer choice, but that's beyond the scope of this post.)
I would be curious to hear your suggestions (perhaps in a future blog entry?) on how to respond online to situations when the underlying business issues are more complicated than most people appreciate, particularly in a medium where people are used to short, bite-size (byte-sized? :-) answers. The challenge of describing complex things to ordinary folks appears in many situations (e.g. technical or financial court cases), but I would think it would be particularly challenging to address on the web.
Thanks,
Chris
Posted by: Chris Durand | November 14, 2008 at 09:29 AM
Chris,
I think your #1 point is right. They were liable and couldn't look the other way.
Your #2 is a problem. That may be a fairly standard industry practice, but I don't think consumers are wild about it. When actually explained to them, I think consumers resent this business model. In this case it was laid bare and they didn't appreciate it. Consumers like to exchange money for something of value. When they perceive that they've bought something that would be very easy to turn on or not, they get resentful.
If I were Creative I would have lined up all my legal weapons, and then taken DanielK aside and gotten him in line before I went out into the community. A sufficient threat of copyright infringement, held at bay as long as he's cooperating, would have allowed them to go out to the community ostensibly together, saying, "We're working with DanielK to address the concerns about features in our product that is in line with our other licensing agreements."
Airing that conflict in the forums in front of unsympathetic users, without having DanielK reigned in, was the critical mistake, and frankly, an unrecoverable one.
Posted by: Shabbir | November 14, 2008 at 10:04 AM