to disable the WordPress 5.5 XML Sitemap
Good news or bad news?
WordPress 5.5 automatically creates a new XML websitemap.
If you have an existing solution to your XML sitemap you might now have two!
Search engine optimization problems can arise from the difference between the XML sitemap you previously created and the native WordPress sitemap.
Where can I find the new WordPress Native XML Sitemap
You can check for new XML sitemaps if you’re using WordPress 5.5 or later. Add /wp–sitemap.xml after your root domain.
Take, for example:
Use the Yoast Search Engine Plugin
Yoast SEO plugin is already installed. Version 14.5 disables the auto-generated WordPress XML sitemap feature.
Yoast 14.5 and newer will redirect you to the Yoast XML sitemap if you request the native WordPress XML Sitemap.
Use the All in One SEO plugin?
All in One SEO plugin version 3.6.0 (released July 8, 2020) will automatically disable the native WordPress XML sitemap.
To disable the Native XML Sitemap, use a plugin
To remove the native XML sitemap WordPress creates, you can use a plugin such as Disable XML Websitemap.
Deactivate the WordPress Native XML sitemap manually
You can find the related FAQ .
You can disable the sitemap feature by using a filter.
You need image, video or Google News Sitemaps
The new native XML sitemap function does not support the addition of image, video, or Google news sitemaps. However, it is likely that this feature will be supported in the future.
Are Search Engines Discouraged?
Site note: If your WordPress admin settings are set “discourage search engine from indexing this website,” (under Settings -> Read), then the native XML sitemap is also disabled. A 404 error will be generated if you request the native XML sitemap (/wp–sitemap.xml), while “discourage Search Engines” is disabled.
What should I do?
If you’re using an existing SEO plugin or sitemap plugin (such a Yoast SEO, All in One SEO), please upgrade to the most current version.
You can disable/deregister native XML sitemaps using filters, or if you don’t want to have one at all.
If you encounter interesting edge cases while updating to WordPress 5.5, let me know.