Home/Field Guide/Sites, CMS & commerce
CONCEPT 21
Search, indexing, and relevance
Diagnose visibility, query behavior, and tuning before making search changes.
Treat search as a derived view
Liferay indexes supported assets into a compatible search engine. Writes to the database and visibility in a search result can be separated by processing time and indexing behavior. Search also applies scope, filters, and permission checks. A missing result is a symptom with several possible causes.
Trace a missing result
- Confirm the asset exists, is active or published as expected, and can be read by the test user through its normal detail path.
- Verify that the asset type and relevant fields are indexed. Inspect index health and use the supported administrative tools to inspect the document when available.
- Reproduce the query with the same scope, locale, filters, and identity. Compare guest and signed-in behavior.
- Check analysis, synonyms, boosts, and exact-match behavior. Reindex when the documented change requires it and plan the load impact.
Tune with a relevance set
Collect representative queries, expected useful results, and protected records that must stay hidden. Use built-in search widgets and available tuning first. Search Blueprints can compose and tune queries on eligible deployments. Treat Blueprint changes as versioned configuration and test performance and permission behavior before promotion.