How to Implement Full-Text Search in Document-Based Authoring (EDS)? | Community
Skip to main content
S
SurabhiAc3
March 13, 2025
Solved

How to Implement Full-Text Search in Document-Based Authoring (EDS)?

  • March 13, 2025
  • 2 replies
  • 799 views

I'm working with Edge Delivery Service (EDS) with document-based authoring in AEM and exploring how to implement full-text search. 

  1. Does document-based authoring support full-text search, and if so, how?
  2. Are Content Fragments or structured content indexed for search within this setup?
  3. What are the recommended approaches, tools, or APIs available to enable full-text search in EDS?
Best answer by giuseppebaglio

1) EDS converts structured documents (Google Docs, Microsoft Word) into web pages, but native full-text search requires additional configuration:

-Indexing via Spreadsheets: EDS automatically indexes published pages using spreadsheets (e.g., query-index.xlsx or Google Sheets). These indexes store metadata like title, description, and lastModified, which can be queried via JSON [1].

-Custom Search Blocks: you can embed third-party libraries like Algolia’s Autocomplete or InstantSearch directly into EDS pages using document-based blocks. For example, an "instant-search" block in a Google Doc can render a dynamic search interface [2].

As per limitations, native EDS indexing focuses on metadata rather than deep content analysis. Full-text search across PDFs, Excel files, or complex assets typically requires external tools [3][4].

 

2) Content Fragments (used in traditional AEM for headless content) are not directly indexed in EDS. Instead, EDS prioritizes document-based content stored in spreadsheets or collaborative tools [1][2]

 

3) you can embed Algolia’s search libraries (Autocomplete.js, InstantSearch.js) into EDS blocks for real-time, performant search with features like faceting and federated results [2].
Another tool like Bounteous’s EDS Search Utility enhances the native spreadsheet API by enabling field-specific searches, client-side filtering and sorting [4]
you can define custom indexing using query-index.xlsx with headers like title, description, and content to extract HTML content for indexing [1]


[1] https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/edge-delivery/build/indexing 
[2] https://www.algolia.com/blog/ecommerce/extending-adobe-edge-delivery-services-for-performant-search 
[3] https://www.argildx.us/technology/fulltext-search-in-aem-pages-assets-custom-search-pdf-excel-and-powerpoint/ 
[4] https://www.bounteous.com/insights/2024/09/04/introducing-our-search-utility-edge-delivery-services/ 

2 replies

giuseppebaglio
giuseppebaglioAccepted solution
New Member
March 13, 2025

1) EDS converts structured documents (Google Docs, Microsoft Word) into web pages, but native full-text search requires additional configuration:

-Indexing via Spreadsheets: EDS automatically indexes published pages using spreadsheets (e.g., query-index.xlsx or Google Sheets). These indexes store metadata like title, description, and lastModified, which can be queried via JSON [1].

-Custom Search Blocks: you can embed third-party libraries like Algolia’s Autocomplete or InstantSearch directly into EDS pages using document-based blocks. For example, an "instant-search" block in a Google Doc can render a dynamic search interface [2].

As per limitations, native EDS indexing focuses on metadata rather than deep content analysis. Full-text search across PDFs, Excel files, or complex assets typically requires external tools [3][4].

 

2) Content Fragments (used in traditional AEM for headless content) are not directly indexed in EDS. Instead, EDS prioritizes document-based content stored in spreadsheets or collaborative tools [1][2]

 

3) you can embed Algolia’s search libraries (Autocomplete.js, InstantSearch.js) into EDS blocks for real-time, performant search with features like faceting and federated results [2].
Another tool like Bounteous’s EDS Search Utility enhances the native spreadsheet API by enabling field-specific searches, client-side filtering and sorting [4]
you can define custom indexing using query-index.xlsx with headers like title, description, and content to extract HTML content for indexing [1]


[1] https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/edge-delivery/build/indexing 
[2] https://www.algolia.com/blog/ecommerce/extending-adobe-edge-delivery-services-for-performant-search 
[3] https://www.argildx.us/technology/fulltext-search-in-aem-pages-assets-custom-search-pdf-excel-and-powerpoint/ 
[4] https://www.bounteous.com/insights/2024/09/04/introducing-our-search-utility-edge-delivery-services/ 

    AmitVishwakarma
    Community Advisor
    AmitVishwakarmaCommunity Advisor
    Community Advisor
    March 15, 2025

    Hi @surabhiac3 ,

    Implementing full-text search within AEM)Edge Delivery Service (EDS) with document-based authoring involves several considerations:

    1. Support for Full-Text Search in Document-Based Authoring:

    Yes, document-based authoring in EDS supports full-text search. EDS allows content creators to use familiar tools like Microsoft Word or Google Docs to author content, which is then transformed into web pages. To enable full-text search, the content from these documents must be indexed appropriately. This involves parsing the documents, extracting textual content, and indexing it using a search engine or indexing service compatible with EDS. Edge Delivery Services Overview

    2. Indexing Content Fragments and Structured Content:

    In AEM, Content Fragments are structured pieces of content that can be reused across multiple pages and channels. To include these fragments in search results, their data needs to be indexed. This typically involves:

    1. Identifying References: Navigating to the content pages, locating 'content-fragment' nodes, and retrieving the fileReference property to identify the path of the fragment.

    2. Extracting Data: Accessing the fragment's path to retrieve the relevant data properties for indexing.

    This approach ensures that both the main content and the associated fragments are searchable. Reference


    3. Recommended Approaches, Tools, or APIs for Enabling Full-Text Search in EDS:

    1. Custom Indexing: Develop custom indexing solutions tailored to your content structure. This may involve creating scripts or services that traverse your content repository, extract textual data, and index it using a search platform compatible with EDS.

    2. Third-Party Search Services: Integrate with external search services like Algolia or Coveo, which offer robust indexing and search capabilities. These platforms can ingest content from AEM and provide advanced search functionalities. Reference

    3. AEM's Built-in Indexing: Leverage AEM's native indexing mechanisms. AEM provides tools and configurations to index content effectively, enabling efficient search operations. Reference

    For a comprehensive understanding and implementation guidance, consider exploring the following resources:

    Edge Delivery Services Overview: Provides insights into the capabilities and architecture of EDS. Reference

    Content Search and Indexing in AEM: Offers detailed information on AEM's indexing strategies and best practices. Reference

    By following these approaches and utilizing the appropriate tools, you can effectively implement full-text search within your EDS environment, ensuring that both document-based content and structured fragments are searchable and accessible to users.

    For a visual walkthrough and deeper insights into document-based authoring with Edge Delivery Services, you might find the following video helpful: Link

    Regards,
    Amit Vishwakarm

     

      Terms & ConditionsAccessibility statement

      Loading footer...