Adobe EDS - Does helix-query.yaml in project repository still works? | Community
Skip to main content
G
gabrielfgmzk
Level 2
November 21, 2025
Solved

Adobe EDS - Does helix-query.yaml in project repository still works?

  • November 21, 2025
  • 2 replies
  • 116 views

Adobe EDS - Does helix-query.yaml in project repository still works?

Hello!

 

My project has been created using Aem Boilerplate XWalk. 

If I understood correctly. If 'helix-query.yaml' is present on repository then no spreadsheet sitemap configuration would be necessary on AEM.

 

The following helix-query.yaml was wrote:

 

version: 1 indices: portuguese: &default include: /home target: /query-index.json properties: title: selectFirst: head > meta[property="og:title"] value: attribute(el, "content") lastModified: select: none value: parseTimestamp(headers["last-modified"], "ddd, DD MMM YYYY hh:mm:ss GMT") robots: select: head > meta[name="robots"] value: attribute(el, "content") validation: select: none value: true

 

When debugging locally with 'aem up --print-index', it seems to be working.

 

info: Index information for /home info: Index: portuguese info: title: "Home" info: lastModified: "" info: robots: "" info: validation: true

 

But there is no change when accessing "https://{branch}-{repo}-{organization}.aem.page/sitemap.xml" or "https://{branch}-{repo}-{organization}.aem.page/query-index.json".

"https://{branch}-{repo}-{organization}.aem.page/helix-query.yaml" returns 404.

 

Maybe I didn't understand the concept correctly, should I just use AEM Admin API?

 

Thank you for your patience,

Gabriel

 

    Best answer by VishalKa5

    Hi @gabrielfgmzk ,

     

    helix-query.yaml does not work in EDS anymore.
    It is only used by the local development simulator (aem up) to help you test indexing.
    The real EDS runtime does not load or publish this file, so:

    • /helix-query.yaml returns 404
    • /query-index.json does not update
    • /sitemap.xml does not change

    In EDS, indexing must be configured through:

    AEM Admin UI > Search & Indexing

    or

    AEM Admin API (the recommended approach)

    These replace the old helix-query.yaml behavior.

    So yes - you still need Admin indexing configuration even if your local aem up --print-index looks correct.

     

    Thanks

    2 replies

    ManviSharma
    Adobe Employee
    ManviSharmaAdobe Employee
    Adobe Employee
    November 21, 2025

    Hello @gabrielfgmzk ,

     

    Have you published a page since you setup the sitemap?

    VishalKa5
    VishalKa5Accepted solution
    Level 5
    November 22, 2025

    Hi @gabrielfgmzk ,

     

    helix-query.yaml does not work in EDS anymore.
    It is only used by the local development simulator (aem up) to help you test indexing.
    The real EDS runtime does not load or publish this file, so:

    • /helix-query.yaml returns 404
    • /query-index.json does not update
    • /sitemap.xml does not change

    In EDS, indexing must be configured through:

    AEM Admin UI > Search & Indexing

    or

    AEM Admin API (the recommended approach)

    These replace the old helix-query.yaml behavior.

    So yes - you still need Admin indexing configuration even if your local aem up --print-index looks correct.

     

    Thanks

    Terms & ConditionsAccessibility statement

    Loading footer...