Skip to main content
View Categories

No properties match on destination landing pages

When guests search from a landing page built for one destination, they may see No properties match.

Why this happens. The landing page is filtered to one specific destination, but the search bar still lets guests select other destinations. When a guest chooses a different market from the dropdown, the page stays locked to the original destination. The two filters conflict, so the search returns no results and produces confusing URLs.

What you can do. Remove the destinations field from the search bar on that page by using the primary_filter_fields attribute in your explorer shortcode.