Skip to content
Adobe Commerce Storefront Logo Adobe Commerce Storefront

Search is only available in production builds. Try building and previewing the site to test it out locally.
Go Live

SEO overview

Search optimization on this storefront depends on two coordinated layers: how Edge Delivery Services serves HTML to crawlers, and how your Commerce catalog URLs and metadata stay consistent across stores.

Two layers to coordinate

Section titled “Two layers to coordinate”

Edge Delivery Services (platform)

Section titled “Edge Delivery Services (platform)”

Edge Delivery Services (EDS) shapes the first HTML response. Document-based pages usually ship most of their text there, while many catalog product detail pages (PDPs) load details later for performance unless you publish server-side metadata or use prerender. Search engines and large language model (LLM) crawlers still rely on that first payload, so Adobe publishes shared SEO and GEO guidance on AEM.live . GEO guidance sits alongside SEO on that page because some crawlers do not fully render every page and rely on that initial HTML payload.

SEO and GEO best practices on AEM.live How EDS treats canonical content, server rendering versus rendering in the browser, sitemaps, robots rules, structured data, and how performance ties to discoverability. Read this alongside your Commerce configuration.

Adobe Commerce storefront (catalog)

Section titled “Adobe Commerce storefront (catalog)”

Your Commerce layer adds URL patterns, folder mapping, canonical choices, structured metadata, and multi-store rules on top of those EDS defaults. Document-based routes and catalog routes behave differently, so search crawlers and social previews can treat thin or duplicate first HTML as low-value unless SEO indexing and SEO metadata remain consistent. In particular, SKUs, configurable products, and store-specific URLs all influence which URL wins and what appears in that first response.

The SEO indexing and SEO metadata pages spell out storefront-specific checks. They extend the platform baseline on AEM.live .

Keep both layers aligned

Section titled “Keep both layers aligned”

Use the same information in the platform response and the catalog: one clear URL per indexable product context, matching metadata, and enough useful text in the first HTML.

  • Match Edge Delivery Services expectations for sitemaps, robots, performance, and primary content in the first HTML. Treat SEO and GEO best practices on AEM.live as the baseline for your mix of document-based and catalog routes.
  • Implement URL rules, folder mapping, canonicals, hreflang, and store-specific crawling behavior from SEO indexing so the URLs you publish are the URLs you want indexed.
  • Publish titles, descriptions, and structured data for catalog pages from SEO metadata so those fields line up with the URLs above.
  • Before go-live, verify with Launch checklist — SEO and indexing. If validators or feeds still see thin PDP HTML, use AEM Commerce prerender.
Section titled “Related links in this documentation”

Use these pages when you implement indexing, metadata, launch checks, or prerender for your storefront:

  • SEO indexing — canonical URLs, product URL format, redirects, hreflang, and multi-store considerations.
  • SEO metadata — titles, descriptions, structured data, and PDP metadata workflows.
  • Sitemaps — sitemap configuration for catalog pages, prerender integration, and multi-store hreflang.
  • Platform limits — URL naming rules, index size caps, and redirect limits that affect Commerce storefronts.
  • Launch checklist — SEO and indexing — tasks to verify before go-live.
  • AEM Commerce prerender — server-rendered HTML when catalog pages rely on client-side data.