Expand my Community achievements bar.

ReplicationAction not finding generated sitemap hence 404

Avatar

Level 2

Hi There,

 

We have sitemap generator working perfectly for top level locale files (i.e us/en/sitemap.xml). However when it comes to lower level pages sitemaps, ReplicationAction is failing to find those files due to path mismatch. For example sitemap for /us/en/about-us/newsroom page is generated under /var/sitemaps/ and as

 

/content/xxx/us/en/about-us-newsroom-sitemap.xml.

 

However ReplicationAction is failing to find resource under 

 

/content/xxx/us/en.sitemap.about-us-newsroom-sitemap.xml

 

Which means ReplicationAction is finding file at wrong place or generated name is incorrect. I dug into ReplicationAction documentation but could not find where I can force it to look into right folder and files. In logs ReplicationAction is failing with following warning

 

*WARN* [sling-default-1] com.adobe.cq.cloudconfig.core.impl.ConfigurationReplicationEventHandler Resource [/content/xxx/us/en.sitemap.about-us-newsroom-sitemap.xml] not found for ReplicationAction and hence throws 404 when it is accessed on publish instance

 

Request community's help

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

6 Replies

Avatar

Community Advisor

Hi, 

Are you using a custom sitemap generator? Or the ootb Sling sitemap generation?



Esteban Bustamante

Avatar

Level 2

I am using AEM sitemap Generator with custom code by extending ResourceTreeSitemapGenerator

Avatar

Level 2

Hi @EstebanBustamante 

 

Even if I use default OOTB Sling Sitemap, I am still facing same issue

Avatar

Community Advisor

Hi,

 

This behavior probably makes sense. The reason this is not common is that you should not replicate the sitemaps from the author to the publisher. Instead, you should configure the publisher to generate a sitemap with content specific to the publisher. If you're trying to replicate from author to publisher, you might also encounter inconsistencies, as the content published on the publisher is not always the same as all the content available on the author.

EstebanBustamante_0-1733834973482.png

 

Please check this: https://experienceleague.adobe.com/en/docs/experience-manager-learn/sites/seo/sitemaps#sitemap-sched... 

 

Hope this helps



Esteban Bustamante

Avatar

Level 2

Hi @EstebanBustamante,

 

Thanks for the kind reply. I already followed that page while implementing sitemaps and our sitemap scheduler configuration is placed under config.dev/ config.stage/ and config.prod/ and I suppose this may be automatically applied to both author and publish instance for those environment.

 

And we have not made anything that would replicate  sitemaps from author to instance. I was just digging logs and found error as mentioned above in logs, so I thought that could be the issue

Avatar

Community Advisor

So, what you pointed out is a "Warning." Is there any issue happening with the sitemap generation? The best way to troubleshoot is by starting a local Publisher instance and checking if the sitemap is generated under /var. I haven’t had any issues in the past using the out-of-the-box Sling sitemap generator.



Esteban Bustamante