People Search Misses a SharePoint Site Owner: Causes and Workarounds
🔍 WiseChecker

People Search Misses a SharePoint Site Owner: Causes and Workarounds

When you search for a SharePoint site owner using People Search in SharePoint, the owner sometimes does not appear in the results. This happens even when the owner is correctly assigned in the site permissions. The root cause is usually related to how SharePoint indexes user profiles and how the search service crawls site membership data. This article explains why People Search fails to return a site owner and provides practical workarounds to fix the missing owner in search results.

Key Takeaways: Fixing SharePoint People Search When a Site Owner Is Missing

  • SharePoint admin center > Search > Manage Search Schema: Check that the crawled property for site owners is mapped to a managed property used by People Search.
  • SharePoint admin center > Search > Crawl Log: Verify that the site content source completed a full crawl recently and did not skip the owner profile.
  • User Profile Service Application > Manage User Properties: Ensure the site owner has a populated SPS-SiteOwners property in their user profile.

ADVERTISEMENT

Why People Search Does Not Show the Site Owner

People Search in SharePoint relies on the search index to return user profiles. When a site owner is missing from search results, the issue is typically caused by one of three factors: incomplete user profile data, incorrect search schema mappings, or a stalled incremental crawl. SharePoint does not automatically add site owners to the search index unless the SPS-SiteOwners property is populated in the user profile and the search schema maps that property to a managed property that People Search queries.

User Profile Property Not Populated

The SharePoint site owner is stored in the user profile under the property SPS-SiteOwners. If this property is empty or not synchronized from the source directory, People Search cannot find the owner. This often occurs when the user was added as a site owner through a SharePoint group rather than directly through the site permissions page, or when the user profile synchronization from Active Directory has not updated the property.

Search Schema Mapping Missing or Incorrect

SharePoint search uses crawled properties to read content from site collections. These crawled properties must be mapped to managed properties that People Search uses. If the crawled property ows_AssociatedMemberGroup or ows_AssociatedOwnerGroup is not mapped to a managed property such as SPSiteOwners, the search index will not contain the site owner information. Without this mapping, People Search cannot return the owner in results.

Search Index Out of Date

SharePoint search crawls sites on a schedule. If a site owner was added or changed after the last full crawl, the search index will not reflect the change until the next crawl completes. Incremental crawls may not pick up permission changes if the site content has not been modified. A full crawl is required to re-index all site membership data.

Steps to Verify and Fix the Missing Site Owner in People Search

Follow these steps in order to diagnose and resolve the issue. Perform each step in the SharePoint admin center or Central Administration.

  1. Check the User Profile Property SPS-SiteOwners
    Go to SharePoint admin center > User profiles > Manage user properties. Search for the site owner by name. Open the user profile and scroll to the SPS-SiteOwners property. If the property is blank, the site owner is not being indexed. Add the site owner to the site again using the site permissions page to trigger a profile update.
  2. Verify the Search Schema Mapping
    In SharePoint admin center, go to Search > Manage Search Schema. Look for the managed property named SPSiteOwners. Click it and check the mapping to crawled properties. Ensure the crawled property ows_AssociatedOwnerGroup is mapped to SPSiteOwners. If the mapping is missing, add it and save the schema.
  3. Request a Full Crawl of the Site Content
    Go to SharePoint admin center > Search > Crawl Log. Select the content source that includes your site collection. Click Start Full Crawl. Wait for the crawl to complete. This may take several hours depending on the size of your farm. After the crawl finishes, test People Search again.
  4. Force Re-index the Site Collection
    If the crawl does not fix the issue, force a re-index of the site collection. Go to Site Settings > Search and offline availability. Under Re-index Site, click Reindex Site. This marks the site for a full crawl on the next scheduled crawl cycle.
  5. Check the People Search Result Source
    In SharePoint admin center, go to Search > Result Sources. Verify that the default People Search result source includes the managed property SPSiteOwners in its query transform. The query should contain {?owstaxIdSiteOwners} or a similar reference to site owner data.

ADVERTISEMENT

If People Search Still Misses the Site Owner

Even after performing the steps above, the site owner may remain missing from People Search. The following scenarios explain additional causes and their workarounds.

Site Owner Was Added via a Security Group

If the site owner is a member of a Microsoft 365 group or a SharePoint security group, the SPS-SiteOwners property may not be populated for that individual. The search index records the group, not the individual members. Workaround: Add the user directly as a site owner through the site permissions page instead of relying on group membership.

User Profile Synchronization Is Paused or Broken

If your environment uses Active Directory synchronization, check that the User Profile Service Application is running and that the synchronization connection is active. A paused sync will stop profile updates from flowing to SharePoint. Workaround: Restart the synchronization timer job in Central Administration > Monitoring > Timer Jobs.

Search Service Application Is Running Low on Resources

When the search service application is under memory or CPU pressure, it may skip indexing of site membership data. This is more common in SharePoint Server on-premises. Workaround: Monitor the search health reports in Central Administration. Increase the number of crawl components or allocate more memory to the search service if needed.

Item SharePoint Online SharePoint Server 2019
User profile property for site owners SPS-SiteOwners is auto-populated from Microsoft 365 groups SPS-SiteOwners must be synchronized from Active Directory
Full crawl trigger Use Reindex Site in site settings Use Start Full Crawl in Search Administration
Search schema management Managed via SharePoint admin center Managed via Central Administration Search Service Application
Common failure mode Group membership not indexed for individual users Profile sync delay or search schema mapping missing

After completing the verification and crawl steps, the site owner should appear in People Search. If the problem persists, review the search schema mappings and the user profile property population as described above. For environments with frequent site owner changes, schedule a weekly full crawl to keep the search index current.

ADVERTISEMENT