Google Sitemap Warning Need Help!

Discussion in 'Google Sitemaps' started by mike_rocker, Jun 10, 2008.

  1. #1
    Hello,

    I'm currently running Wordpress on my site and have installed a Google Sitemap plugin. Everythign seemed to work fine however my pages did not get indexed by Google. I decided to wait till the Google Bot came around.

    My sitemap is located at vgretro.com/sitemap.xml

    When it did on the 7 I checked my Google Webmasters account and found a warning message.

    When we tested a sample of the URLs from your Sitemap, we found that some URLs were not accessible to Googlebot because they contained too many redirects. Please change the URLs in your Sitemap that redirect and replace them with the destination URL (the redirect target). All valid URLs will still be submitted.

    I don't understand what they mean by redirects any know how I can fix this? I though it might have something to do with Wordpress.
     
    mike_rocker, Jun 10, 2008 IP
  2. feras80

    feras80 Well-Known Member

    Messages:
    302
    Likes Received:
    5
    Best Answers:
    0
    Trophy Points:
    110
    #2
    You have to check with the module that turn urL from /blog/archives/6 to something like /name-of-the-entry . It might be redirecting the old URL to the new one. Did you check the htaccess file?
    Let me know what u get
    Cheers
     
    feras80, Jun 10, 2008 IP
  3. mike_rocker

    mike_rocker Peon

    Messages:
    114
    Likes Received:
    2
    Best Answers:
    0
    Trophy Points:
    0
    #3
    Hi Thanks for your reply,

    How do I check the module that turns the URL to the pretty URL? I understand what your saying but not sure how to check that. However when you mentioned the htaccess file I noticed that there is nothing in there.
     
    mike_rocker, Jun 11, 2008 IP
  4. feras80

    feras80 Well-Known Member

    Messages:
    302
    Likes Received:
    5
    Best Answers:
    0
    Trophy Points:
    110
    #4
    Nothing in the htaccees file? mmm
    you have to check with the owner of this module. it might be meta refresh problem.
    cheers
     
    feras80, Jun 11, 2008 IP