---
title: "AI Concierge: Page Scope"
description: "> Keep the AI Concierge chat searching the same destination a guest is already browsing, instead of asking it to search your whole site. --- ## What it does If you run a multi-destination site, a guest chatting from your…"
url: "https://homerunner.io/docs/ai-concierge-page-scope/"
updated: "2026-10-13"
category: "Operator Tools & Tuning"
---

# AI Concierge: Page Scope

> Keep the AI Concierge chat searching the same destination a guest is already browsing, instead of asking it to search your whole site.

---

## What it does

If you run a multi-destination site, a guest chatting from your Big Island page probably wants Big Island results, not a search across every property you manage. Left on its own, the AI Concierge searches sitewide and sends "View all results" to your default results page, even when the guest opened the chat from a page that was already narrowed to one place.

Page scope fixes that by handing the chat the same context the page's own search component is using.

- On a page with a HomeRunner Explorer search component, the chat can automatically pick up that component's filter (location, state, city, property group, type, or amenity) and search within it.
- The chat can also send guests to that page's own results destination instead of your site's default results page.
- If a guest explicitly asks for somewhere else ("what about Maui?"), their request always wins over the page's scope.
- Once the chat narrows a search to the page's scope, it also offers the guest a one-tap way out: a "Beyond [Area]" (or "Search all areas" on a non-destination page) option they can click to widen the search themselves, no need to ask twice.
- For pages where automatic detection cannot tell which search component to follow, you can pin the scope explicitly with a shortcode.

**Automatic detection works when:**

- The page has exactly one HomeRunner Explorer search component, or
- The page has several components, but only one of them shows its filter bar (the interactive search box guests can type into, as opposed to a fixed, curated grid of picks). That one component is treated as the page's real search context.

When a page has more than one component with a filter bar, or none at all, automatic detection stays off for that page and the explicit shortcode is the way to scope it.

## How to turn it on

### 1. Open the AI Concierge settings

In your WordPress admin, go to **HomeRunner > AI Concierge** and scroll to the **Chatbot** section.

### 2. Turn on the scope toggles you want

- Switch on **Respect on-page Explorer filter** to have the chat search within the page's own Explorer filter automatically.
- Switch on **Respect on-page Explorer form action** to send the chat's "View all results" link to that page's own results destination when the page's own Explorer component sets one. A page with no search component at all needs the shortcode below instead; this toggle has nothing to read on that kind of page.

Both are off by default, since they change chat behavior across every Explorer page on your site at once.

### 3. Use the shortcode for pages automatic detection can't handle

For a page with more than one search component, a component built by a page builder outside the normal content area, or a landing page with no search component at all, place the shortcode directly on the page:

```
[hr_concierge_scope location="bigisland" form_action="/big-island-rentals/"]
```

Accepted attributes: `location`, `state`, `city`, `group`, `type`, `amenity` (comma-separated slugs), and `form_action`. The shortcode always takes priority over automatic detection.

## Settings

| Setting | What it controls |
| --- | --- |
| Respect on-page Explorer filter | Scopes chat searches to the page's Explorer filter when detection succeeds. A guest who explicitly asks for a different place still overrides it. Off by default. |
| Respect on-page Explorer form action | Sends the chat's "View all results" link to the page's own results destination when an on-page Explorer component sets one, instead of your site's default. Only applies to pages with a detected Explorer component; a page with no search component needs the `[hr_concierge_scope]` shortcode's own `form_action` attribute instead. Takes priority over the Form Action (testing) field elsewhere in settings. Off by default. |
| Concierge scope shortcode | Kill switch for the [hr_concierge_scope] shortcode described above. On by default, since placing the shortcode on a page is itself the opt-in. |

## Tips

- Page scope reads from your [HomeRunner Explorer](/docs/explorer-shortcode/) search components, so it is most useful on destination or neighborhood landing pages that already carry their own Explorer filter.
- If a multi-component page still is not scoping the way you expect, check whether more than one component on that page shows its filter bar. Only a page with exactly one visible filter bar auto-detects; otherwise, add the shortcode.
- The "Beyond [Area]" option only shows up once a search has actually been narrowed by the page's scope, and it is not a separate setting: it comes free with either scoping method above.
- See [AI Concierge: Property Chat](/docs/ai-concierge-property-chat/) for how the chat itself searches and responds once it has a scope to work with.