This content has been marked as final. Show 4 replies
I started working on Endeca SEO in ATG. i followed spring discover-electronics SEO implementation and created ATG components Accordingly .
i'm able to generate the Endeca SEO URLs. But the problem is not able to get the results.
please let me know what would be the root cause ?
It would be problem with your configuration. I don't see any problem with seeing SEO url's and results associated to it for base configuration but facing problem while configuring advance SEO features like config-path. Is it possible for you to share the components created using Spring App?
1) set key to a property..1 person found this helpful
2) create ProductCategoryKey.properties
Hope it helps... for more details refer Oracle docs.
Just weighing in here. To create site URLs, the current revision of the Endeca Sitemap Generator (v2.1.1) uses Spring configuration. Specifically, the Endeca Sitemap Generator does not know how to consume UrlFormatter configuration specified using Nucleus. As such, if you configure your UrlFormatter (and associated classes) with Nucleus, then you will need to manage two separate versions of your UrlFormatter configuration: a Nucleus version for your application and a Spring version for the Sitemap Generator.
Without getting into any specifics, the purpose of the Endeca Sitemap Generator is to create sitemaps within a multi-dimensional navigation space. This is a unique problem (and big SEO opportunity) for faceted search sites. This is not something that you'll get with any generic sitemap generation utility.
With the above in mind, my understanding is that the forthcoming version of CRS will use the NucleusPublisher mechanism to resolve UrlFormatter components that are managed within a Spring context. While not ideal in the long-term, this does allow you to manage a single UrlFormatter configuration, which can be shared between your application and the Sitemap Generator.
For reference, here's the doc link for the NucleusPublisher: