Title: Error XML declaration allowed
Last modified: November 2, 2016

---

# Error XML declaration allowed

 *  Resolved [AdrianoAgri](https://wordpress.org/support/users/adrianoagri/)
 * (@adrianoagri)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/error-xml-declaration-allowed/)
 * Hi! i have found a problem with sitemap.
    I realize a new website, after a little
   customization and a lot of work to setup everythings in the right way using the
   coming soon mode, it was time to open to public, but working to conect with search
   console i have found this problem with sitemap
 * > This page contains the following errors:
   >  error on line 2 at column 6: XML 
   > declaration allowed only at the start of the document Below is a rendering 
   > of the page up to the first error.
 * with no links or other else in the page.
    I Have a multisite with a multilingual
   plugin, q-translate x, and woocommerce installed. I have a booking theme
 * I have no other sitemap plugin which can cause conflicts
 * Have any idea of what’s wrong?
 * thanks

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Support [amboutwe](https://wordpress.org/support/users/amboutwe/)
 * (@amboutwe)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/error-xml-declaration-allowed/#post-8388042)
 * This happens when something in your WordPress install, either a plugin or your
   theme, is outputting white space and it shouldn’t.
 * The fastest way to find out what is outputting the white space is to run a conflict
   check. If you are unfamiliar with checking for conflicts, we wrote a small guide
   that will walk you through the steps. You can find it here: [How To Check For Plugin Conflicts](https://kb.yoast.com/kb/how-to-check-for-plugin-conflicts/#utm_source=support&utm_medium=forum&utm_campaign=support-link)
    -  This reply was modified 9 years, 5 months ago by [amboutwe](https://wordpress.org/support/users/amboutwe/).
 *  Thread Starter [AdrianoAgri](https://wordpress.org/support/users/adrianoagri/)
 * (@adrianoagri)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/error-xml-declaration-allowed/#post-8388789)
 * Yes… i’ll find it, it’s woo extra fee plugin from prem tiwari, after i have deactivated
   all plugins, and reactivate one by one, when was the woo extra fee turn, it gave
   to me an headers error message, testing the sitemap effectively shows the error.
 * Now i’ll try to contact prem tiwari for support, but what i have to look for?
   white space in headers?
 * i hope to recover it because its very useful for me…
 * thanks amboutwe
 *  Plugin Support [amboutwe](https://wordpress.org/support/users/amboutwe/)
 * (@amboutwe)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/error-xml-declaration-allowed/#post-8388925)
 * In a lot of cases, it’s a single empty line at the end of a file.
 *     ```
       last line
       {blank line}
       ```
   
 * instead of
 * `last line`
    -  This reply was modified 9 years, 5 months ago by [amboutwe](https://wordpress.org/support/users/amboutwe/).

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Error XML declaration allowed’ 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

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

 * 3 replies
 * 2 participants
 * Last reply from: [amboutwe](https://wordpress.org/support/users/amboutwe/)
 * Last activity: [9 years, 5 months ago](https://wordpress.org/support/topic/error-xml-declaration-allowed/#post-8388925)
 * Status: resolved