Help

Overview
Overview What to Expect Pre-Session Checklist Your Onboarding Session
Platform Mental Model Admin & Operator Essentials Guardrails and Governance What to Use When Roles and Responsibilities Post-Session Next Steps Optional Deep-Dives Deep-Dive: Agents and Prompts Deep-Dive: Search and Knowledge Deep-Dive: Functions and Secure Services Deep-Dive: Handoff and Escalation Deep-Dive: Voice Mode Deep-Dive: Analytics and Improvement Facilitator Guide
Overview Account Overview User Management Usage
Overview General User Interface Agent Messages Voice Mode
Admin Chat UI Design Curated Answers Search Settings Conversational Intelligence Data Sync Upload Documents
Overview General Crawl Scope Image Extraction Field Mappings
Overview Creating an Agent Editing An Agent
Overview Editing a Prompt User Segmented Prompts
Overview Writing Your First Function AirScript Functions AirScript Reference
Overview Privacy Security
Analytics API Documents Ingestion API
Human Handoff
Overview Customer Service Insights Categories And Themes Search Insights
Overview Identity Provider Widget SharePoint Integration How It Works SharePoint Checklist Implementation Checklist
Admin Console Authorisation
Methods Script Tag AI Question Input Fields
Overview Optimiser Monitor
Contact Support
No results found

Site Search Funnelback Migration

Airgentic Help

Airgentic can support common Funnelback-style URLs during migration projects when Funnelback compatibility is enabled for the service.

This feature is a compatibility layer. Funnelback URLs are not the default Airgentic URL format, and not every Funnelback parameter is expected to have a one-to-one Airgentic equivalent.

Supported Parameters

Airgentic can parse common Funnelback parameters such as:

Funnelback parameter Purpose
query Search query text
collection Search collection or service hint
start_rank First result number
num_ranks Number of results per page
sort Sort option
f.Display|field=value Filter using Funnelback facet syntax
meta_<field>=value Metadata filter
meta_url URL or host constraint
clive Scope or sub-collection
  1. Parse inbound links only

Start by allowing Airgentic to read existing Funnelback-style deep links.

  1. Validate captured URLs

Test real URLs from analytics, bookmarks, and search result pages.

  1. Decide whether to emit Funnelback-style URLs

Some customers may want Airgentic to continue writing Funnelback-style URLs. Others may prefer Airgentic-native URLs or no URL state.

Example URLs

Basic search:

search.html?query=engineering

Pagination:

search.html?query=engineering&start_rank=11&num_ranks=10

Filter using Funnelback facet syntax:

search.html?query=engineering&f.Format|format=Online

For filter URLs to work, the referenced Airgentic field must exist as a Search Field in Search Configuration > Fields and be enabled as a filter.

Host or URL constraint:

search.html?query=engineering&meta_url=engineering.example.edu

Scope:

search.html?query=engineering&clive=programs

During migration, map the Funnelback field names you want to preserve to Airgentic Search Fields. For example, a Funnelback delivery filter should map to an Airgentic delivery field that is populated from the relevant HTML metadata and enabled as a filter in Fields. Some Search Field and URL compatibility options may initially be configured by Airgentic support.

Use Search Configuration > Scopes to map Funnelback-style scopes or clive values to Airgentic scopes. A typical scope filters one page_type value and controls which filters are shown in that tab.

For sorting, common Funnelback values such as date and adate can map to Airgentic date sort options. Other sort IDs can be passed through when matching Airgentic sort options exist for indexed Search Fields.

Funnelback result display rules usually migrate to Airgentic result cards. Use Search Configuration > Result Cards to recreate important result metadata as badges or custom layout blocks.

Existing Funnelback or search-page CSS may also be reusable. See Styling Site Search for the recommended styling layers and selector approach.

Deferred or Advanced Features

Some Funnelback features may need project-specific work, including:

  • full profile behaviour
  • advanced query parameters such as query_and, query_or, and query_not
  • geographic scopes
  • language-specific constraints

Airgentic support can help review which Funnelback parameters are used by your current search.

You have unsaved changes