Sitemap.xml returns unpublished item paths

[thaitranet]

Describe the Bug

Sitemap.xml returns unpublished item paths from the same BLOB generated on the CM host and published to the Edge.
https://github.com/Sitecore/jss/blob/dev/packages/create-sitecore-jss/src/templates/nextjs-sxa/src/pages/api/sitemap.ts

To Reproduce

1. Add a new item in XMC but don't publish it.
2. Go to https://rendering-host/sitemap.xml to see the item path. It returns 404 when the path is entered.
3. Go to https://edge.sitecorecloud.io/.../media/Project/Sites/.../Sitemaps/.../sitemap.xml to see the same content.

Expected Behavior

The public sitemap.xml should show published URLs only.

Possible Fix

1. Replace sitemap.ts to get routes from Edge GraphQL (without SXA)
2. OR, generate a new sitemap BLOB for published URLs for the Edge and use SXA settings.

Provide environment information

• Sitecore Version: XMC
• JSS Version: 21.6.2
• Browser Name and version: All
• Operating System and version (desktop or mobile):
• Link to your project (if available):

[addy-pathania]

@thaitranet Thanks for registering this. I have added this to our backlog. We will be investing soon.

[alan-null]

Hey @thaitranet
Could you please confirm if the new item created had any workflow assigned?
If not, this is how it works right now by design.

To protect against it, every page MUST have a workflow assigned.

Currently sitemap.xml content has to be created on XM where there is NO information whether something was published or not (like it used to be possible with master & web architecture), thus workflow should be there to control it.

When there is a publish which triggers sitemap refresh all of the pages for a given site are used for sitemap regeneration.

re: Possible Fix

These are good ideas but none is prefect and some of the current functionalities couldn't work or would require extra changes in edge schema.

There are plans to improve current architecture but for now recommendation is to use workflows.