AI agents: the content index is at /llms.txt. Every page is also available as Markdown — send the request header Accept: text/markdown, or append .md to the page URL.
Xperience Docs

Cookie consent

We use necessary cookies (opens in a new tab) to run our website and improve your experience while browsing. Additional cookies are only used with your consent. You may revoke your consent on the Cookies Policy (opens in a new tab) page or in your browser at any time.

Configure (opens in a new tab)
  • Documentation
    InstallationUsing the Xperience interfaceDeveloping websitesConfiguring XperienceManaging usersSecuring websitesDeploying websitesManaging website contentMultilingual websitesMacro expressionsExternal utilitiesIntegrating 3rd party systemsCustom developmentE-commerce featuresOn-line marketing featuresRelease notes - Xperience 13Xperience terminology glossary
  • Tutorial
    Using the Xperience interfaceDeveloper tutorialBusiness tutorialResource hub for marketers
  • API Examples
    ConfigurationContent managementDevelopmentE-commerceOn-line marketingSocial media
  • Community Questions & Answers (opens in a new tab)
  • Contact support (opens in a new tab)
  1. Home
  2. Configuring Xperience
  3. Setting up search on your website
  4. Using locally stored search indexes
  5. Mapping fields for search results

Mapping fields for search results


Was this page helpful?

Send us feedback Go back to top

Related pages

  • Creating local search indexes
  • Building a search interface for local indexes

When setting up search using locally stored indexes, you can separately configure the indexed objects (Page types, Custom tables, Forms, etc.), and choose which data appears in search results.

The appearance and design of the results always depends on the search interface implementation. However, the system allows you to map specific object fields to the most common parts of search results, such as the title, content extract or image. Developers can then access the mapped data in their code using the corresponding properties of SearchResultItem objects, which they process within the search implementation.

  1. Edit the indexed object (most commonly in the Page types, Custom tables or Forms application).

  2. Select the Search tab.

  3. In the Field mapping for search results section, choose source fields for the following parts of search results:

    Description

    SearchResultItem property

    Title field

    The field whose value is used for the title of search results.

    Title

    Content field

    The field whose value is used for the content extract of search results.

    Content

    Image field

    The field that contains the image displayed in search results.

    Image

    Date field

    The field whose value is used for the date and time displayed in search results.

    Created

  4. Click Save.

The search results for the given object type now display data from the assigned fields, provided that developers use the corresponding SearchResultItem properties within the search implementation.

All selected fields are automatically included within search indexes that cover the object type. This applies even for Pages indexes and page types using the HTML output data source (in this case the search itself is based on the processed HTML content of pages, but data for search results is loaded from the assigned fields).

Note: Search result field mapping does not have any effect for Azure Search indexes. The format of Azure search results is fully controlled by the implementation of your search interface. See Integrating Azure Search.