- 2 minutes to read

ContentSearchMaxMatchesPerDocument - System Parameter

New 7.12

ContentSearchMaxMatchesPerDocument is an integer System Parameter that limits how many matches one document lists in the result of a Content Search: the Search content dialog for Articles, Snippets, Templates, and Document Profiles. The Web API reads it for every search.

At a Glance

Property Value
Key ContentSearchMaxMatchesPerDocument
Data type integer (matches per document)
Default 10
Read by Web API
Takes effect At the next search when saved on the System Parameters page; within about 15 seconds in other processes, such as the MCP Endpoint; no restart needed
Status ✅ Active
Since Nodinite 7.12

How It Works

  • Each result card lists up to ContentSearchMaxMatchesPerDocument matches, with the section and line of each; the first two are shown, and Show n more matches expands the rest.
  • Matches beyond the limit are not listed, but the match count on the card still shows the true number.
  • The MCP tool search_content lists at most 5 matches per document, whatever this value.

See Content Search - Limits for all three limits together.

System Parameters page filtered on ContentSearch, showing ContentSearchMaxMatchesPerDocument 10, ContentSearchMaxResults 100, and ContentSearchMaxScannedDocuments 2000 with their descriptions (7.12)
Filter on ContentSearch to see the three Content Search limits together; this page covers ContentSearchMaxMatchesPerDocument.

Choosing a Value

Keep the default. A document with more matches than the limit is usually best read in the reader, where the find bar steps through every match. Raise the value only when you need every match in the result list.

Next Steps