Techdirt's think tank, the Copia Institute, is working with the Trust & Safety Professional Association and its sister organization, the Trust & Safety Foundation, to produce an ongoing series of case studies about content moderation decisions. These case studies are presented in a neutral fashion, not aiming to criticize or applaud any particular decision, but to highlight the many different challenges that content moderators face and the tradeoffs they result in. Find more case studies here on Techdirt and on the TSF website.

Content Moderation Case Study: Dealing With Misinformation In Search (2004)

from the misinformation-goes-way-back-online dept

This series of case studies is published in partnership with the Trust & Safety Foundation to examine the difficult choices and tradeoffs involved in content moderation. Learn more &raquo

Summary: Google?s biggest early innovation in search was that it used inbound links as a tool for determining the popularity of a website, and thus what its relevance to a particular search might be. That feature, however, created some side effects that raised concerns about how search results might lead to misinformation, or how the search engine might be gamed.

One of the earliest examples of this was the discovery in 2004 that the first result of a search on the word ?jew? pointed to a blatantly anti-semitic website, Jewwatch. It was widely theorized that the reason for this was that the singular noun ?jew? was more likely to be used by those pushing anti-semitic arguments, rather than the more common adjective ?jewish? or the phrase ?jewish wo/man? etc. Also, the site Jewwatch had been in existence for many years, and had many inbound links from other sources.

Some also believed that the people behind Jewwatch had used an early search engine optimization technique known as ?Googlebombing? to purposefully game the results ? deliberately linking to Jewwatch from other sites, and using the word ?jew? as the link text.

As this result got attention, Google came under tremendous pressure to change the search result, as people accused the company of anti-semitism or deliberately pointing to the Jewwatch site in search results. The Anti-Defamation League sent a letter to Google asking it to explore whether or not its ranking system needed to be changed (though the ADL also posted an article to its own site telling people that it was clear that the result was not intentional, or done for nefarious reasons). Some politicians, including Senator Chuck Schumer, also got involved to pressure Google to change its results.

Decisions to be made by Google:

  • Should the top search results be manually changed when it is discovered they lead to misinformation and hate?
  • Should the algorithm be changed to try to avoid these results?
  • Should the company do nothing and say that the algorithm decides the results, period?
  • Should any decision set a precedent for future decisions, and if so, what policies and guidelines need to be put in place to deal with future cases?
  • Are there other ways to respond to this situation?
  • How should Google handle attempts to game search via things like Googlebombing?

Questions and policy implications to consider:

  • If any changes are made, will lots of others expect similar changes to be made as well?
  • Will making changes lead to questions regarding the credibility of search results and the Google algorithm?
  • What sorts of policies and processes need to be in place to deal with these kinds of requests?
  • Will any changes have other, unintended consequences as well?
  • Are search engine optimization techniques nefarious? Can they be? If so, how do you distinguish between good intentions and bad intentions?
  • If you block certain techniques, such as Googlebombing, will that stop the practice when used for good purposes as well?

Resolution: Google responded by clearly stating that it had no direct intentions to change its algorithm. However, it did decide to provide more information, by using the advertising space above the top result to encourage people to click through for more information about how the results came about:

The company also stated that it would ?explore additional ways of addressing? issues like this ?in the future.?

Perhaps more interesting, however, was that Google?s users took matters into their own hands, and realized that if Jewwatch was Googlebombing, they could use the same tools to diminish the result. A campaign was quickly organized online, with many people linking the word ?jew? to Wikipedia?s page on Judaism, and indeed, this worked to get that result to the top of the rankings.

Over time, Google?s algorithms were adjusted globally to try to diminish the power of Googlebombing for any reason (good or bad). In 2007, the company announced that it believed its algorithm would filter out attempts at Googlebombing. In that discussion, the employees who helped stop the effectiveness of Googlebombing explained why they did so, and how they believed it was better to take a holistic approach (which was more scalable) than responding to individual ?bad? results:

People have asked about how we feel about Googlebombs, and we have talked about them in the past. Because these pranks are normally for phrases that are well off the beaten path, they haven’t been a very high priority for us. But over time, we’ve seen more people assume that they are Google’s opinion, or that Google has hand-coded the results for these Googlebombed queries. That’s not true, and it seemed like it was worth trying to correct that misperception. So a few of us who work here got together and came up with an algorithm that minimizes the impact of many Googlebombs.

The next natural question to ask is “Why doesn’t Google just edit these search results by hand?” To answer that, you need to know a little bit about how Google works. When we’re faced with a bad search result or a relevance problem, our first instinct is to look for an automatic way to solve the problem instead of trying to fix a particular search by hand. Algorithms are great because they scale well: computers can process lots of data very fast, and robust algorithms often work well in many different languages. That’s what we did in this case, and the extra effort to find a good algorithm helps detect Googlebombs in many different languages. We wouldn’t claim that this change handles every prank that someone has attempted. But if you are aware of other potential Googlebombs, we are happy to hear feedback in our Google Web Search Help Group.

Filed Under: , , ,
Companies: google

Rate this comment as insightful
Rate this comment as funny
You have rated this comment as insightful
You have rated this comment as funny
Flag this comment as abusive/trolling/spam
You have flagged this comment
The first word has already been claimed
The last word has already been claimed
Insightful Lightbulb icon Funny Laughing icon Abusive/trolling/spam Flag icon Insightful badge Lightbulb icon Funny badge Laughing icon Comments icon

Comments on “Content Moderation Case Study: Dealing With Misinformation In Search (2004)”

Subscribe: RSS Leave a comment
6 Comments

Add Your Comment

Your email address will not be published. Required fields are marked *

Have a Techdirt Account? Sign in now. Want one? Register here

Comment Options:

Make this the or (get credits or sign in to see balance) what's this?

What's this?

Techdirt community members with Techdirt Credits can spotlight a comment as either the "First Word" or "Last Word" on a particular comment thread. Credits can be purchased at the Techdirt Insider Shop »

Follow Techdirt

Techdirt Daily Newsletter

Ctrl-Alt-Speech

A weekly news podcast from
Mike Masnick & Ben Whitelaw

Subscribe now to Ctrl-Alt-Speech »
Techdirt Deals
Techdirt Insider Discord
The latest chatter on the Techdirt Insider Discord channel...
Loading...
Older Stuff
15:43 Content Moderation Case Study: Facebook Struggles To Correctly Moderate The Word 'Hoe' (2021) (21)
15:32 Content Moderation Case Study: Linkedin Blocks Access To Journalist Profiles In China (2021) (1)
16:12 Content Moderation Case Studies: Snapchat Disables GIPHY Integration After Racist 'Sticker' Is Discovered (2018) (11)
15:30 Content Moderation Case Study: Tumblr's Approach To Adult Content (2013) (5)
15:41 Content Moderation Case Study: Twitter's Self-Deleting Tweets Feature Creates New Moderation Problems (2)
15:47 Content Moderation Case Studies: Coca Cola Realizes Custom Bottle Labels Involve Moderation Issues (2021) (14)
15:28 Content Moderation Case Study: Bing Search Results Erases Images Of 'Tank Man' On Anniversary Of Tiananmen Square Crackdown (2021) (33)
15:32 Content Moderation Case Study: Twitter Removes 'Verified' Badge In Response To Policy Violations (2017) (8)
15:36 Content Moderation Case Study: Spam "Hacks" in Among Us (2020) (4)
15:37 Content Moderation Case Study: YouTube Deals With Disturbing Content Disguised As Videos For Kids (2017) (11)
15:48 Content Moderation Case Study: Twitter Temporarily Locks Account Of Indian Technology Minister For Copyright Violations (2021) (8)
15:45 Content Moderation Case Study: Spotify Comes Under Fire For Hosting Joe Rogan's Podcast (2020) (64)
15:48 Content Moderation Case Study: Twitter Experiences Problems Moderating Audio Tweets (2020) (6)
15:48 Content Moderation Case Study: Dealing With 'Cheap Fake' Modified Political Videos (2020) (9)
15:35 Content Moderation Case Study: Facebook Removes Image Of Two Men Kissing (2011) (13)
15:23 Content Moderation Case Study: Instagram Takes Down Instagram Account Of Book About Instagram (2020) (90)
15:49 Content Moderation Case Study: YouTube Relocates Video Accused Of Inflated Views (2014) (2)
15:34 Content Moderation Case Study: Pretty Much Every Platform Overreacts To Content Removal Stimuli (2015) (23)
16:03 Content Moderation Case Study: Roblox Tries To Deal With Adult Content On A Platform Used By Many Kids (2020) (0)
15:43 Content Moderation Case Study: Twitter Suspends Users Who Tweet The Word 'Memphis' (2021) (10)
15:35 Content Moderation Case Study: Time Warner Cable Doesn't Want Anyone To See Critical Parody (2013) (14)
15:38 Content Moderation Case Studies: Twitter Clarifies Hacked Material Policy After Hunter Biden Controversy (2020) (9)
15:42 Content Moderation Case Study: Kik Tries To Get Abuse Under Control (2017) (1)
15:31 Content Moderation Case Study: Newsletter Platform Substack Lets Users Make Most Of The Moderation Calls (2020) (8)
15:40 Content Moderation Case Study: Knitting Community Ravelry Bans All Talk Supporting President Trump (2019) (29)
15:50 Content Moderation Case Study: YouTube's New Policy On Nazi Content Results In Removal Of Historical And Education Videos (2019) (5)
15:36 Content Moderation Case Study: Google Removes Popular App That Removed Chinese Apps From Users' Phones (2020) (28)
15:42 Content Moderation Case Studies: How To Moderate World Leaders Justifying Violence (2020) (5)
15:47 Content Moderation Case Study: Apple Blocks WordPress Updates In Dispute Over Non-Existent In-app Purchase (2020) (18)
15:47 Content Moderation Case Study: Google Refuses To Honor Questionable Requests For Removal Of 'Defamatory' Content (2019) (25)
More arrow