Still getting
Gateway Time-out
The gateway did not receive a timely response from the upstream server or application.
This only happens when trying to access the sitemaps with v2.0. When on version 1.7.4 this does not occur.
V2.01 and still sitemap_index.xml not accessible.
Pretty sure this is not a server-side issue. Switching back to v1.7.4 (again)
Anybody else have this issue?
I just noticed that in Google webmaster my with the updated plugin I get this error message: Your Sitemap appears to be an HTML page. Please use a supported sitemap format instead. But, the other sitemaps register ok.
So, I untoggled Check this box to enable xml sitemap functionality and toggled it back on and got mine to be recognized by Google.
Vegastriguy…
I tried that myself, my problem is it won’t generate the sitemap_index.xml file at all. When you or any of the bots try to access it, it throws an Error 504 Gateway Timeout error. I’ve narrowed it down to a compatibility issue between my theme and wordpress seo.
I shot the maker of the theme I use an email to see if they have a solution.
Thanks for the input.
If you’re using W3 Total Cache, this may help:
In the Page Cache section, unclick “Cache 404 (not found) pages”
And in the Browser Cache section, add this to “404 error exception list”:
sitemap(_index)?\.xml
(sitemapindex|[a-z0-9_-]+)\.xml
You may not really need to do both, I’m not sure, but I did, and I haven’t had the problem since. I too was extremely frustrated with this problem, as I searched a lot and couldn’t find the answer, and was using Google Sitemap for a while. Yoast ought to make this clear somewhere.
Not using W3, but did turn off all plugins except yoast, still get the same error, so it’s definitely something between the theme and yoast. Frustrating.
Anonymous User 13711045
(@anonymized-13711045)
I’m getting the same error. When I select a post type to exclude it breaks.
If you’re using any caching program, it might work…
I’m using Zen Cache Pro not W3 and I’ve turned off all other plugins except Yoast … still get the same problem.
It would appear it has a problem with custom post types. When I tell it to NOT include the custom post type it generates the sitemaps fine. This sucks because the custom post type is what I need the sitemaps for.
Interesting. I increased the number of entries per sitemap to 10,000 and it generated the sitemap files. If I leave it at the stock 5000 it times out generating the files.
I installed Better WordPress Google XML Sitemaps and it generates the sitemap without trouble just like yoast 1.7.4 does. Hate to say it but it looks like 2.01 has a serious issue with sitemaps and larger sites.
