That said, there are some interesting engineering challenges here. Valid paths in a cloud-mounted React app are pretty much unknown, which means you’d need some mechanic to communicate them to the sitemap renderer.
For example, suppose you have a dynamic property app that’s pulling in listings from an API. If it’s mounted on property that might look like megsrealty.com/property/123-awesome-lane
But there could the thousands of listings, and they could be dynamic.
When I need to do crazy things like that I reverse proxy the sitemap and mod it exactly how I like.
For now, if you do a wishlist item, I’d probably focus on the use case of adding manual routes, which covers use cases like a custom calculator, a map solution etc. where you have a handful of known static paths.
Ran into this on a client quiz app , easiest workaround was disabling auto-sitemap and hosting a custom one that merges Webflow pages + Cloud routes. Until Webflow supports manual route injection, reverse-proxying or static sitemap overrides are the only reliable options.