- This topic has 3 replies, 2 voices, and was last updated 10 years, 1 month ago by .
- The forum ‘Design Tips and Tricks’ is closed to new topics and replies.
These forums are for general discussion on WordPress and Genesis. Official support for StudioPress themes is offered exclusively at My StudioPress. Responses in this forum are not guaranteed. Please note that this forum will require a new username, separate from the one used for My.StudioPress.
Tagged: Yoast SEO
Using Yoast SEO (http://wordpress.org/plugins/wordpress-seo/). http://skinnychef.com/sitemap_index.xml lists five sitemaps - the first http://skinnychef.com/post-sitemap1.xml results in an error message that prevents search engines' access:
"Content Encoding Error - The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression."
It's only with this single XML sitemap, the others are working fine. I cleared all caches. How do I nuke the sitemap in question and then rebuild?http://skinnychef.com/post-sitemap1.xml
It looks like a timeout error - if you check the error_log in your root directory, I bet you'll see some kind of PHP error around the same time you tried to view the sitemap. Sitemaps are usually huge files, and since 1and1 is notorious for setting low limits on resource usage, it's likely that those limits are causing the problem.
Another option could be if you use a caching plugin that has gzip compression enabled - if the server you're on already has gzip enabled, your caching plugin's attempt to do it again can result in errors.
1. Site is hosted through yours truly websynthesis.
2. Using W3 Total Cache. Cleared cache, deactivated plugin, reloaded http://skinnychef.com/post-sitemap1.xml = still same error.
There's actually another error message showing up for 400ms before the other generic message shows:
XML Parsin Error: no element found
Line Number 1, Column 1:
Sorry about that - your DNS shows that it's pointing to 1and1 so I was ready to blame it on crappy hosting. 🙂
I'd ask Synthesis support since they are able to see more information about the error than anyone here. It's hard to know what's happening without access to the server logs. Hopefully they can get it sorted out for you!
© 2023 WPEngine, Inc.