ShopSite and Google Product Search

Last time, I discussed the value of having your products listed in Google Product Search.  Now I’d like to show you how easy it is for merchants that are using ShopSite Manager or Pro to submit products to Google Product Search.  If you are using ShopSite Starter, then you only have a few products, so you can quickly and easily enter your products into your Google Product Search account by hand.  But if you have many products, both ShopSite Manager and Pro make it simple to submit your products to Google.  In ShopSite, go to Merchandising > Google Services > Product Search and click the Configure button.  Let’s break it down by section. Starting at the top, you’ll see the following:

The first thing to notice is that there are two ways to submit – FTP and API.  The FTP method is used if you have many products (as in, over a couple hundred.)  It creates a file and places it on Google’s upload server that Google retrieves at their convenience, so you may not get an immediate response as to whether the feed was accepted or not.  The API method gets an immediate response from Google for each product submitted, so you can quickly know if it was successful or not.  Depending on which method you use (FTP or API), you would fill in the appropriate fields from your Google account.

The next section of the Configuration screen allows you to set up an e-mail reminder:

When you submit your products to Google, you indicate when they will expire (Monthly, Weekly, or Daily.)  Ideally, you will resubmit your products before they expire, since it may take Google a day or two before the products are validated and relisted.  The next Configuration section allows you to map Google Merchant Center Fields to the corresponding ShopSite field.

In the example settings above, ShopSite uses the Product name as the Title field that is sent to Google.  Likewise, the Regular price is sent for the Price field (we could have also used the On Sale price) and so forth.  You can also indicate the Quantity on hand, the Weight, the landing page that Google will link to, etc.  Google also wants to know the Product Type.  When you create a product in ShopSite (Products > Add a Product), you have the option to set the Product Type as illustrated below.

 

If you’ve indicated that ShopSite should include this product in the feed sent to Google, then the other fields will also be sent for the corresponding categories.

Recently, Google began requiring that two out of three unique product identifiers be sent for each product — Brand, Global Trade Item Number (GTIN), and/or Manufacturer Part Number (MPN).  A GTIN could be a Universal Product Code (UPC) or International Standard Book Number (ISBN).  In version 10 of ShopSite, merchants can add a GTIN or MPN by using an Extra Product Field (set up in Preferences > Extra Fields), as I’ve done below.

If we now go back to Google Product Search Configuration, you’ll see a section where Extra Product Fields are displayed.  Just check the appropriate box(es) to have them automatically sent when ShopSite submits the feed.

Once you have Google Product Search configured, it is easy to submit all of the products that you’ve indicated to Google with the Send Feed button.

Google Product Search

Did you know that Google Product Search is the #1 comparison shopping site?  It is free to use and may even help your search engine ranking.  Long ago, Google Product Search was originally called Froogle.  If you go to froogle.com now, you are redirected to Google Product search.  As is typical of Google, the site still says it is in beta (maybe that’s why the service is free!)

 

froogle.com redirects to the still in beta Google Product Search

 

 

You may be saying to yourself that even if it is the #1 comparison shopping site, how many shoppers are really going to type in the old froogle.com or the new www.google.com/products URL?  Well, Google did not get to be #1 by relying on shoppers going to either of those URLs.  For example, if you go to google.com and search for something, the results will also have a “Shopping” link on the left that, when clicked, takes you to the Google Product Search results.

 

Shopping link takes you to Google Product Search results

 

But Google does not stop there.  Go to google.com and type “buy ipad 2 case” and you’ll get the normal search results plus a set of results from Google Product Search!

 

Set of Google Product Search results

Apparently, the word “buy” tells Google you may be interested in results from its product search.  Clicking the “Shopping results for buy ipad 2 case” link above the images takes you straight to all the results from Google Product Search.

 

Google Product Search Results

So, one way or another Google can easily get shoppers to its product search engine.  This is why it is so important to have your products listed there.  Next time, we’ll discuss how ShopSite makes it easy to submit your products to Google Product Search.

 

When to Upgrade

Two weeks ago, Internet Explorer 9 came out I immediately upgraded my copy of IE on my home computer.  This week, Firefox 4 was released and I immediately upgraded my work and home computer.  I like to get the latest software releases, since the new versions have more features, typically run faster, and include bug fixes.  I have Internet Explorer 8 on my work computer, and you’ll note that I did not immediately upgrade to version 9.  This is because I have to use IE when I run our payroll through our provider.  It seemed prudent to check with them first and make sure I’d still be able to pay my employees after upgrading!

Generally, upgrading or downgrading a browser is not a big deal, so I don’t worry about too many risks. After all, it is pretty trivial to go back to a previous version of a browser or even use an alternate browser.  What about eCommerce?  Mission critical software is a different matter.  When or how often should you upgrade to the latest version?  I know of several ShopSite stores that are running versions of our software that are over 10 years old!  Those merchants are happy with the feature set of the older version of ShopSite and it does what they need.  Other merchants always want the latest updates and embrace the newest features, like those added for Social Networking.

You may think that the “if it ain’t broke, don’t fix it” mindset is the way to go.  But by doing so, you will miss out on new features and probably better performance.  And perhaps that is ok for you.  But what happens if it does break because of a software flaw that had been patched in an update?  Is being down for a day or several days acceptable?  Two recent situations illustrate how being on an older version may cause your store to go down or be down longer than desired as a result of the actions of 3rd parties.

At the beginning of this year, the United States Postal Service decided to change both the names that are returned and the data that is returned by their real-time quotes interface for a few of their shipping options.  Unfortunately, there was no advanced warning that these changes were coming.  ShopSite, like many other carts, had to scramble to adjust to the changes.  Obviously, patches were easiest to do on the latest version of ShopSite and were released to hosts and merchants using v10 sp2 (service pack 2) first.  Those merchants that were already running sp2 could have their host copy over a few files and quickly be back to getting the latest USPS rate quotes.  This was much quicker and easier than for the merchants that needed to upgrade from an earlier version of ShopSite before applying the patches.

A more recent example happened just last week when PayPal moved their data center for Payflow Pro users.  PayPal warned both merchants and us of the coming move and no problem was expected.  However, there was an unforeseen change in how some of the data had been formatted/transmitted.  This caused a problem with some stores that were running the original version 10 of ShopSite, but it had no effect on stores running service pack 2.  ShopSite 10 was released in 2008, service pack 1 (sp1) was released in 2009, and service pack 2 (sp2) was released in July of 2010.  There’s no software fee for the v10 users to get sp1 or sp2, so the reason for not upgrading sooner was probably either a “if it ain’t broke, don’t fix it” mindset or concern that upgrading may break something.

Fear that an upgrade could break something is a valid concern.  A software upgrade can change the way something previously worked, so it is often prudent to wait a little while before upgrading.  That being said, I would think that within 1-3 months any significant upgrade issues would have surfaced.  It is easy to ask your host how upgrades have gone or to check with other ShopSite users in the forum.

If you do not immediately need the new features that an upgrade provides, waiting a few months for any minor wrinkles to be ironed out makes sense.  However, the more successful your store is, the more important it is to stay current with the latest and greatest version. The internet is a rapidly changing animal.  ShopSite is keeping pace by continuously evolving to support the latest interfaces, features, and standards.  It’s great when you can use the same product for 10 years, but our recommendation is that you upgrade more often than once a decade!

 

ShopSite Online Shopping Cart Software BlogShopSite Online Shopping Cart Software On YouTubeShopSite Online Shopping Cart Software On TwitterShopSite Online Shopping Cart Software On FacebookQuestions?888-373-4347E-commerce Blog