Does AEM Edge Delivery | Community
Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
SantoshSai
SantoshSaiAccepted solution
New Participant
July 11, 2025

Hi @vickey-1,

This could be a broader topic (and honestly, depends on your site setup), but I’ll try to cover the basics that helped us get SEO working smoothly on EDS:

Yes, AEM Edge Delivery does support SE!

EDS renders fully structured HTML at the edge, so crawlers like Google can easily read it - unlike SPAs where you often need server-side rendering or pre-rendering tricks.

This is what works OOTB

  • You can define custom <title>, <meta name="description">, Open Graph, and Twitter meta tags directly inside your head.html.

  • It supports clean URLs and even route mapping via fstab.yaml, which is super handy for SEO.

  • You can expose your own /robots.txt and /sitemap.xml, either as static files or through serverless logic.

  • Injecting structured data (JSON-LD) is totally possible - just drop the <script type="application/ld+json"> in your head block.

  • Pages are rendered as plain HTML (no JS-heavy output), so bots can read them easily.

Only different in tradtional AEM: You won’t find page properties like dc:title or cq:tags - instead, metadata is usually defined in the markdown front matter or in the Git-managed templates.

Santosh Sai
View reply

2 replies

BrianKasingli
BrianKasingli
New Participant
July 12, 2025

Yes!, AEM Edge Delivery Services (EDS) supports SEO. One of its key advantages is that pages are server-side rendered and delivered as fully-formed HTML files (from the content source like Google Drive or Share Point). You can inspect the page source (without relying on JavaScript) and see the actual HTML content — which is ideal for search engines to crawl and index. (example: https://www.volvotrucks.ca/en-ca/ )

In addition:

  • You can configure SEO-critical metadata like <title>, <meta name="description">, <meta name="robots">, Open Graph tags, Twitter cards, etc., using a metadata block directly in the content document or a centralized metadata sheet. 

  • URLs are clean and derived from the document name (e.g., lowercase-dashes.html), improving crawlability.

  • Redirects (301s) are handled through a CSV sheet and deployed at the CDN layer to avoid SEO ranking drops.

  • Pages are optimized for Core Web Vitals, improving rankings by ensuring performance, stability, and responsiveness.

You can explore more on this in the Indexing & SEO guide for AEM EDS.

Translate
    SantoshSai
    SantoshSaiAccepted solution
    New Participant
    July 11, 2025

    Hi @vickey-1,

    This could be a broader topic (and honestly, depends on your site setup), but I’ll try to cover the basics that helped us get SEO working smoothly on EDS:

    Yes, AEM Edge Delivery does support SE!

    EDS renders fully structured HTML at the edge, so crawlers like Google can easily read it - unlike SPAs where you often need server-side rendering or pre-rendering tricks.

    This is what works OOTB

    • You can define custom <title>, <meta name="description">, Open Graph, and Twitter meta tags directly inside your head.html.

    • It supports clean URLs and even route mapping via fstab.yaml, which is super handy for SEO.

    • You can expose your own /robots.txt and /sitemap.xml, either as static files or through serverless logic.

    • Injecting structured data (JSON-LD) is totally possible - just drop the <script type="application/ld+json"> in your head block.

    • Pages are rendered as plain HTML (no JS-heavy output), so bots can read them easily.

    Only different in tradtional AEM: You won’t find page properties like dc:title or cq:tags - instead, metadata is usually defined in the markdown front matter or in the Git-managed templates.

    Translate
    Santosh Sai
      Terms & ConditionsAccessibility statement

      Loading footer...