Sitemap configuration and actual generation
Check product status, website assignment, and store view of the listing. A product present in the backend is not automatically publicly accessible at every store address.
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: The sitemap calls /product/expiration model/, this URL provides 404. The product was either deliberately removed or disappeared due to a routing error.
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.
Upon final removal, take the record from the sitemap selection. In the event of unintentional unreachability, restore the URL or set a suitable final destination.
Derogations and scope
A deleted page may correctly deliver 404. The contradictory inclusion in the sitemap is the part to be checked here.
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: Differentiate deleted and accidentally missing pages