Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 8 of 8

Thread: Google Sitemap not working on some sites

  1. #1
    Tom Cox is offline Senior Member
    Join Date
    Nov 2009
    Location
    Los Angeles, CA
    Posts
    104

    Default Google Sitemap not working on some sites

    We have submitted the googleindex.aspx to Google Webmaster tools for all 15 of our aspdnsf sites. Nine of the sites are crawled and updated regularly (some faster than others) but on the other six sites, nothing happens.

    Google doesn't give an error and the status has just been "pending" for months.

    Our SEO firm is telling us that Google doesn't reconginze the googleindex.aspx file and wants a file with an xml extension but that is obviously not accurate because nine of the sites work fine.

    Any ideas why these indexes aren't being crawled?

  2. #2
    ASPAlfred is offline Senior Member
    Join Date
    Nov 2007
    Posts
    2,244

    Default

    Can you check this thread if it's related to that one? That was the error we commonly received here with regards to Google Sitemap.

    Otherwise, we really need an error details to take a look further. There might be a log somewhere from your Google Webmaster account.

  3. #3
    Tom Cox is offline Senior Member
    Join Date
    Nov 2009
    Location
    Los Angeles, CA
    Posts
    104

    Default

    Thanks for the response.

    It's not the "namespace" issue. I noticed that and fixed it a few months ago. Also, I don't see any errors at all. The sitemaps get a green checkmark and the status is "pending" but they never get crawled.

    I'll check again for any errors or logs and I'll re-read that thread to see if there are any other hints.

  4. #4
    deanfp is offline Senior Member
    Join Date
    May 2009
    Location
    Sweden
    Posts
    556

    Default

    Hi Tom

    Do you have more than 20,000 products in the ones that are failing? If so there is a known bug with that.

  5. #5
    Tom Cox is offline Senior Member
    Join Date
    Nov 2009
    Location
    Los Angeles, CA
    Posts
    104

    Default

    Hello Dean,

    We don't have more than 20,000 products in any of the failing sites. In fact these are some of our smaller sites with less than 1,000 items. However, each item is categorized in 5 or 6 categores so we end up with thousands of urls on the sitemaps but more in the range of 5,000, not 20,000.

  6. #6
    jsimacek is offline Senior Member
    Join Date
    Dec 2008
    Location
    Phoenix, AZ
    Posts
    373

    Default

    Tom if you can't resolve the issue, we have an add-on that will generate an xml file sitemap, what Google likes: http://www.ecommercecartmods.com/p-7...torefront.aspx

    We have seen similar unexplained issues like that, so for customers having issues the above does the trick (sends images too).
    Jan Simacek - Compunix, LLC
    AspDotNetStorefront trusted Devnet Partner and Reseller since 2005

    AspDotNetStorefront Mods and Add-Ons at http://www.ecommercecartmods.com/
    - Searching, Filtering and Sorting (like cSearch, Dealer Locator, Price Ranges, Blog)
    - Reports (like Cart Abandonment and Net Sales)
    - Customer Experience (like Question/Answers)
    - Site and Data Management (like Entity Product Mapper, Bulk Updaters, Make/Model/Year filters)

  7. #7
    Tom Cox is offline Senior Member
    Join Date
    Nov 2009
    Location
    Los Angeles, CA
    Posts
    104

    Default

    Hi Jan,

    Thanks for the suggestions. That might be a good solution. I'll check out your add-ons.

    Tom

  8. #8
    Tom Cox is offline Senior Member
    Join Date
    Nov 2009
    Location
    Los Angeles, CA
    Posts
    104

    Default Resolution

    To anyone who finds this thread in the future, we resolved this issue by changing to a new web hosting vendor (in fact we moved to Vortx/AspDotNetStorefont for hosting) and this problem disappeared. It was apparently caused by memory limitations on the servers at our previous hosting service.

    Tom