see screenshot and slack

https://bloomreach.slack.com/archives/C0108FLEYM6/p1644334403886869

Reproduction

to brxsaas-qa sitemap add:

/blog:
  jcr:primaryType: hst:sitemapitem
  jcr:mixinTypes: ['dxphst:mergeable']
  hst:documentrequired: true
  hst:lastmodified: 2022-04-25T14:18:08.080+02:00
  hst:relativecontentpath: xpages/blog/index
  /_default_:
    jcr:primaryType: hst:sitemapitem
    jcr:mixinTypes: ['dxphst:mergeable']
    hst:componentconfigurationid: hst:pages/page-not-found
    hst:parameternames: [topic]
    hst:parametervalues: ['${1}']
    hst:relativecontentpath: xpages/blog/${1}/index
    /_any_:
      jcr:primaryType: hst:sitemapitem
      jcr:mixinTypes: ['dxphst:mergeable']
      hst:componentconfigurationid: hst:pages/page-not-found
      hst:relativecontentpath: xpages/blog/${1}/${2}

and add document structure below 'xpages' :

then going to the CM preview shows in the 'sitemap' the values 'index' instead of 'folder-1' and 'folder-2' which are the actual URLs

Finding

The entire 'index' mentioning was pretty confusing as it has nothing to do with the _index_ matchers which I assumed first and to which this document is linked.

Solution

In general, the JCR Node Name for an xpage doc is the same as the pathInfo in the URL, unless you have a setup like above with 'xpages/blog/${1}/index'. To make sure the sitemap always shows the right values, do not use the jcr node name but the last part of the pathInfo from the HstLink