Alan Vo

Available for remote roles

Menu
  1. Home
  2. Blog
  3. Magento
  4. Adobe Commerce Live Search on production catalogues

Magento

Adobe Commerce Live Search on production catalogues

Magento

Adobe Commerce Live Search is the SaaS catalogue search I install on Adobe Commerce 2.4.4 and newer when OpenSearch is no longer the storefront search I want merchandisers to live in. I am Alan Vo, a Gold Coast web developer with 18 years on Magento, Shopify and WooCommerce catalogues. This note is a production cutover: Composer, feed sync, the Product Listing Page widget, English semantic search, and the limits that still surprise a large SKU store.

Adobe’s What is Live Search page is the product definition I implement against. Once the extension is on, the default Magento search field becomes the Live Search field. A popover suggests products as the shopper types. From Live Search 4.0.0 a Product Listing Page widget, on by default, serves search results and category browse from Catalog Service instead of the old Search Adapter. Read Boundaries and limits first. CMS search, tier pricing in the widget, and native search-term redirects are not in the box.

Why Adobe Commerce Live Search matters on a Magento catalogue

Adobe Commerce Live Search matters on a Magento catalogue because it moves relevance, facets and merchandising off the application box and onto Adobe’s SaaS index. You stop retuning OpenSearch analyzers after every attribute import. You start treating search as a feed job plus an Admin workspace under Marketing, SEO and Search, Live Search.

What changed through 2025 and 2026 is a deprecated adapter, a default PLP widget, and semantic search for English catalogs. Adobe’s Get started with Live Search article (updated 2 September 2026) is explicit: Catalog Service surfaces catalog data for SaaS, and Live Search consumes it. From Live Search 3.0.2 the Catalog Service extension is bundled. From 4.0.0 the Search Adapter only gets security updates. The supported storefront path is the widget that calls the Catalog Service API.

Semantic search, in Adobe’s Semantic search topic (also updated 2 September 2026), adds meaning-based matching next to keywords. A shopper can type “dress for a beach wedding” and still hit products that never used those words. It is English only. Adobe Commerce as a Cloud Service enables it by default on eligible English catalogs. Cloud and on-premises merchants turn it on in Settings. There are no boost sliders. You wait for reindex.

The other change is coexistence. OpenSearch and Live Search cannot both be enabled on the same Commerce instance. On an existing store Adobe’s install path keeps Elasticsearch serving while SaaS syncs, then you enable the Live Search storefront modules and disable Elasticsearch and OpenSearch. That window is where I see the most production mistakes: OpenSearch goes off before the product feed has landed, or both stacks stay half-on and the storefront 500s.

Adobe Commerce Live Search catalogue work on a large monitor

I still treat native Magento search as a fallback, not a feature. Faceted navigation and crawl budget stay in Magento faceted navigation and crawl budget and in the Magento SEO audit checklist for 2026. Live Search does not fix a filter URL explosion. It can make a clean category faster to browse.

How Adobe Commerce Live Search actually works

Adobe Commerce Live Search actually works as the magento/live-search Composer package, catalog feeds exported to Adobe SaaS, and two storefront widgets that query a dedicated GraphQL endpoint. After install, Commerce shares catalog and search data with SaaS. Merchandisers then manage facets, synonyms and rules in the Live Search workspace.

On a new instance the path is: confirm cron and indexers, composer require magento/live-search, disable the Elasticsearch and OpenSearch modules Adobe lists, run setup:upgrade, then set the catalog exporter indexers to Update by Schedule (product, variant, attributes, prices, website and customer-group scopes, categories, category permissions). On an existing instance Adobe tells you to disable Magento_LiveSearchAdapter, Magento_LiveSearchStorefrontPopover and Magento_LiveSearchProductListing first so Elasticsearch keeps serving while you sync. Only after feeds land do you enable those modules and disable OpenSearch.

API keys come from the Commerce license holder through the Commerce Services Connector. Then I run saas:resync in Adobe’s published order: product attributes, products, customer groups, websites, prices, product overrides, variants, categories, category permissions. The first sync can take from 30 minutes to several hours. Search and category browse are down during that sync. Incremental updates after that can take up to 15 minutes.

I verify export in System, Data Transfer, Data Feed Sync Status, then delivery in the Data Management Dashboard. In the database I look for cde_products_feed and cde_product_attributes_feed (older versions used catalog_data_exporter_* names). In the Admin GraphQL workspace I want a product count close to merchandising, and facets that match the attributes I marked filterable. Firewalls must allow commerce.adobe.io.

On the storefront, search-as-you-type starts at two characters. A partial match allows 20 characters per word. The popover shows name, sku and category_ids. If a non-fuzzy query returns nothing, Live Search runs a second fuzzy pass with a maximum edit distance of 1, including adjacent transpositions. Filters can use any indexed filterable attribute. A facet is the subset you show shoppers. Fields such as inStock can filter in the API without appearing as a facet.

Warehouse shelves standing in for a Magento inventory grid

Semantic search uses predefined attributes such as name and description. You do not pick them. Existing rules, synonyms, facets and category merchandising stay in force. Language on the Settings workspace must stay English or semantic search turns itself off. A language change can take 5 to 60 minutes to show.

Indexing limits matter. Live Search indexes up to 450 product attributes per store view: 50 sortable, 200 filterable, 200 searchable. sku, name and categories are always searchable. You can configure 100 facets, with 100 buckets each unless Adobe raises the cap. A query can return 10,000 results and 100 per page. Search merchandising allows 50 rules per store view, 10 conditions and 25 events per rule. Synonyms cap at 200. Category merchandising is one rule per category per store view. Rules apply only on the default sort: Most Relevant for search, Position for categories. Change the sort and pins drop off.

Luma, or a Luma-based theme, gets the popover. Blank theme does not. Headless storefronts must wire events themselves. Healthcare stores on the HIPAA-ready extension must not send protected health information through Live Search. Adobe lists it as a non-HIPAA-ready service.

Production checklist before you cut storefront search over

A Magento store is ready for Live Search when the catalog feed matches merchandising, widgets are on, and OpenSearch is off only after SaaS is serving.

  1. Read Boundaries and limits. If you need CMS search, bring-your-own ranking, or merchandising beyond the 50-rule cap, pick another engine.
  1. Confirm Adobe Commerce 2.4.4 or newer, working cron, and indexers. This is not a Magento Open Source extra you drop onto a cheap VPS.
  1. Install magento/live-search with Composer. On a live store, keep native search serving until saas:resync finishes.
  1. Set the catalog exporter indexers to Update by Schedule. Confirm Product Feed and Product Prices Feed are running, not stalled.
  1. Connect Commerce Services API keys once. Scope the Live Search workspace to each store view. Facets are per scope.
  1. Mark searchable attributes with intent. Adobe wants Use in Search on short, precise values. sku, name and categories stay on. I turn search off on long description text. A shirt described as “short sleeves” will otherwise rank for “shorts”.
  1. For facets, set Use in Search, Use in Search Results Layered Navigation, and Use in Layered Navigation to Filterable (with results). Wrong properties hide the attribute from Add Facet.
Boxed products on a packing bench
  1. Enable Product Listing Widgets (default on 4.0.0+). Flush configuration cache. Confirm search and category browse both render the widget.
  1. Assign every sellable SKU to a real category. Live Search does not invent one. Unassign products from categories you do not want searchable.
  1. Decide semantic search per English store view. Leave it off on a non-English catalog. Wait for index time: up to about 30 minutes on a medium catalog, hours on millions of SKUs.
  1. Write synonyms from actual zero-result queries. Keep brand and part-number terms. Semantic search will not invent your house SKU language.
  1. Allowlist commerce.adobe.io. Test two-character typeahead, a known typo, a facet URL such as ?color=red, and a deep category browse.
  1. On headless or Hyva storefronts, confirm required Live Search events fire. Intelligent merchandising and the Performance dashboard stay empty without them. Do not send health data through this service.

What breaks after you enable Live Search

The first thing that breaks is Advanced Search. Adobe disables that module and removes the footer link. A theme or CMS block that still points at the old route becomes a 404 that looks like a relevance bug.

The second break is OpenSearch left half-enabled. The two engines cannot share an instance. A leftover Magento_OpenSearch module, or a cloud SEARCH_CONFIGURATION that still points at OpenSearch, will fight the widget. “Module does not exist” during disable is fine when that module was never installed. A 500 on /catalogsearch/result is not.

The third is catalog hibernation on non-production. A testing environment with no search query for 90 days goes to sleep and returns nothing. An empty catalog 45 days after create hibernates in production and testing. The wake-up is a support request titled “Reactivate Live Search” plus environment IDs. I have seen staging reviews fail a week before go-live because nobody searched staging for three months.

The fourth is attribute shape on configurables. Live Search indexes parent and child values together. A configurable shirt appears when you filter blue if any variant is blue. That is correct for colour. It is wrong for flags that describe the parent only, such as new_arrival set true on the parent and false on a child. The parent then matches both values. I keep whole-product flags on the parent and I do not facet them from children.

Watch product still used as a Magento PDP example

The fifth is merchandising that only works on default sort. Pins disappear when a shopper switches to price. Category rules disappear when they leave Position. Tell merchandisers that before they schedule a tile that “always” pins a SKU.

The sixth is widget limits. Add to cart in the widget is for simple products. Tier prices do not show. VAT is included and cannot be shown separately. Sort direction cannot be flipped the old Magento way. Adobe calls out first-paint cost on catalogs over 50,000 SKUs. Dynamic facets on high-cardinality attributes can time out. I pin those facets or I drop them.

The seventh is SEO adjacency plus headless eventing. Live Search can accept facet values as URL parameters. That is another crawl surface if you let Google index every ?color= combination. I still only index facets that deserve a landing page. Without events, the Performance workspace is fiction. Luma hid that work. A custom theme does not.

How to measure Adobe Commerce Live Search after go-live

You measure Adobe Commerce Live Search with the Performance workspace, a short list of business queries, and a zero-results export, not with a homepage Lighthouse score. Adobe asks you to review unique searches, replay historical zero-result queries, compare the same query before and after enablement, then watch click-through, conversion and zero-results rate.

I keep about 30 queries the merchandiser cares about: brand, SKU, synonym, typo, natural language, and a known dead query. I run them logged out on production after index time, then again as a customer if B2B shared catalogs are in play. Live Search can hide products missing from the default shared catalog. Category facets can still list categories a customer group cannot open. Those are measurement findings, not “search is broken.”

I compare storefront result counts to admin enabled SKUs in that store view. A large gap is a feed or category-assignment problem. I spot-check price against Default Display Currency. I confirm incremental edits appear inside the 15-minute window Adobe documents.

Revenue is still gateway orders. I do not invent a conversion lift for a search ticket. On the retail conversion Magento work the published figure is year-on-year sales, which mixed merchandising, UX and operations. Search made the SKU findable. It did not write the PDP.

Search Console still matters. If the PLP widget is client-rendered and a crawler sees an empty grid, you have an SEO problem that looks like a search win in Admin. I view-source a search URL and a category URL. I want product links in HTML, or a server-render story I can defend.

Retail aisle used while thinking through Magento filters

Related Magento work on this site

Catalogue search is the same job I did when I directed ecommerce across three Magento stores in the retail conversion work, where year-on-year sales increased $2.5 million over three years. Shoppers had to find an appliance SKU without a layered-nav dead end. I have also shipped Magento storefronts as contract work, including the Never Never Distillery Magento shop, where product names and pack sizes have to be searchable without dumping the whole description into the index, and the Arteriors Magento catalogue, where lighting and furniture attributes are the actual query language. Those builds are why I treat Live Search as a feed and a facet policy, not as a checkbox on a sales deck.

Adobe Commerce Live Search FAQ

What does Adobe Commerce Live Search replace on Magento?

Adobe Commerce Live Search replaces the standard Magento catalog search field, and from version 4.0.0 the supported product listing page, with a SaaS index plus popover and PLP widgets. It does not replace category SEO, robots, canonicals or your PDP. Advanced Search is disabled. OpenSearch cannot stay on.

Can Adobe Commerce Live Search run next to OpenSearch?

No. Adobe’s install guide says OpenSearch and Live Search cannot both be enabled on the same Commerce instance. On an existing store you keep native search up only while the SaaS feeds sync, then you switch. A cloud deploy variable that still points at OpenSearch will undo the Admin work.

How long does Adobe Commerce Live Search take to index?

Adobe Commerce Live Search takes from about 30 minutes to several hours for the first catalog sync, depending on size. Semantic search on a medium catalog can need up to half an hour after you save. Millions of SKUs can need a few hours. Incremental product edits can take up to 15 minutes. I do not announce go-live inside that window.

Does Adobe Commerce Live Search index CMS pages?

No. Adobe Commerce Live Search indexes products from the Commerce database. CMS pages and blocks are not indexed. If you need content search, Adobe’s boundaries page tells you to consider another engine. I keep blog and guide search on a separate tool, or I accept that /catalogsearch is products only.

Adobe Commerce Live Search catalogue work on a large monitor

Keep reading

Contact if you want this kind of work on a live store.