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/bu...
[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-po...
[4] https://www.bounteous.com/insights/2024/09/04/introducing-our-search-utility-edge-delivery-services/
