Skip to main content

Blogger problems with Google Sitemap [Fixed]

With the myriad of services that Google offers, its a wonder that any of them work together sometimes.

With this shiny new blog, I wanted to submit a google sitemap (using Google's webmaster tools of course).  If you follow the directions out there on the interwebs about how to do that, it seems that there are some pitfalls.

I followed the directions to use mysite.com/atom.xml, and even tried mysite.com/rss.xml as my feed, but when I checked back in with Google Webmaster tools, sure enough, all my submitted URLs have errors.

The reason it gave was:  "This url is not allowed for a Sitemap at this location. Problem detected on: feedproxy.google.com/~r/etc etc etc. -- Details URL not allowed"


Turns out that certain settings make your blog entries pass through another of Google's services.  The problem that the Google Webmaster service has with this is that the URLs (which start with feedproxy.google.com...) are not the same base URL as the blog (which was "mysite.com/etc/etc" before), hence the "URL not allowed" statement.  I can't claim another site's content as my own, now can I?

Ok, so here is the fix for people with Blogger accounts.  Instead of using people's recommendations of submitting "mysite.com/atom.xml", instead submit "mysite.com/feeds/posts/default?orderby=updated"

Works like a charm, and now my URLs are properly being picked up.  Another hack to make Google work with Google.  Lovely.

Popular posts from this blog

Making Macbook Air with 128GB SSD usable with Bootcamp

I recently got a new Macbook Air 11" (the 2012 version) and loaded it with goodies like 8GB ram and 2GHz Core i7.  What I DIDN'T upgrade was the internal SSD.  My config came with 128GB SSD and I refused to pay $300+ to upgrade it to 256GB.  Yeah I know, some call me cheap, but SSds cost $75-$150 for 240GB, so adding another 128GB for $300 seemed way too steep for me.  I figured "ok, I'm going to make 128G work!"

Here is the story of how that went...

Installing python 3.4.x on OSX El Capitan

I love "brew" package manager, but sometimes being too progressive breaks things.  I have several python apps that I maintain that get deployed to AWS using Elastic Beanstalk.  AWS eb can deploy with python 2.7 or 3.4.  Any recent 'brew install python3" will get 3.5.1. #annoying

Dell XPS M1330 + Snow Leopard Hackintosh

I have been working with a Dell XPS M1330 laptop for a few years now.  It doesn't quite match up to the newest notebooks in terms of performance, but it certainly still has some life in it.  I had previously installed OSX 10.5.x on it as an experiment, and had moderate success.  I decided to revisit this idea again to install Snow Leopard (OSX 10.6) on the Dell M1330, and keep some notes for those of you brave enough to Hackintosh your own machine...