AbleCommerce Shopping Cart Software

The second day after using Google’s webmaster tools, when I returned to check on the site map, I see this warning in the site map area.

“
URLs not followed
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.
â€

Hi

Are you using secure https or http?
I think the AC feed makes it an https - not sure why - maybe someone else can comment as to why AC does this?

But we changed ours all to http before we loaded them up and that worked with a successful upload. However, as others have said, Google still seems slow to index - even with the site map feed.

Also, you might check a few in your browser to see it they actually go to the right page without a redirect.

Don

All of my sitemap.xml URLs are HTTP, none are https

Hi Joe,

When you did the site map feed off the dashboard to your local computer, did they come over as https or http? Ours all came from AC as https and we had to manually change them to http. I read in another thread that others experienced the same problem ... I am just wondering if we are doing something wrong.

How long after a successful upload to Google before your Google Organic Index ( Cache ) is updated. We did ours WED and still no update.

Don

Mine have always come out as http:, I never had the problem with HTTPS links showing my sitemap.xml file. Since Day 1.

When I did my first few Google Base uploads, it would take 2-3 days and then I'd get an email saying the Feed was processed and x number of ok items with x number of rejected items.

Now when I do it (about once a week), I don't get any emails. I just log into the account and check the status and the last-update date. If the last-update date matches near the date I uploaded, then I consider it good.

I'm certain Google Base is working for me, I'm getting orders from it every day. I can tell because the referrer is Google.com/Products instead of just google.com with some item keywords.

Plus I'm using the AC7 Affiliate feature to track orders results from specific product feeds. It's not completely accurate, but it's better than just guessing one-by-one using the Referrer URL.

I initially had an entirely different site map issue, which helped me to overlook the https issue.

I have a case open with Able to discuss further, and probably will not be able to follow up further until Monday afternoon.

However, currently when I generate a sitemap file from admin, it does generate the XML with Https in all links.

This causes a redirect to the products.aspx page, rather than to the actual product page.

The site does have a SSL cert installed and I did check that in the admin area.

Until I get a reply and in reference to the good reference post
Dev Site to Live site:
viewtopic.php?t=6574

I recommend everyone look at the sitemap xml directly, prior to posting it to Google.

Again I will follow up with more detail, as soon as I can fully understand the other issue I had and provide a complete answer.

Hey guys, do me a quick favor...

Open your ac_StoreSettings table and tell me what each of you have as values for the following keys:

Store_StoreURL
SSLEnabled
SSLEncryptedUri

I have to add that I think only Think that this behavior is caused by my replication method from Dev to Live, and some file mapping Data in my database.

http://demo.ablecommerce.com/ac7/ ( part of the case I have open)

True

Blank

and some file mapping Data in my database.

What sort of file mapping are you doing?

Ok I do not want to confuse anyone, or upset able, but as this is extremmly important i will share my experence. Please give me a few minutes to construct it.

while your waiting go take a look at CommonSiteMap_SiteMapDataPath in the ac_Storesetting table.

Ok I do not want to confuse anyone, or upset Able, but as this is extremely important I will share my experience. Please remember that I currently have an Open case and an ongoing discussing with able regarding this. In which I have informed them of this post.

My First issue was, after generating my site map file for the first time, It was generated with my development IP in the links rather than the Live site URL. My Store URL was and is correct in the admin side. This prompted me to open a case with able.

While it appears that the above did not in fact take place. What it appears to have happened is that the CommonSiteMap_SiteMapDataPath in the ac_Storesetting table did not get updated after I Transferred My Dev database to my live site in conjunction with me not Excluding the transfer of the Sitemap File from the Dev site to the live site.

So the CommonSiteMap_SiteMapDataPath Equaled My dev site folder. Once I realized that and viewed the file the Links where correct except that they get generated with the Https.

My current work around for this is:

In the ac_Storesetting table I CommonSiteMap_SiteMapDataPath to Equal a folder outside my web root.

I then manually do a find and replace on “httpsâ€

Hello,

It sure seems like this is all due to your migration from development to production with the exception of the SSL issue rather than any flaws in AbleCommerce, unless I'm misreading something.

Hi Mike,

What about the demo store for AC in the table? Should we change this?
http://demo.ablecommerce.com/ac7/

**********************************************************
From Peter :

“Also while looking through the database I found this in the ac_StoreSettings table:

Store_StoreUrl http://demo.ablecommerce.com/ac7/ should I change this?â€

Mike

I agree that most of this is certainty due to the Dev site to Live site migration.
: Except for

1 The Https issue
2 The Store_StoreUrl http://demo.ablecommerce.com/ac7/ issue

So far I have added to the Migration script to exclude the additional following things:
\Admin\Marketing\Feeds directory

And Sitemap.xml in the root as well as any .sitemap files I’ve created.

Had I originally excluded the .xml the first part of the error, linking the Dev IP instead of the live site name would not have happened.