Google Base account now international

Friday, May 09, 2008 at 5:11 PM

Posted by Gilbert Dietrich, German Google Base Team

Many of you have been asking for a way to easily upload and publish items for different countries to Google Base from the comfort of your account. We listened to your feedback and have created an international dashboard within your Google Base account, which lets you select different target countries for your feeds. This means that you no longer need to log in to three separate domains (.com .co.uk, and .de) to submit feeds to each country. Now you can simply log in to your usual account and have access to all your feeds, regardless of the country for which they were registered.

For example, if you select "US" as your target country from the drop-down menu instead of "All", only your US feeds will be displayed in your account. Within your Account Settings you can also choose a dashboard display language of your choice, independent of the country to which you are submitting your feeds.

Additionally, you can easily register your feeds for the various countries using one account. During the registration process, if you want to specify a location different than your default target country, you will be able to choose your desired target country for that particular feed.


Please visit our Help Center for more information on this topic. As always, we welcome any suggestions for ways we can make it even easier for you to upload and publish your items to Google Base.

Updating our attribute requirements for submitting products

Thursday, May 01, 2008 at 9:18 AM

Posted by Jessica Ng, Product Marketing Manager

If you're a Google Product Search provider, you've always known that we classify our attributes into three categories: "required," "recommended," and "optional." We've recently updated the list of attributes in each category to make it easier for providers to submit their product information and prioritize the attributes relevant to their products. Here is an updated list of attribute requirements, along with some information on what the categories mean.

Required attributes are attributes that you're, well, required to include for all your items. We won't be able to process and approve items in your feed that are missing required attributes. The following is a list of required attributes:

description
id
link
price
title

Recommended attributes are ones that we strongly recommend including for your data feeds, and we consider them as important as required attributes. However, we realize that not all providers and items have this information available; therefore, if your feed contains items without this information, we will still process them, but it will be more difficult to ensure that they appear for relevant search queries. The following is a list of recommended attributes:

brand
condition
image_link
isbn
mpn
upc

All other attributes are optional attributes. Optional attributes give you more ways to describe your items and additionally help shoppers find your products.

We hope that this update will make it easier for you to create data feeds and prioritize the time spent on them. For more information on these attributes, you can visit our feed guidelines here. Also, keep your eyes out for status messages on the data feeds dashboard that will provide additional guidance on the attributes we're recommending for your items.

To see attribute requirements for submitting item types other than Products, please visit the data feed overview in the Help Center.

Zappos.com finds the perfect fit with Google Product Search

Monday, April 28, 2008 at 11:51 AM



In Q1, we attended several industry events where merchants were interested in hearing about other merchants' experiences with our commerce solutions products, particularly Google Product Search. With that in mind, we wanted to share some feedback we recently received from Zappos.com.

Zappos offers shoes, bags, and apparel as an online retailer that stocks more than 3 million SKUs and has more than 7 million customers. Zappos started using Google Product Search to drive more traffic and sales to their site.

In a case study, Darrin Shamo, manager of Zappos' SEM/SEO initiatives, recently shared with us that "Product Search brought in an average of 380,000 visitors a month during the vital holiday shopping season of November-December 2007 -- an increase of 400% over the year before. And the conversion rate was higher than all other comparison shopping engines in our portfolio."

"Our objective here is to lower marketing costs while hitting our target return on investment (ROI) across campaigns," Shamo continued. "Google Product Search is free, and that helps us accomplish this goal. By adding Product Search to our comparison shopping engine mix, we are able to boost our aggregate ROI by 11%."

Learn more about Google Product Search.

Schedule your data feeds

Wednesday, April 23, 2008 at 9:39 AM

Posted by Dimitris Meretakis, Product Manager

To keep your items in Base current, you should send us a new data feed as often as your item information changes. The great news is that you don't have to send us your file manually anymore. Now Google Base can download your data feed from your website. Here's how to get started:

  1. Make sure your updated data feed is available on a fixed, externally accessible URL on your website.
  2. Define the schedule that Google Base should follow to retrieve the bulk upload file from that URL.

Google Base will retrieve and process your data feed according to the schedule you define. You can set daily, weekly or monthly schedules and specify the exact time your file should be retrieved. Just make sure that your bulk upload URL belongs to the website you registered in your Account Settings. Within your Account Settings you can also choose whether you want to receive email notifications when Base retrieves and processes your data feed. You can find all the details and step-by-step instructions about setting your schedule in our Help Center article.

Publishing priority for Base API items

Thursday, April 10, 2008 at 9:47 AM

Posted by Dimitris Meretakis, Product Manager

The Google Base data API is used to manage and publish all kinds of data. Some of this data is particularly time-sensitive, like news or events that will expire in a matter of hours. Other data has more value over the long term, such as recipes that are intended to be used and shared indefinitely.

To streamline the publishing process and make sure that time-sensitive items appear in the snippets feed as quickly as possible, Google Base now differentiates between high- and low-priority items. High-priority items are published immediately. Low-priority items are published to the snippets feed within a day, and are still instantly available on the items feed.

For now, the default priority is "high." On May 8, we'll set the default priority to "low" and set quotas for high-priority items to ensure fairness. We'll provide more information about quotas in an upcoming blog post, so keep your eyes peeled.

For detailed information about how the new priorities work, refer to the documentation. As always, if you have questions or comments, we'd love to hear from you.

Thanks for your participation in Google Base.

New API Features

Wednesday, January 09, 2008 at 12:53 AM

By Alex Dovlecel, Google Base API Engineering Team

If you've been wondering what the Google Base API team has been working on lately, wonder no more. We are happy to tell you that a couple of new features were released in the last couple of weeks.


Location queries
We think locations are extremely useful for building a large variety of applications. Mashups of Google Maps spring to mind. They look cool and are easy to develop. That's why we devoted some of our time to improving location queries.Now you can:
  • Query addresses: The radius (or lack thereof) in a location query will help you tune your results. If a radius is not provided, Google Base will match the items that are located in the specified area (zip code, city, state, country). If you include a radius, then Google Base will return the items located at a distance less than the radius from the center of the specified area. Sounds complicated? It's not. Let's take a couple of examples:
    [location:@"Mountain View, CA"] will match items located in the city of Mountain View, California. It doesn't matter if they are close or far from the center of the town.
    [location:@"Mountain View, CA" + 1mi] will match items located within one mile of Mountain View's geographic center.
    [location:@"Washington"] will match items located in Washington. You can do the same for countries by replacing Washington with a country name like Switzerland, or France. By providing a ZIP code in the address string, like in this query: [location:@"93430, CA"] the API will make sure to return only items that are located in the given zip code (Mountain View, California).

  • Query rectangular areas: For certain types of applications (like Google Maps mashups), querying for a rectangular lat/long boundary is important. Now you can easily do this by using the following syntax: [location: @+12.9+12.20..@+14.5+12.45].
For more information about location queries, refer to the developer's guide.


Reference attributes
We know items are not always isolated entities. Sometimes it makes sense to have one item point to another. Of course, you can build a relation between two items by using attributes of type "url", but that can be cumbersome. To address this case, we introduced a new "reference" attribute type. Now you can insert an item containing attributes that reference another Google Base item by passing the ID of the referenced item. For example the attribute
<g:my_ref_attribute type='reference'>17891817243016304554> refers to the item that can be accessed at http://www.google.com/base/feeds/snippets/17891817243016304554
You can also query for items that reference another item. The query [my ref attribute(reference): 17891817243016304554] will return all the items that have a reference attribute named "my ref attribute" which points to the item identified by http://www.google.com/base/feeds/snippets/17891817243016304554.

Make no mistake - Google Base is definitely not a relational database. You can't do join operations in queries. Google Base does not enforce referential integrity for your items. References can help you interconnect your data, so that you or anyone else who finds your data can more easily navigate from one item to the next.
For more information about reference attributes, refer to the developer's guide.


Images and thumbnails
If you want to embed images for items in Google Base in your website, we have good news for you. Images are now stored at base.googlehosted.com, and you can link to them directly. The Base API also supports a new value for the content query parameter called thumbnails. If you include the thumbnails argument, all of your g:image_link attributes will include links to the related thumbnails.

For example, querying reviews for "Golden Compass":
http://www.google.com/base/feeds/snippets/-/reviews?bq=golden+compass&content=thumbnails

... will return, among the others, the item:
http://www.google.com/base/feeds/snippets/11204632290451546619

...which contains links to thumbnails:
<g:image_link type='url'>http://i.walmart.com/i/p/09/78/06/79/87/0978067987924_100X100.jpg
<gm:thumbnail width='60' height='60'>
http://base.googlehosted.com/base_media?q=http%3A%2F%2Fi.walmart.com%2Fi%2Fp%2F09%2F78%2F06%2F79%2F87%2F0978067987924_100X100.jpg&dhm=ffffffff80c81128&size=5
</gm:thumbnail>
<gm:thumbnail width='90' height='90'>
http://base.googlehosted.com/base_media?q=http%3A%2F%2Fi.walmart.com%2Fi%2Fp%2F09%2F78%2F06%2F79%2F87%2F0978067987924_100X100.jpg&dhm=ffffffff80c81128&size=2
</gm:thumbnail>
<gm:thumbnail width='120' height='120'>
http://base.googlehosted.com/base_media?q=http%3A%2F%2Fi.walmart.com%2Fi%2Fp%2F09%2F78%2F06%2F79%2F87%2F0978067987924_100X100.jpg&dhm=ffffffff80c81128&size=3
</gm:thumbnail>
<gm:thumbnail width='220' height='220'>
http://base.googlehosted.com/base_media?q=http%3A%2F%2Fi.walmart.com%2Fi%2Fp%2F09%2F78%2F06%2F79%2F87%2F0978067987924_100X100.jpg&dhm=ffffffff80c81128&size=4
</gm:thumbnail>
</g:image_link>

For more information about using images in your application, refer to the developer's guide.

We hope these new features will spark some ideas for applications to build on top of Google Base. The more you use the API, the more we'll give back. Stay tuned to find out about more new features coming soon.

Feed status notifications

Wednesday, December 12, 2007 at 11:41 AM

By: Dimitris Meretakis, Product Manager

You may not be aware of the steps your uploaded data goes through on Google Base. Here's a snapshot. First, you upload your file; next, Google processes your feed; and third, after processing is complete, users will be able to see your data in their search results.

And starting today, you
have the option of receiving a notification email after we've completed the processing (the second step), which will summarize the results. To turn this on, go to Settings. You can choose whether you want to be notified in one of three instances: always, only if there's an error, or never. Learn more about status notifications.