Adobe Experience Manager

This is for:

Developer System Administrator

Adobe Experience Manager integrates with Coveo so you can index website pages and assets, enrich them with metadata, and surface relevant results in Coveo-powered experiences.

About Adobe Experience Manager

Adobe Experience Manager is a content management system for managing digital experiences, websites, and assets.

Why use Coveo with Adobe Experience Manager?

Connect your repository to a unified index so users can find relevant Adobe Experience Manager content alongside content from other systems.

  • Index the items and metadata that are relevant to your users.

  • Once indexed, surface this content alongside content from your other sources. Present it in a single Coveo-powered search interface with filtering, ranking, and personalized results, or make it available to an LLM app or agent through a Coveo MCP Server connection.

A Coveo source that uses a generic connector, like the Sitemap source, retrieves content and metadata from Adobe Experience Manager and indexes it in Coveo. A Coveo-powered search interface can then surface the indexed content.

The following diagram shows the recommended Adobe Experience Manager integration.

Adobe Experience Manager integration diagram | Coveo Analytics

1

The Coveo Sitemap source retrieves content using the Adobe Experience Manager API; use a Coveo Web source when no sitemap is available.

2

The Coveo Atomic search interface sends requests to the Coveo Search API. The Search API returns results and AI-generated answers back to the interface. Another way to query the Coveo index is through an MCP client and Coveo MCP Server connection. See AI assistants and agents for more information.

3

The Coveo Atomic search interface sends analytics data to the Coveo Platform.

Prerequisites

Integrate Adobe Experience Manager with Coveo

Follow these steps to select a source, index your Adobe Experience Manager content, and verify the results.

Step 1: Create and configure the source

Create a Coveo Sitemap source and configure the sitemap URLs, crawling scope, authentication when required, and metadata extraction.

Prefer a Sitemap source when possible

The AEM indexing guidance recommends a Sitemap source because it’s faster and provides more options for indexing metadata than a Web source. The Coveo Web source is a fallback when no suitable sitemap is available.

Sitemap and Web sources don’t support the Same users and groups as in your content system content-security option. To index item-level permissions, choose a generic source that supports the Same users and groups as in your content system content-security option like the Coveo Push source, and test the experience with representative users.

Step 2: Index your Adobe Experience Manager content

Build the source, then use the Content Browser (platform-ca | platform-eu | platform-au) to verify the indexed pages, assets, URLs, and metadata.

Step 3: Create source mappings and fields

Create the required source mappings and fields to index the metadata you want to use in search experiences.

Step 4: Build the search interface

  1. Confirm that Coveo Atomic is the right approach for the Adobe Experience Manager search experience by following Choose the right approach.

  2. If applicable, follow Atomic getting started documentation to start building the Coveo Atomic search interface.

    Tip

    Create your search interface project using the npm create @coveo/ui command line tool.

Considerations

  • Plan sitemap coverage and content updates

    A Sitemap source indexes the URLs in its sitemap. Include asset URLs in the sitemap when you need to index AEM DAM assets. To use refresh updates, sitemap entries need a valid last-modified value; newly added or deleted sitemap entries require a rescan or rebuild.

  • Choose metadata extraction deliberately

    Sitemap sources can extract metadata in sitemap entries, JSON-LD, HTML metadata, or using web scraping configurations. By default, HTML head metadata is not indexed by a Sitemap source. Enable or configure the applicable extraction methods before creating mappings.

What’s next?