root/google/base.google.com/base/guidelines.html

[ ](http://base.google.com/base)
  ** Google Base - Editorial Guidelines **
  


[ Google Base Home  ](http://base.google.com/base)

[ About Google Base ](http://base.google.com/base/help/about.html)

[ Help Center ](http://base.google.com/support/?hl=en_US)

[ Program Policies ](http://base.google.com/base/help/base_policies.html)

[ Bulk Upload Instructions ](http://base.google.com/base/help/overview.html)

[ Contact Us ](http://base.google.com/support/bin/request.py?hl=en_US)

  


** A few words about Attribute Search **

Google users search Google Base data in a way that is fundamentally different from how they search the web: they use attributes. Attributes allow searchers to precisely refine their search in a way that web search does not. For example, searchers can specify the exact color, price range, size, brand, or any other attribute of what they are searching for. Attributes are a very powerful tool for search refinement: they allow searchers to quickly narrow in on exactly the set of items they're interested in. 

Because they're such a powerful tool, users search Google Base data almost exclusively with attributes; keywords are much less important. That means that in order to be found, your items must have the attributes a user will want to use to refine his search. (For instance, users searching for digital cameras may want to view cameras with a certain range of megapixels, so providers wanting users to find their digital camera listings should include the megapixel attribute.) Without these attributes, users won't find your item, because Google Base won't know whether your item has the attribute or not. 

Since users search Google Base data with attributes, a Google Base item with no attributes will be as hard for users to find as a page on the web with no title or description. 

In these editorial guidelines, you'll find our suggestions for creating easily discoverable items for Google Base. 

** The Basics **

The most effective item communicates a clear message to a targeted audience. Once you determine whom you want to reach, you need to develop appropriate text and attributes for an item to convey your information to users. Below you'll find some tips to help you create effective items and meet your goals. 

Underlying all the Editorial Guidelines are three simple principles: 

  * Be honest and factual. 
  * Describe your message clearly and accurately. 
  * Include relevant and complete information about your items with attributes. 

Our Editorial Guidelines can assist you with reaching your goals in the following areas: 

  * [ Item Content ](guidelines.html#content) - The information you submit to Google Base, via single item posting, bulk upload, or through the Google Base API. 
  * [ Site Structure and Design ](guidelines.html#structure) - The destination for users who select your items in the search results. 

** Item Content **

  * ** Use Standard Spelling and Grammar. **

    * Avoid repeated and unnecessary use of punctuation, capitalization or symbols. 

      * Don't use exclamation points in your item titles. 
      * The use of symbols, numbers, letters should adhere to the true meaning of the symbol. 

    * Avoid gimmicky repetition. 
    * Use unique call to action phrases specific to your items for your item titles 
    * Avoid offensive or inappropriate language. 

_ Creating useful titles will help make your items more appealing for users and optimize your impressions. _   
  
** Bad: **   
title: Google Hat!!!!! L@@K!!   
title: APPLE IPOD I-POD I POD 80GB   
  
** Good: **   
title: Google Infant Rib Hat   
title: Apple iPod 80GB 
    
    
              <?xml version="1.0"?> <rss version="2.0">
    <channel xmlns:g="http://base.google.com/ns/1.0">
    <title> Google Products</title>
    <link>http://www.googlestore.com/</link>
    <description>Information about Google clothes.</description>
    <item>
    <title>Classic Infant Rib Hat</title>
    <link> http://www.googlestore.com/product.asp?catid=3&code=GO0137&orig=P </link>
    <description> Protect a little head with this fashion-forward ribbed washable
    cotton baby cap. White with silkscreened four-color Google logo.
    One size. </description>
    <g:image_link>http://www.googlestore.com/images/products/GO0137E.jpg</g:image_link>
    <g:expiration_date>2006-11-15<g:expiration_date>
    <g:price>5.50</g:price>
    <g:currency>USD </g:currency>
    <g:condition>new</g:condition>
    <g:color>white</g:color>
    <g:brand>Google</g:brand>
    <g:apparel_type>baby hat</g:apparel_type>
    </item>
    </channel>
    </rss>
             

  * ** Provide detailed attribute information. **

    * Use our predefined attributes and item types when possible, rather than creating custom attributes and item types. 
    * Follow industry standards for items similar to yours when deciding which attributes to include. Be sure to include any information you think a user might use to refine a search for your product. 

      * For a list of recommended predefined attributes, choose from one of our [ Standard Item Types ](http://base.google.com/base/help/types.html)
      * Use custom attributes to include information specific to your items. For example, in a posting for a book you're selling, you might include the custom attribute "c:pages:integer" with the value "346" in your bulk upload along with other relevant predefined attributes such as "isbn," "format" and "author."  Learn more about creating custom attributes [ here ](http://base.google.com/base/custom-attributes.html) . 

    * Adhere to best practices for attribute formatting. 

      * The information included in your bulk upload should match the information available on your website. For example, your bulk upload should include the complete description of your item displayed on your website. The more relevant information you include for your items, the better we'll be able to match your items to users' queries. 
      * Use short and clear attribute values. For example, instead of including "eggplant with mustard pinstripes" in the "color" attribute for your blazer, use a standard color such as "purple." 
      * Avoid including punctuation in your attribute values. For example, instead of including "Pets > Dogs > Dog food" in the "product_type" attribute, you could include "Dog food." 
      * For more information regarding a specific attribute, please refer to our list of [ Predefined Attributes ](http://base.google.com/base/help/attributes.html) . 

    * Avoid the use of promotional or boilerplate text in your item descriptions. 

_ Including relevant attributes and properly formatted attribute values allows users to find your items. _   
  
** Bad: **   
color: eggplant with mustard pinstripes   
c:writer:string: Malcolm Gladwell   
  
** Good: **   
color: purple   
author: Malcolm Gladwell 

  * ** Adhere to Program Policies **

    * As a business, Google must make decisions about where we draw the line in regards to the items that we accept. We therefore may not accept items containing some content or relating to certain products or services. We reserve the right to exercise editorial discretion when it comes to the items that we accept on our site, as noted in our terms and conditions. Please note that the decisions we make concerning items in no way affect the search results that we deliver. To learn more, please review our [ Program Policies ](http://base.google.com/base/help/base_policies.html) . 

** Site Structure and Design **

  * ** Adhere to best practices to increase your items' impressions, clicks and conversions. **

    * Use individual pages for each of your item destination links, rather than listing several items on the same page. 
    * Display price information on static product pages. 
    * Have a professional and cleanly designed site with functional links and easy to follow content. 
    * Include images of your items when possible. 

For additional technical and content optimization tips for the creation of your website, please see our [ webmaster guidelines ](http://www.google.com/support/webmasters/bin/answer.py?answer=35769) . 

  


(c)2006 Google - [ Google Home ](http://www.google.com/) - [ Google Base Home ](http://base.google.com/base) - [ Terms of Service ](http://base.google.com/base/help/tos.html) - [ Privacy Policy ](http://www.google.com/privacy.html)   
[ Program Policies ](http://base.google.com/base/help/base_policies.html) - [ Google Base Blog ](http://googlebase.blogspot.com/)