Systems and methods for providing a service directory for automatic search engine indexing

Systems, methods, and non-transitory computer-readable media can present a service directory landing page comprising a plurality of selectable service category options associated with a plurality of pre-defined service categories. A search results page is presented, including one or more search results based on search criteria. Each of the one or more search results is associated with an entity page of a social networking system. The service directory landing page and the search results page are accessible without logging into the social networking system. Each entity page on the social networking system is accessible only when logged into the social networking system.

FIELD OF THE INVENTION

The present technology relates to the field of social networking systems. More particularly, the present technology relates to systems and methods for providing a service directory to assist in automated search engine indexing.

BACKGROUND

Today, people often utilize computing devices (or systems) for a wide variety of purposes. Users can use their computing devices, for example, to interact with one another, create content, share content, and view content. In some cases, a user can utilize his or her computing device to access a social networking system (or service). The user can provide, post, share, and access various content items, such as status updates, images, videos, articles, and links, via the social networking system.

A social networking system can include one or more pages associated with entities on the social networking system. For example, the social networking system can include one or more pages associated with merchants and/or service providers looking for exposure with consumers. In certain contexts, individual users can be distinguished from entity users on the social networking system. For example, an entity user or an entity account can be associated with a particular entity, and can be controlled by one or more administrators of the entity account, whereas an individual user can be associated with a particular individual. Both individual users and entity users can interact with one another on the social networking system by, for example, sending messages to one another, posting content to other users' accounts, sharing content publicly for publication to other users' newsfeeds, and the like. Interactions between users on a social networking system can be mutually beneficial. Participation in the social networking system by users can be encouraged and promoted by improving tools and features to facilitate interaction on the social networking system.

SUMMARY

Various embodiments of the present disclosure can include systems, methods, and non-transitory computer readable media configured to present a service directory landing page comprising a plurality of selectable service category options associated with a plurality of pre-defined service categories. A search results page is presented, including one or more search results based on search criteria. Each of the one or more search results is associated with an entity page of a social networking system. The service directory landing page and the search results page are accessible without logging into the social networking system. Each entity page on the social networking system is accessible only when logged into the social networking system.

In an embodiment, the search criteria include a service category and a particular location.

In an embodiment, the search results page comprises a plurality of alternative service category options associated with the service category.

In an embodiment, a selection of an alternative service category from the plurality of alternative service category options is received. An updated search results page is presented based on the selection of the alternative service category option.

In an embodiment, the search results page comprises a plurality of alternative location options associated with the particular location.

In an embodiment, a selection of an alternative location option from the plurality of alternative location options is received. An updated search results page is presented based on the selection of the alternative location option.

In an embodiment, the services directory landing page is associated with a particular location.

In an embodiment, the particular location is automatically determined based on user information.

In an embodiment, the plurality of selectable service category options are selected from the plurality of pre-defined service categories based on the particular location.

In an embodiment, the plurality of selectable service category options are selected from the plurality of pre-defined service categories based on a popularity of each service category of the plurality of pre-defined service categories in the particular location.

DETAILED DESCRIPTION

Service Directory for Automated Search Engine Indexing

People often utilize computing devices (or systems) for a wide variety of purposes. Users can use their computing devices to, for example, interact with one another, access content, share content, and create content. In some cases, content items can include postings from users of a social networking system. The postings may include text and media content items, such as images, videos, and audio. The postings may be published to the social network for consumption by others.

A social networking system can include one or more pages associated with entities on the social networking system. For example, the social networking system can include one or more pages associated with merchants and/or service providers looking for exposure with consumers. In certain contexts, individual users can be distinguished from entity users on the social networking system. For example, an entity user or an entity account can be associated with a particular entity, and can be controlled by one or more administrators of the entity account, whereas an individual user can be associated with a particular individual. Both individual users and entity users can interact with one another on the social networking system by, for example, sending messages to one another, posting content to other users' accounts, sharing content publicly for publication to other users' newsfeeds, and the like. Interactions between users on a social networking system can be mutually beneficial. Participation in the social networking system by users can be encouraged and promoted by improving tools and features to facilitate interaction on the social networking system.

Under conventional approaches, entity pages on a social networking system can help merchants and/or service providers provide information about their businesses or services to consumers. However, entities with entity pages on a social networking system may wish to attract customers or consumers that are not members of the social networking system. The social networking system may also wish to have non-members of the social networking system access entity pages on the social networking system so as to encourage non-members to interact on and/or join the social networking system. However, under conventional approaches, it can be difficult for consumers to discover entity pages on a social networking system of which they are not a member. This may be the case, for example, because such entity pages are not easily found through third party search engines. Accordingly, such conventional approaches may engender these and other problems arising in computer technology.

An improved approach rooted in computer technology overcomes the foregoing and other disadvantages associated with conventional approaches specifically arising in the realm of computer technology. In general, a service directory can be provided on a social networking system that allows users to find entity pages on a social networking system. In various embodiments, the service directory can be publicly accessibly such that users may utilize the service directory regardless of whether or not the user is a user or member of the social networking system. The services directory can have a linking structure that maximizes public exposure of entity pages using selectable, e.g., click-through, options. This linking structure can, thereby, increase exposure of entity pages to automated search engine crawlers. By making various portions of the service directory publicly available, and permitting new entity pages to be discovered by clicking on various links within the service directory, entity pages on the social networking system can be easily discovered and indexed by automated search engine crawlers, thereby increasing visibility through third party search engines, even if the entity pages themselves are only accessible by users logged into the social networking system.

While the examples used herein may describe a service directory in which a user can search for service categories and/or entity pages on a social networking system, the approaches described herein can be adapted to searches for any user on a social networking system. As such, the approaches described herein need not be limited to searches for entity pages or service categories on a social networking system.

FIG. 1illustrates an example system100including an example service directory module102, according to an embodiment of the present disclosure. The service directory module102can be configured to provide a service directory in which a plurality of entity pages on a social networking system are categorized into various, pre-defined service categories. In certain embodiments, an entity page can be associated with one or more pre-defined service categories based on service category selections made by an administrator of the entity page. Each entity page can also be associated with one or more locations. An entity page can be associated with one or more locations based on location information specified by, for example, an administrator of the entity page. As will be described in greater detail herein, the service directory can be organized using a linking structure that is useful for optimizing automated search engine indexing. The linking structure allows an automated search engine crawler to be exposed to as many entity pages as possible by automatically clicking through links or selectable portions of the service directory. As the automated search engine crawler is exposed to more entity pages, the automated search engine crawler can index the entity pages by, for example, associating said entity pages with various service categories and locations.

The services directory can have a landing page on which a user can perform a search for entity pages on the social networking system. The landing page can also include service category options that are selectable by a user. When a user selects a service category option, a search can be run for entity pages associated with the selected service category option. Once the user runs a search by, for example, manually entering search criteria or selecting a service category option, the user can be presented with a search results page that includes one or more entity pages on the social networking system that match the search. In certain embodiments, the service directory landing page and the search results page can be publicly accessible, such that users are able to access these pages without logging into or being members of the social networking system. By making these pages publicly accessible, automated search engine crawlers are able to navigate and index the various entity pages that are listed as search results. In certain embodiments, the search results page can also include links to related service categories or related locations that, when selected, lead to new search results that may include different entity pages from the initial search. As the automated search engine crawler selects different related service categories or related locations, the automated search engine crawler will be exposed to more entity pages for indexing. Updated search results pages can also include even more related service categories and related locations, such that the automated search engine crawler can continue to click through links to expose the crawler to more and more entity pages.

As shown in the example ofFIG. 1, the service directory module102can include a landing page module104and a search results module106. In some instances, the example system100can include at least one data store110. The components (e.g., modules, elements, etc.) shown in this figure and all figures herein are exemplary only, and other implementations may include additional, fewer, integrated, or different components. Some components may not be shown so as not to obscure relevant details. In various embodiments, one or more of the functionalities described in connection with the service directory module102can be implemented in any suitable combinations.

In some embodiments, the service directory module102can be implemented, in part or in whole, as software, hardware, or any combination thereof. In general, a module, as discussed herein, can be associated with software, hardware, or any combination thereof. In some implementations, one or more functions, tasks, and/or operations of modules can be carried out or performed by software routines, software processes, hardware, and/or any combination thereof. In some cases, the service directory module102can be implemented, in part or in whole, as software running on one or more computing devices or systems, such as on a user or client computing device. For example, the service directory module102, or at least a portion thereof, can be implemented as or within an application (e.g., app), a program, or an applet, etc., running on a user computing device or a client computing system, such as the user device610ofFIG. 6. In another example, the service directory module102, or at least a portion thereof, can be implemented using one or more computing devices or systems that include one or more servers, such as network servers or cloud servers. In some instances, the service directory module102can, in part or in whole, be implemented within or configured to operate in conjunction with a social networking system (or service), such as the social networking system630ofFIG. 6. It should be understood that there can be many variations or other possibilities.

The service directory module102can be configured to communicate and/or operate with the at least one data store110, as shown in the example system100. The data store110can be configured to store and maintain various types of data. In some implementations, the data store110can store information associated with the social networking system (e.g., the social networking system630ofFIG. 6). The information associated with the social networking system can include data about users, user identifiers, social connections, social interactions, profile information, demographic information, locations, geo-fenced areas, maps, places, events, pages, groups, posts, communications, content, feeds, account settings, privacy settings, a social graph, and various other types of data. In some embodiments, the data store110can store information that is utilized by the service directory module102. For example, the data store110can store entity page information, service category groupings, historical service directory search information, and the like. It is contemplated that there can be many variations or other possibilities.

The landing page module104can be configured to provide a service directory landing page. The landing page can be the first page a user is exposed to when accessing the service directory. The landing page can be configured to allow a user to search for a service category. The landing page can also be configured to allow a user to select a service category from various service category options. For example, the user can be provided with a list of service category options. Service category options can be presented as, for example, selectable icons or selectable text. Searching for and/or selecting a service category can yield a set of search results of entity pages that satisfy search criteria (e.g., are associated with the selected service category). For example, if a user needs a plumber, the user can enter the search term “plumber” or “plumbing,” or the user can select a service category option associated with the service category “plumbing.” In this case, the user can be presented with a list of one or more entities that match the service category. In certain embodiments, the search may also include a location field to specify a particular location. In this way, search results can be limited to entities that are located near the specified location and/or service the specified location. In certain embodiments, as will be discussed in greater detail below, the landing page may be associated with a particular location, such that when a user selects a service category option listed on the landing page, a search is run for entity pages that match both the selected service category and the particular location.

In certain embodiments, the landing page can be available publicly, such that users can access the landing page regardless of whether or not they are signed into or members of a social networking system. By making the landing page available publicly, the landing page can be made available to automated search engine crawlers. As will be described in greater detail herein with respect to various example scenarios, the landing page provides a multitude of click-through options that allow an automated search engine crawler to continuously click through to new pages and perform new searches that expose the search engine crawler to more and more entity pages on the social networking system. The landing page module202is discussed in greater detail herein with respect toFIG. 2.

The search results module106can be configured to run a search and provide search results in a search results page. As mentioned, a search may be run based on various search criteria, such as user entered search terms (e.g., a service category, location information, an entity name, etc.) or selection of a service category option by a user. Search criteria can also include a location that is either entered by a user, or automatically determined by a computing system, as will be described in greater detail herein.

A search results page can include one or more search results corresponding to entity pages on a social networking system that match search criteria. Each search result can lead users to an associated entity page. In certain embodiments, entity pages on a social networking system may be accessible only to logged-in users of the social networking system, or certain portions of entity pages may be accessible only to logged-in users. As such, entity pages may not be completely accessible, or accessible at all, to automated search engine crawlers, which are typically not logged into a social networking system, and are, therefore, generally treated as non-members or logged out users. As discussed above, however, service directory search results pages can be made publicly accessible, so that search results are available to users regardless of whether said users are logged into or members of a social networking system. By making search results available publicly, they are also accessible to automated search engine crawlers. The automated search engine crawlers can then index all of the terms on a search results page and associate them with the various entity pages listed in the search results, even if entity pages themselves cannot be accessed by the crawler. As entity pages are indexed more frequently, and more frequently associated with various search terms (e.g., service categories or locations), entity pages may be more favorably ranked in third party search engine ranking algorithms.

Each search result can include information about an entity associated with the search result, such as the entity's name, a description of the entity, address, phone number, service categories associated with the entity, etc. Each entry can also include social context information for each entity. For example, social context information can include a rating and/or reviews for the entity (e.g., reviews posted to the social networking system by other users of the social networking system, or reviews posted to other sites), the number of users on the social networking system that have liked or followed the entity page, the number of users that have visited the entity page, and the like. Each entry in the search results list can also include one or more call to action buttons or icons. A call to action button can be selected by a user to take a particular action with respect to the entity and/or the entity page. For example, the user can select a “Like” call to action button to like a particular entity's page, or can select a “Message” call to action button to send a message to an entity's page. Certain call to action buttons can be presented by default for each entity page (e.g., a “Like” or “Message” button), while other call to action buttons can be specifically selected by an entity page. For example, certain entity pages may offer online appointment scheduling services, and can offer a “Book Now” call to action button that directs the user to the online appointment scheduling service. The information provided for each entity page can be indexed by an automated search engine crawler to associate each entity page with the information provided.

The search results module106can also be configured to provide one or more related search criteria. For example, the search results module106can provide a list of related service categories that are related to or similar to a current service category currently being explored by a user or search engine crawler. If the search engine crawler selects one of the related service categories, another search can be run based on the selected related service category. In certain embodiments, related service categories can be determined based on hierarchical groupings of categories. For example, the service directory can include tiered levels of categories, each level defining categories with greater specificity. For example, a first or highest tier of categories can be somewhat broad, e.g., automotive, home improvement, spa/beauty/personal care, etc. Each category in this highest level of categories can then include one or more sub-categories. For example, the “automotive” category can include the categories “auto repair,” “car dealership,” “car wash,” etc.; the “home improvement” category can include the categories “cleaning,” “electrician,” “gardening,” “mover,” “painter,” “plumbing,” etc. Each of these narrower, lower level categories can further include their own lower level categories, e.g., the automotive repair category can include “glass repair,” “engine repair,” “body shop,” etc. Based on these tiered groupings of categories, related service categories can be recommended to the user. For example, if the user has searched for “plumber,” it can be determined that “plumber” is a sub-category of the higher level category “home improvement,” and all other categories that fall under “home improvement” can be recommended to the user. In certain embodiments, other related categories that are not in the same grouping, but still related to the current service category can be recommended. For example, if a user searches for restaurants, related service categories may include service categories for after-dinner activities, even if the after-dinner activities do not fall into the same categorical grouping as the category “restaurants.”

The related service categories provide selectable links that an automated search engine crawler can select to expose the search engine crawler to new entity pages. For example, if the search engine crawler initially selects the service category “plumbing,” the search results may expose the search engine crawler to a variety of entity pages associated with the service category “plumbing.” However, if “painter” is listed as a related service category, the automated search engine crawler can select, or click through to the “painter” service category, and be exposed to brand new search results for entity pages that are associated with the service category “painter.” By providing this linking structure, the service directory can expose an automated search engine crawler to all entity pages on a social networking system associated with the service category “plumbing,” and then expose the automated search engine crawler to all entity pages on the social networking system associated with the related service category “painter.” It should be appreciated that the “painter” service category search results will have its own set of related service categories, that will lead the automated search engine crawler to additional search results and additional entity pages, and this can continue indefinitely until the search engine crawler has indexed all entity pages on a social networking system.

In certain embodiments, when a user runs a search for a particular service category (e.g., a crawler selecting a particular service category option), the search results can display category “breadcrumbs” indicative of any higher level categories to which the particular service category belongs. For example, if the search engine crawler initially selects a service category option for “plumbing,” the service category “plumbing” may belong to the higher level category “home improvement,” which itself may belong to the higher level category “services.” In this example, the breadcrumbs might be displayed as follows: “Services>Home Improvement>Plumbing.” These breadcrumbs on the search results page allow the search engine crawler to index these terms with each of the entity pages listed in the search results. As such, if an entity page is listed in the search results for “plumbing,” the entity page will not only be associated by the crawler with the category “plumbing,” but also “home improvement” and “service.” The breadcrumbs can also be selectable so as to expose an automated search engine crawler to even more selectable links that lead to different search results and entity pages. For example, an automated search engine crawler can select the breadcrumb category “home improvement” to yield new search results for all entity pages associated with the category “home improvement.” Presumably, the search results for the category “home improvement” will be different than those that were presented for the “plumbing” search results, and the automated search engine crawler will be exposed to different entity pages it can index.

The search results module106can also be configured to provide a list of alternative locations that are nearby or otherwise relate to the location specified in the current search criteria (e.g., within a threshold distance or threshold number of geolocations). For example, if a user searches for plumbers in Palo Alto, Calif., the user may be provided with alternative locations nearby Palo Alto, Calif., such as Mountain View, Calif.; San Jose, Calif.; Fremont, Calif., etc. By selecting one of these alternative locations, the user can run a new search based on the selected alternative location, e.g., search for plumbers in Mountain View, Calif. Certain service categories may be more amenable to a broader geographic search area, whereas other service categories may require a more localized search. For example, if a user is searching for a coffee shop in a particular neighborhood, it may not be particularly useful to recommend a coffee shop in a neighboring city; whereas if a user is searching for a plumber in a particular city, the user may still be interested in plumbers in nearby cities so long as those plumbers also service the user's city. As such, the alternative locations recommended to a user may vary based on the service category specified in the current search, and a location-sensitivity associated with the service category.

Similar to the discussion above with respect to related service categories and breadcrumb categories, presentation of selectable alternative locations can provide an automated search engine crawler with more selectable options that will yield new search results, i.e., new entity pages to be indexed. For example, if a search engine crawler is initially presented with search results for internet service providers in San Francisco, a set of entity pages for internet services providers near San Francisco can be presented. These entity pages can be indexed by the search engine crawler. The search results can include a list of alternative locations including Palo Alto, Sacramento, and Los Angeles. If the automated search engine crawler selects “Los Angeles,” a new set of search results can be presented for internet service providers in Los Angeles, which can be also indexed by the crawler. The search results for internet service providers in Los Angeles can include different alternative locations, such as San Diego, Palm Springs, and Phoenix. By continuously clicking through alternative location recommendations, the automated search engine crawler can be exposed to entity pages for internet service providers from city to city to city until all entity pages for internet service providers in all cities have been indexed.

In certain embodiments, search results can be paginated, with each page of search results containing a pre-determined number of search results. The search results page can include links to access additional pages of search results. The paginated search results allow an automated search engine crawler to access all search results by clicking through the various page links, as opposed to, for example, a single page, infinite scroll presentation, which requires scrolling to load additional results, rather than clicking or selecting.

FIG. 2illustrates an example landing page module202configured to provide a user with a landing page for navigating and/or searching a service directory, according to an embodiment of the present disclosure. In some embodiments, the landing page module104ofFIG. 1can be implemented as the landing page module202. As shown in the example ofFIG. 2, the landing page module202can include a default location module204and a category selection module206.

The default location module204can be configured to determine a default location for a services directory landing page. In certain embodiments, when a user is presented with a landing page, presentation of the landing page can depend on a particular location determination by the default location module204. For example, a background image of the landing page may be associated with the particular location, or service category options may be selectively presented based on the particular location.

The landing page can include a search function. The search function can allow a user to specify a particular location by manually entering location criteria to limit the search to entity pages that are associated with and/or relevant to the location specified by the user. However, if the “user” is an automated search engine crawler, the crawler may not be able to define or fill in location information. The default location module206can be configured to predict or determine a user's location, and automatically fill in location information. The user's location can be predicted and/or determined based on any available information. This can include, for example, a city of residence or hometown specified by the user on a social networking system, a location associated with the user's current IP address, a recent check-in posted to the social networking system by the user, a recent status update posted to the social networking system indicative of a particular location, previous searches performed by the user containing location information, etc. In certain embodiments, a location associated with an automated search engine crawler's IP address can be entered as a default location. If a location cannot be determined based on available information, a pre-determined default location can be entered. For example, if a user's location cannot be determined, it can be pre-determined that the location “Palo Alto, Calif.” is automatically entered.

The category selection module206can be configured to present one or more service category options for selection by a user (such as an automated search engine crawler). As discussed above, in addition to a search function, the landing page can include one or more service category options that a user can select. Selection of a particular service category option can result in a search being run for the selected service category. A set of service categories can be pre-defined by, for example, a social networking system. In certain embodiments, a subset of service categories can be featured and/or selected for presentation. For example, a set of featured service categories may be presented in a more easily visible way, such as larger icons that have images associated with each featured service category. A subset of featured service categories can be selected based on various featured category selection criteria. For example, service categories can be ranked based on category ranking criteria. The category ranking criteria can include the popularity of the service category (e.g., the frequency with which the service category is selected and/or searched), to name one example. In certain embodiments, ranking of service categories can vary based on location information specified by the default location module204. For example, service categories can be ranked based on popularity in the specified location. If the default location module204specifies a location of Seattle, Wash., the eight most popular service categories for Seattle can be displayed as featured service categories. There may be various groupings of service category options displayed. For example, a subset of ten featured category options can be selected and displayed with large image icons in a first portion of a user interface, and another subset of fifty categories can be selected and displayed textually in another portion of the user interface to give the user additional service category options to select. Alternatively, if it is feasible to display all service category options to a user, then the user may be presented with all service category options defined by the social networking system. For example, featured category options can be presented in a first portion of a user interface, and then a listing of all service category options can be listed in another portion of the user interface.

The various, selectable service category options listed on the landing page present an automated search engine crawler with multiple options for being exposed to and indexing entity pages on a social networking system. For example, if a landing page includes selectable service category options for Plumbing, Gardening, Painters, Massages, and Electricians, an automated search engine crawler can begin by selecting “Plumbing” to index all entity pages returned by a search for “Plumbing.” The automated search engine crawler can then select “Gardening” to index all entity pages returned by a search for “Gardening,” and so forth. By presenting a large number of selectable service category options on the landing page, an automated search engine crawler can be exposed to a very large number of entity pages. While it may be the case that search results are limited to a particular location determined by the default location module204, as discussed above, each set of search results can include alternative location recommendations which can lead the automated search engine crawler to entity pages in alternative locations.

FIG. 3illustrates an example scenario300associated with providing a service directory landing page, according to an embodiment of the present disclosure. The example scenario300includes a landing page interface302. The landing page interface302includes a search portion304, which has a search box306for a user to enter search terms, a location box308for a user to enter location information, and a search button310for a user to run a search. In some cases, the user can be a non-member of a social networking system that provides the service directory landing page, or a member that is not logged into the social networking system. In other cases, the user can be logged into the social networking system. The location box308can be pre-filled with location information based on a prediction or determination of a current user's location, or a pre-determined default location. In certain embodiments, a background portion of the search portion304can include an image associated with the location information stated in the location box308.

The landing page interface302also includes a featured categories portion312. The featured categories portion312includes a subset of categories that have been selected from a larger set of categories based on featured category selection criteria. As discussed above, featured category selection criteria can vary. For example, in the example scenario300, the featured categories portion312includes eight featured categories314a-314h. These eight featured categories may have been selected based on a ranking of categories according to popularity for the determined location. In this example, the eight most popular categories for users in Palo Alto, Calif. would be displayed. Popularity may be determined based on the number of users who have searched for each category in a predetermined period of time, e.g., the last day, the last week, the last 30 days, or the last year. If a user, such as an automated search engine crawler, selects a featured category314a-314h, a search can be run for entities associated with the selected category. For example, if a user selects the “arts and marketing” category314f, a search can be run for entity pages associated with the category “arts and marketing” in Palo Alto, Calif.

Below the featured categories portion312is an additional categories portion316, in which additional categories are listed. The additional categories can include the featured categories314a-314h, or can exclude them. The additional categories portion316may include all service category options available for selection (e.g., all service categories defined by a social networking system), or may include a different subset of service categories. For example, if the featured categories portion312represents the top eight service categories based on ranking criteria, the additional categories portion316may include the top fifty service categories based on the same or different ranking criteria. The user can select any category within the additional categories portion316to run a search for entities associated with that service category.

FIG. 4illustrates an example scenario400associated with providing search results in a search results page, according to an embodiment of the present disclosure. The example scenario400includes a search results interface402. The search results interface402includes a search portion404, which includes a search box406and a location box408. The search portion404can display the search parameters or search criteria used for a current search. For example, in the example scenario402, the user has run a search for plumbers in New York, N.Y. It should be understood that, while these search criteria may have been entered manually by a user, they may also be the result of a selection by a user, such as an automated search engine crawler. For example, the location “New York, N.Y.” may have been automatically determined (for example, by the default location module204), and the search term “plumbers” may be the result of a service category option selection by an automated search engine crawler.

The search results interface402displays search results for the current search in a search results portion412. The search results portion412includes category breadcrumbs422to provide higher level category groups to which the searched category belongs. In the example scenario400, the current search is for the category “plumbers,” which falls under the higher level category “home improvement,” which falls under the higher level category “services.”

The search results portion412also includes search results414,416. Each search result414,416is associated with a particular entity page on a social networking system. The first search result414is associated with the entity page for the entity “Green Boot Plumbing.” The search result414includes information about Green Boot Plumbing, such as a rating (4.7stars), a phone number, an address, business hours, a review of the entity, and a description of the entity.

The search results portion412also includes additional location recommendations426. The additional location recommendations426can include locations nearby the location used for the current search. This may include, for example, neighboring cities or neighborhoods, or cities in the same metropolitan area or state. The additional location recommendations426may be selectable, such that if a user (such as an automated search engine crawler) selects one of the additional location recommendations, a new search can be run using the selected location. For example, if the user selects “Newark,” a new search can be run for plumbers in Newark, and new search results presented.

The search results portion412also includes additional service category recommendations428. The additional service category recommendations can include additional service categories that are in some way related to the service category in the current search. For example, the additional service category recommendations can include one or more service categories that are grouped into the same higher level category as the currently searched service category. In the example scenario400, the currently searched service category, “plumbing,” falls in the higher level category “home improvement.” As such, the additional service category recommendations can include other service categories that fall within the higher level category “home improvement.” If the currently searched service category has lower level categories associated with it, the additional service category recommendation can include these lower level categories. For example, if the service category plumber had associated with it lower level categories such as “copper plumbing,” “toilet repair,” “sink repair,” “rain shower installation,” these lower level categories could be listed in the additional service category recommendations428. The additional service category recommendations can be selectable by the user to run a new search using the newly selected service category.

The search results interface402also includes selectable page numbers430. The search results may be divided into pages, with each page of search results containing a pre-determined number of search results. As discussed above, separating search results into discrete pages accessible by clicking on selectable links allows for an automated search engine crawler to move through the entire list of search results, indexing all entity pages along the way.

FIG. 5illustrates an example method500associated with providing a service directory for automated search engine indexing, according to an embodiment of the present disclosure. It should be appreciated that there can be additional, fewer, or alternative steps performed in similar or alternative orders, or in parallel, within the scope of the various embodiments discussed herein unless otherwise stated.

At block502, the example method500can receive a plurality of entity pages on a social networking system. At block504, the example method500can associate each of the plurality of entity pages with one or more service categories selected from a plurality of pre-defined service categories. At block506, the example method500can present a service directory landing page comprising a plurality of selectable service category options associated with the plurality of pre-defined service categories for selection by a user. At block508, the example method500can present a search results page including one or more search results based on search criteria, each of the one or more search results being associated with an entity page of the plurality of entity pages. The service directory landing page and the search results page are accessible without logging into the social networking system, and the plurality of entity pages are accessible only when logged into the social networking system.

It is contemplated that there can be many other uses, applications, and/or variations associated with the various embodiments of the present disclosure. For example, in some cases, user can choose whether or not to opt-in to utilize the disclosed technology. The disclosed technology can also ensure that various privacy settings and preferences are maintained and can prevent private information from being divulged. In another example, various embodiments of the present disclosure can learn, improve, and/or be refined over time.

Social Networking System—Example Implementation

The user device610comprises one or more computing devices that can receive input from a user and transmit and receive data via the network650. In one embodiment, the user device610is a conventional computer system executing, for example, a Microsoft Windows compatible operating system (OS), Apple OS X, and/or a Linux distribution. In another embodiment, the user device610can be a device having computer functionality, such as a smart-phone, a tablet, a personal digital assistant (PDA), a mobile telephone, etc. The user device610is configured to communicate via the network650. The user device610can execute an application, for example, a browser application that allows a user of the user device610to interact with the social networking system630. In another embodiment, the user device610interacts with the social networking system630through an application programming interface (API) provided by the native operating system of the user device610, such as iOS and ANDROID. The user device610is configured to communicate with the external system620and the social networking system630via the network650, which may comprise any combination of local area and/or wide area networks, using wired and/or wireless communication systems.

The external system620includes one or more web servers that include one or more web pages622a,622b, which are communicated to the user device610using the network650. The external system620is separate from the social networking system630. For example, the external system620is associated with a first domain, while the social networking system630is associated with a separate social networking domain. Web pages622a,622b, included in the external system620, comprise markup language documents614identifying content and including instructions specifying formatting or presentation of the identified content.

In some embodiments, the social networking system630can include a service directory module646. The service directory module646can, for example, be implemented as the service directory module102, as discussed in more detail herein. As discussed previously, it should be appreciated that there can be many variations or other possibilities. For example, in some embodiments, one or more functionalities of the service directory module646can be implemented in the user device610.

Hardware Implementation