I’m integrating Coveo with AEM 6.5.23, and I want to make sure that my AEM page metadata and cq:tags are properly indexed in Coveo.
I can crawl the content using the Coveo web connector, but I’m not sure how to:
Expose custom metadata fields (like cq:tags) from AEM to Coveo.
Map those fields in the Coveo index.
Has anyone set up field mapping for AEM metadata in Coveo? A sample configuration or mapping JSON would be really helpful.
Regards,
Karishma.
Solved! Go to Solution.
Stemap - make sure your pages output metadata that Coveo can read - easiest via sitemap.
In sitemap XML, include custom metadata:
<url>
<loc>https://www.example.com/mypage.html</loc>
<coveo:metadata>
<title><![CDATA[Page Title]]></title>
<description><![CDATA[Meta description here]]></description>
<tags><![CDATA[tag1;tag2;tag3]]></tags>
</coveo:metadata>
</url>
Extend AEM’s sitemap generator to include these.
Once you done, create fields in Coveo
and last step is add mapping - link metadata to these fields.
Stemap - make sure your pages output metadata that Coveo can read - easiest via sitemap.
In sitemap XML, include custom metadata:
<url>
<loc>https://www.example.com/mypage.html</loc>
<coveo:metadata>
<title><![CDATA[Page Title]]></title>
<description><![CDATA[Meta description here]]></description>
<tags><![CDATA[tag1;tag2;tag3]]></tags>
</coveo:metadata>
</url>
Extend AEM’s sitemap generator to include these.
Once you done, create fields in Coveo
and last step is add mapping - link metadata to these fields.
I’ve set up something similar recently. You can expose cq:tags and other custom metadata by adding them as meta properties in your page component’s HTML head (for example, using data attributes or <meta> tags). Then, configure your Coveo web connector mapping to capture those fields.
In Coveo, create custom fields that match the metadata names and map them in your JSON field mapping file. Adobe’s docs and some community threads helped a lot — I actually found a few clear examples shared via Rabattpocket too.
Hope that points you in the right direction!
Views
Replies
Total Likes
Views
Likes
Replies