Use Managed Properties for Better Search: Practical Checklist for SharePoint Owners

As a SharePoint site owner, you may notice that search results do not always show the most relevant files or metadata. This often happens because SharePoint Search relies on crawled properties that are not optimized for how your users search. Managed properties are the key to fixing this: they let you map raw crawled data into searchable, refinable fields that users can filter and sort by. This article provides a practical checklist for creating and managing managed properties so your search results become more accurate and useful.

What Are Managed Properties and Why They Matter for Search

SharePoint Search works by crawling content and storing metadata in crawled properties. These crawled properties are raw data extracted from documents, list items, and pages. For example, a document library column named “Project Name” becomes a crawled property like ows_Project_x0020_Name. However, crawled properties cannot be used directly in search queries or refiners. Managed properties bridge this gap: they are user-friendly names that you map to one or more crawled properties. Once mapped, a managed property can be set as searchable, queryable, retrievable, or refinable.

When a managed property is marked as searchable, its content is included in the full-text search index. Queryable means users can use it in search queries with syntax like ProjectName:Alpha. Retrievable allows the property value to appear in search results. Refinable adds the property to the refinement panel so users can filter results. Without managed properties, users can only search across the default set of properties like Title, Author, and Created. This limits the ability to find content by custom metadata that is meaningful to your organization.

Prerequisites Before You Start

To create and manage managed properties, you need at least SharePoint administrator permissions in the SharePoint admin center. You also need a search service application that is configured for your tenant. For on-premises SharePoint Server, you need access to Central Administration and the Search Service Application. For SharePoint Online, the steps are done in the SharePoint admin center under Search. Ensure that the content you want to improve search for has already been crawled at least once. If no crawled properties appear for your custom columns, run a full crawl or wait for the incremental crawl to complete.

Checklist: Steps to Create and Configure Managed Properties

Follow this checklist to create managed properties that improve search relevance for your site. Each step builds on the previous one.

1. Identify the metadata columns that matter most
   Review your site columns and document library columns. Focus on columns that users frequently search or filter by, such as Project Name, Department, Document Type, or Status. Make a list of these columns and their display names.
2. Find the corresponding crawled properties
   In the SharePoint admin center, go to Search > Managed Properties. Click Crawled Properties. Search for a term related to your column, such as Project. Look for crawled properties with a name like ows_Project_x0020_Name or ows_ProjectName. Note the exact crawled property name. If you do not see it, run a full crawl first.
3. Create a new managed property
   In Managed Properties, click New Managed Property. Give it a clear name, such as ProjectName. The name cannot contain spaces or special characters. Set the Type to Text for most custom columns. Choose the appropriate type if your column is Date, Integer, Decimal, or Yes/No.
4. Map the crawled property to the managed property
   In the Mapping section, click Add Mapping. Paste or type the crawled property name exactly. Select the Include in hash set check box if you plan to use the property for refiners. Click OK.
5. Set the search behavior flags
   Under Searchable, select Yes to include the property content in full-text search. Under Queryable, select Yes to allow users to query the property directly. Under Retrievable, select Yes to show the property value in search results. Under Refinable, select Yes to enable refiners. For most custom metadata, enable all four flags. For date columns, you may want to disable Searchable but keep the other flags.
6. Allow multiple values if needed
   If your column allows multiple values, select Allow multiple values. This is common for choice columns that allow multiple selections. If you are unsure, leave it unchecked.
7. Save the managed property
   Click OK to save. The property appears in the list of managed properties. It may take up to 15 minutes for the change to take effect in SharePoint Online. For on-premises, you may need to run a full crawl.
8. Test the managed property in search
   Go to a site that uses the column. Perform a search query using the property name, for example ProjectName:Alpha. Verify that results appear and that the property value shows in the result display. If not, check that the crawled property is populated and that the mapping is correct.
9. Add the managed property to a search result refinement
   If you enabled Refinable, go to the search results page and verify that the property appears in the refinement panel. If it does not, you may need to add it to the Refinement configuration in the search result web part.

Common Mistakes and Limitations When Using Managed Properties

No crawled properties appear for my custom columns

Crawled properties are only created after a full crawl of the content. In SharePoint Online, full crawls happen automatically when new content is added, but it may take several hours. To force a crawl, go to the Search administration page and click Reindex site or Reindex list/library. In on-premises, run a full crawl of the content source that contains the site. After the crawl completes, check the Crawled Properties list again.

Managed property returns no results even after mapping

This usually occurs because the crawled property is not populated with data. Verify that the column contains values in at least one item. Also ensure that the crawled property name is spelled exactly as it appears in the Crawled Properties list. If the crawled property has a category, verify that you are searching in the correct category. In some cases, the crawled property may be a variant of the column name, such as ows_ProjectName instead of ows_Project_x0020_Name.

Refinement panel does not show the managed property

The Refinable flag must be set to Yes. Additionally, the refinement panel in the search results page must include the managed property. Edit the search results web part, go to the Refinement section, and add the managed property to the refiners list. If the property is not listed, ensure it is set as Refinable and that a full crawl has completed.

Search results include duplicate entries for the same property

This can happen when multiple crawled properties map to the same managed property and contain similar data. For example, both ows_ProjectName and ows_Project_x0020_Name may map to the same managed property. Remove the duplicate mapping and keep only the correct crawled property. Then run a full crawl to refresh the index.

Managed Property Settings: Comparison of Key Flags

Flag	Enabled (Yes)	Disabled (No)
Searchable	Content is included in full-text search index	Content is not searchable by keywords alone
Queryable	Users can query with PropertyName:value	Property cannot be used in query syntax
Retrievable	Property value appears in search results	Value is hidden from search result display
Refinable	Property appears in refinement panel	Property is not available for filtering

For most custom metadata columns, enable all four flags. Only disable Searchable for properties that contain long text or that do not need to be found by keyword search, such as date fields. Disable Queryable if you do not want users to query the property directly. Disable Retrievable if the value is sensitive and should not appear in result snippets.

Conclusion

You now have a practical checklist to create and configure managed properties that improve search in SharePoint. By mapping crawled properties to managed properties and setting the correct flags, you make custom metadata searchable, queryable, retrievable, and refinable. Start by identifying the top three to five columns that your users search most often and apply this checklist to each one. As a next step, consider creating managed properties for date fields to enable date range refiners, which can dramatically improve how users find time-sensitive documents. Remember to run a full crawl after any mapping change to ensure the search index reflects your updates.