Sitemap configuration and actual generation
Control sitemap configuration and public deployment for the relevant Store View. A sitemap for another store does not replace this assignment.
Under Marketing › SEO & Search › Site Map, check the generated file and its path as well as the associated store context. The configuration and the last successful rebuild are different things.
Where to check the setting in Magento
Under Marketing → SEO & Search → Site Map, check the sitemap assignment to the Store View. Check the creation time, file path and accessibility of the registered products. In the case of automatic generation, the responsible cron run must also work.
Example of this specific finding
Illustrative control case: A shop has many new products, but no well-maintained sitemap endpoint. A one-time URL export would become obsolete after the next import.
follow-up audit in Magento
After a product change, create a new file or check the schedule. Compare the public sitemap with active product status and reachable target URLs.
Provide a regularly generated selection of final public URLs. Check new, removed and excluded products after a normal data update.
Derogations and scope
A small, well-linked website can be found without a sitemap. A sitemap does not replace meaningful internal navigation.
Reference: Magento Open Source or Adobe Commerce with classic storefront. Consider store views and extensions; other storefront architectures have their own configurations.
Classify the general error
Definition, system-independent causes and further correction examples: Use a reliable URL source instead of any export