Manage search verticals (2023)

  • Article
  • 7 minutes to read

Search verticals are tabs on the search results page that display results of a specific type or from selected sources. For example, the Files vertical displays results categorized as files, making it easier for users to find documents. You can customize verticals in Microsoft Search to meet the needs of your organization or individual departments. Microsoft Search has two types of verticals, standard or standard and custom verticals. Default verticals like Everyone, Files, and People give you easy access to your most-used search results.

You can manage industries at two levels:

  • Good organization- An organization-level industry is displayed on the search results page when users search from your page.SharePointhome page,microsoft officeand Microsoft Search onCompartment
  • site level- A site-level branch is displayed on the search results page when users search a SharePoint site. For example, you might want to allow your customer service representatives to search for Severity 1 incidents directly on your department's SharePoint site.

The standard vertical

Default verticals are at the organization level in as-is experiencesSharePoint,microsoft officeand Microsoft Search onCompartmentor at the SharePoint site level on each site's search results page.

Here's a rundown of the customization options for the out-of-the-box verticals.

customization typeGood organizationsite level
rename verticalsYY
Disable verticalsPartialY
Add a queryPartialY

custom industries

You can add search industries relevant to your organization. For example, you could create one industry for marketing-related content and another for sales based on the type of information each department needs. You can add verticals to display results for content indexed by chart connectors or by SharePoint.

Create or change search branches

Industry management is run by a wizard, which guides you through the steps of defining the industry name, content source, and content scope to search. You can use a limited number ofKeyword Query Language (KQL)to define the scope of the vertical search for a specific content source. Filters can also be added to preconfigured and custom verticals at the organization and location level. For more information about filters, seeManage filters.

Manage lines of business at the organization level

  1. I amMicrosoft 365 admin center, go toVerticalpage in theadjustmentSection.
  2. Select an existing vertical and clickto editor clickAddto create a new vertical.
  3. After completing the setup steps, you can check and save the vertical.

Manage verticals at the site level

  1. On the SharePoint site where you want to manage lines of business, open the settings window by clicking the gear.
  2. ChooseAdditional Informationand then selectShow all site settings.
  3. Find the Microsoft search section, and then selectConfigure search settings.
  4. In the navigation pane, go to Personalized experience, and then selectVertical.
  5. Select an existing vertical and clickto editor clickAddto create a new vertical.
  6. Once you have established your settings, you can review and save the vertical.

Show industry on search results page

ASearch Results DesignIt is required for the graphical connector results to be rendered on the vertical search page. If you make sure you have a proper results layout, you can enable vertical search. After you activate or update an industry, it will take a few hours before you can see the changes on the search page. You can add cacheClear=true to the URL in SharePoint and Office to see the changes immediately. In Bing, add &features=uncachedVerticals to the working vertical URL to see the changes immediately.


Added branches are not visible inSharePointyofficewhen viewed by mobile web browsers.

Advanced configuration options

Multiple connections in a vertical

A search vertical can display results from multiple connector sources. This option offers flexibility in the design of your search results page. The vertical configuration process allows administrators to select multiple connections in the Content Source step.

There are so manysemantic tagsas possible this experience is amplified. Add semantic tags at schema definition and fetch time.Learn more about how to create and manage semantic tags.hereit is additional information for creating and managing semantic tags.


  • A link can be added as a content source in a single vertical. You cannot use cross-branch connections.

To set up a query for a search industry to which multiple connection sources have been added, use common source properties to build the query.

Keyword Query Language (KQL)

A query can be added to a branch to limit the results displayed in the search branchKeyword Query Language (KQL)(limited support). This page lists the available properties. We recommend using free text keywords and property constraints with Boolean operators to build the KQL. Dynamic ranking operators such as XRANK, proximity operators, and words are not supported.

Here are some sample queries.

Archive Page Results ExclusionNICHT (Pfad:http// ODERPfad:http//
Exclude results based on file type propertiesNO (file type: htm)

Use variables in the branch KQL query section to provide dynamic data as input to the branch query. Profile and Query String are the types of query variables that can be used.


You can use profile query variables to contextualize search results for the logged in user. Profile query variables retrieve values ​​from logged in usersProfile. For example, to create a "Tickets" vertical so that the user can find the support tickets assigned to them, you can specify the following query in the "Query" section during vertical creation on the admin page.

Asignado a: {Profile.accounts.userPrincipalName}

This trims the search results to show only the items assigned to the person doing the search.

profileresourceexposes the properties as collections. For example, information related to email addresses is disclosed through email capture, jobs as position capture, etc. All properties available in the user profile are exposed as query variables.

Imagine a user who has three email addresses available in the email collection, as shown here:

"emails": [{ "address": "", "id": "xyz", "source": { "Created by": "xyz", "Created on": "2222 ", " Type: "offiziell" }, "Typ": "Haupt" }, { "Address": "", "id": "abc", "Quelle": { "Erstellt von": "abc" , "Created on": "3333", "Type": "unofficial", }, "type": "work" }, { "address": "", "id": "pqr" , "source": { "Created by": "pqr", "Created on": "4444", "Type": "personal" }, "type": "personal" } ]
  • The consultationMyProperty: {Profile.emails.address}will decide to do itMy property: "".

  • To resolve all values ​​of the address attribute, use the multi-value expansion syntax. The consultation{|Mi propiedad:{Profile.emails.address}}will decide to do it((MyProperty:"")O(My property: "")O(My property: "")).

Use the operator "|" to solve multi-valued variables. See the table below for more examples of increasing the profile.

#Syntaxreturn value
2MyProperty:{Profile.emails}{Profile.emails} This will not be fixed becauseEmailsIts an object
3{?MyProperty:{Profile.emails}}This won't be fixed becauseEmailsis an object He "?" -the operator ignores query variables that are not resolved. This variable is removed as it is passed further down the query stack.
4{|My Property: {Profile.emails.source.Type}}((MyProperty:"official") OR (MyProperty:"unofficial") OR (MyProperty:"personal"))

Query String Variables

Query string variables allow you to customize search results based on how users interact with SharePoint sites. It does this by adding key-value pairs to the search URL. Suppose you have a SharePoint site that provides information about a project with a simple web part that shows the work in progress. Clicking the In Progress web part links users to the Work Items search branch, which refines the results to display only items marked asIn process.

This can be done by specifying the following query in the Query during vertical build section on the admin page.

Status:{query string.status}

The SharePoint Site Button Web Part URL must be updated to pass the following key-value pair: https://{your-domain}{site-name}/_layouts/15 /search. aspx/ {vertical id}?state=In progress

Query state:{QueryString.state} resolves to state:In progress.

Here are more examples of query string expansion.

#query syntaxURL Syntaxreturn value
1MyPropiedad:{QueryString.state}https://{Ihre-Domain}{Site-Name}/_layouts/15/search.aspx/{vertikale-ID}?state=InProgressMyProperty:In progress
2MiPropiedad:{QueryString.state} OR MiPropiedad:{QueryString.priority}https://{Ihre-Domain}{Site-Name}/_layouts/15/search.aspx/{vertikale-ID}?state=InProgress&priority=1MyProperty:InProgress OR MyProperty:1
3{?MyPropiedad:{QueryString.state}}https://{Ihre-Domain}{Site-Name}/_layouts/15/search.aspx/{vertikale-ID}?State=InProgressThe state is not resolved here because QueryStrings is case sensitive. He "?" -the operator ignores query variables that are not resolved. This variable is removed as it is passed further down the query stack.
4{|MyPropiedad: {QueryString.state}}https://{Ihre-Domain}{Site-Name}/_layouts/15/search.aspx/{vertikale-ID}?state=InProgress,Cerrado(MyProperty:InProgress) ODER (MyProperty:Closed)
the | -operator is used to resolve multivalued variables. Variable values ​​must be passed using the comma delimiter as shown in the URL syntax.
5{MyPropiedad: {QueryString.state}}https://{Ihre-Domain}{Site-Name}/_layouts/15/search.aspx/{vertikale-ID}?state=InProgress,CerradoMyProperty:In progress
Only the first state value of the URL is taken here because the query syntax does not define it as a multi-valued variable.


  • Language localization does not apply to out-of-the-box industry names after they have been changed.
  • Custom verticals are not displayed in the mobile view of Microsoft Search.
  • Adding queries in the people vertical is not supported.
  • Vertical changes and new industries are not visible to an organization's guest users.
  • Vertical reordering is not supported.
  • Vertical renaming for the All tab is not supported in Microsoft Search in Bing.
  • Query string variables can only be used on SharePoint sites.

Problem solving

Below is a list of common problems you may encounter and the steps you should take to fix them.

I see the error message "Something went wrong" on the vertical.Both the vertical type and the result type are required to complete the configuration. Make sure both are set to the content source.
I don't see any content source on the vertical side.Make sure you have configured connectors and indexed data.
Top Articles
Latest Posts
Article information

Author: Neely Ledner

Last Updated: 02/23/2023

Views: 6352

Rating: 4.1 / 5 (42 voted)

Reviews: 89% of readers found this page helpful

Author information

Name: Neely Ledner

Birthday: 1998-06-09

Address: 443 Barrows Terrace, New Jodyberg, CO 57462-5329

Phone: +2433516856029

Job: Central Legal Facilitator

Hobby: Backpacking, Jogging, Magic, Driving, Macrame, Embroidery, Foraging

Introduction: My name is Neely Ledner, I am a bright, determined, beautiful, adventurous, adventurous, spotless, calm person who loves writing and wants to share my knowledge and understanding with you.