Sitemap.xml & Yoast sitemap-index.xml question

A website and Wordpress Blog on same domain

[edwardsgs]

I'm working on a medium size web site ~2600 pages. The primary site is mainly php. We've recently added a Wordpress Blog to the same domain & use Yoast Wordpress SEO. We've always used GSiteCrawler to create sitemap.xml. But now Yoast creates a sitemap-index.xml and its four xmls files: post-sitemap.xml, page-sitemap.xml, category-sitemap.xml, post_tag-sitemap.xml.

So now between Yoast & GSiteCrawler, the Blog files are getting listed in sitemaps twice. I'm wondering if there are any negative consequences of this. Or any conflict between having a sitemap.xml and a sitemap-index.xml?

I could easily turn Yoast's XML sitemap feature off. Maybe this is nothing to worry about. Ideas, Suggestions?

Thanks - Scott

[diberry]

I think you probably should turn off one or the other, just to avoid confusion. I just installed Yoast's plugin and was hoping it would replace another sitemap plugin, but it's generating errors (WMT says it can't crawl some of the links, which actually aren't even IN the sitemap, and in any case are not blocked - who knows, it may be a WMT issue, but the sitemap from the other plugin never did this).

[edwardsgs]

Thanks for your response diberry. I decided to use the Yoast sitemaps for the Wordpress portion of this website and I eliminated all of the Wordpress files from the sitemap I built using GSiteCrawler for the remainder of the website. As to your issue - Since the links that Google is trying to crawl and generating errors for aren't in your sitemap, Could they be internal, followed links on pages that the Yoast sitemap listed that your earlier sitemap did not? We've been having good luck with the Yoast sitemap - it makes life a lot simpler for our Wordpress sites.

[diberry]

No, they are images, actually. Old images I replaced ages ago. I've left a comment in the plugin's Wordpress forum, so we'll see if he gets back to me with suggestions. It may well be I haven't configured something properly, but I've gone over it several times. No idea!

[diberry]

Ooookay, on one site this problem resolved itself inexplicably after a few days... long after Google had cached the new robots.txt. Whatever! I'm now testing it on another site.