Share via

Search index fragmentation after manual site reindexing

Benladi Rosangela 20 Reputation points
2026-04-10T00:00:12.2466667+00:00

I encounter the error "Search query returned no results" for newly uploaded documents even after triggering a manual "Reindex Site" in our SharePoint Server Subscription Edition environment.  Despite the Crawler service account having full read permissions, the indexer seems to skip certain subwebs entirely during the incremental crawl, leading to a massive discrepancy between the SQL content database and the Search Index

Microsoft 365 and Office | SharePoint Server | For business
0 comments

Answer accepted by question author

Teddie-D 16,370 Reputation points Microsoft External Staff Moderator
2026-04-10T01:44:37.8333333+00:00

Hi @Benladi Rosangela 

When subsites don’t appear in search results, the issue often comes down to permissions, crawl rules, site settings, or crawl health.  

Based on your description and the steps you’ve already taken, it appears the issue is unlikely to be related to permissions or indexing eligibility but may instead stem from crawl discovery or scope. 

Here are some additional checks you may try:  

1.Verify crawl status  

Go to Central Administration > Manage Service Applications > Search Service Application > Crawl Log  

-Filter by Skipped or Errors during the most recent incremental crawl.   

-Identify whether the affected subsite URLs appear in the crawl log at all.   

-If they appear, review the associated error codes for clues (e.g., Access Denied, URL not found, Timeout).   

If a subsite never appears in the crawl log, it may not have been discovered by the crawler, which requires further investigation at the content source level.  

2.Check permissions  

-Default Content Access Account (Search Crawl Account) has at least Full Read permissions at the Web Application level (already confirmed in your case). 

-Any subsites with unique permissions explicitly grant access to the crawl account.   

-No Deny permissions exist at the site, list, or library level, as these override inherited access and prevent indexing.   

3.Review crawl rules  

Check whether any crawl rules are unintentionally excluding relevant URLs or managed paths:   

-Go to Search Service Application > Crawl Rules   

-Confirm that no rules are excluding paths that contain the affected subsites.   

Previously configured exclusion rules may cause subsites to be skipped silently during incremental crawls.   

4.Validate site & Library search settings  

-At the site level: Site Settings > Search and Offline Availability > Confirm Allow this site to appear in search results is set to Yes.  

-At the library level: Library Settings > Advanced Settings > Search > Allow items to appear in search results.  

5.Force a full crawl  

-Incremental crawls may skip subsites if the change log is out of sync with the content database.  

-Run a Full Crawl from Search Service Application > Content Sources to resynchronize.  
(Remember to schedule full crawls during off-peak hours since they can be resource-intensive). 

6.Monitor crawl health  

-Check ULS Logs for search-related errors.  

-Verify that Continuous Crawl or Incremental Crawl timer jobs are running properly.  

-If issues persist, restarting the crawl component may help.  

I hope this helps. 

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".   

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.  

Was this answer helpful?

0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-04-10T00:00:24.66+00:00

    The symptoms indicate that content is either not being indexed yet or is being excluded from search, even after a manual reindex. In SharePoint environments this typically comes down to one of three areas: permissions/privileges on the content source, crawl/indexing latency or issues, or configuration that excludes specific subsites/content from being searchable.

    For on‑premises file shares, a common cause of “no results” despite read permissions is that the crawl account cannot read security descriptors. In that case, the crawl log shows an error similar to:

    The crawl account did not have sufficient privileges to access the security attributes of this file or folder. Ensure the crawl account has the 'Manage auditing and security log' privilege.

    If such an error appears for any of the affected paths, the fix is to grant the Manage auditing and security log (SeSecurityPrivilege) user right to the SharePoint content access (crawl) account on the server that hosts the content:

    1. On the content server, run gpedit.msc.
    2. Go to Computer Configuration → Windows Settings → Security Settings → Local Policies → User Rights Assignment.
    3. Open Manage auditing and security log.
    4. Add the crawl/content access account.
    5. Apply the change (or add via GPO if using domain Group Policy).

    After adjusting this right, run a full crawl on the affected content source and then test search again.

    If the problem is not a permissions failure but missing results in general, also consider:

    • Newly uploaded content may not yet be crawled; there is always some latency between upload and searchability.
    • Content or subsites can be configured to be excluded from search, which will cause “no results” even if permissions and crawling are otherwise healthy.
    • In SharePoint Online scenarios, missing results can also be caused by site or subsite search visibility settings and may require reindexing and configuration changes. For on‑premises, similar principles apply: ensure the site and subwebs are configured to allow their content to be indexed.

    If, after verifying permissions, reindexing, and crawl completion, results are still missing or subwebs are skipped, the next step is to review crawl logs and search configuration in detail and, if necessary, open a support case, as large discrepancies between the content database and the index can indicate deeper crawl/index issues.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.