Google Sitemaps Bug To Be Fixed Soon?

Oct 27, 2008 • 7:21 am | comments (1) by twitter Google+ | Filed Under Google Search Engine Optimization
 

The other day we reported Google Webmaster Tools Showing 0 Pages Indexed For Sitemaps Users. In short, some of those who have submitted a Sitemap file via Google Webmaster Tools were having issues with those Sitemaps.

Many saw their Sitemap files remain in the "pending" status, while others noticed the index count of their Sitemaps stats were reporting 0 pages indexed. Now, none of these reporting glitches have a direct impact on the Google search results, but nevertheless they can cause webmasters to worry.

Google is aware of the issue and opened an official thread at Google Groups where Googler, JohnMu said:

As some of you have noticed, things are still a bit slow over on the Sitemaps side of things, especially regarding new Sitemap file submissions and the indexed URL count shown in Webmaster Tools.

Rest assured that the team has been busy working on these issues. We're hoping that things should be back to normal within a few days or so. As I have more information, I'll post here to keep you updated.

Keep in mind that we'll still continue to crawl and index your websites normally, so you shouldn't see any change in the way your site is indexed and ranking in our search results.

One webmaster at WebmasterWorld noticed some improvements. He said:

I've seen some change... a few sitemaps that were *pending* are now showing normal, but others have not updated. A mixed bag.

Hopefully things will clear up soon.

Forum discussion at WebmasterWorld, Google Groups (official) and Google Groups 2.

Previous story: Video Recap of Weekly Search Buzz :: October 26, 2008
 

Comments:

Rob Abdul

10/28/2008 09:28 am

There also appears to be a problem with the mobile site map. Error “Your Sitemap or Sitemap index file doesn't properly declare the namespace” It appears that I am not the only one with this error message in Google Web Master Tools. The strange thing is it seems to correct itself some days. So I decided to ignore these errors.

blog comments powered by Disqus