Cleanup unwanted sitemap | Community
Skip to main content
A
Ajay_KR
Level 2
September 11, 2025
Solved

Cleanup unwanted sitemap

  • September 11, 2025
  • 3 replies
  • 740 views

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.

Best answer by arunpatidar

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.


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. 

3 replies

giuseppebaglio
giuseppebaglio
Level 10
September 11, 2025

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.

 

 
    A
    Ajay_KRAuthor
    Level 2
    September 11, 2025

    Hi @giuseppebaglio ,

     

    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

    arunpatidar
    Community Advisor
    arunpatidarCommunity AdvisorAccepted solution
    Community Advisor
    September 11, 2025

    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.


    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. 

    Arun Patidar
      HrishikeshKagne
      Community Advisor
      HrishikeshKagneCommunity Advisor
      Community Advisor
      September 11, 2025

      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.

      Hrishikesh Kagane
        kautuk_sahni
        Community Manager
        kautuk_sahniCommunity Manager
        Community Manager
        September 12, 2025

        @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!

        Kautuk Sahni
        Terms & ConditionsAccessibility statement

        Loading footer...