SEO & SSR in Storefronts using Adobe Edge Delivery Services

[olsalas711]

Hi everyone,

I’m working on a storefront project using Adobe Edge Delivery Services (EDS) and wanted to clarify the expected behavior around Server-Side Rendering (SSR) and SEO.

In particular, I'm reviewing how dynamic content (e.g., product names, links, headers fetched via GraphQL or similar APIs) is treated in the SSR output.

Scenario:
Some pages (like PLP and PDP) display content that is rendered client-side, and when inspecting the HTML source (view-source), this content does not appear to be present in the initial SSR response from the edge.

Questions:

What is the recommended way to ensure that critical content (titles, product names, links) is included in the SSR output for SEO purposes?

Can this be addressed using enhancements in helix-markup.yaml, scripts.js, or other EDS configurations?

Are there known strategies for SSR fallback or crawler-specific behavior in EDS to ensure search engines receive a fully rendered version of the page?

My main goal is to ensure the storefront is SEO-friendly and fully indexable, while still leveraging the dynamic and performant architecture of EDS.

Any guidance, best practices, or examples would be greatly appreciated!

Thanks in advance

[arunpatidar · Accepted solution]

Hi @olsalas711 

Please check a really nice article about it at aem.live

https://www.aem.live/blog/folder-mapping-deprecated