Understanding `landingPage` Behavior in AjaxSearch for Evolution CMS

AjaxSearch can be confusing when the same search parameters produce different behavior depending on whether a landing page is set. That is because landingPage changes the context in which the search form resolves and where the request ultimately lands.

If one setup points the search to a dedicated results page and another leaves the request in the current section, the difference is not cosmetic. It affects which parents, depth rules, and output templates actually participate in the request.

The practical lesson is to treat landingPage as part of the query architecture, not as a visual convenience. Once you do that, the inconsistent behavior becomes easier to debug.