Hi Community,
Has anyone here used ACS Commons Sitemap Generator for AEM in a production setup?
We are evaluating options for generating sitemaps in our AEM as a Cloud Service project. I know ACS Commons has a sitemap generation feature, but I have also seen that AEM now provides OOTB (out-of-the-box) sitemap generation in recent versions.
For those who have tried both, what’s your recommendation? Any pros/cons I should be aware of before deciding?
Hi @martinsm4,
I’d suggest going with the OOTB sitemap generation in AEMaaCS. Here’s why:
Deprecation Notice: The ACS Commons Sitemap Generator is actually deprecated for AEM as a Cloud Service. You can see the note here: ACS Commons Sitemap Docs. It’s still fine for older on-prem or AMS setups, but for Cloud Service, it’s not the recommended path going forward.
Better Integration: The OOTB feature is built specifically for AEMaaCS. It handles multi-site setups, respects publish/unpublish states, and integrates cleanly with the page tree without requiring extra code.
Official Support: Since it’s part of the product, you get support from Adobe and don’t have to maintain custom logic or worry about breakage after upgrades.
If you’re starting a new project or migrating to Cloud Service, I’d configure the OOTB sitemap with proper include/exclude rules and call it a day. Adobe has a good guide here: AEM OOTB Sitemap Documentation.
In short - for AEMaaCS, skip the ACS version and stick with the OOTB one. It’s future-proof, simpler to maintain, and aligns with Adobe’s recommendations.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.