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 Troubleshooting

Airgentic Help

This page lists common Site Search issues and what to check first.

No Results

Try these checks:

  1. Broaden from This site to All sites, if that control is available.
  2. Try a simpler query.
  3. Check whether the relevant pages have been crawled.
  4. Check whether a category or filter is too narrow.
  5. Confirm the index has been updated after recent configuration changes.

Wrong or Missing Categories

Check:

  • Manual category mappings.
  • Auto-generated mappings.
  • Muted auto mappings.
  • URL path depth fallback.
  • Scope configuration on Search Configuration > Scopes.
  • Whether the index has been updated after category changes.

See Configuring Search Result Categories.

If categories exist in the index but tabs are missing or ordered unexpectedly, also check Configuring Search Scopes.

Missing Filters

Check:

  • The Search Field exists in Search Configuration > Fields.
  • Show this field as a search filter is enabled.
  • The field has values on matching documents.
  • The current scope is configured to show that filter.
  • A reprocess or reindex has run since the field was added.

See Configuring Filters.

If the field exists and values are indexed but the filter appears only in some tabs, check the scope's Filters shown in this scope setting.

Sort Options Are Missing or Do Not Change Results

Check:

  • The field is configured in Search Configuration > Fields.
  • The field type is sortable, such as date, number, keyword/filter value, or URL/path.
  • The field has values in the index.
  • The current scope has the intended default sort.
  • The index has been updated after adding or changing the field.

Text and hierarchy fields are not usually available as result sort options.

Field Exists But Has No Values

Check:

  • The metadata names are correct and use the same casing/names emitted by the website.
  • The source is set to HTML metadata for metadata-backed fields.
  • The field type is appropriate, usually Keyword / filter value for simple filters.
  • If the field should contain multiple values, Multi-valued is enabled and the split separator matches the metadata format.
  • If the field should be a drill-down filter, the field type is Hierarchy / drill-down path and the hierarchy delimiter matches the indexed value.
  • The crawler has reprocessed pages since the field was added.

For standard result fields such as title, description, image, and date, also check which configuration source is active. Existing services usually use Web Crawl Configuration > Standard Result Fields. If the service has not enabled Use Search Fields for standard result fields, changes to those standard rows in Fields will not override the web crawl mappings.

See Configuring Indexed Fields.

No AI Answer

AI answers may be hidden when:

  • AI answers are disabled for the search layout.
  • The query is too unclear or too narrow.
  • The AI determines that the top results do not support a useful answer.
  • The service is configured for search-only mode.

Normal search results can still appear without an AI answer.

Result Cards Look Wrong

Check:

  • The current scope is assigned to the intended result card in Search Configuration > Scopes.
  • The result card uses the intended layout in Search Configuration > Result Cards.
  • Badge fields exist in Search Configuration > Fields and have values in the index.
  • The result has an image value if the selected layout depends on thumbnails.
  • Custom layout blocks reference fields that exist and have values.
  • The index has been updated if a new field was added for a badge or custom layout block.

Use the card preview in Result Cards to test one card, and use Search Configuration > Preview to test the full search page.

See Configuring Result Cards and Layouts.

If the result card data is correct but the page needs visual adjustments, see Styling Site Search.

Inline Search Does Not Appear

Check:

  • The Airgentic script tag is present.
  • data-account-id and data-service-id are correct.
  • Inline search is enabled for the service.
  • The page includes:
<div data-airgentic="search"></div>

See Adding Site Search to Your Website.

Funnelback URLs Do Not Work

Check:

  • Funnelback compatibility is enabled for the service.
  • Inbound parsing is enabled.
  • The URL uses supported parameters.
  • Unsupported parameters are not required for the expected result.

See Funnelback Migration Guide.

Results Look Stale

Search results may be stale if content or configuration changed but the index has not been updated.

Ask an administrator to run the appropriate reprocess or reindex job.

You have unsaved changes