Title: namespace doesn&#039;t properly declare after moving to https
Last modified: August 31, 2016

---

# namespace doesn't properly declare after moving to https

 *  Resolved [sfsbruce](https://wordpress.org/support/users/sfsbruce/)
 * (@sfsbruce)
 * [10 years, 1 month ago](https://wordpress.org/support/topic/namespace-doesnt-properly-declare-after-moving-to-https/)
 * I move my site to https and after submitting sitemap to webmaster tools https
   version account I got this error
    `Your Sitemap or Sitemap index file doesn't
   properly declare the namespace. Expected: http://www.sitemaps.org/schemas/sitemap/
   0.9 Found: https://www.sitemaps.org/schemas/sitemap/0.9`
 * then I’ve checked the sitemap page I found out that the sitemap src also move
   to https
 * `<urlset xmlns="https://www.sitemaps.org/schemas/sitemap/0.9">`
 * How to fix this?
 * [https://wordpress.org/plugins/wordpress-seo/](https://wordpress.org/plugins/wordpress-seo/)

The topic ‘namespace doesn't properly declare after moving to https’ is closed to
new replies.

 * ![](https://ps.w.org/wordpress-seo/assets/icon-256x256.gif?rev=3419908)
 * [Yoast SEO - Advanced SEO with real-time guidance and built-in AI](https://wordpress.org/plugins/wordpress-seo/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-seo/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordpress-seo/)
 * [Active Topics](https://wordpress.org/support/plugin/wordpress-seo/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-seo/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordpress-seo/reviews/)

## Tags

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

 * 0 replies
 * 1 participant
 * Last reply from: [sfsbruce](https://wordpress.org/support/users/sfsbruce/)
 * Last activity: [10 years, 1 month ago](https://wordpress.org/support/topic/namespace-doesnt-properly-declare-after-moving-to-https/)
 * Status: resolved