LANDING PAGE IDENTIFICATION, TAGGING AND HOST MATCHING FOR A MOBILE APPLICATION

• US 20080040389A1
• Filed: 12/14/2006
• Published: 02/14/2008
• Est. Priority Date: 08/04/2006
• Status: Active Grant

• Current Assignee: R2 Solutions LLC (Acacia Research Corporation)
• Original Assignee: Yahoo! Inc. (Apollo Global Management, Inc.)
• Inventors: Seth, Siddharth, Rao, Sudhir Kumar Rama, Prabhakar, Bangalore Subbaramaiah
• Granted Patent: US 9,268,873 B2
• Time in Patent Office: Days
• US Class Current: 707/104.1
• CPC Class Codes: G06F 16/9577 Optimising the visualization of content, e.g. distillation of HTML documents

Abstract

A system, apparatus, and method are disclosed to provide an enhanced search index for searchable content by limited capability devices, such as mobile phones. A URL analyzer determines clusters of mobile web page URLs and corresponding tokens. A landing page identifier evaluates cluster URLs and the tokens to identify landing page URLs for mobile web pages likely to be relevant to an associated search term. A mapper associates the landing page URLs with related domain hosts that include conventional web pages generally not accessible to limited capability devices. A category tagger associates the landing page URLs with categories of conventional web pages that share a content topic. The landing page URLs, and corresponding tokens, domain host information, and categories are added to the search index. A submitted search term is evaluated relative to the tokens, domain host information, and categories to determine relevant mobile web landing pages as search results.

Claims

1. A method for providing a search index, comprising:

identifying a landing page uniform resource locator (URL) from among a plurality of mobile web page URLs that correspond to a plurality of mobile web pages accessible with a limited capability computing device;

associating the landing page URL with a web host based at least in part on a token determined from the landing page URL, wherein the web host includes web pages that are not accessible with a limited capability computing device;

associating the landing page URL with a web category based at least in part on the web host, wherein the web category identifies a content topic shared by web pages that are not accessible with a limited capability computing device; and

providing the landing page URL, the token, information associated with the web host, and the category to a search index that is used to associate a search term with the landing page URL based at least in part on at least one of the token, the web host, or the category.

2. The method of claim 1, wherein identifying the landing page URL comprises:

determining a cluster of mobile web page URLs from among the plurality of mobile web page URLs, wherein the cluster is determined at least in part based on a parameter that exists in each web pager URL in the cluster;

selecting a cluster URL from among the cluster of mobile web pager URLs, wherein the cluster URL represents the cluster;

determining a token from the cluster URL, wherein the token is determined at least in part based on a frequency with which the token appears in the cluster of mobile web page URLs; and

determining whether the cluster URL satisfies at least one landing page criterion.

3. The method of claim 2, wherein the cluster URL is selected at least in part based on at least one of the following:

a number of mobile web page URLs that have a lower position in a hierarchical tree of URLs relative to the cluster URL; and

a frequency with which the cluster URL is identified in mobile web pages corresponding to the plurality of mobile web page URLs.

4. The method of claim 2, wherein the at least one landing page criterion comprises at least one of the following:

a number of levels below the cluster URL in a hierarchical tree of the plurality of mobile web page URLs; and

a match between the token and a predefined keyword indicating a landing page.

5. The method of claim 1, wherein the landing page URL and the web host are associated with a same domain.

6. The method of claim 1, wherein associating the landing page URL with the web host comprises:

accessing a list of web host names associated with a domain that is also associated with the landing page URL;

determining the web host from the list if the token matches one of the web host names; and

determining the web host based on a match between the token and metadata associated with the web host if the token does not match any of the web host names in the list.

7. The method of claim 1, wherein the token comprises at least one of the following:

a directory path parameter and a query parameter.

8. The method of claim 1, wherein associating the landing page URL with the web category comprises at least one of the following:

matching the web host to the web category from a list of web categories determined from web pages that are not accessible by a limited capability device; and

matching the token to the web category from a list of web categories determined from web pages that are not accessible by a limited capability device.

9. The method of claim 1, further comprising:

validating a mobile web page associated with one a non-landing page URL from among the plurality of mobile web page URLs that is not identified as the landing page URL; and

submitting the non-landing page URL as a seed to a crawler.

10. A computer readable storage medium storing computer readable instructions that instruct a processor to perform a plurality of operations, including the operations of claim 1.

11. The computer readable storage medium of claim 10 further storing computer readable instructions that instruct the processor to perform the operations of:

determining a cluster of mobile web page URLs from among the plurality of mobile web page URLs, wherein the cluster is determined at least in part based on a parameter that exists in each web pager URL in the cluster;

selecting a cluster URL from among the cluster of mobile web pager URLs, wherein the cluster URL represents the cluster;

determining a token from the cluster URL, wherein the token is determined at least in part based on a frequency with which the token appears in the cluster of mobile web page URLs; and

determining whether the cluster URL satisfies at least one landing page criterion.

12. A server for providing a search index, comprising:

a transceiver for receiving and for sending information over a network;

a processor in communication with the transceiver; and

a memory storing program code that is operative to cause the processor to automatically perform actions comprising;

identifying a landing page uniform resource locator (URL) from among a plurality of mobile web page URLs that correspond to a plurality of mobile web pages accessible with a limited capability computing device;

associating the landing page URL with a web host based at least in part on a token determined from the landing page URI, wherein the web host includes web pages that are not accessible with a limited capability computing device;

associating the landing page URL with a web category based at least in part on the web host, wherein the web category identifies a content topic shared by web pages that are not accessible with a limited capability computing device; and

providing the landing page URL, the token, information associated with the web host, and the category to a search index that is used to associate a search term with the landing page URL based at least in part on at least one of the token, the web host, or the category.

13. The server of claim 12, wherein the memory further stores program code that is operative to cause the processor to automatically perform actions comprising:

determining a cluster of mobile web page URLs from among the plurality of mobile web page URLs, wherein the cluster is determined at least in part based on a parameter that exists in each web pager URL in the cluster;

selecting a cluster URL from among the cluster of mobile web pager URLs, wherein the cluster URL represents the cluster;

determining a token from the cluster URL, wherein the token is determined at least in part based on a frequency with which the token appears in the cluster of mobile web page URLs; and

determining whether the cluster URL satisfies at least one landing page criterion.

14. The server of claim 13, wherein the at least one landing page criterion comprises at least one of the following:

a number of levels below the cluster URL in a hierarchical tree of the plurality of mobile web page URLs; and

a match between the token and a predefined keyword indicating a landing page.

15. The server of claim 12, wherein the landing page URL and the web host are associated with a same domain.

16. The server of claim 12, wherein the memory further stores program code that is operative to cause the processor to automatically perform actions comprising:

accessing a list of web host names associated with a domain that is also associated with the landing page URL;

determining the web host from the list if the token matches one of the web host names; and

determining the web host based on a match between the token and metadata associated with the web host if the token does not match any of the web host names in the list.

17. The server of claim 12, wherein the token comprises at least one of the following:

a directory path parameter and a query parameter.

18. The server of claim 12, wherein the memory further stores program code that is operative to cause the processor to automatically perform actions comprising:

matching the web host to the web category from a list of web categories determined from web pages that are not accessible by a limited capability device; and

matching the token to the web category from a list of web categories determined from web pages that are not accessible by a limited capability device.

19. A system for providing a search index, comprising:

a uniform resource locator (URL) analyzer that determines a cluster of mobile web page URLs that correspond to a plurality of mobile web pages accessible with a limited capability computing device, and wherein the URL analyzer determines a token based at least in part on a parameter of the mobile web page URLs;

a landing page identifier that identifies a landing page URL from the cluster;

a mapper that maps the landing page URL to a web host based at least in part on a token determined from the landing page URL, wherein the web host includes web pages that are not accessible with a limited capability computing device; and

a category tagger that associates the landing page URL with a web category based at least in part on the web host, wherein the web category identifies a content topic shared by web pages that are not accessible with a limited capability computing device; and

the search index including the landing page URL, the token, information associated with the web host, and the category, the search index being accessible by a search service to associate a search term with the landing page URL based at least in part on at least one of the token, the web host, or the category, and wherein the search term is submitted through a limited capability device.

20. The system of claim 19, further comprising a web crawler that accesses the plurality of mobile web pages to obtain the mobile web page URLs.