--- title: Adobe Experience Manager slug: q93b0597 canonical_url: https://docs.coveo.com/en/q93b0597/ collection: integrations source_format: adoc --- # Adobe Experience Manager + + 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](https://business.adobe.com/products/experience-manager/adobe-experience-manager.html) is a content management system for managing digital experiences, websites, and assets. ## Why use Coveo with Adobe Experience Manager? Connect your [repository](https://docs.coveo.com/en/2739.md) to a unified [index](https://docs.coveo.com/en/204.md) so users can find relevant Adobe Experience Manager content alongside content from other systems. * Index website pages and assets in Coveo. * Preserve metadata that can populate searchable and filterable [fields](https://docs.coveo.com/en/200.md). * Combine Adobe Experience Manager content with content from other [sources](https://docs.coveo.com/en/246.md). ## Recommended integration architecture A Coveo source that uses a [generic connector](https://docs.coveo.com/en/pa6h0282.md), like the Sitemap source, retrieves content and metadata from Adobe Experience Manager and saves it in a Coveo index. 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](https://docs.coveo.com/en/assets/images/integrations/adobe-experience-manager-integration-diagram.svg) | 1 | The Coveo Sitemap source retrieves content using the Adobe Experience Manager API; use a [Coveo Web source](https://docs.coveo.com/en/malf0160.md) 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. An alternative way to query the Coveo index is through an MCP client–Coveo MCP Server connection. See [AI assistants and agents](https://docs.coveo.com/en/q9ad0472.md) for more information. | | 3 | The Coveo Atomic search interface sends analytics data to the Coveo Platform. | ## Prerequisites * Access to the Adobe Experience Manager content and assets that must be searchable. * A Coveo organization with privileges to create and manage sources. * A decision about the Adobe Experience Manager [connector](https://docs.coveo.com/en/2734.md) strategy and the metadata to expose. ## 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: Choose an indexing strategy Review [the Sitemap and Web connector comparison](https://docs.coveo.com/en/l89f0171.md#sitemap-and-web-connector-comparison-table) to determine how to index the Adobe Experience Manager pages and assets that you want to make searchable. Use a Sitemap source when Adobe Experience Manager provides a sitemap that includes the required URLs and metadata. Use a [Web source](https://docs.coveo.com/en/malf0160.md) only when a sitemap is unavailable or unsuitable. ### Step 2: Create and configure the source Create a [Sitemap source](https://docs.coveo.com/en/1967.md) and configure the sitemap URLs, crawling scope, authentication when required, and metadata extraction. If you must use a Web source, follow [Add a Web source](https://docs.coveo.com/en/malf0160.md) to configure its starting URLs, crawl scope, authentication, and metadata extraction. ### Step 3: Index your Adobe Experience Manager content [Build the source](https://docs.coveo.com/en/2039.md), then use the [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)) to verify the indexed pages, assets, URLs, and metadata. ### Step 4: Create source mappings and fields Create the required [source mappings and fields](https://docs.coveo.com/en/1640.md) to index the metadata you want to use in search experiences. ### Step 5: 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](https://docs.coveo.com/en/3368.md). 1. If applicable, follow [Atomic getting started documentation](https://docs.coveo.com/en/atomic/latest/#where-do-i-start) to start building the Coveo Atomic search interface. > **Tip** > > Create your search interface project using the [npm create @coveo/ui](https://docs.coveo.com/en/q8qh2338.md) command line tool. ## Considerations * **Prefer a Sitemap source when possible** The AEM indexing guidance recommends a Sitemap source because it is faster and provides more metadata-indexing options than a Web source. The Web source discovers content by following page links, so it is a fallback when no suitable sitemap is available. * **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 use Coveo metadata in sitemap entries, JSON-LD, HTML metadata, or web scraping configurations. By default, HTML head metadata is not indexed by a Sitemap source, so enable or configure the applicable extraction method before creating mappings. * **Do not assume Adobe Experience Manager permissions are synchronized** Sitemap and Web sources do not support the [**Same users and groups as in your content system**](https://docs.coveo.com/en/1779.md) content-security option. Before exposing non-public content, configure an appropriate Coveo content-security scope and test the experience with representative users. ## What's next? * See [source update schedules](https://docs.coveo.com/en/1933.md) to configure when your source checks for changed content. * See [Achieve relevance](https://docs.coveo.com/en/n9qd0422/) to improve the relevance of the Adobe Experience Manager search experience. * See the [integration directory](https://docs.coveo.com/en/q7ki1127.md) for other Coveo integration opportunities.