Hello all,
Is there a way to clean up the generated sitemap which is no longer required.
We had sitemap generated for path /content/test/page1 and /content/test/page2 through sitemap scheduler.
Later, we disabled the sitemap generation for /content/test/page2 by disabling "Generate Sitemap" checkbox on properties page. But the sitemap node(under var/sitemap) is still present. How to get rid of it.
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
You can also unpublished the /var/sitemaps/sitemap-name with the help of Adobe representative.
Additionally you can block the crawler access of that sitemap from robots.txt or file access from CDN or dispatcher.
hi @Ajay_KR,
You can manually delete the sitemap nodes under /var/sitemaps that correspond to the paths for which sitemap generation was disabled. This typically requires permission to access and manage the repository content. If the operation is to be executed only once, I would not find a more elegant yet complex solution.
Hi @giuseppebag ,
Thank you for the response.
This cleanup is required on AEMaaCS Publish(Stage and Production) environment. Since we do not have access to CRXDE, deleting the node manually will not work.
Regards,
Ajay
Views
Replies
Total Likes
You can contact your Adobe representative, who has rights/access and can assist with this one-time operation. I think they will be happy to help you.
Hi @Ajay_KR ,
When you uncheck Generate Sitemap, AEM stops updating it, but it doesn’t auto-delete the old sitemap node.
To clean it up, you need to manually remove the sitemap node under /var/sitemaps/<path> (via CRXDE, Repo browser, or Groovy script).
AEM won’t auto-clean - you must delete the sitemap node yourself.
@Ajay_KR Just checking in! Were you able to get this resolved? If you found your own solution, sharing the details would be a big help to others who might face the same issue later on. And if one of the replies here helped, whether it fully solved the problem or simply pointed you in the right direction, marking it as accepted makes it much easier for future readers to find. Thanks again for helping close the loop and contributing to the community!
Views
Replies
Total Likes