WordPress sitemap deployment

CMS and site-platform connections are supported in reviewed environments for the platforms listed in the Extensions Hub; access and management depend on the Site entitlement and current capabilities. Platform detection does not establish which provider owns the current sitemap.

Before deploying a generated set:

1. identify the authoritative sitemap generator and prevent two systems from publishing conflicting outputs;
2. review the generated files and determine how future content changes will be reflected;
3. deploy through an authorised process — the Sitemap Workbench can use configured SFTP or FTP credentials when the user has the publish capability; and
4. re-scan the public sitemap and verify search-console submission separately.

Keep connection and publication separate

Connecting Flowpane does not give permission to modify the Site. Managed changes must be explicitly enabled separately and covers only offered supported actions. A Flowpane-managed sitemap is distinct from third-party plugin output and from a set you upload through your normal hosting process.

After a change, check that the declared sitemap is the one the public Site actually serves. If plugin output returns after an update, resolve ownership with the maintainer before publishing another competing set.