Google Webmaster Tools Invalid URL errors [#741374]

Google Webmaster Tools is reporting three Invalid URLs:

http://s/forumgif
http://
http://weekly

I don't see those URLs actually in the sitemap so I'm not sure if it's an issue with Google or that there's some other code in the sitemap that is causing the errors. I've resubmitted the sitemap twice and these errors continue to generate.

Any ideas what could be causing the problem?

Comments

Comment #1

Anonymous (not verified) commented 13 March 2010 at 12:22

Status:

Active

» Fixed

You'll have to ask Google. If you look at the sitemap.xml report and don't see the URL's where do they get them?

Comment #2

Lloyd commented 19 March 2010 at 16:22

Status:

Fixed

» Active

Re-opening this as it does appear to be something going on in Drupal. There are other reports of the exact same issue when using XML Sitemap. Hopefully someone can assist. The sitemap in question is small - www.mytermbroker.com/sitemap.xml. I ran it through an xml sitemap validator and received the message:

"validator crash during target reading
Error: Character data not allowed in prolog
in unnamed entity at line 1 char 1 of http://www.mytermbroker.com/sitemap.xml
"

In looking at the sitemap, every URL being generated is using https instead of http. I have a few pages that are secured via Secure Pages but certainly not all of them. I do think the default in that module is for admin pages to be secure so perhaps that's causing the issue.

Comment #3

Anonymous (not verified) commented 19 March 2010 at 16:24

Status:

Active

» Postponed (maintainer needs more info)

@Lloyd: My bet is that your problem is caused by Page cached by Boost @ 2010-03-18 23:23:30, expires @ 2010-03-19 05:23:30

Are you using version 1.2 or version 2.0-alpha2?

Comment #4

Lloyd commented 19 March 2010 at 16:59

Version:

6.x-1.2

» 6.x-2.0-alpha2

I'm now using 6.x-2.0-alpha2. I've configured the base URL in both the module and in settings.php. I read in an older post about disabling the update upon new/changed site content and only running on cron, but I don't think that applies anymore. I disabled caching of xml files in Boost.

I'll post back if this resolves the issue.

Thanks.