I would save a copy and then delete the old sitemap that you generated, and then add the new Yoast sitemap through GWT >> Crawl >> Sitemap >> Add/Test Sitemap.
I am having the same problem. One of my new clients had a website hosted on a company created with a website builder in use by that company, and I changed the DNS to my hosting company/folder containing a WordPress site. The site is live and We enabled Google Analytics and GWT. The former site map appeared in GWT. When I test the new sitemap generated by Yoast, I get the same message about the robots.txt blocking – there are 14 errors. When I view the current robots.txt (see it live), it has no blocking directives in it. How can I fix this? I would hate to have my new client’s website performance plummet because of work that we did to improve his performance. The live site is http://herewetow.com.
Zee
(@laserjobs)
PatBirch it is probably just google has cached the old robots.txt. You can resubmit it in Google Sitemaps or wait for google to update it.
Current robots.txt:
User-agent: *
Disallow: /wp-admin/
Okay. Thanks. I also canceled the website builder tool product in the client’s account, and hopefully that will remove any of the old sitemaps that appear to be in conflict. Thanks! I’m going to leave the issue open, in case it does not clear up. Once or if it does resolve, I’ll close it.
