When you create a managed property in SharePoint search but that property does not show up in search results, the cause is almost always a mismatch between the crawled property and the managed property settings. SharePoint search relies on a two-step pipeline: crawling extracts raw values into crawled properties, and the search schema maps those to managed properties. If the mapping is missing, the property is not searchable or displayable. This article explains the exact pipeline failure and provides step-by-step instructions to fix the mapping so your managed property appears in search results.
Key Takeaways: Fixing a Managed Property That Does Not Appear in Search
- Search schema > Crawled property mapping: Every managed property must be mapped to at least one crawled property. Without this mapping, the property has no data to index.
- Full crawl after schema changes: Incremental crawls do not pick up new or updated managed properties. A full crawl is required to populate the search index with the new mapping.
- Managed property settings for query and retrieve: Enable the Searchable and Retrievable checkboxes in the managed property settings to allow the property to appear in results and be displayed in the search result web part.
Why a Managed Property Does Not Show in Search Results
SharePoint search works in three stages: crawling, indexing, and querying. During crawling, the search crawler reads content and stores raw values in crawled properties. Crawled properties have names like ows_ProjectName or c_ProjectName. These crawled properties are then mapped to managed properties through the search schema. Managed properties are what users search against and what the search results web part displays.
If a managed property does not appear in search results, one of these conditions is true:
- The managed property has no crawled property mapped to it.
- The crawled property contains no data because the site column or content type is not populated.
- The managed property has the Searchable or Retrievable checkbox turned off.
- Only an incremental crawl was run after the schema change. A full crawl is required.
- The search schema was changed on a tenant level but the site collection uses a custom search configuration that overrides the tenant settings.
The most common root cause is a missing crawled property mapping. When you create a managed property from scratch, SharePoint does not automatically assign a crawled property to it. You must manually select the correct crawled property that holds the data you want to expose in search.
Steps to Map the Crawled Property and Enable the Managed Property for Search
Follow these steps in order. Do not skip the full crawl step.
- Open the Search Schema in the SharePoint admin center
Go to SharePoint admin center > Search > Search Schema. This page lists all managed properties and crawled properties for the tenant. If you are working on a specific site collection, use Site Settings > Search Schema instead. - Locate the managed property that is not appearing
In the Managed Properties section, type the name of your property in the filter box. Click the property name to open its settings page. If the property does not exist, create a new managed property by clicking New Managed Property. - Check the current crawled property mapping
Scroll to the Mapping to crawled properties section. If the list is empty, no crawled property is mapped. Click Add a Mapping to open the crawled property picker. - Select the correct crawled property
In the crawled property picker, search for the crawled property that corresponds to your site column. For example, if your site column is namedProjectName, the crawled property is usuallyows_ProjectNameorc_ProjectName. Select the crawled property and click OK. If you do not see the crawled property, run a full crawl first (see step 7) and then return to this step. - Enable Searchable and Retrievable
In the managed property settings, scroll to the Searchable checkbox and turn it on. Also turn on Retrievable if you want the property value to appear in search results. Optionally turn on Queryable if you want users to search specifically for this property using a query likeProjectName:Contoso. Click OK or Save to apply the changes. - Verify the mapping in the crawled property
Switch to the Crawled Properties tab in the Search Schema page. Find the crawled property you mapped. Click it and verify that your managed property appears in the Mapped to Managed Properties section. If it does not, the mapping was not saved. Repeat steps 3 through 5. - Request a full crawl
Go to SharePoint admin center > Search > Search Administration. Under Crawl Schedule, click Start Full Crawl for the content source that contains your site. A full crawl can take minutes to hours depending on the size of your content. Wait for the crawl status to show Idle before testing. - Test the managed property in search results
Perform a search on the site that contains the content with the property. If you enabled Queryable, you can search using the syntaxManagedPropertyName:value. For example,ProjectName:Contoso. If you only enabled Retrievable, search for a term that exists in the content and check the result display properties.
If the Managed Property Still Does Not Appear After the Main Fix
Search result web part does not show the property value
Even if the managed property is Retrievable, the default search result web part may not display it. You must configure the display template or the modern search result web part to show the property. In modern SharePoint, edit the search result web part, go to Properties > Search result properties, and add the managed property name to the list of displayed properties. In classic search, modify the XSLT in the display template.
Site column exists but crawled property is missing
If you added a site column after the last full crawl, the crawled property may not exist yet. Run a full crawl first, then check the crawled property list again. If the crawled property still does not appear, verify that the site column has data in at least one item. An empty column does not generate a crawled property.
Tenant search schema vs site collection search schema
SharePoint allows site collection administrators to create a custom search schema that overrides the tenant-level schema. If the managed property is defined at the tenant level but the site collection has a custom schema, the property will not appear. Go to the site collection’s Search Schema page and check if a custom schema is active. If it is, either delete the custom schema or recreate the managed property at the site collection level.
Managed property is overridden by a result source
Result sources can limit which managed properties are returned in search results. If you have a custom result source that restricts properties, the managed property will not appear. Check the result source query transform in Search Administration > Result Sources. Remove any property restrictions in the query transform.
Managed Property Settings: Searchable vs Retrievable vs Queryable
| Setting | Effect on Search Results | When to Enable |
|---|---|---|
| Searchable | The property content is indexed and matches search queries | Always enable if you want users to find content by searching this property |
| Retrievable | The property value can be displayed in search result web parts | Enable if you want to show the property value in the result list |
| Queryable | Users can query the property directly using PropertyName:value syntax |
Enable only if you need precise property-based queries |
A managed property must have Searchable enabled to appear in results at all. Retrievable controls display only. Queryable is optional and usually not needed for simple keyword searches.
Conclusion
A managed property that does not appear in search results is almost always fixed by mapping it to the correct crawled property and running a full crawl. Verify that the crawled property exists and contains data. Enable the Searchable and Retrievable checkboxes in the managed property settings. After the full crawl completes, test the property with a search query. If the property still does not appear, check for a site collection custom schema or a result source that overrides the tenant settings. Use the search result web part configuration to display the property value in the search results.