---
title: "Toolkit: Destination Search"
description: "> A single search bar that guests can drop into a hero or landing page, so they can jump straight to a home, island, city, or resort without opening your full destination filter. ## What it does A tabbed destination…"
url: "https://homerunner.io/docs/toolkit-destination-search/"
updated: "2026-10-25"
category: "Search & Discovery"
---

# Toolkit: Destination Search

> A single search bar that guests can drop into a hero or landing page, so they can jump straight to a home, island, city, or resort without opening your full destination filter.

## What it does

A tabbed destination popup is great for your main search bar, but it needs the full Explorer search to live in. Landing pages, heroes, and other one-off spots need something lighter: a single field guests can type into and go. Destination Search is that field. Guests start typing and get grouped matches back across your homes, islands, cities, and resorts. Picking a home takes them straight to that property page. Picking a destination takes them to your results page with that destination applied.

- One search field, placeable anywhere with a shortcode
- Results are grouped under headings ("Homes," "Islands," "Cities," "Resorts"), in the order you set, so a guest can see at a glance what kind of match they got
- Picking a home goes straight to its property page
- Picking a destination goes to your results page with that destination already applied
- Loads its destination data only when a guest actually reaches for the field, so pages carrying the shortcode pay no extra cost until then

If you already run [Destination Filter](/docs/toolkit-destination-filter/), Destination Search reuses the exact same destination data and settings, so the two never drift apart. You do not need Destination Filter to use Destination Search; it works standalone.

## How to turn it on

![The Destination Search module's settings in the HomeRunner Toolkit Hub](https://homerunner.io/wp-content/uploads/2026/10/toolkit-destination-search-hub-1.png)

### 1. Switch on Destination Search in the Toolkit Hub

In your WordPress admin, go to the HomeRunner Toolkit hub and switch on Destination Search.

### 2. Drop the shortcode where you want the search field

Place `[homerunner_destination_search]` on any page or in any YOOtheme element, such as a homepage hero or a destination landing page. No results URL is required to start, but see the setting below to enable destination picks.

### 3. Set your search results page

For a destination pick (an island, city, or resort) to go anywhere, Destination Search needs to know your results page. If [Destination Filter](/docs/toolkit-destination-filter/) is also enabled, this is shared with that module's settings. Otherwise, set it in Destination Search's own panel in the Hub (see Settings below). Without a results page set, the search still works for finding homes by name; destination picks just have nowhere to send the guest.

### 4. Order the search groups

Search across also controls the order groups appear in, and which one guests see ranked first, Homes, Islands & sides, Cities, and Resorts. If Destination Filter is on, set this from Destination Filter's own settings panel, since the two modules share it there. If Destination Filter is off, use the up and down buttons next to each group in Destination Search's own panel (see Settings below). Existing sites keep their current order until you change it.

Resort tags that carry no prefix can join the Resorts group as well: list them one per line under "Resort tags without a prefix" on the module settings page (Toolkit 3.328.0 and later), and they match in the type-ahead exactly as written in your PMS.

## Settings

If Destination Filter is enabled, Destination Search's settings (placeholder, groups, results count, minimum characters, and results page) are managed from Destination Filter's panel instead, since the two modules share one search configuration. A note in the Destination Search panel links you straight there.

If Destination Filter is off, Destination Search has its own panel:

| Setting | What it controls |
| --- | --- |
| Placeholder | The text shown in the empty search field. Defaults to "Search homes, islands, cities…" |
| Search across | Which groups the search matches against, and in what order: Homes (property names), Islands & sides, Cities, and Resorts. Use the up and down buttons next to each group to reorder them; each checked group gets its own heading in the results, in that order, so the group at the top is also the one guests see ranked first. Existing sites keep their current order until you change it. |
| Results per group | How many matches show per group before the rest collapse behind a "+N more" link. |
| Minimum characters | How many characters a guest has to type before results appear. |
| Search results page | Where a destination pick redirects to, with that destination applied. Home picks always go straight to the property page regardless of this setting. |

Every one of these can also be overridden for a single placement using shortcode attributes (`placeholder`, `groups`, `results_url`, `max_per_group`, `min_chars`, `show_counts`, `autofocus`, `class`, and the browse and sheet attributes below), without changing the site-wide defaults. See [Destination Filter](/docs/toolkit-destination-filter/) for the full attribute table.

## Browse by resort and the phone sheet

Since Toolkit 3.340 the search field can open with a list of your resorts before a guest types anything. Each resort shows its icon, its name, a count of homes and the homes themselves, plus a "See all" link that opens your results page filtered to that resort. Homes outside any resort sit in a final group of their own. Typing swaps the list for the usual grouped results, and clearing the field brings the list back. Grouping follows your resort tags, so a home appears under a resort only when it carries that resort's tag.

Both features are off until you turn them on in the shortcode, so existing placements and the Destination Filter popup keep working as before.

![The Destination Search field in a site header with the Browse by resort panel open, listing resorts with home counts and See all links](https://homerunner.io/wp-content/uploads/2026/10/toolkit-destination-search-browse-desktop.png)
Desktop: the field is focused and empty, so the Browse by resort panel lists each resort with its homes, a count and a See all link.

![The Destination Search phone sheet: a title bar with a close button, the search field, and the Browse by resort list with one collapsed row per resort](https://homerunner.io/wp-content/uploads/2026/10/toolkit-destination-search-phone-sheet.png)
Phone with sheet="phone": tapping the field opens a full-screen sheet; resorts start collapsed and expand on tap.

| Attribute | What it does |
| --- | --- |
| `browse` | Set to `resorts` to show the browse list while the field is focused and empty. Leave it out to keep the plain search field. |
| `browse_label` | The heading above the list. Defaults to "Browse by resort". |
| `other_label` | The heading for the group of homes outside any resort. Defaults to "Other homes". |
| `browse_open` | Whether each resort starts expanded: `desktop` (the default) expands them on screens 640 px and wider and collapses them on phones, `all` expands them everywhere, `none` collapses them everywhere so guests tap a resort to see its homes. |
| `sheet` | Set to `phone` to open the search as a full-screen sheet on phones (screens narrower than 640 px), with a title bar and a close button. Off by default. |
| `sheet_title` | The title in the sheet's bar. Defaults to "Find a resort or home". |

For example, a header search that browses by resort and opens as a sheet on phones: `[homerunner_destination_search groups="resorts,homes" browse="resorts" sheet="phone" results_url="https://example.com/vacation-rentals/"]`.

To show your own resort icon in the results and on the browse headers, open Toolkit Hub, then Destination Search, and paste one SVG into the Resort icon field. Shapes only, no scripts or links, under 20 KB; an icon that fails those checks saves as blank and the built-in icon stays. Use `fill="currentColor"` or `stroke="currentColor"` so it follows your text color. The list and the sheet use the same colour variables as the rest of the search box, listed in the [Styling Reference](/docs/toolkit-styling-reference/).

## Tips

- Use `results_url` on the shortcode to send one placement to a different results page than your site-wide default, useful for a destination-specific landing page.
- For the full tabbed "Find Your Destination" popup inside your main Explorer search bar, use [Destination Filter](/docs/toolkit-destination-filter/) instead. The two share the same underlying destination data, so tagging your properties once covers both.
- If picking a destination does nothing, check that a search results page is set, either in Destination Filter's panel (if enabled) or in Destination Search's own panel.
- If you want one kind of match to show first, for example listing Resorts ahead of individual Homes, move it to the top of Search across rather than leaving guests to scroll past the other headings.
- This field always waits for a guest to pick a suggestion before doing anything. Destination Filter's popup additionally lets its Apply button act on text a guest types but never picks; if you want that fallback, use Destination Filter's search bar instead of, or alongside, this shortcode.
