Title: Sitemap vs. WordPress native one
Last modified: August 27, 2021

---

# Sitemap vs. WordPress native one

 *  Resolved [Rodrigo](https://wordpress.org/support/users/rghedin/)
 * (@rghedin)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/sitemap-vs-wordpress-native-one/)
 * Hi David,
 * I’m looking for a simpler/less bloated SEO plugin and yours fits the bill as 
   far as I can see!
 * I have one doubt, however. Since 5.5, WordPress has a native sitemap generator.
   How does Simple SEO deals with this native feature?

Viewing 1 replies (of 1 total)

 *  Plugin Author [David Cole](https://wordpress.org/support/users/coleds/)
 * (@coleds)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/sitemap-vs-wordpress-native-one/#post-14820093)
 * Simple SEO generates /sitemap.xml in the root directory, WP generates /wp-sitemap.
   xml in the root directory. So far with all WP sites I’ve seen there is no wp-
   sitemap; I imagine there is additional code needed in the theme to generate the
   sitemap.
 * You can submit which ever sitemap you want to Google, Bing, etc.

Viewing 1 replies (of 1 total)

The topic ‘Sitemap vs. WordPress native one’ is closed to new replies.

 * ![](https://ps.w.org/cds-simple-seo/assets/icon-256x256.png?rev=2076401)
 * [Simple SEO](https://wordpress.org/plugins/cds-simple-seo/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/cds-simple-seo/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/cds-simple-seo/)
 * [Active Topics](https://wordpress.org/support/plugin/cds-simple-seo/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/cds-simple-seo/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/cds-simple-seo/reviews/)

## Tags

 * [sitemap](https://wordpress.org/support/topic-tag/sitemap/)

 * 1 reply
 * 2 participants
 * Last reply from: [David Cole](https://wordpress.org/support/users/coleds/)
 * Last activity: [4 years, 11 months ago](https://wordpress.org/support/topic/sitemap-vs-wordpress-native-one/#post-14820093)
 * Status: resolved