Google sitemap warning?

Discussion in 'Google Sitemaps' started by monicalou123, Jun 19, 2007.

0
  1. #1
    My webmaster tools show that my sitemap status is warning. I don't know what happen on my sitemap. My sitemap is generate by GSiteCrawler. Any Idea?
     
    monicalou123, Jun 19, 2007 IP
  2. karamkshetra

    karamkshetra Peon

    Messages:
    254
    Likes Received:
    8
    Best Answers:
    0
    Trophy Points:
    0
    #2
    Just check the URL for which it is showing the warning, may be it have something to do with some error.
     
    karamkshetra, Jun 19, 2007 IP
  3. RhymeR

    RhymeR Guest

    Messages:
    1
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #3
    Resumbit ;)
     
    RhymeR, Jun 23, 2007 IP
  4. blafrog

    blafrog Peon

    Messages:
    84
    Likes Received:
    3
    Best Answers:
    0
    Trophy Points:
    0
    #4
    I have this warning last night, and it's gone today. Not sure where's the problem..
     
    blafrog, Jun 23, 2007 IP
  5. ineedaspo

    ineedaspo Peon

    Messages:
    22
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #5
    dont use that generator any more
     
    ineedaspo, Jun 23, 2007 IP
  6. windtalker

    windtalker Well-Known Member

    Messages:
    926
    Likes Received:
    34
    Best Answers:
    0
    Trophy Points:
    145
    #6
    The warning probably meant there were urls on the sitemap the googlebot could not find or crawl.
     
    windtalker, Jun 24, 2007 IP
  7. NexusTech

    NexusTech Peon

    Messages:
    32
    Likes Received:
    5
    Best Answers:
    0
    Trophy Points:
    0
    #7
    Resubmit and check to see what URL it's warning you about.

    Mine was returning errors consistently, no matter what I did. I thought it was Gsitecrawler, too, but the errors were inconsistent.

    Then I realized my host was blocking IPs for a set period of time for too many connections within a set time period. Google was one of them.

    I told them that was a bad idea. They continued sending me 'cookie-cutter' responses, so I switched hosts and the errors went away.
     
    NexusTech, Jun 24, 2007 IP