---
title: "Conversion Kit: Property Finder"
description: "> A fast, searchable dropdown of your rentals that you drop anywhere with a shortcode, so a guest can type a property name and jump straight to its page. --- ## What it does Property Finder renders a searchable dropdown…"
url: "https://homerunner.io/docs/ckit-property-finder/"
updated: "2026-10-13"
category: "Booking & Lead Capture"
---

# Conversion Kit: Property Finder

> A fast, searchable dropdown of your rentals that you drop anywhere with a shortcode, so a guest can type a property name and jump straight to its page.

---

## What it does

Property Finder renders a searchable dropdown of your properties. A guest starts typing a rental name, the list filters live, and selecting a result takes them straight to that property's page. It is a lightweight "go directly to the place I already have in mind" tool, ideal for headers, landing pages, and "find your rental" sections.

Unlike a full search experience, this is deliberately simple and quick. It is for guests who know (or half-know) which property they want and just need a fast path to it.

Key points:

- Placed anywhere with the `[hrck_property_finder]` shortcode.
- Filters the list as the guest types and navigates to the chosen property.
- Supports multiple instances on the same page, each working independently.
- Caches the property list for speed and refreshes automatically when you add or edit properties.

This tool does not capture email and does not require guest accounts. It is a navigation aid, not a CTA.

## How to turn it on

### 1. Open the Conversion Kit tools

Go to **HomeRunner > Conversion Kit** and find **Property Finder** in the tool list.

### 2. Enable the tool

Toggle **Property Finder** on.

### 3. Place the shortcode

Add `[hrck_property_finder]` to any page, post, or component area where you want the search dropdown to appear.

## Shortcode options

You can scope which properties appear and customize the placeholder per instance:

- `placeholder="Find your villa…"` overrides the default prompt text for that one dropdown.
- `city`, `state`, `tag`, `type`, `amenity`, `group`, and `location` each filter by their own property taxonomy (for example `city="Austin"`). Give one of these a comma-separated list, for example `state="texas,north-carolina"`, to match any of several values. Combine different attributes to narrow further, for example `tag="pet-friendly" amenity="pool"` matches properties with both.
- `ids="12,34,56"` shows only those specific properties, in the order you list them, and ignores `limit`. Any other attributes you add still narrow the list.
- `exclude="78,90"` hides specific properties.
- `limit="25"` caps how many properties the dropdown will include.

Example: `[hrck_property_finder city="Austin" placeholder="Search Austin rentals…"]`

## Settings

| Setting | What it controls |
| --- | --- |
| **Default Placeholder** | The prompt text shown in the search box. Default: "Search by Rental Name…". Override per shortcode with the `placeholder` attribute. |
| **No-Match Message** | Shown inside the dropdown when nothing matches the search. Default: "We couldn't find a rental by that name. Try a different search." |
| **Colors** | Background, focused background, border, text, placeholder, icon, and dropdown hover (background and text) colors so the dropdown matches your brand. Defaults: background `#EAF6FB`, focused background `#ffffff`, border `#6eb6de`, text `#152c54`, placeholder `#5d7286`, icon `#152c54`, hover background `#EAF6FB`, hover text `#152c54`. |
| **Border Radius** | Corner rounding of the search box, in pixels. Default: 6. |
| **Max Width** | Width cap of the search box, in pixels. Default: 400. Set to 0 for no maximum, so the box fills its container. |
| **Max Dropdown Height** | How tall the results list can grow before it scrolls, in pixels. Default: 300. |
| **Cache TTL** | How long the property list is cached, in minutes. Default: 60. Set to 0 to turn caching off. Refreshes automatically when you add or edit properties. |

## Tips

- Put a Property Finder in your site header so returning guests can jump to a known rental from any page.
- Use the taxonomy attributes to build location-specific finders, for example one finder per destination page scoped with `city`.
- You can place several finders on one page (a different `city` on each) without them interfering with each other.
- For a deeper, attribute-based discovery experience rather than name search, pair this with [Vibe Profile](/docs/ckit-vibe-profile/).