Updating Pagination link URL

Question

For pagination can we avoid using #1 after the page URL.

For eg -

/abc.html#1

instead have structure like this

/abc/page/1 or
/abc/?page=1 or
/abc/page/1.html. with results maybe from 1 -10 in first page

SantoshSai · Accepted Answer

Hi @manjulakumar,Yes, you can and should avoid using #1 (fragment identifiers) in URLs for pagination in AEM. Here's a breakdown of your options and best practices:Fragment (#) is not sent to the server; it’s processed only by the browser.You can’t handle it on the server side (e.g., AEM servlet, component logic).It’s bad for SEO: search engines may ignore it or index only the first page.It can interfere with analytics and routing in SPA/MFE frameworks.Recommended Alternatives1. /abc/page/1.html2. /abc/?page=13. /abc/page/1

BrianKasingli · Answer

Hello @manjulakumar,Yes, it’s definitely possible to move away from the #1 fragment style in your pagination URLs. That # part is handled only in the browser—it doesn’t trigger a server request—so it's not ideal for scenarios where the backend (like AEM) needs to process different pages of results. URL structures like /abc?page=1 or /abc/page/1.html, you can handle this by writing a custom servlet in AEM that uses the Query Builder API. By passing the page parameter, your servlet can calculate the correct offset and return results for each page dynamically. The Query Builder is great for this because it integrates well with AEM’s permissions and content structure.# Search with "your_search_term" and get results for Page 1curl -X GET "http://your_server/bin/findPagePaths?q=your_search_term&page=1"# Search with "another_search_term" and get results for Page 2curl -X GET "http://your_server/bin/findPagePaths?q=another_search_term&page=2" In fact, I’ve written an article that shows exactly how to do this:AEM Effective Pagination with Query Builder API - https://sourcedcode.com/blog/aem/aem-effective-pagination-with-query-builder-api