WO2010008800A2 - Query identification and association - Google Patents

Query identification and association Download PDF

Info

Publication number
WO2010008800A2
WO2010008800A2 PCT/US2009/048159 US2009048159W WO2010008800A2 WO 2010008800 A2 WO2010008800 A2 WO 2010008800A2 US 2009048159 W US2009048159 W US 2009048159W WO 2010008800 A2 WO2010008800 A2 WO 2010008800A2
Authority
WO
WIPO (PCT)
Prior art keywords
query
candidate
page
candidate query
web
Prior art date
Application number
PCT/US2009/048159
Other languages
English (en)
French (fr)
Other versions
WO2010008800A3 (en
Inventor
Ramananthan V. Guha
Shivakumar Venkataraman
Vineet Gupta
Gokay Baris Gultekin
Pradnya Karbhari
Abhinav Jalan
Original Assignee
Google Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Google Inc. filed Critical Google Inc.
Priority to AU2009271386A priority Critical patent/AU2009271386A1/en
Priority to CA2729067A priority patent/CA2729067A1/en
Priority to CN200980131937.XA priority patent/CN102124462B/zh
Priority to JP2011516497A priority patent/JP5542812B2/ja
Priority to BRPI0914623A priority patent/BRPI0914623A2/pt
Priority to EP09798466A priority patent/EP2313839A4/en
Publication of WO2010008800A2 publication Critical patent/WO2010008800A2/en
Publication of WO2010008800A3 publication Critical patent/WO2010008800A3/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • G06Q30/0241Advertisements
    • G06Q30/0251Targeted advertisements
    • G06Q30/0255Targeted advertisements based on user history
    • G06Q30/0256User search
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/951Indexing; Web crawling techniques
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising

Definitions

  • the Internet enables access to a wide variety of web documents, e.g., video and/or audio files, web pages for particular subjects, news articles, etc. Such access to these web documents has likewise enabled opportunities for targeted advertising.
  • web documents of particular interest to a user can be identified by a search engine in response to a user query.
  • the query can include one or more search terms, and the search engine can identify and, optionally, rank the web documents based on the search terms in the query and present the web documents to the user (e.g., according to the rank).
  • This query can also be an indicator of the type of information of interest to the user.
  • the targeted advertisements can include links to landing pages, and the selection of a link can cause the landing page to be displayed on a web browsing device.
  • Advertisers typically attempt to anticipate the specific queries submitted by users that may be related to the advertiser's product or service offered.
  • the keywords specified by advertisers can include keywords related to the product or service offered by the advertiser. These keywords can be broadly matched to the product or service offered by the advertiser, e.g., the keyword “flower” may broadly match to "florist” in a web document. Such broad matching can, however, produce less than desirable results (e.g., fewer conversions).
  • an advertiser may not identify a particularly relevant keyword (referred to as a "missing keyword"). Thus, a query including a missing keyword may be deemed less relevant to the advertiser's content. Accordingly, specific queries for products may sometimes not result in the selection of advertisements linking to landing pages that are highly relevant to the query.
  • one aspect of the subject matter described in this specification can be embodied in methods that include the actions of identifying a candidate query from queries stored in a query log; generating relevancy scores for a plurality of web documents, each relevancy score associated with a corresponding web document and being a measure of the relevance of the candidate query to the web document; selecting a web document having an associated relevancy score that exceeds a relevancy threshold; and associating the selected web document with the candidate query.
  • Other embodiments of this aspect include corresponding systems, apparatus, and computer program products.
  • Another aspect of the subject matter described in this specification can be embodied in methods that include the actions of defining query extraction criteria, the query extraction criteria configured to identify queries related to a subject relevance; identifying a candidate query from the queries stored in a query log according to the extraction criteria; generating relevancy scores for a first set of web documents, each relevancy score associated with a corresponding web document in the first set of web documents and being a measure of the relevance of the candidate query to the web document; selecting web documents having an associated relevancy score that exceeds a relevancy threshold; and generating a query-page candidate tuple from the selected web documents and the candidate query.
  • Other embodiments of this aspect include corresponding systems, apparatus, and computer program products.
  • Fig. 1 is a block diagram of an example online environment.
  • Fig. 2 is a block diagram illustrating an example operational process.
  • Fig. 3 is a block diagram showing an example extraction process.
  • Fig. 4 is a block diagram of an example candidate query-page process.
  • Fig. 5 is a block diagram of an example filtering process.
  • Fig. 6a is a block diagram illustrating an example association of query-page tuples with advertisements.
  • Fig. 6b is a block diagram illustrating an example association of query-page tuples with an existing advertisement.
  • Fig. 6c is a block diagram illustrating another example association of query-page tuples with an advertisement.
  • Fig. 6d is a block diagram illustrating another example association of a query-page tuple with an advertisement.
  • Fig. 7 is a block diagram illustrating an example association of query-page tuples with a query category.
  • Fig. 8 is a flow diagram of an example process for identifying query-page candidate tuples.
  • Fig. 9 is a flow diagram of an example process for query extraction.
  • Fig. 10 is a flow diagram of an example process for filtering query-page candidate tuples.
  • Fig. 11 is a flow diagram of an example process for associating a query-page tuple with an advertisement group.
  • Fig. 12 is a flow diagram of an example process for associating a query with a category.
  • Fig. 13 is an example computer system.
  • Fig. 1 is a block diagram of an example online environment 100.
  • the online environment 100 can facilitate the identification and serving of web documents, e.g., web pages, advertisements, etc., to users.
  • a computer network 110 such as a local area network (LAN), wide area network (WAN), the Internet, or a combination thereof, connects advertisers 102, a search engine 112, publishers 106, and user devices 108.
  • Example user devices 108 include personal computers, mobile communication devices, television set-top boxes, etc.
  • the online environment 100 may include many thousands of advertisers, publishers and user devices.
  • a user device such as user device 108a, can submit a search query 109 to the search engine 112, and a search results page 111 can be provided to the user device 108a in response to the search query 109.
  • the search results page 111 can include one or more links to web documents provided by the publishers 106.
  • the search query 109 can include one or more search terms.
  • a search term can be of the form of one or more keywords submitted as part of a search query through a search engine 112 that is used to retrieve responsive search results.
  • a user of the user device 108a can search for an online store to purchase a star shaped cake pan.
  • the search query 109 submitted can be for "star cake pan.”
  • the search terms in this example can be "star,” "cake,” and "pan.”
  • the publishers 106 can include general content servers that receive a request in the form of the search query 109 for content (e.g., web documents related to articles, discussion threads, music, video, graphics, other web document listings, information feeds, product reviews, etc.), and retrieve links to content on the search results page 111 in response to the search query 109.
  • content servers related to news content providers, retailers, independent blogs, social network sites, products for sale, or any other entity that provides content over the network 110 can be a publisher.
  • the search engine 112 can index the content provided by the publishers 106 and advertisers 102 (e.g., an index of cached web documents such as web index 120) for later search and retrieval of search results 118 that are relevant to the queries.
  • An exemplary search engine 112 is described in S. Brin and L. Page, "The Anatomy of a Large-Scale Hypertextual Search Engine," Seventh
  • Search results can be identified and ranked by various relevancy scores, e.g., information retrieval ("IR") scores based on text of cached and indexed web documents, feature vectors of identified documents, and other search processing techniques.
  • IR scores can be computed from, for example, dot products of feature vectors corresponding to a query and a document, page rank scores, and/or combinations of IR scores and page rank scores, and so on.
  • the search results 118 can include, for example, lists of web document titles, snippets of text extracted from those web documents and hypertext links to those web documents, and may be grouped into a predetermined number (e.g., ten) of search results. Search results 118 can also be ranked by the search engine 112, and presented as content on the search results page 111.
  • the search terms in the search query 109 control the search results 118 that are provided by the search engine 112 through the search results page 111.
  • the search engine 112 can retrieve and rank search results 118 based on the search terms submitted through a search query 109. For example, a search query for "star cake pan” can produce search results that are related to online retailers of cake pans, based on the search terms "star,” "cake,” and "pan.”
  • the search results page 111 can include advertisements 116, or can include executable instructions, e.g., JavaScriptTM instructions, that can be executed at the user device 108a to request advertisements 116 over the network.
  • the advertisements 116 can be in the form of graphical advertisements, such as banner advertisements, text only advertisements, image advertisements, audio advertisements, video advertisements, advertisements combining one of more of any of such components, etc., or any other type of electronic advertisement document.
  • the advertisements 116 also include embedded information, such as a links to landing pages. Any web document can be a landing page; a landing page is any web document that is, or can be, linked to from another web document, advertisement, or search result.
  • the landing page can be a web document that describes and/or offers for sale the advertiser's product or service.
  • the landing page can, for example, also be a homepage for the advertiser, e.g., a company's home page.
  • the advertisements 116 can be selected by the advertising management system 104 based on the keywords of the search query submitted to the search engine 112.
  • the advertisers 116 are associated with keywords, and when particular keywords are identified in search queries, the advertisements 116 that are associated with those keywords can be selected for display on the search results page 111.
  • the advertisements can also be selected from an auction.
  • advertisers 102 can select, or bid, an amount the advertisers are willing to pay for each interaction with an advertisement, e.g., a cost-per-click amount an advertiser pays when, for example, a user clicks on an advertisement.
  • the cost-per-click can include a maximum cost-per-click, e.g., the maximum amount the advertiser is willing to pay for each click of advertisement based on a keyword.
  • the rank of an advertisement that is displayed can be determined by multiplying the maximum cost-per-click for the advertisement by a quality score of the advertisement, the latter of which can be determined, in part, by the advertisement's relevance to the keywords of the query.
  • the advertisement can then be placed among other advertisements in order of increasing or decreasing rank.
  • the advertisement management system 104 can store the advertisement information in the advertisement data 124.
  • the advertisement management system 104 can also store information related to advertising campaigns in the campaign data 126.
  • the campaign data 126 can, for example, specify advertising budgets for advertisements, associate keywords with advertisements and landing pages, and specify when, where and under what conditions particular advertisements may be served for presentation.
  • the advertisers 102, publisher 106, user devices 108, and/or the search engine 112 can also provide usage information to the advertisement management system 104.
  • This usage information can include measured or observed user behavior related to advertisements 116 that have been served, such as, for example, whether or not a conversion or a selection related to an advertisement 116 has occurred.
  • the advertisement management system 104 performs financial transactions, such as crediting the publishers 106 and charging the advertisers 102 based on the usage information.
  • Such usage information can also be processed to measure performance metrics, such as a click-through rate ("CTR”), conversion rate, etc.
  • CTR click-through rate
  • a click-through can occur, for example, when a user of a user device, selects or "clicks" on a link to a web document returned by the publisher or the advertising management system.
  • the CTR is a performance metric that is obtained by, for example, dividing the number of users that clicked on the web document, e.g., a link to a landing page, an advertisement 116, or a search result 118, by the number of times the web document was delivered.
  • a "conversion" occurs when a user consummates a transaction related to a previously served advertisement 116. What constitutes a conversion may vary from case to case and can be determined in a variety of ways. For example, a conversion may occur when a user clicks on an advertisement 116, is referred to the advertiser's landing page, and consummates a purchase there before leaving that landing page. Other actions that constitute a conversion can also be used.
  • the keywords that the advertisers 102 associate with advertisements can be selected based on keywords that the users may use when searching for information related to the commercial offering being advertised.
  • a commercial offering can be any opportunity on a landing page for a transaction, e.g., the sale of a product or service.
  • the advertisers 102 are able to associate their advertisements 116 for the commercial offering with the keywords of the query.
  • a retailer of cake pans can anticipate that a user searching for cake pans will likely include the search terms "cake" and "pan” in their search query.
  • the retailer of cake pans can associate its advertisement with the keywords "cake" and "pan.” Searches that include the keywords cake and pan can result in the presentation of an advertisement provided by the retailer of cake pans.
  • Fig. 2 is a block diagram 200 illustrating an example operational process.
  • the three phases include an extraction phase, a candidate query-page phase, and a filtering phase. These phases are illustrative only and more or fewer phases can be used.
  • the query-page identifier 114 can identify that the query log 128 includes a query for "train cake pan.”
  • the query for "train cake pan” can be considered commercially relevant if it was submitted in excess of a minimum frequency of submission threshold, and if it was not submitted in excess of the maximum frequency of submission threshold.
  • the candidates are filtered (e.g., to create query-page tuples).
  • the query-page tuples represent the subset of the query-page candidate tuples that meet one or more filtering criteria.
  • a filter 208 can remove query-page candidate tuples if the tuple is not relevant to the commercial offering, e.g., queries that result in the identification of pages from the entire web index 120 that do not have a discernable intent, as measured by one or more statistical processes, and/or query-page candidate tuples for which the intent measure diverges from the intent measure of the identified landing pages from the entire web index.
  • a suggestion vector and/or a query intent vector can be used to determine whether the candidate tuple is relevant to the commercial offering.
  • filtered selections can be associated with an advertisement.
  • a query-page tuple can be associated with an advertisement by associating the query with the advertisement, and linking the advertisement to the landing page of the tuple.
  • These associations can be stored in ad groups 212, which in some implementations are a collection of associations of keywords, advertisements and landing pages.
  • the candidate query of "train cake pan” can be associated with an advertisement that links to the landing page that offers train cake pans for the Online Store A.
  • Fig. 3 is a block diagram 300 showing an example extraction process (e.g., associated with query-page identifier 114).
  • a query extractor 302 identifies from the query log 128 a set of candidate queries that meet one or more extraction criteria 308.
  • the extraction criteria 308 can include criteria regarding the frequency of submission of the query, the timing of the query, the type of the query, and other criteria.
  • the frequency specified by the submission criterion can be selected to identify queries that occur at least a minimum number of times and occur less than a maximum number of times.
  • the lower threshold can be selected to protect user privacy and to identify queries that are likely to again be submitted in the future.
  • a query that is submitted less than 50 times per year may not be commercially relevant; instead, it may be a focused query submitted by one user.
  • the upper threshold can be selected to filter out queries that are submitted frequently, as these queries tend to be either generic queries (e.g., "credit cards") or queries that are of topical or pop-culture interests (e.g., a famous person's name).
  • the query extractor 302 may also use timing criteria to analyze the timing of the query to determine if the query is commercially relevant.
  • a query may not have the same level of commercial relevancy at different times. For example, a query for "pirate eye patch" may be commercially relevant during Halloween because people are more likely to search for costumes during Halloween. That same query may not be commercially relevant during non- Halloween time periods.
  • the query extractor 302 may also use type criteria to analyze the type of the query to determine if the query is commercially relevant. In some implementations, a query is not commercially relevant if it is not directed towards a commercial offering.
  • the extraction criteria 308 can be used to eliminate queries that are educational, news related, or otherwise not directed towards a commercial offering. For example, the extraction criteria 308 can identify educational websites, news sites, current events and query phrases (such as "how to " queries, "history of." queries, etc.) as types of queries that are not directed to commercial offerings.
  • a query is not commercially relevant if there are already advertisements associated with the query.
  • the query may also not be commercially relevant if the query has a low click-through rate; or is an expansion of a stem query that has already been selected according to the extraction criteria 308, and so on.
  • the query extractor 302 may encounter a series of unrelated queries as shown in table 1 that are possible candidate queries.
  • the extraction criteria 308 may specify a minimum number of submissions in a one- month period of 50, and a maximum number of submissions during that same one-month period of 50,000.
  • the first query, "Mr. Celebrity,” is a very common query that was submitted more than the requisite minimum number of times. However, the frequency of submission on the first query also exceeded a maximum number of submissions. Thus, the query extractor 302 does not identify "Mr. Celebrity" as a candidate query.
  • the other three queries, "red box,” “train cake pans,” and “Battle Tactics,” are queries that are submitted within the range of frequency of submission. Thus, each of these is identified as a candidate query.
  • Fig. 4 is a block diagram 400 of an example candidate query-page process (e.g., associated with query-page identifier 114).
  • a candidate query search evaluator 408 can use the search engine 112 and proper subset criteria 406 and the candidate queries to identify landing pages relevant to the candidate queries 306. The landing pages are used by the candidate query search evaluator 408 to identify query-page candidate tuples 410.
  • the proper subset criteria 406 identifies web pages with commercial offerings by identifying the type of the web page. Pages such as news pages, blogs, forums, and the like are not included in the proper subset, while pages related to companies or retailer are included in the proper subset to be searched. These pages can be identified and differentiated by, for example, a list of domain names; top level domain extensions, such as .biz, .com, .org, .edu; or web sites.
  • the proper subset criteria 406 identifies data that can be indicative of commercial offerings.
  • the proper subset criteria 406 can include common phrases of commercial intent, e.g. "purchase,” "sale,” “shopping cart,” etc. Other criteria for determining whether a web page has a commercial offering can also be used, e.g., web pages that are linked to pages with commercial offerings can be considered as commercial offerings, and included in the proper subset. In some implementations, other considerations (i.e., other than commercial offering) can be used to evaluate the subset.
  • the proper subset criteria 406 identifies web pages of advertisers 102 that have requested web pages to be searched. For example, an advertiser can provide a site map of its domain for inclusion in the proper subset criteria 406.
  • the candidate query search evaluator 408 can cause the search engine 112 to search the proper subset of the web index 120 defined by the proper subset criteria 406 for landing pages related to the candidate queries 306.
  • the search engine 112 can assign a relevancy score to each landing page returned from the proper subset of the web index 120 for each candidate query.
  • the candidate queries 306 can include the query "train cake pans.”
  • the search engine 112 can search the proper subset for landing pages responsive to the candidate query "train cake pans.” All landing pages responsive to "train cake pans" can be assigned relevancy scores indicated in Table 2.
  • the candidate query search evaluator 408 can select landing pages identified from the proper subset based on the relevancy scores of the landing pages. In some implementations, the candidate query search evaluator 408 selects only the landing pages having a relevancy score that exceeds a relevance threshold. For example, if the relevance threshold is 85, then for the candidate query "train cake pans," the listed landing pages of Stores A, B, and C, each of which are assigned a relevancy score over the relevancy threshold of 85, are sufficiently relevant that they are selected by the candidate query search evaluator 408.
  • These selected landing pages are then associated with the corresponding candidate query in a query-page candidate tuple 410.
  • Table 3 lists the query-page candidate tuples for the candidate query "train cake pans.”
  • the search engine 112 can be configured to perform a modified search on the proper subset of the web index 120 when identifying query-page candidate tuples. For example, estimated performance of the query, such as a predicted click through rate, can be omitted in a ranking process, and the ranking can be solely dependent on how relevant the candidate query is to the content of the web document. Other search algorithm modifications can also be made, e.g., ignoring keyword bids; ignoring geographic factors; and so on.
  • Fig. 5 is a block diagram of an example filtering process (e.g., associated with query- page identifier 114).
  • a filter 502 can be used to select from the query-page candidate tuples 410 the query-page tuples that meet one or more filtering criteria.
  • the filtering criteria can, for example, include dominant intent measures, query-page intent measures, generic query lists, and/or other criteria that are selected to eliminate query- page candidate tuples that would not result in commercially viable advertising suggestions.
  • the filter 502 can select from the candidate tuples 410 the tuples that likely present the better advertising opportunities to advertisers.
  • a candidate tuple presents a likely advertising opportunity only where the dominant intent of the candidate query matches the intent of the selected landing pages of the candidate tuples 410. Thus, where there is no dominant intent of the candidate query, or where the dominant intent of the candidate query does not match the intent of the selected landing page, the candidate tuples 410 do not present a likely advertising opportunity.
  • the dominant intent of the candidate query can be measured by use of an intent vector for the candidate query.
  • the intent vector is a vector representation of the search results returned in response to using the candidate query to search the entire web index 120.
  • the intent vector includes commonly associated terms from the identified landing pages, e.g., terms from the 10 highest ranked landing pages, for example.
  • the filter 502 can use the terms in the intent vector to calculate an intent measure.
  • the intent measure identifies whether the candidate query has a dominant intent.
  • candidate queries for which the landing pages produce an intent vector with a high intent measure have a dominant intent; conversely, candidate queries for which the landing pages produce an intent vector with a low intent measure have no dominant intent.
  • the low intent measure indicates that the candidate query may be a generic query, or may be a query that is a poor expression of the users' interests. For example, Table 4 identifies the terms commonly associated from landing pages identified by using the candidate query "train cake pan.”
  • the dominant intent of the candidate query "Battle Tactics” can be determined by analysis of Table 7. All the terms commonly associated with the candidate query are related to the study of military tactics and warfare. Thus the candidate query "Battle Tactics" has a high intent measure related to the study of military tactics and warfare.
  • the ad group classifier 602 identifies suggested advertisement groupings that pair query-page tuples 504 with advertisements.
  • the pairings of advertisements with query-page tuples 504 can be suggested for association as suggestions 606, or the pairings can be automatically associated with each other into ad groups 212.
  • the suggestions 606 can be presented to the advertisers through the advertiser front end 608.
  • Fig. 6b is a block diagram 625 illustrating an example association of query-page tuples 504 with an existing advertisement in an ad group 212.
  • the ad group 212 includes an advertisement that includes a link to a landing page.
  • the landing page has also been identified in a query-page tuple by the query page identifier 114.
  • Fig. 6d is another block diagram 675 illustrating an example association of a query- page tuple with an advertisement.
  • the advertiser may not have an existing advertising campaign, and thus there is no existing ad data 212 with which the query-page tuple can be associated.
  • Figs. 6b and 6c illustrate two example processes by which a query-page tuple that includes a selected candidate query and associated web document are associated with the ad group 212. Other association processes can also be used.
  • the query-page tuple 504 can be used to suggest an advertisement for the advertiser 102.
  • the advertiser 102 may receive a notification of an advertising opportunity for one of its landing pages and one or more suggested queries as defined by the query-page tuple 504. If the advertiser 102 accepts the suggestion, then corresponding advertising data 212 can be created for the advertiser.
  • the advertiser 102 can provide a creative, bid information, and a budget to the advertising management system 104 to begin advertising offerings for the landing page indicated by the query-page tuple 504.
  • the ad group classifier 602 can process a site map of the website of the advertiser 102 and can suggest advertising data for interior nodes of the site map for which the children landing pages are included in the query-page tuples 504.
  • a retailer that sells clothing apparel may have a site map that includes a node "Shoes,” which, in turn, includes child nodes "Women's Shoes” and "Men's Shoes.”
  • the retailer may offer, in corresponding web documents that are children of the "Women's Shoes” and "Men's Shoes” nodes, women's and men's shoes of a particular brand that are marketed by the shoe manufactures as being casual and comfortable shoes.
  • the query-page identifier may identify query-page tuples 504 for each of these web documents and provide these suggestions to the retailer. Through use of the query-page tuples 504, the retailer can form an advertising campaign for the particular shoes.
  • the query-page tuples 504 have other uses in addition to facilitating targeted advertising.
  • the query-page tuples 504 can be used to generate a query- category map 704 that describes relevant user queries for certain categories.
  • Fig. 7 is a block diagram 700 illustrating an example association of query-page tuples 504 with a query category.
  • a query categorizer 702 can access the query-page tuples and a web directory 706 to generate the query-category map 704.
  • the web director 706 can be a pre-existing directory of web documents classified according to hierarchal categories.
  • Example web directories include the Open Directory Project, the Google Directory, or any other directory in which web documents are organized into categories.
  • the query categorizer 702 can identify a category in the category directory to which the selected web document of the query-page tuple belongs, and can associate the candidate query with the identified category so that the candidate query can be presented in response to a selection of the identified category.
  • query-page identifier 114 can use different extraction criteria, proper subset criteria, and filtering criteria for each category.
  • the extraction criteria and the filtering criteria described above can be used when processing the web index 120 and query logs 128 for web properties that include commercial offerings.
  • other extraction and filtering criteria can be used to identify relevant content for the other subject relevance.
  • queries and/or pages that include the phrase "research paper" can be included when identifying query-page tuples 504 for an educational subject relevance, and queries and/or pages that include the term "shopping cart" can be excluded for educational subject relevance.
  • the proper subset criteria can also be tailed to identify a subset of the web index 120 related to the subject relevance.
  • the proper subset criteria can define a proper subset of web properties based on the web properties included in each category, and the subsequent processing to identify query-page tuples 504 can be limited to pages in each category subset.
  • the query category 702 can identify a category to associate with the candidate query based on possible categorizations of the landing page.
  • the query categorizer 702 can identify possible categorizations of the landing page based on the keywords in the landing page, for example.
  • Facilitating targeted advertising and query categorization are two examples of how query-page tuples 504 can be used.
  • query-page tuples 504 can be created for any type of relevance factor, e.g., commercial, educational, religious, political, etc., and can be used to facilitate more effective and efficient distribution of relevant information. For example, queries related to tax filings and that are relevant to a governmental agency's tax-related web documents can be identified and these web documents can be boosted in the search results page for those queries.
  • relevance factor e.g., commercial, educational, religious, political, etc.
  • Fig. 8 is a flow diagram of an example process 800 for identifying query-page candidate tuples.
  • the process 800 can, for example, be implemented by the query-page identifier 114 of Fig. 1, and as described in Figs. 2-4.
  • Fig. 9 is a flow diagram of process 900 for query extraction.
  • the process 900 can, for example, be implemented by the query-page identifier 114 of figure 1, and/or the query extractor 302 of Fig. 3.
  • the process 900 can, for example, be used to implement stage 802 of Fig. 8.
  • Stage 902 identifies a query.
  • the query-page identifier 114, or the query extractor 302 can identify a query from the query log 128.
  • Fig. 10 is a flow diagram of an example process 1000 for filtering query-page candidate tuples.
  • the process 1000 can, for example, be implemented by the query-page identifier 114 of Fig. 1 and/or the candidate query search evaluator 408 of Fig. 4 and the filter 502 of Fig. 5.
  • the process 1000 can be used to filter the query-page candidate tuples generated by the process 800.
  • Stage 1002 selects a candidate query-page tuple.
  • the query-page identifier 114 of Fig. 1 and/or the candidate query search evaluator 408 can select a candidate query-page tuple from the query-page candidate tuples 410.
  • Stage 1004 searches the collection of documents.
  • the query-page identifier 114 or the candidate query search evaluator 408 can cause the search engine to search the entire web index 120 with the candidate query of the selected query-page candidate tuple.
  • Stage 1006 generates a first vector.
  • the query-page identifier 114 or the filter 502 can generate a suggestion vector for a web document identified in the query-page candidate tuple.
  • the query-page identifier 114 or the filter 502 can determine the similarity measure between the suggestion vector and the intent vector.
  • Stage 1012 determines if the similarity measure of the first vector to the second vector exceeds a threshold. For example, the query-page identifier 114 or the filter 502 determines if the similarity measure of the first vector to the second vector exceeds a threshold.
  • Fig. 11 is a flow diagram of an example process 1100 for associating a query-page tuple with an advertisement group.
  • the process 1100 can, for example, be implemented by the query-page identifier 114 or the ad group classifier 602 of Fig. 6.
  • Stage 1102 compares the candidate query and the associated web document to an advertisement group.
  • the query-page identifier 114 or the ad group classifier 602 can compare the keywords from the query-page tuples to keywords associated with advertisements in ad groups 212.
  • the keywords of the query-page tuples can include keywords of the candidate queries, keywords of the associated web document, etc.
  • the keywords of the advertisement group include keywords from search terms that the advertisement is associated with, keywords from the title of the advertisements and from landing pages associated with the advertisements, etc.
  • Stage 1104 determines whether the candidate query and the associated web document are relevant to the advertisement group. For example, based on the comparison of stage 1102, the ad group classifier 602 can determine whether the query-page tuple is relevant to the advertisement group 212. For example, when the keywords associated with an advertisement group include one or more of the keywords of the candidate query, the ad group classifier 602 determines that the candidate query and the associated web document are relevant to the advertisement group.
  • stage 1106 associates the candidate query and the web document with the advertisement group. For example, if the query-page identifier 114 or the ad group classifier 602 determines that the query-page tuple is relevant to the advertisement group, the candidate query can be associated with the advertisement group.
  • the ad group classifier 602 can associate the candidate query with an existing advertisement, or it can generate a new advertisement based on the existing advertisements.
  • Fig. 12 is a flow diagram of an example process 1200 for associating a query with a category.
  • the process 1200 can, for example, be implemented by the query-page identifier 114 of Fig. 1 and/or the query categorizer 702 of Fig. 7.
  • Stage 1202 identifies a query-page tuple.
  • the query-page identifier 114 and/or the query categorizer 702 can identify a query-page tuple from the query page tuples 504.
  • Stage 1204 identifies in a category directory the categories to which the associated landing page belongs.
  • the query-page identifier 114 and/or the query categorizer 702 can identify a category in a web director to which the associated landing page of the selected query-page tuple belongs.
  • Stage 1204 associates the candidate query with the identified category.
  • the query-page identifier 114 and/or the query categorizer 702 can associate the candidate query of the selected query-page tuple with the category identified in stage 1204.
  • Fig. 13 is block diagram of an example computer system 1300.
  • the system 1300 can be used to implement the query page identifier 114 and/or the query extractor 302, candidate query search evaluator 408, filter 502, ad group classifier 602, and query categorizer 702 of Figs. 1-7. Other computer systems, however, can also be used.
  • the system 1300 and includes a processor 1310, a memory 1320, a storage device 1330, and an input/output device 1340. Each of the components 1310, 1320, 1330, and 1340 can, for example, be interconnected using a system bus 1350.
  • the processor 1310 is capable of processing instructions for execution within the system 1300. In one implementation, the processor 1310 is a single-threaded processor. In another implementation, the processor 1310 is a multi-threaded processor.
  • the processor 1310 is capable of processing instructions stored in the memory 1320 or on the storage device 1330.
  • the storage device 1330 is capable of providing mass storage for the system 1300.
  • the storage device 1330 is a computer-readable medium.
  • the storage device 1330 can, for example, include a hard disk device, an optical disk device, or some other large capacity storage device.
  • the input/output device 1340 provides input/output operations for the system 1300.
  • the input/output device 1340 can include one or more of a network interface devices, e.g., an Ethernet card, a serial communication device, e.g., and RS-232 port, and/or a wireless interface device, e.g., and 802.11 card.
  • the input/output device can include driver devices configured to receive input data and send output data to other input/output devices, e.g., keyboard, printer and display devices 1360.
  • Embodiments of the subject matter and the functional operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them.
  • Embodiments of the subject matter described in this specification can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a tangible program carrier for execution by, or to control the operation of, data processing apparatus.
  • the tangible program carrier can be a computer readable medium.
  • the computer readable medium can be a machine readable storage device, a machine readable storage substrate, a memory device, a composition of matter effecting a machine readable propagated signal, or a combination of one or more of them.
  • the processing devices disclosed herein encompass all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers.
  • the apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.
  • a computer The essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data.
  • a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Accounting & Taxation (AREA)
  • Development Economics (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Game Theory and Decision Science (AREA)
  • General Business, Economics & Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Information Transfer Between Computers (AREA)
PCT/US2009/048159 2008-06-23 2009-06-22 Query identification and association WO2010008800A2 (en)

Priority Applications (6)

Application Number Priority Date Filing Date Title
AU2009271386A AU2009271386A1 (en) 2008-06-23 2009-06-22 Query identification and association
CA2729067A CA2729067A1 (en) 2008-06-23 2009-06-22 Query identification and association
CN200980131937.XA CN102124462B (zh) 2008-06-23 2009-06-22 查询识别和关联
JP2011516497A JP5542812B2 (ja) 2008-06-23 2009-06-22 クエリ識別および関連付け
BRPI0914623A BRPI0914623A2 (pt) 2008-06-23 2009-06-22 identificação de consulta e associação
EP09798466A EP2313839A4 (en) 2008-06-23 2009-06-22 IDENTIFICATION AND ASSOCIATION OF INTERROGATIONS

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US7494508P 2008-06-23 2008-06-23
US61/074,945 2008-06-23

Publications (2)

Publication Number Publication Date
WO2010008800A2 true WO2010008800A2 (en) 2010-01-21
WO2010008800A3 WO2010008800A3 (en) 2010-03-25

Family

ID=41432301

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2009/048159 WO2010008800A2 (en) 2008-06-23 2009-06-22 Query identification and association

Country Status (8)

Country Link
US (2) US8171021B2 (ru)
EP (1) EP2313839A4 (ru)
JP (1) JP5542812B2 (ru)
CN (1) CN102124462B (ru)
AU (1) AU2009271386A1 (ru)
BR (1) BRPI0914623A2 (ru)
CA (1) CA2729067A1 (ru)
WO (1) WO2010008800A2 (ru)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2014503897A (ja) * 2010-12-14 2014-02-13 マイクロソフト コーポレーション 広告主による抽象的オブジェクトへの入札を可能にすること
JP2014529113A (ja) * 2011-07-21 2014-10-30 アリババ・グループ・ホールディング・リミテッドAlibaba Group Holding Limited 情報のリダイレクト

Families Citing this family (69)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8073681B2 (en) 2006-10-16 2011-12-06 Voicebox Technologies, Inc. System and method for a cooperative conversational voice user interface
US8060503B2 (en) * 2006-12-22 2011-11-15 Fujitsu Limited Ranking nodes for session-based queries
US7818176B2 (en) 2007-02-06 2010-10-19 Voicebox Technologies, Inc. System and method for selecting and presenting advertisements based on natural language processing of voice-based input
US8140335B2 (en) 2007-12-11 2012-03-20 Voicebox Technologies, Inc. System and method for providing a natural language voice user interface in an integrated voice navigation services environment
US9305548B2 (en) 2008-05-27 2016-04-05 Voicebox Technologies Corporation System and method for an integrated, multi-modal, multi-device natural language voice services environment
US8171021B2 (en) * 2008-06-23 2012-05-01 Google Inc. Query identification and association
US8886636B2 (en) * 2008-12-23 2014-11-11 Yahoo! Inc. Context transfer in search advertising
US8812362B2 (en) * 2009-02-20 2014-08-19 Yahoo! Inc. Method and system for quantifying user interactions with web advertisements
US8326637B2 (en) 2009-02-20 2012-12-04 Voicebox Technologies, Inc. System and method for processing multi-modal device interactions in a natural language voice services environment
US9171541B2 (en) * 2009-11-10 2015-10-27 Voicebox Technologies Corporation System and method for hybrid processing in a natural language voice services environment
US20110166928A1 (en) * 2010-01-06 2011-07-07 Sharitable, Llc Method of Sharing Possessions among Friends Connected through a Social Network
US20110238686A1 (en) * 2010-03-24 2011-09-29 Microsoft Corporation Caching data obtained via data service interfaces
US8533044B2 (en) * 2010-04-14 2013-09-10 Microsoft Corporation Considering user-relevant criteria when serving advertisements
US8392435B1 (en) * 2010-04-14 2013-03-05 Google Inc. Query suggestions for a document based on user history
US9129300B2 (en) * 2010-04-21 2015-09-08 Yahoo! Inc. Using external sources for sponsored search AD selection
US20110295678A1 (en) * 2010-05-28 2011-12-01 Google Inc. Expanding Ad Group Themes Using Aggregated Sequential Search Queries
US20120016741A1 (en) * 2010-07-19 2012-01-19 Google Inc. Targeting content without keywords
US8515968B1 (en) 2010-08-13 2013-08-20 Google Inc. Tie breaking rules for content item matching
CN102479193B (zh) * 2010-11-22 2015-04-01 百度在线网络技术(北京)有限公司 一种基于匹配出价系数进行匹配搜索推广的方法和设备
US9519714B2 (en) * 2010-12-22 2016-12-13 Microsoft Technology Licensing, Llc Presenting list previews among search results
US9495461B2 (en) * 2011-03-22 2016-11-15 Excalibur Ip, Llc Search assistant system and method
US10643355B1 (en) 2011-07-05 2020-05-05 NetBase Solutions, Inc. Graphical representation of frame instances and co-occurrences
US8756218B1 (en) * 2011-08-16 2014-06-17 Google Inc. Query classification based on search engine results
US8190609B1 (en) 2011-08-18 2012-05-29 Google Inc. Identifying alternative products
US9104751B2 (en) * 2011-10-12 2015-08-11 Microsoft Technology Licensing, Llc Supplemental search results having social connection endorsement data on a SERP
US9075799B1 (en) * 2011-10-24 2015-07-07 NetBase Solutions, Inc. Methods and apparatus for query formulation
US9727892B1 (en) * 2011-10-28 2017-08-08 Google Inc. Determining related search terms for a domain
US8983996B2 (en) 2011-10-31 2015-03-17 Yahoo! Inc. Assisted searching
US9164985B1 (en) 2011-11-29 2015-10-20 Google Inc. Techniques for detecting poor machine translations of key terms
US9858313B2 (en) * 2011-12-22 2018-01-02 Excalibur Ip, Llc Method and system for generating query-related suggestions
US20130211905A1 (en) * 2012-02-13 2013-08-15 Microsoft Corporation Attractiveness-based online advertisement click prediction
CN103365842B (zh) * 2012-03-26 2016-08-24 阿里巴巴集团控股有限公司 一种页面浏览推荐方法及装置
US20130282481A1 (en) * 2012-04-20 2013-10-24 Increase Visibility Mexico, S. De R.L. De C.V. System and methods for electronic advertising management
US8849799B1 (en) * 2012-05-09 2014-09-30 Google Inc. Content selection using boolean query expressions
US9158857B2 (en) * 2012-06-05 2015-10-13 Google Inc. Identifying landing pages for images
US20140025657A1 (en) * 2012-07-21 2014-01-23 Trulia, Inc. Automated landing page generation and promotion for real estate listings
US10192238B2 (en) * 2012-12-21 2019-01-29 Walmart Apollo, Llc Real-time bidding and advertising content generation
US9536259B2 (en) 2013-03-05 2017-01-03 Google Inc. Entity-based searching with content selection
US9240016B2 (en) 2013-03-13 2016-01-19 Salesforce.Com, Inc. Systems, methods, and apparatuses for implementing predictive query interface as a cloud service
US20140280098A1 (en) * 2013-03-15 2014-09-18 Quixey, Inc. Performing application search based on application gaminess
US9418114B1 (en) 2013-06-19 2016-08-16 Google Inc. Augmenting a content item using search results content
US9305307B2 (en) 2013-07-15 2016-04-05 Google Inc. Selecting content associated with a collection of entities
US9298779B1 (en) 2013-07-16 2016-03-29 Google Inc. Combining content with a search result
US9342839B2 (en) 2013-07-16 2016-05-17 Google Inc. Combining content with a search result
EP2833307A1 (en) 2013-07-30 2015-02-04 Google, Inc. Handling search queries
US9367529B1 (en) 2013-07-31 2016-06-14 Google Inc. Selecting content based on entities
US9436946B2 (en) 2013-07-31 2016-09-06 Google Inc. Selecting content based on entities present in search results
CN103455552A (zh) * 2013-08-01 2013-12-18 百度在线网络技术(北京)有限公司 基于兴趣词的兴趣点挖掘方法及装置
US20150088648A1 (en) * 2013-09-24 2015-03-26 Google Inc. Determining commercial intent
US9299028B2 (en) * 2013-11-04 2016-03-29 Adobe Systems Incorporated Identifying suggestive intent in social posts
US10311364B2 (en) 2013-11-19 2019-06-04 Salesforce.Com, Inc. Predictive intelligence for service and support
EP2884444A1 (en) * 2013-12-10 2015-06-17 Google, Inc. Handling search queries
US9672288B2 (en) 2013-12-30 2017-06-06 Yahoo! Inc. Query suggestions
US9652508B1 (en) * 2014-03-05 2017-05-16 Google Inc. Device specific adjustment based on resource utilities
US20150379074A1 (en) * 2014-06-26 2015-12-31 Microsoft Corporation Identification of intents from query reformulations in search
WO2016044321A1 (en) 2014-09-16 2016-03-24 Min Tang Integration of domain information into state transitions of a finite state transducer for natural language processing
EP3195145A4 (en) 2014-09-16 2018-01-24 VoiceBox Technologies Corporation Voice commerce
WO2016061309A1 (en) 2014-10-15 2016-04-21 Voicebox Technologies Corporation System and method for providing follow-up responses to prior natural language inputs of a user
US10614799B2 (en) 2014-11-26 2020-04-07 Voicebox Technologies Corporation System and method of providing intent predictions for an utterance prior to a system detection of an end of the utterance
US10431214B2 (en) 2014-11-26 2019-10-01 Voicebox Technologies Corporation System and method of determining a domain and/or an action related to a natural language input
US10817519B2 (en) * 2016-06-06 2020-10-27 Baidu Usa Llc Automatic conversion stage discovery
WO2018023106A1 (en) 2016-07-29 2018-02-01 Erik SWART System and method of disambiguating natural language processing requests
CN109992764B (zh) * 2017-12-29 2022-12-16 阿里巴巴集团控股有限公司 一种文案生成方法及装置
US11314794B2 (en) * 2018-12-14 2022-04-26 Industrial Technology Research Institute System and method for adaptively adjusting related search words
CN110555165B (zh) * 2019-07-23 2023-04-07 平安科技(深圳)有限公司 信息识别方法、装置、计算机设备和存储介质
US20220035675A1 (en) * 2020-08-02 2022-02-03 Avatar Cognition Barcelona S.L. Pattern recognition system utilizing self-replicating nodes
CN113204579B (zh) * 2021-04-29 2024-06-07 北京金山数字娱乐科技有限公司 内容关联方法、系统、装置、电子设备及存储介质
CN115037739B (zh) * 2022-06-13 2024-02-23 深圳乐播科技有限公司 文件传输方法、装置、电子设备及存储介质
US20240004947A1 (en) * 2022-06-30 2024-01-04 Citrix Systems, Inc. Systems and Methods of Determining Web Resource Relevance

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6772150B1 (en) * 1999-12-10 2004-08-03 Amazon.Com, Inc. Search query refinement using related search phrases
CN1826596A (zh) * 2002-09-24 2006-08-30 Google公司 用于提供相关广告服务的方法和装置
US7197497B2 (en) * 2003-04-25 2007-03-27 Overture Services, Inc. Method and apparatus for machine learning a document relevance function
US20050033771A1 (en) * 2003-04-30 2005-02-10 Schmitter Thomas A. Contextual advertising system
US20040249808A1 (en) * 2003-06-06 2004-12-09 Microsoft Corporation Query expansion using query logs
US7260568B2 (en) * 2004-04-15 2007-08-21 Microsoft Corporation Verifying relevance between keywords and web site contents
CA2572468A1 (en) * 2004-06-30 2006-01-12 Shumeet Baluja Generating and/or serving local area advertisements, such as advertisements for devices with call functionality
JP2006079454A (ja) * 2004-09-10 2006-03-23 Fujitsu Ltd 検索キーワード分析方法、検索キーワード分析プログラムおよび検索キーワード分析装置
US7739708B2 (en) * 2005-07-29 2010-06-15 Yahoo! Inc. System and method for revenue based advertisement placement
US7962479B2 (en) * 2005-11-09 2011-06-14 Yahoo! Inc. System and method for generating substitutable queries
US7788131B2 (en) * 2005-12-15 2010-08-31 Microsoft Corporation Advertising keyword cross-selling
US20070192293A1 (en) * 2006-02-13 2007-08-16 Bing Swen Method for presenting search results
US7689554B2 (en) * 2006-02-28 2010-03-30 Yahoo! Inc. System and method for identifying related queries for languages with multiple writing systems
US7818315B2 (en) * 2006-03-13 2010-10-19 Microsoft Corporation Re-ranking search results based on query log
US7577643B2 (en) * 2006-09-29 2009-08-18 Microsoft Corporation Key phrase extraction from query logs
KR100851041B1 (ko) * 2006-11-08 2008-08-12 엔에이치엔(주) 유알엘 입력을 통한 광고 키워드 추천 방법 및 그 시스템
US7739264B2 (en) * 2006-11-15 2010-06-15 Yahoo! Inc. System and method for generating substitutable queries on the basis of one or more features
US7827172B2 (en) * 2007-03-14 2010-11-02 Yahoo! Inc. “Query-log match” relevance features
US20090192983A1 (en) * 2008-01-28 2009-07-30 Yahoo! Inc. Method and system for mining, ranking and visualizing lexically similar search queries for advertisers
US8171021B2 (en) * 2008-06-23 2012-05-01 Google Inc. Query identification and association
JP2010059671A (ja) 2008-09-03 2010-03-18 Chugoku Electric Power Co Inc:The コンクリート構造物の型枠の固定装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of EP2313839A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2014503897A (ja) * 2010-12-14 2014-02-13 マイクロソフト コーポレーション 広告主による抽象的オブジェクトへの入札を可能にすること
JP2014529113A (ja) * 2011-07-21 2014-10-30 アリババ・グループ・ホールディング・リミテッドAlibaba Group Holding Limited 情報のリダイレクト

Also Published As

Publication number Publication date
CN102124462B (zh) 2015-04-01
BRPI0914623A2 (pt) 2015-10-20
US20120215776A1 (en) 2012-08-23
US8631003B2 (en) 2014-01-14
EP2313839A2 (en) 2011-04-27
CN102124462A (zh) 2011-07-13
AU2009271386A1 (en) 2010-01-21
JP5542812B2 (ja) 2014-07-09
JP2011525678A (ja) 2011-09-22
WO2010008800A3 (en) 2010-03-25
US20090319517A1 (en) 2009-12-24
CA2729067A1 (en) 2010-01-21
US8171021B2 (en) 2012-05-01
EP2313839A4 (en) 2012-12-19

Similar Documents

Publication Publication Date Title
US8631003B2 (en) Query identification and association
US8738426B2 (en) Taxonomy based targeted search advertising
US8886636B2 (en) Context transfer in search advertising
CN105765573B (zh) 网站通信量优化方面的改进
US8566160B2 (en) Determining placement of advertisements on web pages
US20100030647A1 (en) Advertisement selection for internet search and content pages
US8655912B2 (en) Computer-implemented method and system for combining keywords into logical clusters that share similar behavior with respect to a considered dimension
US20110196737A1 (en) Semantic advertising selection from lateral concepts and topics
US20050071224A1 (en) System and method for automatically targeting web-based advertisements
US20140258002A1 (en) Semantic model based targeted search advertising
US20100057577A1 (en) System And Method For Providing Topic-Guided Broadening Of Advertising Targets In Social Indexing
US20090037399A1 (en) System and Method for Determining Semantically Related Terms
KR20080080989A (ko) 광고 키워드 교차-판매를 용이하게 하는 시스템 및 방법
JP2017076435A (ja) 広告キャンペーンの生成
US9613135B2 (en) Systems and methods for contextual analysis and segmentation of information objects
US20070233503A1 (en) Bidding for on-line survey placement
US20080215504A1 (en) Revenue Allocation in a Network Environment
Agarwal et al. The Emerence of Global Search Engines: Trends in History and Competition
WO2012097159A1 (en) Serving advertisements based on article availability
Ergezer New method for reaching consumers over the internet:" search engine marketing”
Tavşanoğlu Decision support system for search engine advertising campaign management by determining negative keywords
US20090094117A1 (en) Natural targeted advertising engine
US20160019588A1 (en) System and Method for Displaying Search Results
Vattikonda An Advertiser Centered Approach to Improve Sponsored Search Effectiveness

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200980131937.X

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09798466

Country of ref document: EP

Kind code of ref document: A2

ENP Entry into the national phase

Ref document number: 2729067

Country of ref document: CA

Ref document number: 2011516497

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2009271386

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: 8392/CHENP/2010

Country of ref document: IN

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2009798466

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2009271386

Country of ref document: AU

Date of ref document: 20090622

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: PI0914623

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20101223