{"id":82,"date":"2009-02-26T09:54:44","date_gmt":"2009-02-26T17:54:44","guid":{"rendered":"http:\/\/palblog\/?p=82"},"modified":"2009-10-13T20:51:30","modified_gmt":"2009-10-14T03:51:30","slug":"the-searcher-and-the-advertiser","status":"publish","type":"post","link":"https:\/\/blog.fxpal.net\/?p=82","title":{"rendered":"The Searcher and the Advertiser"},"content":{"rendered":"<p>One of my ongoing information retrieval interests revolves around the relationship between the search engine user and the search engine advertiser.\u00a0 In a search engine that is supported by advertising, there is a natural conflict of interest that exists between the users and the advertisers.\u00a0 Users want to find the information that is most relevant to themselves and advertisers want the users to see the information that is most financially rewarding to the advertiser. These two sets of information do not always overlap.<\/p>\n<p><!--more-->Web search engines play a crucial role is mediating this conflict.\u00a0 They often, and vocally, claim that they successfully negotiate between these two interests because they physically separate advertising results from organic results.\u00a0 However, it is sometimes glaringly obvious that separation alone is not enough.\u00a0 In particular, when it comes to user control of advertising results, via the engine&#8217;s own query operators, search engines can and do place the desires of the advertisers (and thus the search engine&#8217;s own financial interests) above the desires of the users.<\/p>\n<p>Take the following concrete example: Imagine a user interested in searching for [cellular phones].\u00a0 However, suppose that this user has done business in the past with (again just for example) Verizon and does not want to do business with them in the future.\u00a0 So the user instructs the engine not to show any results containing the term &#8220;verizon&#8221;.\u00a0 The full query is [cellular phones -verizon].\u00a0 (The minus operator is <a href=\"http:\/\/www.google.com\/support\/websearch\/bin\/answer.py?answer=136861\" target=\"_blank\">defined by the search engine<\/a> as having the following functionality: &#8220;Attaching a minus sign immediately before a word indicates that you do not want pages that contain this word to appear in your results.&#8221;)<\/p>\n<p>The top results returned by the search engine are:<\/p>\n<p><img decoding=\"async\" loading=\"lazy\" class=\"alignnone\" title=\"[cellular phones -verizon] query\" src=\"http:\/\/www.fxpal.com\/people\/jeremy\/wp-content\/focus-on-the-user_crop.bmp\" alt=\"\" width=\"645\" height=\"428\" \/><\/p>\n<p>Verizon is correctly absent from the <em>unsponsored<\/em> results pages.\u00a0 But it is quite present &#8212; ranked at the top in fact &#8212; of the <em>sponsored<\/em> results pages.\u00a0 Both the display text as well as the landing page of that top sponsored result contain the term &#8220;verizon&#8221;.<\/p>\n<p>Verizon is likely a high rate keyword bidder on the phrase [celluar phones].\u00a0 So in the absence of any other information, it is natural that their page gets displayed when that phrase is used as part of a query.\u00a0 There was, however, other information: the [-verizon] term.\u00a0 The search engine user specifically requested that pages with that term not appear.<\/p>\n<p>The search engine summarily ignored that user request and served the advertiser page anyway.<\/p>\n<p>So even though ad result pages are separated from the organic result pages,\u00a0 it is quite clear that there is an ongoing, unresolved conflict between the searcher and the advertiser.\u00a0 And the search engine, rather than focusing on the user&#8217;s needs, placed the needs of the advertiser on top.\u00a0 Quite literally.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>One of my ongoing information retrieval interests revolves around the relationship between the search engine user and the search engine advertiser.\u00a0 In a search engine that is supported by advertising, there is a natural conflict of interest that exists between the users and the advertisers.\u00a0 Users want to find the information that is most relevant [&hellip;]<\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[123],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/blog.fxpal.net\/index.php?rest_route=\/wp\/v2\/posts\/82"}],"collection":[{"href":"https:\/\/blog.fxpal.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.fxpal.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.fxpal.net\/index.php?rest_route=\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.fxpal.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=82"}],"version-history":[{"count":18,"href":"https:\/\/blog.fxpal.net\/index.php?rest_route=\/wp\/v2\/posts\/82\/revisions"}],"predecessor-version":[{"id":122,"href":"https:\/\/blog.fxpal.net\/index.php?rest_route=\/wp\/v2\/posts\/82\/revisions\/122"}],"wp:attachment":[{"href":"https:\/\/blog.fxpal.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=82"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.fxpal.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=82"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.fxpal.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=82"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}