Welcome to WebmasterWorld Guest from 220.127.116.11
I've created a page called "sitemap.xml.gz" and placed in my root directory.
The Google Sitemaps bot found the page but I'm getting the following error message every day:
"General HTTP error Couldn't parse HTTP response"
This is the code I placed on the sitemap.xml.gz file:
<?xml version="1.0" encoding="UTF-8"?>
< urlset xmlns="http://www.google.com/schemas/sitemap/0.84">
I took this from the Google examples page, so it should be o.k. Does anyone know why I am getting this error message and what I can do to fix it?
Thanks in advance :-)
and the spaces between < and the tag names :
< url> is forbidden as it should be <url>
but it shouldn't give a HTTP error
If you used a text editor like Notepad to create your sitemap file, it is unacceptable, it saves it in ascii I beleive.
You MUST use a program that can save your Sitemap file in UTF-8.
For example, I used a program that automatically generated my sitemap in the proper format, then I submitted it.
The text file must use UTF-8 encoding!
BTW, have you noticed errors in the date that Google Claims they crawled your sitemap last?
3 days ago it said May 14 was the last day they crawled my sitemap. Then 2 days ago it said May 8 after was the last crawl date! Now it's back to saying it was last crawled on May 14 again!
Google is definitely doing a lot of testing, and turning on and off of filters this week. Also noticed on many searches Google did away with Supplemental Results.
Hope this helps you!
Also, try an online server-header tool or a tool like the Firefox "Live HTTP Headers" extension to see what exactly is the HTTP response that the sitemaps bot can't parse.
Note: the encoding is only an issue of you have non-ASCII characters in the file, otherwise UTF-8 is compatible with US-ASCII.
My sitemap file does not have this command as far as I know, so maybe it's forcing Google to expect it to be in UTF-8 mode, but if an ASCII editor was used instead it could cause a problem.
We'll know for sure when they dig up Jimmy Hoffa's bones.
... this would only be a problem if the file contains characters values above chr(127) (=Windows 'umlauts' and other 'foreign' characters). If the textual content is pure 7bit ASCII, then the use of a simple ASCII editor is no problem, because the resulting text is UTF-8 compliant then.
When I view the HTTP Headers error message, it says:
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
Whitespace is not allowed at this location. Error processing resource 'http://www.mywebsite.com/sitemap.xml.gz'. Lin...
I don't have whitespace in the <> tags as far as I can tell, not sure why it is giving me this response.