<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Long Island Web Design &#124; Unreal Web Marketing</title>
	<atom:link href="http://www.unrealstudio.com/feed" rel="self" type="application/rss+xml" />
	<link>http://www.unrealstudio.com</link>
	<description></description>
	<lastBuildDate>Wed, 16 May 2012 21:22:33 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Creating Web Pages &#8211; Online Course</title>
		<link>http://www.unrealstudio.com/seo/creating-web-pages-online</link>
		<comments>http://www.unrealstudio.com/seo/creating-web-pages-online#comments</comments>
		<pubDate>Wed, 09 May 2012 19:58:58 +0000</pubDate>
		<dc:creator>unrealweb777</dc:creator>
				<category><![CDATA[Online Training Courses]]></category>
		<category><![CDATA[and CSS]]></category>
		<category><![CDATA[Creating Web Pages]]></category>
		<category><![CDATA[Dreamweaver and Expression]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[HTML5]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false">http://www.unrealstudio.com/?p=830</guid>
		<description><![CDATA[Create and post your very own Web site on the Internet using HTML in this extensive, hands-on, six week workshop. First, you&#8217;ll learn about the capabilities of the World Wide Web and the fundamentals of web design. Then, with your instructor&#8217;s patient guidance, you&#8217;ll plan the content, [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft" title="web-page-online-course" src="http://www.ed2go.com/common/images/0/3971.jpg" alt="" width="450" height="150" /></p>
<p>Create and post your very own Web site on the Internet using HTML in this extensive, hands-on, six week workshop. First, you&#8217;ll learn about the capabilities of the World Wide Web and the fundamentals of web design. Then, with your instructor&#8217;s patient guidance, you&#8217;ll plan the content, structure and layout of your Web site, create pages full of neatly formatted text, build links between the pages and to the outside world, and add color, backgrounds, graphics, and tables. You&#8217;ll also learn critical and timely information on securing the best possible location in search engine listings, and powerful no-cost or low-cost web marketing strategies.</p>
<p><a href="https://www.ed2go.com/cgbooks/Enrollment/Enroll.aspx?ProductId=7" target="_blank">ENROLL NOW</a></p>
<p>&nbsp;</p>
<p>A new section of each course starts monthly. If enrolling in a series of two or more courses, please be sure to space the start date for each course at least two months apart.</p>
<p>All courses run for six weeks, with a two-week grace period at the end. Two lessons are released each week for the six-week duration of the course. You do not have to be present when lessons are released. You will have access to all lessons until the course ends. However, the interactive discussion area that accompanies each lesson will automatically close two weeks after the lesson is released. As such, we strongly recommend that you complete each lesson within two weeks of its release.</p>
<p>The final exam will be released on the same day as the last lesson. Once the final exam has been released, you will have two weeks to complete all of your course work, including the final exam.</p>
<p id="ctl00_cphMain_ucProductDetails1_pSyllabusIntro3">Week One</p>
<section>
<h5>Wednesday &#8211; Lesson 01</h5>
<p>In this lesson, you&#8217;ll get started by learning where the Web is and how it works. We&#8217;ll cover some important concepts and terminology, and hopefully clear up some buzzwords you may have heard but not quite understood. Then we&#8217;ll go hands-on and get started creating your first website.</p>
<h5>Friday &#8211; Lesson 02</h5>
</section>
<p> Today, you&#8217;ll create your first Web page. You&#8217;ll learn how to add tags and content to your page, view your page in a browser, reopen it in an editor to make additions and changes, save those changes, and then view the updated page in a Web browser. These skills will apply to every Web page you ever create, and they&#8217;ll get you started on creating any page you can imagine.</p>
<section>
<h4>Week  Two</h4>
<h5>Wednesday &#8211; Lesson 03</h5>
</section>
<p> In today&#8217;s lesson, you&#8217;ll learn to beef up your pages with the design elements that you see in most websites. We&#8217;ll discuss how to add headings, paragraphs, numbered lists, and bulleted lists to your pages, and we&#8217;ll also talk about the secrets to adding special characters like &amp;copy; and &amp;trade. Finally, you&#8217;ll discover how to add links to other peoples&#8217; pages and to other pages within your own site.<br />
<strong>Friday &#8211; Lesson 04</strong></p>
<p>Here&#8217;s your chance to add some visual excitement to your website! Today, we&#8217;re going to learn the basics about adding pictures to your Web pages. You&#8217;ll discover how to download pictures right off the Web, and you&#8217;ll also learn how to prepare and use your own pictures from a digital camera.</p>
<section>
<h4>Week  Three</h4>
<h5>Wednesday &#8211; Lesson 05</h5>
</section>
<p> Tables are a terrific way to neatly organize content into rows and columns. You&#8217;ve no doubt seen tables used in other websites and countless other forms of publication. In today&#8217;s lesson, you&#8217;ll learn how to use HTML to create tables in your own Web pages!</p>
<p><strong> Friday &#8211; Lesson 06</strong></p>
<p>If you&#8217;ve been involved in Web development at all during the last 20 years, you may have heard about HTML, XHTML, HTML5, and CSS. If you&#8217;re new to all of this, it&#8217;s a confusing mess of alphabet soup. In this lesson, you&#8217;ll learn the who, how, what, when, where, and why of these technologies—and what you should use now so your website is in sync with current specs and future trends.</p>
<section>
<h4>Week  Four</h4>
<h5>Wednesday &#8211; Lesson 07</h5>
</section>
<p> Virtually all modern websites use CSS style rules for all their website styling. In today&#8217;s lesson, you&#8217;ll learn what a style rule is, and you&#8217;ll get some hands-on practice creating your own styles rules. You&#8217;ll learn how to center and align pictures and text, and you&#8217;ll discover the secrets to jazzing up your site with colors (and how to choose from the millions of color options available to you).</p>
<p><strong>Friday &#8211; Lesson 08</strong></p>
<p>Today&#8217;s lesson will introduce you to more advanced HTML and CSS topics, including how to create a page layout with a navigation bar. You&#8217;ll learn how to create a page layout using div tags to put named page divisions in a Web page, and we&#8217;ll discuss how to style your page divisions by adding an internal style sheet and some style rules.</p>
<section>
<h4>Week  Five</h4>
<h5>Wednesday &#8211; Lesson 09</h5>
</section>
<p> Most websites consist of multiple pages with some common content on each page. Today&#8217;s lesson will teach you to use a layout page as template so you can build multipage websites more quickly. We&#8217;ll cover liquid versus fixed layouts, how design a layout, and how to easily build additional pages from your layout page. This will help you to develop more professional-looking pages using the same modern coding techniques that seasoned professionals use!<br />
<strong>Friday &#8211; Lesson 10</strong></p>
<p>Getting a site on the Internet is one thing. Getting people to notice it is quite another. In today&#8217;s lesson, you&#8217;ll learn about Internet directory services, search engines, Web-crawling infobots (not as creepy as they sound), and things you can do to make your own site stand out in the crowd!</p>
<section>
<h4>Week  Six</h4>
<h5>Wednesday &#8211; Lesson 11</h5>
</section>
<p> In today&#8217;s lesson, you&#8217;ll learn how to publish your website for the whole world to see—well, at least anyone on the Internet. And best of all, you&#8217;ll learn how to keep your site on the Internet, for free, forever!<br />
<strong>Friday &#8211; Lesson 12</strong></p>
<p>In today&#8217;s lesson, you&#8217;ll learn about authoring systems like Dreamweaver and Expression Web, and how they can make Web development quicker and easier. You&#8217;ll also learn a couple of ways to get an online presence without creating your own website!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.unrealstudio.com/seo/creating-web-pages-online/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google over optimization penalties &#8211; Matt Cutts Video</title>
		<link>http://www.unrealstudio.com/seo/google-optimization-penalties-matt-cutts-video</link>
		<comments>http://www.unrealstudio.com/seo/google-optimization-penalties-matt-cutts-video#comments</comments>
		<pubDate>Fri, 16 Mar 2012 18:13:02 +0000</pubDate>
		<dc:creator>newyorkseo</dc:creator>
				<category><![CDATA[Search Engine Optmization Tips]]></category>
		<category><![CDATA[Google over optimization penalties]]></category>
		<category><![CDATA[google search results]]></category>
		<category><![CDATA[matt cutts]]></category>
		<category><![CDATA[over optimization]]></category>

		<guid isPermaLink="false">http://www.unrealstudio.com/?p=740</guid>
		<description><![CDATA[Matt Cutts said the new over optimization penalty will be introduced into the search results in the upcoming month or next few weeks.  The purpose is to “level the playing field,” Cutts said.  To give sites that have great content a better shot at ranking above sites [...]]]></description>
			<content:encoded><![CDATA[<p>Matt Cutts said the new over optimization penalty will be introduced into the search results in the upcoming month or next few weeks.  The purpose is to “level the playing field,” Cutts said.  To give sites that have great content a better shot at ranking above sites that have content that is not as great but do a better job with SEO.<br />
</p>
<p>
	<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="100%" height="300px" id="ava3-2729147" title="">
  <param name="movie" value="http://www.unrealstudio.com/wp-content/plugins/ava-video-gallery/ava_video.swf" />
  <param name="quality" value="high" />
  <param name="wmode" value="transparent" />
  	<param name="flashvars" value="title=Too Much SEO
Links or Content, Which is better?
Organic Link Building Tips
Building Large Sitemaps&controls=&color1=000000&color2=ffffff&round=20&autoplay=0&skin=1&youtube=&overplay=0&rows=4&round=20&video0=Bz0KQNPDUoc&title0=Too Much SEO&tipo0=2&image0=&video1=qXgni6U6qk8&title1=Links or Content, Which is better?&tipo1=2&image1=&video2=MkLFlaWxgJA&title2=Organic Link Building Tips&tipo2=2&image2=&video3=OshuVtzh14I&title3=Building Large Sitemaps&tipo3=2&image3=&cantidad=4" />
	   <param name="allowFullScreen" value="true" />
  <param name="swfversion" value="9.0.45.0" />
  <!-- This param tag prompts users with Flash Player 6.0 r65 and higher to download the latest version of Flash Player. Delete it if you dont want users to see the prompt. -->
  <param name="expressinstall" value="http://www.unrealstudio.com/wp-content/plugins/ava-video-gallery/Scripts/expressInstall.swf" />
  <!-- Next object tag is for non-IE browsers. So hide it from IE using IECC. -->
  <!--[if !IE]>-->
  <object type="application/x-shockwave-flash" data="http://www.unrealstudio.com/wp-content/plugins/ava-video-gallery/ava_video.swf" width="100%" height="300px">
    <!--<![endif]-->
    <param name="quality" value="high" />
    <param name="wmode" value="transparent" />
    	<param name="flashvars" value="title=Too Much SEO
Links or Content, Which is better?
Organic Link Building Tips
Building Large Sitemaps&controls=&color1=000000&color2=ffffff&round=20&autoplay=0&skin=1&youtube=&overplay=0&rows=4&round=20&video0=Bz0KQNPDUoc&title0=Too Much SEO&tipo0=2&image0=&video1=qXgni6U6qk8&title1=Links or Content, Which is better?&tipo1=2&image1=&video2=MkLFlaWxgJA&title2=Organic Link Building Tips&tipo2=2&image2=&video3=OshuVtzh14I&title3=Building Large Sitemaps&tipo3=2&image3=&cantidad=4" />
		   <param name="allowFullScreen" value="true" />
    <param name="swfversion" value="9.0.45.0" />
    <param name="expressinstall" value="http://www.unrealstudio.com/wp-content/plugins/ava-video-gallery/Scripts/expressInstall.swf" />
    <!-- The browser displays the following alternative content for users with Flash Player 6.0 and older. -->
    <div>
      <h4>Content on this page requires a newer version of Adobe Flash Player.</h4>
      <p><a href="http://www.adobe.com/go/getflashplayer"><img src="http://www.adobe.com/images/shared/download_buttons/get_flash_player.gif" alt="Get Adobe Flash player" width="112" height="33" /></a></p>
    </div>
    <!--[if !IE]>-->
  </object>
  <!--<![endif]-->
</object>
<script type="text/javascript">
<!--
swfobject.registerObject("ava3-2729147");
//-->
</script><br/></p>
]]></content:encoded>
			<wfw:commentRss>http://www.unrealstudio.com/seo/google-optimization-penalties-matt-cutts-video/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google’s New Privacy Policy</title>
		<link>http://www.unrealstudio.com/seo/googles-privacy-policy</link>
		<comments>http://www.unrealstudio.com/seo/googles-privacy-policy#comments</comments>
		<pubDate>Fri, 17 Feb 2012 16:22:45 +0000</pubDate>
		<dc:creator>newyorkseo</dc:creator>
				<category><![CDATA[Search Engine Optmization Tips]]></category>
		<category><![CDATA[Website Marketing Articles]]></category>
		<category><![CDATA[Alma Whitten Google]]></category>
		<category><![CDATA[Google’s New Privacy Policy]]></category>
		<category><![CDATA[personalized results]]></category>

		<guid isPermaLink="false">http://www.unrealstudio.com/?p=724</guid>
		<description><![CDATA[In January, Google announced that it was overhauling its more than 60 privacy policies and replacing them with one. As Alma Whitten, Google’s Director of Privacy in Product and Engineering, wrote in the announcement, the idea is to create a “beautifully simple, intuitive user experience across Google.” [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.unrealstudio.com/seo/googles-privacy-policy/danny-sullivan" rel="attachment wp-att-725"><img class="alignleft size-full wp-image-725" title="danny-sullivan" src="http://www.unrealstudio.com/wp-content/uploads/2012/02/danny-sullivan.jpg" alt="" width="175" height="175" /></a>In January, Google announced that it was overhauling its more than 60 privacy policies and replacing them with one. As Alma Whitten, Google’s Director of Privacy in Product and Engineering, wrote in the <a href="http://googleblog.blogspot.com/2012/01/updating-our-privacy-policies-and-terms.html">announcement</a>, the idea is to create a “beautifully simple, intuitive user experience across Google.”</p>
<p>The search giant said the main change for users would be that it could combine information from one service with its other services, thus providing a more fluid user experience. For example, if you conduct several searches on Google on a particular item, Google could assume that you want a video on that item if you then visit YouTube. <strong> What do you think of Google’s new privacy policy? Does it affect you at all? <a href="http://www.webpronews.com/googles-new-privacy-policy-danny-sullivan-provides-insight-2012-02#comments">We’d love to hear your thoughts.</a></strong></p>
<p>According to <a href="http://searchengineland.com/author/danny-sullivan">Danny Sullivan</a>, the Executive Editor of <a href="http://searchengineland.com/">Search Engine Land</a>, the new policy will provide users with more personalized results. He told us that it really wasn’t surprising that Google made the change since most other tech and Internet companies have one privacy policy for all their products and services.</p>
<p>“Google, which kind of has come from privacy policies on a per product basis, is kind of playing catch up, so that they have the ability to be more flexible both in what they may do with the information and how they may use the information to improve products and services,” he said.</p>
<p>This flexibility is what has some people worried, however. Under the new policy, Google could potentially take the information it gathers when users search to target them with ads. Although Google says it will not do this, the new policy gives it the right if it so chooses.</p>
<p>“Potentially, it gives Google a lot of new rights,” said Sullivan.</p>
<p><a href="http://www.webpronews.com/googles-new-privacy-policy-danny-sullivan-provides-insight-2012-02" target="_blank">READ FULL ARTICLE</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.unrealstudio.com/seo/googles-privacy-policy/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Canonical TAG, when to use it</title>
		<link>http://www.unrealstudio.com/seo/canonical-tag</link>
		<comments>http://www.unrealstudio.com/seo/canonical-tag#comments</comments>
		<pubDate>Tue, 06 Dec 2011 15:59:37 +0000</pubDate>
		<dc:creator>newyorkseo</dc:creator>
				<category><![CDATA[Search Engine Optmization Tips]]></category>
		<category><![CDATA[301 redirect canonical]]></category>
		<category><![CDATA[bing tag format]]></category>
		<category><![CDATA[canonical http headers]]></category>
		<category><![CDATA[Canonical TAG]]></category>
		<category><![CDATA[canonical" a hint or a directive]]></category>
		<category><![CDATA[directive]]></category>
		<category><![CDATA[Is rel="canonical"]]></category>
		<category><![CDATA[link rel="canonical" href="]]></category>
		<category><![CDATA[url canonicalization]]></category>
		<category><![CDATA[website redirect]]></category>
		<category><![CDATA[Yahoo]]></category>

		<guid isPermaLink="false">http://www.unrealstudio.com/?p=605</guid>
		<description><![CDATA[What Information Have the Engines Provided About the Canonical URL Tag? &#160; Carpe diem on any duplicate content worries: we now support a format that allows you to publicly specify your preferred version of a URL. If your site has identical or vastly similar content that&#8217;s accessible [...]]]></description>
			<content:encoded><![CDATA[<p><strong><strong>What Information Have the Engines Provided About the Canonical URL Tag?</strong></strong></p>
<p>&nbsp;</p>
<p>Carpe diem on any <a href="http://googlewebmastercentral.blogspot.com/2008/09/demystifying-duplicate-content-penalty.html">duplicate<br />
content worries</a>: we now support a format that allows you to publicly specify<br />
your preferred version of a URL. If your site has identical or vastly similar<br />
content that&#8217;s accessible through multiple URLs, this format provides you with<br />
more control over the URL returned in search results. It also helps to make sure<br />
that properties such as link popularity are consolidated to your preferred<br />
version.</p>
<p>Let&#8217;s take our old example of a <a href="http://bp2.blogger.com/_o5Na_9269nA/RuleCxWoOXI/AAAAAAAAAuU/akzGuAnW5nQ/s1600-h/swedish-fish.jpg" rel="wp-prettyPhoto[605]">site<br />
selling Swedish fish</a>. Imagine that your preferred version of the URL and its<br />
content looks like this:</p>
<p>http://www.example.com/product.php?item=swedish-fish</p>
<p><a href="http://2.bp.blogspot.com/_o5Na_9269nA/SZRdbN6z2XI/AAAAAAAACGM/A3ruVwqPK1U/s1600-h/swedish-fish1.png" rel="wp-prettyPhoto[605]"><img id="BLOGGER_PHOTO_ID_5301965383496096114" src="http://2.bp.blogspot.com/_o5Na_9269nA/SZRdbN6z2XI/AAAAAAAACGM/A3ruVwqPK1U/s320/swedish-fish1.png" alt="" border="0" /></a></p>
<p>However, users (and Googlebot) can access<br />
Swedish fish through multiple (not as simple) URLs. Even if the key information<br />
on these URLs is the same as your preferred version, they may show slight<br />
content variations due to things like sort parameters or category navigation:</p>
<p>http://www.example.com/product.php?item=swedish-fish&#038;category=gummy-candy</p>
<div><a href="http://2.bp.blogspot.com/_o5Na_9269nA/SZR00RdWxII/AAAAAAAACGk/FyvDI6WBAq0/s1600-h/gummy-candy-swedish-fish-6.png" rel="wp-prettyPhoto[605]"><img id="BLOGGER_PHOTO_ID_5301991102710465666" src="http://2.bp.blogspot.com/_o5Na_9269nA/SZR00RdWxII/AAAAAAAACGk/FyvDI6WBAq0/s400/gummy-candy-swedish-fish-6.png" alt="" border="0" /></a></div>
<p>Or they have completely identical content,<br />
but with different URLs due to things such as a tracking parameters or a session<br />
ID:</p>
<p>http://www.example.com/product.php?item=swedish-fish&#038;trackingid=1234&#038;sessionid=5678</p>
<div><a href="http://2.bp.blogspot.com/_o5Na_9269nA/SZRdbN6z2XI/AAAAAAAACGM/A3ruVwqPK1U/s1600-h/swedish-fish1.png" rel="wp-prettyPhoto[605]"><img id="BLOGGER_PHOTO_ID_5301965383496096114" src="http://2.bp.blogspot.com/_o5Na_9269nA/SZRdbN6z2XI/AAAAAAAACGM/A3ruVwqPK1U/s320/swedish-fish1.png" alt="" border="0" /></a></div>
<p>Now, you can simply add this <strong>&lt;link&gt;</strong> tag to specify<br />
your preferred version:</p>
<p><strong>&lt;link<br />
rel=&#8221;canonical&#8221; href=&#8221;http://www.example.com/product.php?item=swedish-fish&#8221;<br />
/&gt;</strong></p>
<p>inside the <strong>&lt;head&gt;</strong> section of the<br />
duplicate content URLs:</p>
<p>http://www.example.com/product.php?item=swedish-fish&#038;category=gummy-candy</p>
<p>http://www.example.com/product.php?item=swedish-fish&#038;trackingid=1234&#038;sessionid=5678</p>
<p>and<br />
Google will understand that the duplicates all refer to the canonical URL: http://www.example.com/product.php?item=swedish-fish.<br />
Additional URL properties, like PageRank and related signals, are transferred as<br />
well.</p>
<p>This standard can be adopted by any search engine when crawling and<br />
indexing your site.</p>
<p>Of course you may have more questions. <a href="http://research.google.com/pubs/author3778.html">Joachim Kupke</a>, an<br />
engineer from our Indexing Team, is here to provide us with the answers:</p>
<p><strong>Is rel=&#8221;canonical&#8221; a hint or a directive? </strong><br />
It&#8217;s a hint that we honor strongly. We&#8217;ll take your preference into account, in conjunction with other signals, when calculating the most relevant page to display in search results.</p>
<p><strong>Can I use a relative path to specify the canonical, such as &lt;link rel=&#8221;canonical&#8221; href=&#8221;product.php?item=swedish-fish&#8221; /&gt;?</strong><br />
Yes, relative paths are recognized as expected with the <strong>&lt;link&gt;</strong> tag. Also, if you include a <strong>&lt;base&gt;</strong> link in your document, relative paths will resolve according to the base URL.</p>
<p><strong>Is it okay if the canonical is not an exact duplicate of the content?</strong><br />
We allow slight differences, e.g., in the sort order of a table of products. We also recognize that we may crawl the canonical and the duplicate pages at different points in time, so we may occasionally see different versions of your content. All of that is okay with us.</p>
<p><strong>What if the rel=&#8221;canonical&#8221; returns a 404?</strong><br />
We&#8217;ll continue to index your content and use a heuristic to find a canonical, but we recommend that you specify existent URLs as canonicals.</p>
<p><strong>What if the rel=&#8221;canonical&#8221; hasn&#8217;t yet been indexed?</strong><br />
Like all public content on the web, we strive to discover and crawl a designated canonical URL quickly. As soon as we index it, we&#8217;ll immediately reconsider the rel=&#8221;canonical&#8221; hint.</p>
<p><strong>Can rel=&#8221;canonical&#8221; be a redirect?</strong><br />
Yes, you can specify a URL that redirects as a canonical URL. Google will then process the redirect as usual and try to index it.</p>
<p><strong>What if I have contradictory rel=&#8221;canonical&#8221; designations?</strong><br />
Our algorithm is lenient: We can follow canonical chains, but we strongly recommend that you update links to point to a single canonical page to ensure optimal canonicalization results.</p>
<p>from <a href="http://ysearchblog.com/2009/02/12/fighting-duplication-adding-more-arrows-to-your-quiver/">Yahoo!</a>:</p>
<blockquote dir="ltr"><p>• The URL paths in the &lt;link&gt; tag can be absolute or relative, though we recommend using absolute paths to avoid any chance of errors.</p>
<p>• A &lt;link&gt; tag can only point to a canonical URL form within the same domain and not across domains. For example, a tag on http://test.example.com can point to a URL on http://www.example.com but not on http://yahoo.com or any other domain.</p>
<p>• The &lt;link&gt; tag will be treated similarly to a 301 redirect, in terms of transferring link references and other effects to the canonical form of the page.</p>
<p>• We will use the tag information as provided, but we’ll also use algorithmic mechanisms to avoid situations where we think the tag was not used as intended. For example, if the canonical form is non-existent, returns an error or a 404, or if the content on the source and target was substantially distinct and unique, the canonical link may be considered erroneous and deferred.</p>
<p>• The tag is transitive. That is, if URL A marks B as canonical, and B marks C as canonical, we’ll treat C as canonical for both A and B, though we will break infinite chains and other issues.</p></blockquote>
<p>and from <a href="http://blogs.msdn.com/webmaster/archive/2009/02/12/partnering-to-help-solve-duplicate-content-issues.aspx">Live/MSN</a>:</p>
<blockquote dir="ltr">
<ul>
<li>This tag will be interpreted as a hint by Live Search, not as a command. We&#8217;ll evaluate this in the context of all the other information we know about the website and try and make the best determination of the canonical URL. This will help us handle any potential implementation errors or abuse of this tag.</li>
<li>You can use relative or absolute URLs in the “href” attribute of the link tag.</li>
<li>The page and the URL in the “href” attribute must be on the same domain. For example, if the page is found on “http://mysite.com/default.aspx”, and the ”href” attribute in the link tag points to “http://mysite2.com”, the tag will be invalid and ignored.
<ul>
<li>However, the “href” attribute can point to a different subdomain. For example, if the page is found on “http://mysite.com/default.aspx” and the “href” attribute in the link tag points to “http://www.mysite.com”, the tag will be considered valid.</li>
</ul>
</li>
<li>Live Search expects to implement support for this feature sometime in the near future.</li>
</ul>
</blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.unrealstudio.com/seo/canonical-tag/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Invests in Privacy for Profit</title>
		<link>http://www.unrealstudio.com/seo/google-invests-privacy-profit</link>
		<comments>http://www.unrealstudio.com/seo/google-invests-privacy-profit#comments</comments>
		<pubDate>Thu, 20 Oct 2011 18:43:32 +0000</pubDate>
		<dc:creator>newyorkseo</dc:creator>
				<category><![CDATA[Search Engine Optmization Tips]]></category>
		<category><![CDATA[google analytics changes]]></category>
		<category><![CDATA[Google Encrypted Search Means No Info For Individual Queries]]></category>
		<category><![CDATA[Google Invests in Privacy for Profit]]></category>
		<category><![CDATA[google not tracking organic referrals]]></category>

		<guid isPermaLink="false">http://www.unrealstudio.com/?p=596</guid>
		<description><![CDATA[Guess what? Google just pissed on the SEO community and tried to call it rain. Again! - Since Google’s announcement yesterday that they would now be encrypting search result URLs by default for all users, the community has been out for blood. The change is going to [...]]]></description>
			<content:encoded><![CDATA[<p>Guess what? Google just pissed on the SEO community and tried to call it rain.</p>
<p>Again! -</p>
<p>Since Google’s <a href="http://googlesystem.blogspot.com/2011/10/google-encryped-search-for-logged-in.html">announcement</a> yesterday that they would now be encrypting search result URLs by default for all users, the community has been out for blood. The change is going to fix known privacy issues, so why is this a bad thing?</p>
<blockquote><p>“<strong>How will this change impact Google Analytics users?</strong><br />
When a signed in user visits your site from an organic Google search, all web analytics services, including Google Analytics, will continue to recognize the visit as Google “organic” search, but will no longer report the query terms that the user searched on to reach your site. Keep in mind that the change will affect only a minority of your traffic. You will continue to see aggregate query data with no change, including visits from users who aren’t signed in and visits from Google “cpc”.’</p></blockquote>
<p>As of this morning, here’s what we see in Outspoken Media’s Organic Search Traffic report for the last 24 hours:</p>
<p><img title="Google Not Provided Referral Data" src="http://outspokenmedia.com/wp-content/uploads/2011/10/google-not-provided-referral-data.png" alt="Google Not Provided Referral Data" width="443" height="191" /></p>
<p>According to Google’s Matt Cutts, the change is only supposed to affect referral data in the <a href="http://searchengineland.com/google-to-begin-encrypting-searches-outbound-clicks-by-default-97435">single digit percents</a> — only users who are signed into Google and searching.</p>
<p>That’s a pretty big assumption on Google’s part about my client’s users and referral sources. Remember, they’re AVERAGING based on the entirety of the Internet. In the case of Outspoken Media, yes, this “(not provided)” data does account for a small percent of traffic for that 24-hour period of time. To be exact, it accounts for 1.2% of our visits for that timeframe. But what about clients who have a stronger user base with Google accounts? We spoke with one such client yesterday and approximately 30% of their current users are signed up with Gmail accounts. That’s more than a single digit percentage and they already have a small amount of traffic!</p>
<p>&nbsp;</p>
<p>The recommendations from both studies were immediate action on the part of Google to correct these issues:</p>
<blockquote><p>“We argue that solutions should be quickly deployed to protect users against these two types of attacks. The session hijacking attack is harmful not only because it allows an attacker to collect a lot of private information, including sometimes the search history, but also because it can be exploited to add potentially compromising entries [25]. It can also be used to modify the search results displayed to the victim. In fact, Google allows to delete or promote—i.e., show as first—results using a button associated to them. An adversary hijacking a session cookie can perform searches on the victim’s behalf and influence the results corresponding to these searches as she wishes. For instance, this attack can be a powerful tool for censorship, as it can be used to remove or promote some pages displayed after a Google search.”</p></blockquote>
<p>In each document were recommendations to both users and Google on how to counteract the threat of hijacking:</p>
<p><strong>USER ACTIONS</strong></p>
<ul>
<li>Log out from any Google service when performing a search</li>
<li>Delete and disable the Web History service</li>
<li>Disable personalization from anonymous cookies or always delete Google cookies</li>
<li>Sign out from Google accounts when connecting from a shared network or to use a vpn to encrypt the traffic and prevent cookie interception.</li>
</ul>
<p>&nbsp;</p>
<p><a href="http://outspokenmedia.com/seo/google-invests-in-privacy-for-profit/?utm_source=bronto&amp;utm_medium=email&amp;utm_term=Google+Invests+in+Privacy+for+Profit&amp;utm_content=Moz+Top+10+-+October+2011%2C+Issue+1&amp;utm_campaign=Moz+Top+10+-+October+%231">READ FULL ARTICLE HERE</a> By Rhea Drysdale is the Chief Executive Officer of Outspoken Media.</p>
<p>&nbsp;</p>
<p>This is what Google is saying:</p>
<p>&nbsp;</p>
<h1><a href="http://analytics.blogspot.com/2011/10/making-search-more-secure-accessing.html">Making<br />
search more secure: Accessing search query data in Google Analytics</a></h1>
<p>Tuesday, October 18, 2011 | 11:17 AM</p>
<p>Labels: <a href="http://analytics.blogspot.com/search/label/Announcements" rel="tag">Announcements</a>, <a href="http://analytics.blogspot.com/search/label/googlenew" rel="tag">googlenew</a></p>
<div>
<p>As search becomes an increasingly customized experience, particularly for<br />
signed in users, we believe that protecting these personalized search results is<br />
important. As part of that effort, today the Google Search team announced that<br />
SSL Search on <a href="https://www.google.com/">https://www.google.com</a> will<br />
become the default experience for signed in users on Google.com (see the <a href="http://googleblog.blogspot.com/2011/10/making-search-more-secure.html">Official<br />
Google Blog</a> post to learn more). Protecting user privacy is important to us,<br />
and we want to take this opportunity to explain what the Google Analytics team<br />
is doing to help you continue measuring your website effectively in light of<br />
these changes.</p>
<p><strong>How will this change impact Google Analytics<br />
users?</strong><br />
When a signed in user visits your site from an organic Google<br />
search, all web analytics services, including Google Analytics, will continue to<br />
recognize the visit as Google “organic” search, but will no longer report the<br />
query terms that the user searched on to reach your site. Keep in mind that the<br />
change will affect only a minority of your traffic. You will continue to see<br />
aggregate query data with no change, including visits from users who aren’t<br />
signed in and visits from Google “cpc”.</p>
<p><strong>What is Google Analytics<br />
doing about it?</strong><br />
We are still measuring all SEO traffic. You will still be<br />
able to see your conversion rates, segmentations, and more.</p>
<p>To help you<br />
better identify the signed in user organic search visits, we created the token<br />
“(not provided)” within Organic Search Traffic Keyword reporting. You will<br />
continue to see referrals without any change; only the queries for signed in<br />
user visits will be affected. Note that “cpc” paid search data is not<br />
affected.</p>
<p>Our team continues to explore ways that we can surface relevant<br />
information, like search query data, to help you measure the effectiveness of<br />
your website and marketing efforts, and as always, we welcome any <a href="mailto:analytics-feedback@google.com">feedback or comments</a> that you<br />
have. Thank you for continuing to help us improve Google<br />
Analytics.</p>
<p>Posted by Amy Chang, Google<br />
Analytics team</p>
<p>&nbsp;</p>
<p>Google announced that it is going to begin encrypting search queries with SSL (Secure Sockets Layer) as the default experience at Google.com when you search logged into your Google account. http://www.google.com will become https://www.google.com.</p>
<p>“This is especially important when you’re using an unsecured Internet connection, such as a WiFi hotspot in an Internet cafe,” <a href="http://googleblog.blogspot.com/2011/10/making-search-more-secure.html">says</a> Google product manager Evelyn Kao.</p>
<p>There’s a chance that your Google experience will be slower with SSL because the computer your’e using has to establish a secure connection with Google. This is interesting, considering that Google has put so much effort into speeding things up.</p>
<p>It’s worth noting that you can just go to https://www.google.com when you’re signed out, and still use encrypted search.</p>
<p>Naturally, webmasters and SEOs are contemplating the effects this will have on search engine optimization and analytics.</p>
<p>Sites visited from Google’s organic listings will be able to tell that the traffic is coming from Google, but they won’t be able to receive info about each individual query. They will, however, receive an aggregated list of the top 1,000 search queries that drove traffic to the site for each of the past 30 days in Webmaster Tools.</p>
<p>“This information helps webmasters keep more accurate statistics about their user traffic,” says Kao. “If you choose to click on an ad appearing on our search results page, your browser will continue to send the relevant query over the network to enable advertisers to measure the effectiveness of their campaigns and to improve the ads and offers they present to you.”</p>
<p>“When a signed in user visits your site from an organic Google search, all web analytics services, including Google Analytics, will continue to recognize the visit as Google ‘organic’ search, but will no longer report the query terms that the user searched on to reach your site,” says Amy Chang <a href="http://analytics.blogspot.com/2011/10/making-search-more-secure-accessing.html">on the Google Analytics blog</a>. “Keep in mind that the change will affect only a minority of your traffic. You will continue to see aggregate query data with no change, including visits from users who aren’t signed in and visits from Google ‘cpc’.”</p>
<p>“We are still measuring all SEO traffic. You will still be able to see your conversion rates, segmentations, and more,” she adds. “To help you better identify the signed in user organic search visits, we created the token ‘not provided)’ within Organic Search Traffic Keyword reporting. You will continue to see referrals without any change; only the queries for signed in user visits will be affected. Note that ‘cpc’ paid search data is not affected.”</p>
<p>Google is making the encrypted search available on all of its search properties except for Maps.</p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.unrealstudio.com/seo/google-invests-privacy-profit/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Base Products Feed Specification</title>
		<link>http://www.unrealstudio.com/seo/google-base-products-feed-specification</link>
		<comments>http://www.unrealstudio.com/seo/google-base-products-feed-specification#comments</comments>
		<pubDate>Thu, 20 Oct 2011 14:11:25 +0000</pubDate>
		<dc:creator>newyorkseo</dc:creator>
				<category><![CDATA[Ecommerce Tips]]></category>
		<category><![CDATA[Search Engine Optmization Tips]]></category>
		<category><![CDATA[froogle feed format]]></category>
		<category><![CDATA[google base feed attributes]]></category>
		<category><![CDATA[google base feed format]]></category>
		<category><![CDATA[Google Base Products Feed Specification]]></category>

		<guid isPermaLink="false">http://www.unrealstudio.com/?p=587</guid>
		<description><![CDATA[Below is a list of the attributes you need to provide to Google Base for your items to be listed in the Google Product Search (Froogle). Some of these attirbutes are required and some are not. Please read them carefully so that you don&#8217;t have any issues. [...]]]></description>
			<content:encoded><![CDATA[<p>Below is a list of the attributes you need to provide to Google Base for your items to be listed in the Google Product Search (Froogle).</p>
<p>Some of these attirbutes are required and some are not. Please read them carefully so that you don&#8217;t have any issues. If you dont provide the required data, your feed wont go live.</p>
<p>Before creating your feed, choose the <a href="answer.py?answer=160567">file format</a> that is right for you.</p>
<p>The document is divided into several sections.<br />
Each section describes the relevant attributes, and <a href="answer.py?answer=1344057">requirements for each<br />
attribute</a>:</p>
<ol>
<li><strong>Basic Product Information: </strong>Attributes to describe the basic<br />
information about your products, such as title, description and type of<br />
product.</li>
<li><strong>Availability &amp; Price: </strong>Attributes to specify the<br />
availability and prices of your listings.</li>
<li><strong>Unique Product Identifiers: </strong>Attributes to ensure your<br />
products appear on the right product page, such as brands, UPCs, and EANs.</li>
<li><strong>Apparel Products: </strong>Attributes to describe apparel products,<br />
such as color or gender.</li>
<li><strong>Product Variants: </strong>Attributes to correctly describe<br />
variations of a product that only differ by color, material, pattern, or<br />
size.</li>
<li><strong>Tax &amp; Shipping: </strong>How to include information to supply<br />
tax and cost of shipping information for your products.</li>
<li><strong>Nearby Stores (US &amp; UK only): </strong>How to include<br />
information to show your physical stores in addition to your online store</li>
<li><strong>Loyalty Points (Japan only): </strong>Attributes to specify the<br />
loyalty points Google Shopping users gain when buying the item.</li>
<li><strong>Multiple Installments (Brazil only): </strong>Attributes to specify<br />
multiple payment programs to buy items.</li>
<li><strong>Additional Attributes</strong>: Other attributes to describe your<br />
products.</li>
</ol>
<p>We use the term <strong>item</strong> to describe a single<br />
product listing. If you are using Text or Tab delimited format, an item is<br />
equivalent to one line in your data feed. Items are similar to products, but we<br />
assume that products can occur in multiple variations. These variations -<br />
<em>product variants</em> &#8211; differ by color, material, pattern, or size. We use<br />
<strong>item</strong> to refer to a <strong>single variation of a<br />
product.</strong></p>
<p>&nbsp;</p>
<p><a><strong>Important Note:</strong></a></p>
<div>
<div>
<div>
<ul>
<li>If you are using a <a href="answer.py?answer=160567">delimited format</a>, you can use the attribute names in either<br />
English or the language of your target country. Make sure that the attribute<br />
names (e.g., &#8216;condition&#8217;) and values (e.g., &#8216;new&#8217;) are always in the same<br />
language.</li>
<li>If you are using XML or API, you <strong>must</strong> use English attribute<br />
names shown within the brackets.</li>
<li>If you are using XML or API, you must use an underscore in place for a space<br />
within an attribute name (e.g., &#8220;image_link&#8221; instead of &#8220;image link&#8221;.) A space<br />
within an attribute value is allowed (e.g., &#8220;in stock&#8221;).</li>
</ul>
<h2>1. Basic Product Information</h2>
<p>The following attributes contain basic information about your<br />
items.</p>
<p>&nbsp;</p>
<p><a name="id"></a>id [id]- An identifier of the item</p>
<div>
<div>
<p>The identifier for each item has to be unique within your account, and cannot<br />
be re-used between feeds. If you have multiple feeds, ids of items within<br />
different feeds must still be unique. You can use any sequence of letters and<br />
digits for the item id.</p>
<p><strong>When to include:</strong> Required for all items.</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Alphanumeric characters</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>tddy123uk</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:id&gt;tddy123uk&lt;/g:id&gt;</code></td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>Once an item is submitted, the id must not change when you update your data<br />
feed or be used for a different product at a later point in time.</li>
<li>For Switzerland only: If your website is in multiple languages, submit one<br />
feed per language. You may re-use the same id for the same item in each version<br />
of the feed for each language.</li>
</ul>
</div>
</div>
<p>&nbsp;</p>
<p><a name="title"></a>title [title] &#8211; Title of the item</p>
<div>
<div>
<p>This is the name of your item which is required. We recommend you include<br />
characteristics such as color or brand in the title which differentiates the<br />
item from other products.</p>
<p><strong>When to include:</strong> Required for all items.</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Text. Should not be longer than 70 characters</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>Mens Pique Polo Shirt</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;title&gt;Mens Pique Polo<br />
Shirt&lt;/title&gt;</code></td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p><strong>Important:</strong></p>
<ul>
<ul>
<li>Follow our <a href="answer.py?answer=188483">Editorial guidelines</a> closely. For example, <strong>do not</strong> include any promotional text such as &#8220;Free<br />
shipping&#8221;, and do not use BLOCK CAPITALS.</li>
<li>For variant products, you are required to include the common title of the<br />
variant items. For example if “Mens Pique Polo Shirt” is available in red and<br />
blue colors, you can have one of the following titles:</li>
</ul>
</ul>
<p>Mens Pique Polo Shirt (Can be used for both variants)</p>
<p>Mens Pique Polo Shirt &#8211; Red (For the red shirt)</p>
<p>Mens Pique Polo Shirt &#8211; Blue (For the blue shirt)</p>
</div>
</div>
<p>&nbsp;</p>
<p><a name="description"></a>description [description] &#8211; Description of<br />
the item</p>
<div>
<div>
<p>Include only information relevant to the item, but be comprehensive since we<br />
use this text to find your item. We recommend you submit around 500 to 1000<br />
characters, but you can submit up to 10000 characters.</p>
<p><strong>When to include:</strong> Required for all items.</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Text</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>This teddy bear is fuzzy and cuddly. The bear is yellow with with white paws<br />
and stuffed with high quality hypoallergenic synthetic cotton.</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;description&gt;This teddy bear is fuzzy and cuddly. The bear is<br />
yellow with with white paws and stuffed with high quality hypoallergenic<br />
synthetic cotton.&lt;/description&gt;</code></td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>Make sure to follow our <a href="answer.py?answer=188483">Editorial guidelines</a> closely. For example, do not include any<br />
promotional text such as &#8220;Free shipping&#8221;, do not use BLOCK CAPITALS, and do not<br />
include a description of your store.</li>
</ul>
</div>
</div>
<p>&nbsp;</p>
<p><a name="google_product_category"></a>google product category<br />
[google_product_category] &#8211; Google&#8217;s category of the item</p>
<div>
<div>
<p>This attribute indicates the category of the product being<br />
submitted. It is only applicable to a small subset of categories, unlike the <a href="answer.py?answer=160081">Product Type Attribute</a> which is<br />
applicable to all categories. For this reason, the &#8216;Google product category&#8217;<br />
attribute should not replace the &#8216;product type&#8217; attribute. Note: This attribute<br />
accepts only one value. If your items fall into multiple categories, include<br />
only one category which is the most relevant. You can include multiple<br />
categories in the &#8216;product type&#8217; attribute .</p>
<p>Any category from Google’s taxonomy must include the full path. For example,<br />
&#8216;Apparel &amp; Accessories &gt; Clothing &gt; Jeans&#8217; is an acceptable value, but<br />
&#8216;Jeans&#8217; is not. This attribute only accepts values that are predefined by<br />
Google’s taxonomy.</p>
<p><strong>When to include:</strong> Required for all items that belong to the<br />
&#8216;Apparel and Accessories&#8217;, &#8216;Media&#8217;, and &#8216;Software&#8217; categories, and are in feeds<br />
which target the US, UK, Germany, France, or Japan.</p>
<p>If your products do not fall into one of the categories listed below, or if<br />
your feed doesn&#8217;t target one of the required countries, this attribute is<br />
recommended but not required. If you choose not to provide a Google Product<br />
Category value for other product categories, leave the attribute blank.</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Predefined values from Google&#8217;s product taxonomy</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>Apparel &amp; Accessories &gt; Clothing &gt; Dresses</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:google_product_category&gt;Apparel &amp;amp; Accessories<br />
&amp;gt; Clothing &amp;gt;<br />
Dresses&lt;/g:google_product_category&gt;</code></td>
</tr>
</tbody>
</table>
<p><strong>Apparel &amp; Accessories</strong></p>
<ul>
<li>&#8216;Apparel &amp; Accessories &gt; Clothing&#8217;</li>
<li>&#8216;Apparel &amp; Accessories &gt; Shoes&#8217;</li>
<li>&#8216;Apparel &amp; Accessories&#8217;</li>
</ul>
<p><strong>Important:</strong> Products that fall<br />
into clothing or shoes categories must use the categories listed above (&#8216;Apparel<br />
&amp; Accessories &gt; Clothing&#8217; or &#8216;Apparel &amp; Accessories &gt; Shoes&#8217;) or<br />
the more specific categories provided in the <a href="answer.py?answer=160081">full Google product taxonomy</a>. It is not sufficient to provide<br />
the general category &#8216;Apparel &amp; Accessories&#8217; for these items. Items that do<br />
not belong in the clothing or shoes categories should include the &#8216;Apparel &amp;<br />
Accessories&#8217; value or the more specific categories provided in the Google<br />
product taxonomy.</p>
<p><strong>Media</strong></p>
<ul>
<li>&#8216;Media &gt; Books&#8217;</li>
<li>&#8216;Media &gt; DVDs &amp; Movies&#8217;</li>
<li>&#8216;Media &gt; Music&#8217;</li>
</ul>
<p><strong>Important:</strong> Provide the most appropriate categorization for<br />
bundled products of differing product types. For example, a book bundled with a<br />
DVD could be labeled with either &#8216;Media &gt; Books&#8217; or &#8216;Media &gt; DVDs &amp;<br />
Movies&#8217;.</p>
<p><strong>Software</strong></p>
<ul>
<li>Software &gt; Video Game Software</li>
</ul>
<p><strong>Important:</strong> The category &#8216;Software &gt; Video Game Software&#8217;<br />
includes computer games.</p>
</div>
</div>
<p>&nbsp;</p>
<p><a name="product_type"></a>product type [product_type] &#8211; Your<br />
category of the item</p>
<div>
<div>
<p>This attribute also indicates the category of the product being sold, but is<br />
applicable to all categories. Unlike the &#8216;Google product category&#8217;, You can<br />
include more than one &#8216;product type&#8217; attribute value if products apply to more<br />
than one category. Please include the full category string. For example, if your<br />
products belong in <strong>Refrigerators</strong> list the full string: Home<br />
&amp; Garden &gt; Kitchen &amp; Dining &gt; Kitchen Appliances &gt;<br />
Refrigerators. Any separator such as &gt; or / may be used.</p>
<p>You can include multiple values of this attribute if you have multiple<br />
categories assigned to products.</p>
<p><strong>When to include:</strong> Strongly recommended for all items if you<br />
have a categorization for your items.</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Text. You may include multiple product types if it&#8217;s appropriate for your<br />
item. Separate by a comma for tab-delimited; Include multiple<br />
&lt;product_type&gt; attributes for XML.</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>Home &amp; Garden &gt; Kitchen &amp; Dining &gt; Appliances &gt;<br />
Refrigerators</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:product_type&gt;Home &amp;amp; Garden &amp;gt; Kitchen &amp;amp;<br />
Dining &amp;gt; Appliances &amp;gt;<br />
Refrigerators&lt;/g:product_type&gt;</code></td>
</tr>
</tbody>
</table>
</div>
</div>
<p>&nbsp;</p>
<p><a name="link"></a>link [link] &#8211; URL directly linking to your item&#8217;s page on<br />
your website</p>
<div>
<div>
<p>The user is sent to this URL when your item is clicked on Product Search. We<br />
also refer to this as the <strong>landing page</strong>. It must point to a page<br />
showing the exact item the user was looking at. You can use tracking URLs to<br />
distinguish users coming from Product Search.</p>
<p><strong>When to include:</strong> Required for all items.</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>URL (this must include the http:// portion)</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td><a href="http://www.example.com/asp/sp.asp?cat=12&amp;id=1030">http://www.example.com/asp/sp.asp?cat=12&amp;id=1030</a></td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;link&gt;<a href="http://www.example.com/asp/sp.asp?cat=12&amp;id=1030">http://www.example.com/asp/sp.asp?cat=12&amp;amp;id=1030</a>&lt;/link&gt;</code></td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>Read our <a href="answer.py?answer=188484">policies</a> carefully. All your URLs must link directly to<br />
webpages about your products without pop ups. We don&#8217;t allow landing pages<br />
requiring sign ups, passwords, or direct links to files/email addresses.</li>
<li>If you&#8217;re performing maintenance on your site that affects your landing<br />
pages, you&#8217;re required to remove your items from Product Search during that<br />
time.</li>
<li>If multiple products are on the same page, it has to be straightforward for<br />
the user to find the right product. We recommend only one product per page.</li>
<li>For variations of the same product, we recommend you submit URLs that<br />
pre-select the variant which the user clicked on in Google Product Search.</li>
<li>The URL must not redirect or forward to a location external to your<br />
site.</li>
<li>The URL must start with &#8216;http://&#8217; or &#8216;https://&#8217; and use the domain name you<br />
verified in Google Webmaster Tools and in the Settings of your Merchant Center<br />
account.</li>
<li>Any symbols used must be replaced by URL encoded entities (e.g. comma =<br />
%2C).</li>
</ul>
</div>
</div>
<p>&nbsp;</p>
<p><a name="image_link"></a>image link [image_link] &#8211; URL of an image<br />
of the item</p>
<div>
<div>
<p>This is the URL of an associated image for a product. Submit full-size images<br />
for your products and do not submit thumbnail versions of the images. For all<br />
apparel products, we require images of at least 250 x 250 pixels and recommend<br />
images of at least 400 x 400 pixels.</p>
<p>If you have multiple images of the item, submit the main view using this<br />
attribute, and include all other views in the &#8216;additional image link&#8217;<br />
attribute.</p>
<p><strong>When to include:</strong> Required for all items (For feeds targeting<br />
Japan, this is a recommended attribute, not a required attribute).</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>URL. (Must start with &#8216;http://&#8217; or &#8216;https://&#8217;.)</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>http://www.example.com/image1.jpg</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:image_link&gt;http://www.example.com/image1.jpg&lt;/g:image_link&gt;</code></td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>If you have no image for your item, you cannot submit the item.</li>
<li><strong>For feeds targeting the US and products that fall under “Apparel<br />
&amp; Accessories” and all corresponding sub-categories:</strong> If you are<br />
submitting product variants that differ in ‘‘color’, or ‘pattern’, or<br />
‘material’, we require you to submit specific images corresponding to each of<br />
these variants. If you do not have the correct image for the variation of the<br />
product, you may not submit that variant. We recommend specific images for<br />
‘size’ variants too. However, if these are not available you may submit the same<br />
image URL for items that differ in ‘size’.</li>
<li><strong>For all other countries and categories:</strong> If you cannot<br />
provide the appropriate images to submit your items as variants, you may list<br />
your variant products as a single item with multiple values for the variant<br />
attributes and provide the available image.</li>
<li>Do not submit a placeholder such as &#8220;No image&#8221;, logo of the brand or logo of<br />
your store. Images of products must not contain logos or other promotions within<br />
the image.</li>
</ul>
<p><strong>Formatting</strong></p>
<ul>
<li>The accepted image formats are GIF, JPG (or JPEG), PNG, BMP, and TIF and the<br />
file extensions for these images should correspond to their format.</li>
<li>Any symbols used within the image URL must be replaced by URL encoded<br />
entities (e.g. comma = %2C).</li>
</ul>
</div>
</div>
<p>&nbsp;</p>
<p><a name="additional_image_link"></a>additional image link<br />
[additional_image_link] &#8211; Additional URLs of images of the item</p>
<div>
<div>
<p>If you have additional images for this item, include them in this attribute.<br />
For example, if you have images that show the product from a different angle<br />
than the main image, or if you have images of the packaging or the product in<br />
various settings.</p>
<p>You can include up to 10 additional images per item by including the<br />
attribute multiple times. For tab-delimited, separate each URL by a comma. For<br />
XML, include each URL as a separate &lt;additional_image_link&gt; attribute.</p>
<p><strong>When to include:</strong> For all items with multiple images.</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>URL (Must include the http:// portion.)</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>http://www.example.com/image1.jpg</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:additional_image_link&gt;http://www.example.com/image1.jpg&lt;/g:additional_image_link&gt;</code></td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>The same rules as for image link apply.</li>
</ul>
</div>
</div>
<p>&nbsp;</p>
<p><a name="condition"></a>condition [condition] &#8211; Condition or<br />
state of the item</p>
<div>
<p>There are only three accepted values:</p>
<ul>
<li>&#8216;new&#8217;: The product is brand-new and has never been used. It&#8217;s in its<br />
original packaging which has not been opened.</li>
<li>&#8216;refurbished&#8217;: The product has been restored to working order. This<br />
includes, for example, remanufactured printer cartridges.</li>
<li>&#8216;used&#8217;: If the two previous values don&#8217;t apply. For example, if the product<br />
has been used before or the original packaging has been opened or is<br />
missing.</li>
</ul>
<p><strong>When to include:</strong> Required for all items.</p>
<div>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Three predefined values accepted:</p>
<ul>
<li>&#8216;new&#8217;</li>
<li>&#8216;used&#8217;</li>
<li>&#8216;refurbished&#8217;</li>
</ul>
</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>used</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:condition&gt;used&lt;/g:condition&gt;</code></td>
</tr>
</tbody>
</table>
</div>
<p><strong>Important:</strong></p>
<ul>
<li>If you are submitting with English attribute names, the three accepted<br />
values are &#8216;new&#8217;, &#8216;used&#8217; and &#8216;refurbished&#8217;. Please remember that if you submit<br />
an attribute name in English, you must also submit the attribute value in<br />
English.</li>
</ul>
<h2>2. Availability &amp; Price</h2>
<p>The attributes in this section are required<br />
in order to specify the availability and prices of your items. The availability<br />
and prices of your items can change quite frequently, and you need to make sure<br />
Google is notified of these changes as they happen. You can find advice on<br />
providing the most up-to-date or fresh data <a href="answer.py?answer=188489">here</a>.</p>
<p>We regularly check these attributes, and if<br />
the values provided in these attributes are found to be different from the<br />
information presented on your website, we will remove all your items from<br />
Product Search. Please see our <a href="answer.py?answer=188484">policies</a> for more details.</p>
<p>&nbsp;</p>
<p><a name="availability"></a>availability [availability] -<br />
Availability status of the item</p>
<div>
<div>
<p>The availability attribute only has four accepted values:</p>
<ul>
<li>&#8216;in stock&#8217;: Include this value if you are certain that it will ship (or be<br />
in-transit to the customer) in 3 business days or less. For example, if you have<br />
the item available in your warehouse.</li>
<li>&#8216;available for order&#8217;: Include this value if it will take 4 or more business<br />
days to ship it to the customer. For example, if you don’t have it in your<br />
warehouse at the moment, but are sure that it will arrive in the next few days.<br />
For unreleased products, use the value &#8216;preorder&#8217;</li>
<li>&#8216;out of stock&#8217;: You’re currently not accepting orders for this product.</li>
<li>&#8216;preorder&#8217;: You are taking orders for this product, but it’s not yet been<br />
released.</li>
</ul>
<p><strong>When to include:</strong> Required for all items in feeds targeting<br />
the US, Japan, UK, Germany, France. Recommended for all other countries.<br />
However, you need to use this attribute with one of the following if you want to<br />
submit items that are out of stock in your data feed. If you don&#8217;t use this<br />
attribute, all the items in your data feed must be in stock on your site.</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Four predefined values accepted:</p>
<ul>
<li>&#8216;in stock&#8217;</li>
<li>&#8216;available for order&#8217;</li>
<li>&#8216;out of stock&#8217;</li>
<li>&#8216;preorder&#8217;</li>
</ul>
</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>in stock</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:availability&gt;in<br />
stock&lt;/g:availability&gt;</code></td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>You need to clearly indicate the availability of an item on the item&#8217;s<br />
landing page by either explicitly noting the status (such that it&#8217;s clear which<br />
of the above values describe the availability of the item), or mention how many<br />
days it takes until the item ships. (Note: It is acceptable to include<br />
&#8216;available for order&#8217; in your feed and note &#8220;out of stock&#8221; on your<br />
website.)</li>
<li>Items that are no longer sold have to be removed from the feed<br />
entirely.</li>
</ul>
</div>
</div>
<p>&nbsp;</p>
<p><a name="price"></a>price [price] &#8211; Price of the item</p>
<div>
<div>
<p>The price of the item has to be the most prominent price on the landing page.<br />
If multiple items are on the same page with multiple prices, it has to be<br />
straightforward for the user to find the correct item and corresponding<br />
price.</p>
<p><strong>When to include:</strong> Required for all items.</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Number</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>15.00 USD</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:price&gt;15.00<br />
USD&lt;/g:price&gt;</code></td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>For the US, don&#8217;t include tax in the price. For all other countries, value<br />
added tax (VAT) has to be included in the price.</li>
<li>The price must include a currency according to <a href="http://www.iso.org/iso/support/faqs/faqs_widely_used_standards/widely_used_standards_other/currency_codes/currency_codes_list-1.htm">ISO 4217 Standard</a>.</li>
<li>Make sure to read our <a href="answer.py?answer=188484">policies</a> in detail. Only items with fixed prices are allowed<br />
in Product Search. Items with variable prices, such as auctions, and prices that<br />
require a membership in a club are not allowed.</li>
<li>For items sold in bulk quantities, the price for the lowest purchasable<br />
number of items must be provided (not the per unit price) and the same price has<br />
to be the most prominent on the landing page.</li>
<li>For products on sale, we recommend including the &#8216;sale price&#8217; attribute and<br />
submit the regular price (before sale) in the &#8216;price&#8217; attribute. In this case,<br />
the sale price (instead of the regular price) must be the most prominent price<br />
on the page.</li>
</ul>
</div>
</div>
<p>&nbsp;</p>
<p><a name="sale_price"></a>sale price [sale_price] &#8211; Advertised sale<br />
price of the item</p>
<div>
<div>
<p>Use this attribute to submit the advertised sale price of<br />
the item. Learn more about <a href="answer.py?answer=1196048">submitting sale price information</a>.</p>
<p><strong>When to include:</strong> Recommended for items on sale. If your item<br />
is on sale and you don’t include this attribute, the sale price must be updated<br />
as the value in the &#8216;price&#8217; attribute.</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Format</td>
<td>Number</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>15.00 USD</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:sale_price&gt;15.00<br />
USD&lt;/g:sale_price&gt;</code></td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>You must still include the &#8216;price&#8217; attribute in your feed, which must<br />
reflect the non-sale price you have previously sold the item for.</li>
<li>The price must include a currency.</li>
<li>Submitted sale prices must exactly match the price displayed on your<br />
website. Both prices must be displayed on the landing page (the regular price<br />
and the sale price), but the sale price must be most<br />
prominent.</li>
</ul>
</div>
</div>
<p>&nbsp;</p>
<p><a name="sale_price_effective_date"></a>sale price<br />
effective date [sale_price_effective_date] &#8211; Date range during which the item is<br />
on sale</p>
<div>
<div>
<p>Used in conjunction with sale price. This attribute<br />
indicates the date range during which the sale price applies. Learn more about<br />
<a href="answer.py?answer=1196048">submitting sale price<br />
information</a>.</p>
<p><strong>When to include:</strong> Recommended for items which use the &#8216;sale<br />
price&#8217; attribute.</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Format</td>
<td>ISO8601, with start and end dates separated by a forward slash (/)</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>2011-03-01T13:00:00Z/2011-03-11T15:30:00Z</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:sale_price_effective_date&gt;2011-03-01T13:00:00Z/2011-03-11T15:30:00Z&lt;/g:sale_price_effective_date&gt;</code></td>
</tr>
</tbody>
</table>
</div>
</div>
<h2>3. Unique Product Identifiers</h2>
<p>Unique product identifiers such as <strong>UPC</strong>,<br />
<strong>EAN</strong>, <strong>JAN</strong> or <strong>ISBN</strong> allow us to<br />
show your listing on the appropriate product page. If you don&#8217;t provide the<br />
required unique product identifiers, your store may not appear on product pages,<br />
and all your items may be removed from Product Search.</p>
<p>We require unique product identifiers for all products -<br />
except for custom made goods. For apparel, you must submit the &#8216;brand&#8217;<br />
attribute. For media (such as books, movies, music and video games), you must<br />
submit the &#8216;gtin&#8217; attribute. In all cases, we recommend you submit all three<br />
attributes.</p>
<p>You need to submit at least two attributes of<br />
&#8216;brand&#8217;, &#8216;gtin&#8217; and &#8216;mpn&#8217;, but we recommend that you submit all three if<br />
available. For media (such as books, movies, music and video games), you must<br />
submit the &#8216;gtin&#8217; attribute, but we recommend that you include &#8216;brand&#8217; and &#8216;mpn&#8217;<br />
if available. <a href="answer.py?answer=160161">Learn<br />
more.</a></p>
<p>&nbsp;</p>
<p><a name="brand"></a>brand [brand] &#8211; Brand of the item</p>
<div>
<div>
<p><strong>When to include:</strong> Required for all items &#8211; except for books,<br />
media and custom made goods, or if you&#8217;re providing &#8216;mpn&#8217; and &#8216;gtin&#8217;.</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Text</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>Acme</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:brand&gt;Acme&lt;/g:brand&gt;</code></td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>You must not provide your store name as the brand unless you manufacture the<br />
product.</li>
</ul>
</div>
</div>
<p>&nbsp;</p>
<p><a name="gtin"></a>gtin [gtin] &#8211; Global Trade Item Number (GTIN) of the<br />
item</p>
<div>
<div>
<p>In this attribute, you will include Global Trade Item Numbers (GTINs) for<br />
your products. These identifiers include UPC (in North America), EAN (in<br />
Europe), JAN (in Japan), and ISBN (for books). You can include any of these<br />
values within this attribute:</p>
<ul>
<li>UPC: 12-digit number such as 001234567891</li>
<li>EAN: 13-digit number such as 1001234567891</li>
<li>JAN: 8 or 13-digit number such as 12345678 or 1234567890123</li>
<li>ISBN: 10 or 13-digit number such as 0451524233. If you have both, only<br />
include 13-digit number.</li>
</ul>
<p><strong>When to include:</strong> Required for all items &#8211; except apparel and<br />
custom made goods, or if you&#8217;re providing &#8216;brand&#8217; and &#8216;mpn&#8217;.</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>8-, 12-, or 13-digit number (UPC, EAN, JAN, or ISBN)</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>001234567891</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:gtin&gt;12345678&lt;/g:gtin&gt;</code></td>
</tr>
</tbody>
</table>
</div>
</div>
<p>&nbsp;</p>
<p><a name="mpn"></a>mpn [mpn] &#8211; Manufacturer Part Number (MPN) of the<br />
item</p>
<div>
<div>
<p>This code uniquely identifies the product to its manufacturer. In particular,<br />
the combination of brand and MPN clearly specifies one product.</p>
<p><strong>When to include:</strong>Required for all items &#8211; except apparel,<br />
media, and custom made goods, or if you&#8217;re providing &#8216;brand&#8217; and &#8216;gtin&#8217;.</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Alphanumeric characters</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>GO12345OOGLE</td>
</tr>
<tr>
<td>XML</td>
<td>&#8216;&lt;g:mpn&gt;GO1234568OOGLE&lt;/g:mpn&gt;&#8217;</td>
</tr>
</tbody>
</table>
</div>
</div>
<h2>4. Apparel Products</h2>
<p>Apparel includes all products that fall under<br />
&#8216;Apparel &amp; Accessories&#8217; (including all sub-categories) in <a href="answer.py?answer=160081">Google’s product taxonomy</a>.</p>
<p><strong>For US merchants:</strong>: The following attributes<br />
in this section are required across all products in the &#8216;Apparel &amp;<br />
Accessories&#8217; product category (including all subcategories):</p>
<ul>
<li>gender</li>
<li>age group</li>
<li>color</li>
</ul>
<p>In addition, the ‘size’ attribute is only required for the<br />
apparel subcategories &#8216;Apparel &amp; Accessories &gt; Clothing&#8217; and &#8216;Apparel<br />
&amp; Accessories &gt; Shoes&#8217;. Recommended for other product categories (might<br />
become required in the future).</p>
<p><strong>For all other countries:</strong> While the apparel<br />
attributes listed here are not currently required for countries outside the US,<br />
they may become required in the future. Therefore, we strongly recommend that<br />
you include all the relevant attributes where possible, even for countries<br />
outside the US.</p>
<p>&nbsp;</p>
<p><a name="gender"></a>gender [gender] &#8211; Gender of the item</p>
<div>
<div>
<p>Three predefined values accepted:</p>
<ul>
<li>Male</li>
<li>Female</li>
<li>Unisex</li>
</ul>
<p><strong>When to include: </strong>Required for all apparel items in feeds<br />
that target the US. Recommended for other countries and product categories<br />
(might become required in the future).</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Format</td>
<td>There are only three values accepted:</p>
<ul>
<li>Male</li>
<li>Female</li>
<li>Unisex</li>
</ul>
</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>male</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:gender&gt;male&lt;/g:gender&gt;</code></td>
</tr>
</tbody>
</table>
<p><strong>Important</strong></p>
<ul>
<li>This attribute is required for items in the ‘apparel and accessories’<br />
category targeting the US. However, this attribute is only recommended for<br />
‘pinback buttons’, ‘tie clips’, ‘wristbands’, ‘shoe covers’, ‘shoe laces’,<br />
‘spurs’, ‘watch bands’ within the ‘apparel and accessories’<br />
category.</li>
</ul>
</div>
</div>
<p>&nbsp;</p>
<p><a name="age_group"></a>age group [age_group] &#8211; Target age group<br />
of the item</p>
<div>
<div>
<p>The only two accepted values of this attribute are:</p>
<ul>
<li>Adult</li>
<li>Kids</li>
</ul>
<p><strong>When to include: </strong>Required for all apparel items in feeds<br />
that target the US. Recommended for other countries and product categories<br />
(might become required in the future).</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Format</td>
<td>There are only two values accepted:</p>
<ul>
<li>Adult</li>
<li>Kids</li>
</ul>
</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>adult</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:age_group&gt;adult&lt;/g:age_group&gt;</code></td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>This attribute is required for items in the ‘apparel and accessories’<br />
category targeting the US. However, this attribute is only recommended for<br />
‘pinback buttons’, ‘tie clips’, ‘wristbands’, ‘shoe covers’, ‘shoe laces’,<br />
‘spurs’, ‘watch bands’ within the ‘apparel and accessories’ category.</li>
<li>If an item is <strong>not</strong> clearly just for ‘kids, it should be<br />
declared as ‘adult’, as only one value may be submitted per<br />
item.</li>
</ul>
</div>
</div>
<p>&nbsp;</p>
<p><a name="color_apparel"></a>color [color] &#8211; Color of the item</p>
<div>
<div>
<p><em>Note: This attribute is also described in the section on Variant<br />
Products. Please do not submit two versions of this attribute per item.</em></p>
<p>This defines the dominant color(s) of an item. When a single item has<br />
multiple colors:</p>
<ul>
<li>Combine them with ‘/’ in order of prominence (dominant color first, then<br />
accent colors). For example, a black shoe with green accents should have a color<br />
value of &#8216;Black / Green&#8217;. This attribute can also be used for finishes as well<br />
(e.g., &#8216;Mahogany&#8217; vs. &#8216;Stainless Steel&#8217;).</li>
<li>If you&#8217;re using XML, you must represent the &#8216;/&#8217; with &amp;#47;</li>
</ul>
<p><strong>When to include: </strong>Required for all apparel items in feeds<br />
that target the US. Recommended for other countries and product categories<br />
(might become required in the future).</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Text</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>Black</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:color&gt;Black&lt;/g:color&gt;</code></td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>This attribute is required for all items in the ‘apparel and accessories’<br />
category targeting the US.</li>
<li><strong>For apparel variants submitted to the<br />
US:</strong> Each different color or color combination must be submitted as its<br />
own item, in conjunction with the &#8216;item group id&#8217;. Visit <a href="answer.py?answer=1347943">submitting apparel products</a><br />
for more details.</li>
<li>Use consistent names of colors across variants of the same product, as well<br />
as across multiple products of the same category.</li>
<li>The values you provide may be displayed to users, so provide values that<br />
they will be able to understand.</li>
</ul>
</div>
</div>
<p>&nbsp;</p>
<p><a name="size_apparel"></a>size [size] &#8211; Size of the item</p>
<div>
<div>
<p><em>Note: This attribute is also described in the section on Variant<br />
Products. Please do not include two versions of this attribute per<br />
item.</em></p>
<p>This indicates the size of a product. You may any provide<br />
values which are appropriate to your items. Examples for sizing values can be<br />
found <a href="answer.py?answer=1347943">in this article</a>.</p>
<p><strong>When to include: </strong>Required for all apparel items in the<br />
&#8216;clothing&#8217; and &#8216;shoes&#8217; product categories in feeds that target the US.<br />
Recommended for other countries and product categories (might become required in<br />
the future).</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Text</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>XL</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:size&gt;XL&lt;/g:size&gt;</code></td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>This attribute is required for ‘clothing’ and ‘shoes’ sub-categories within<br />
the ‘apparel and accessories’ category targeting the US.</li>
<li><strong>For apparel variants submitted to the<br />
US:</strong> Each different size or size combination must be submitted as its<br />
own item, in conjunction with the &#8216;item group id&#8217;. Visit <a href="answer.py?answer=1347943">submitting apparel products</a><br />
for more details.</li>
<li>If sizes are complex, condense them into one value (e.g., “16/34 Tall” for<br />
neck size 16 inches, sleeve length 34 inches, and “Tall” fit).</li>
<li>Use consistent size values across variants of the same product, as well as<br />
across multiple products of the same category. For example, within a group of<br />
t-shirts, use “S”, “M” , and “L” as sizes, not “S”, “Medium” , and “Lrg”.</li>
<li>You may use the same ‘image’ URL value for size variants if specific images<br />
are not available but we recommend that the ‘link’ attribute leads to a page<br />
which specifies all the details about the variant item.</li>
<li>The values you provide may be displayed to users, so provide values that<br />
they will be able to understand.</li>
</ul>
<p><strong>Submitting variant apparel products</strong></p>
<p>If you have apparel products which vary by ‘size’, ‘color’, ‘pattern’, or<br />
‘material’, you must include all the required attributes outlined in this<br />
section, and also follow the approach outlined below.</p>
</div>
</div>
<h2>5. Product Variants</h2>
<p>We define variants as a group of identical products that only<br />
differ by the attributes ‘color’, ‘material’, ‘pattern’, or ‘size’.</p>
<p>Variant-level information is required only for products in the<br />
“&#8217;Apparel &amp; Accessories&#8217; category, and all related subcategories. Apparel<br />
variants are only <strong>required</strong> for feeds targeting the US. For<br />
feeds targeting other countries, the attributes are recommended and may be<br />
required in the future.</p>
<p>If you don&#8217;t include variant attributes in your feed, you<br />
shouldn&#8217;t submit several variants of the same product as separate listings (ex:<br />
the same product in different colors, sizes). These items will be considered as<br />
duplicates which is against our Program Policies. You can find more details<br />
about submitting variant data below.</p>
<p>By submitting variant products, you will help shoppers more<br />
easily find what they are looking for by either enabling them to navigate<br />
between the different product variations on a details page or helping them<br />
discover additional colors, sizes, patterns etc. for a given product.</p>
<p><strong>How to submit variant data</strong></p>
<ul>
<li>Begin by submitting an item for each variant. For example, if you offer a<br />
t-shirt in 4 colors and 5 sizes, you need to submit 20 item variants.</li>
<li>Include unique ‘id’ attribute values for each item variant, just like you<br />
would for all the other items in your feed.</li>
<li>To identify these items as variants of one another, you are required to<br />
include the ‘item group id’ attribute (required for US apparel items only) and<br />
submit identical values of this attribute for each variant in a given<br />
group.</li>
<li>Include variant attributes that indicate what makes each variant unique .<br />
You can use one or more of the following attributes: ‘color’, ‘material’,<br />
‘pattern’, or ‘size’.</li>
<li>You must only include <strong>single values</strong> for each of these<br />
variant attributes and the values of these attributes must be unique across all<br />
variants in the group. For example: If one item in a variant group includes the<br />
values “Blue” and “L” for the ‘color’ and ‘size’ attributes, all other items in<br />
the variant group must have values for ‘color’ and ‘size’, and each offer must<br />
have a different combination of values for those attributes.</li>
<li>You only need to send us data for variant attributes if your product varies<br />
by that specific attribute. So, if your shirts are all made of cotton, there’s<br />
no need to send the “Material” attribute. However, if your shirts were available<br />
in three colors and three sizes, you would send us nine separate line items,<br />
varying by color and size.</li>
<li>For apparel items, it is <strong>required</strong> that you provide a unique<br />
image of the specific variant if the item differs by ‘color’, ‘pattern’ or<br />
‘material’. For variants that differ only by ‘size’, you may submit identical<br />
images. We recommend sending separate images for variant products in other<br />
categories as well. But at this time we will not enforce this as a requirement<br />
for any category other than Apparel &amp; Accessories.</li>
<li>We also <strong>recommend</strong> you submit URL links that pre-select the<br />
variant. For example, if a user selects the red dress in size 10, they should be<br />
taken to a landing page, where the “red” and “size 10” options are already<br />
selected. If this is not possible, you may include identical link attribute<br />
values for each of the variant items within a group.</li>
</ul>
<p><strong>For US merchants submitting apparel variants:</strong></p>
<p>For apparel products that vary by &#8216;color&#8217;, &#8216;material&#8217;,<br />
&#8216;pattern&#8217;, and/or &#8216;size&#8217;, it is required to include the ‘item group id’ for each<br />
variant, where each item has a unique combination of attribute values to<br />
describe each variant.</p>
<p><strong>For all other countries and categories:</strong></p>
<p>All variant attributes in this section are<br />
<strong>recommended</strong> for apparel- and non-apparel variants, but may<br />
become required in the future. However, If you choose to include ‘item group<br />
id’, it is required that you also include at least one of the following variant<br />
attributes: ‘color’, ‘size’, ‘pattern’, ‘material’ and following the<br />
corresponding variant guidelines.</p>
<p>Please see <a href="answer.py?answer=1347943">this article </a>for more information on submitting variant<br />
apparel products.</p>
<p><strong>Important:</strong> When naming your variant<br />
products, be sure to include the title common to all variant items. Visit the<br />
‘title’ attribute for more details.</p>
<p>&nbsp;</p>
<p><a name="item_group_id"></a>item group id [item_group_id] &#8211; Shared<br />
identifier for all variants of the same product</p>
<div>
<div>
<p>All items that are color/material/pattern/size variants of the same product<br />
must have the same item group id. If you have a “Parent SKU” that is shared by<br />
all variants of a product, you can provide that as the value for &#8216;item group<br />
id&#8217;.</p>
<p><strong>When to include:</strong>Required for variant apparel products in the<br />
US. For other countries, if variant data is submitted with specific images then<br />
include the ‘item group ID’.</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Alphanumeric code</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>AB12345</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:item_group_id&gt;AB12345&lt;/g:item_group_id&gt;</code></td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>This attribute is required only for variant apparel products in the US.</li>
<li>The <strong>‘Item group id’</strong> attribute is different from the<br />
<strong>‘ID’ </strong>attribute. An ‘Item group ID’ attribute will have common<br />
values for a group of variants whereas the ‘ID’ attribute should have unique<br />
values across a group of variants and for all other items, as well.</li>
<li>The values provided for item group id must be unique between products, and<br />
only shared by items that are variants of the same product.</li>
<li>If you send us an ‘item group id’ attribute, we will automatically look for<br />
variant attributes. Conversely, if you did send us ‘Item group id’, you should<br />
ensure you send us at least one variant attribute.</li>
</ul>
</div>
</div>
<p>&nbsp;</p>
<p><a name="color_apparel"></a>color [color] &#8211; Color of the item</p>
<div>
<div>
<p><em>Note: This attribute is also described in the section on Variant<br />
Products. Please do not submit two versions of this attribute per item.</em></p>
<p>This defines the dominant color(s) of an item. When a single item has<br />
multiple colors:</p>
<ul>
<li>Combine them with ‘/’ in order of prominence (dominant color first, then<br />
accent colors). For example, a black shoe with green accents should have a color<br />
value of &#8216;Black / Green&#8217;. This attribute can also be used for finishes as well<br />
(e.g., &#8216;Mahogany&#8217; vs. &#8216;Stainless Steel&#8217;).</li>
<li>If you&#8217;re using XML, you must represent the &#8216;/&#8217; with &amp;#47;</li>
</ul>
<p><strong>When to include: </strong>Required for all apparel items in feeds<br />
that target the US. Recommended for other countries and product categories<br />
(might become required in the future).</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Text</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>Black</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:color&gt;Black&lt;/g:color&gt;</code></td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>This attribute is required for apparel products targeting the US.</li>
<li><strong>For apparel variants submitted to the<br />
US:</strong> Each different color or color combination must be submitted as its<br />
own item, in conjunction with the &#8216;item group id&#8217;. Visit <a href="answer.py?answer=1347943">submitting apparel products</a><br />
for more details.</li>
<li>Use consistent names of colors across variants of the same product, as well<br />
as across multiple products of the same category.</li>
<li>The values you provide may be displayed to users, so provide values that<br />
they will be able to understand.</li>
</ul>
</div>
</div>
<p>&nbsp;</p>
<p><a name="material"></a>material [material] &#8211; Material of the<br />
item</p>
<div>
<div>
<p>The material or fabric that a product is made out of. For example, a high<br />
heel pump might have values of “Leather”, “Denim”, “Suede”, etc.</p>
<p><strong>When to include: </strong>Required for all apparel items that differ<br />
by material for feeds that target the US. Recommended for other countries and<br />
product categories (might become required in the future).</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Text</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>Leather</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:material&gt;Leather&lt;/g:material&gt;</code></td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li><strong>For apparel variants submitted to the US</strong>: Each item that<br />
differs in ‘material’ must be submitted as its own item, in conjunction with the<br />
&#8216;item group id&#8217;.</li>
<li>The values you provide may be displayed to users, so provide values that<br />
they will be able to understand.</li>
</ul>
</div>
</div>
<p>&nbsp;</p>
<p><a name="pattern"></a>pattern [pattern] &#8211; Pattern/Graphic of<br />
the item</p>
<div>
<div>
<p>The pattern or graphic print featured on a product. For example, a t-shirt<br />
might have a logo of a sports team and have pattern values of “Bears”, “Tigers”,<br />
etc. A dress might come in two prints, and have pattern values of “Polka Dot”,<br />
“Striped”, “Paisley”, etc.</p>
<p>As a rule of thumb, if a user can choose to select different patterns on the<br />
landing page of your product, include all variant items in the same item group.<br />
Otherwise, use separate item groups.</p>
<p><strong>When to include: </strong>Required for all apparel items that differ<br />
by pattern for feeds that target the US. Recommended for other countries and<br />
product categories(might become required in the future).</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Text</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>Striped</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:pattern&gt;Striped&lt;/g:pattern&gt;</code></td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li><strong>For apparel variants submitted to the US:</strong> Each item that<br />
differs in ‘pattern’ must be submitted as its own item, in conjunction with the<br />
&#8216;item group id&#8217;.</li>
<li>The values you provide may be displayed to users, so provide values that<br />
they will be able to understand.</li>
</ul>
</div>
</div>
<p>&nbsp;</p>
<p><a name="size_apparel"></a>size [size] &#8211; Size of the item</p>
<div>
<div>
<p><em>Note: This attribute is also described in the section on Variant<br />
Products. Please do not include two versions of this attribute per<br />
item.</em></p>
<p>This indicates the size of a product. You may any provide<br />
values which are appropriate to your items. Examples for sizing values can be<br />
found <a href="answer.py?answer=1347943">in this article</a>.</p>
<p><strong>When to include: </strong>Required for all apparel items in the<br />
&#8216;clothing&#8217; and &#8216;shoes&#8217; product categories in feeds that target the US.<br />
Recommended for other countries and product categories.</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Text</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>XL</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:size&gt;XL&lt;/g:size&gt;</code></td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>The values you provide may be displayed to users, so provide values that<br />
they will be able to understand.</li>
<li><strong>For apparel variants submitted to the<br />
US:</strong> Each different size or size combination must be submitted as its<br />
own item, in conjunction with the &#8216;item group id&#8217;. Visit <a href="answer.py?answer=1347943">submitting apparel products</a><br />
for more details.</li>
<li>If sizes are complex, condense them into one value (e.g., “16/34 Tall” for<br />
neck size 16 inches, sleeve length 34 inches, and “Tall” fit).</li>
<li>Use consistent size values across variants of the same product, as well as<br />
across multiple products of the same category. For example, within a group of<br />
t-shirts, use “S”, “M” , and “L” as sizes, not “S”, “Medium” , and “Lrg”.</li>
<li>You may use the same ‘image’ URL value for size variants if specific images<br />
are not available but we recommend that the ‘link’ attribute leads to a page<br />
which specifies all the details about the variant item.</li>
</ul>
</div>
</div>
<h2>6. Tax &amp; Shipping</h2>
<p>Taxes and shipping are an important part of the total cost of<br />
items. In fact, shipping cost is the most common reason for users abandoning<br />
their shopping choices. The &#8216;tax&#8217; attribute is only applicable to feeds<br />
targeting the US &#8211; for all other countries, value added tax (VAT) has to be<br />
included in the price.</p>
<p>There are three ways to specify tax (US only) and shipping<br />
costs:</p>
<ol>
<li><strong>Settings in the Merchant<br />
Center: </strong>We offer various ways to specify tax and shipping costs if your<br />
pricing structure is relatively simple. For example, if you have one shipping<br />
price for all your items, or if you use a structure based on the weight of the<br />
packaged item (in that case, include the shipping weight attribute), our system<br />
can easily accommodate your tax and shipping information. <a href="answer.py?answer=160162">Learn<br />
more.</a></li>
<li><strong>Attributes in the feed: </strong>By using the tax and shipping<br />
attributes below, you can model more complex tax and shipping cost<br />
structures.</li>
<li><strong>Combination of the two: </strong>You can specify default tax and<br />
shipping information in the Merchant Center, and then override those defaults<br />
for certain products by specifying the attributes below.</li>
</ol>
<p>You are required to use one of the ways above to specify tax<br />
and shipping in the US, and only shipping information in the UK, Germany and<br />
France.</p>
<p>If you can’t provide accurate tax or shipping information,<br />
please provide estimates. For example, you can provide tax as well as shipping<br />
cost for each product and state individually by using the tax and shipping<br />
attributes. Please estimate tax and shipping costs such that the total cost in<br />
Product Search results is either correct or overestimated for the majority of<br />
users.</p>
<p>&nbsp;</p>
<p><a name="tax"></a>tax [tax]
<div>
<div>
<div>
<div>This<br />
attribute is only available in the US. For feeds targeting Australia the price<br />
attribute should include GST.</div>
</div>
<div>
<div>This<br />
attribute is only available in the US. For feeds targeting France the price<br />
attribute should include VAT.</div>
</div>
<div>
<div>This<br />
attribute is only available in the US. For feeds targeting the United Kingdom<br />
the price attribute should include VAT.</div>
</div>
<div>
<div>This<br />
attribute is only available in the US. For feeds targeting Japan the price<br />
attribute should be tax inclusive.</div>
</div>
<div>
<div>This<br />
attribute is only available in the US. For feeds targeting Germany the price<br />
attribute should include VAT.</div>
</div>
<div>
<div>This<br />
attribute is only available in the US. For feeds targeting China the price<br />
attribute should be tax inclusive.</div>
</div>
<div>
<div>This<br />
attribute is only available in the US. For feeds targeting the Netherlands the<br />
price attribute should be tax inclusive.</div>
</div>
<div>
<div>This<br />
attribute is only available in the US. For feeds targeting Italy the price<br />
attribute should include VAT.</div>
</div>
<div>
<div>This<br />
attribute is only available in the US. For feeds targeting Spain the price<br />
attribute should include VAT.</div>
</div>
<div>
<div>This<br />
attribute is only available in the US. For feeds targeting Brazil the price<br />
attribute should include VAT.</div>
</div>
<div>
<div>This<br />
attribute is only available in the US. For feeds targeting Switzerland the price<br />
attribute should include VAT.</div>
</div>
<div>
<div>
<p>The tax attribute is an item-level override for merchant-level tax settings<br />
as defined in your Google Merchant Center account. This attribute is only<br />
accepted in the US, if your feed targets a country outside of the US, please do<br />
not use this attribute.</p>
<p>This attribute has four parts:</p>
<ul>
<li>country (optional): The country an item is taxed in<br />
according to <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166 standard </a>(at the moment, it&#8217;s always &#8216;US&#8217;)</li>
<li>region (optional): The geographic region that a tax rate applies to. In the<br />
US, the two-letter state abbreviation, ZIP code, or ZIP code range using *<br />
wildcard.</li>
<li>rate (required): The tax rate as a percent of the item price, i.e., a number<br />
as a percentage</li>
<li>tax_ship (optional): Boolean value for whether you charge tax on shipping, y<br />
for yes or n for no &#8211; the default value is n</li>
</ul>
<p>You can include this attribute up to 100 times to specify taxes for each<br />
state individually. If you decide to submit it explicitly for each state, make<br />
sure to cover every state (even the states where you do not charge tax). Note<br />
you can also specify that you charge no tax for a state.</p>
<p><strong>When to include: </strong>For items in<br />
feeds which target the US, use this attribute if you want to specify taxes for a<br />
particular item, or you want to override the default tax costs specified in the<br />
Merchant Center settings. If you do not provide tax information using one of<br />
these methods for each item, your items won’t show up in Product Search<br />
results.<a href="answer.py?answer=160162">Learn more.</a></p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Each tax attribute group consists of four sub-attributes:</p>
<table border="1" cellspacing="0" cellpadding="5">
<tbody>
<tr>
<td><strong>Name</strong></td>
<td><strong>Requirement</strong></td>
<td><strong>Description</strong></td>
<td><strong>Examples</strong></td>
</tr>
<tr>
<td>country</td>
<td>required</td>
<td>The country an item is taxed in (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166</a> country code)</td>
<td>US</td>
</tr>
<tr>
<td>region</td>
<td>optional</td>
<td>The geographic region that a tax rate applies to, e.g., in the US, the<br />
two-letter state abbreviation, ZIP code, or ZIP code range using * wildcard</td>
<td>CA, 946*</td>
</tr>
<tr>
<td>rate</td>
<td><strong>required</strong></td>
<td>The tax rate as a percent of the item price, i.e., number, as a<br />
percentage</td>
<td>5.00</td>
</tr>
<tr>
<td>tax_ship</td>
<td>optional</td>
<td>Boolean value for whether you charge tax on shipping, &#8216;y&#8217; for yes or &#8216;n&#8217; for<br />
no &#8211; the default value is &#8216;n&#8217;</td>
<td>y</td>
</tr>
</tbody>
</table>
<p><strong>Note</strong>: You can submit multiple<br />
values for this attribute.</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>Separate each sub-attribute with a colon, and each tax attribute group with<br />
a comma. Do not enclose sub-attribute values within quotations. <strong>All<br />
colons, even for blank values, are required, i.e., three colons are<br />
required.</strong><br />
<code>::0:</code><br />
<code>US::0:</code><br />
<code>US:CA:8.25:y,US:926*:8.75:y</code></td>
</tr>
<tr>
<td>XML</td>
<td>The four sub-attributes are country, region, rate, and tax ship. Include<br />
each tax attribute group as a separate attribute.</p>
<div><code>&lt;g:tax&gt;</code><br />
<code><br />
&lt;g:country&gt;US&lt;/g:country&gt;</code><br />
<code><br />
&lt;g:region&gt;MA&lt;/g:region&gt;</code><br />
<code><br />
&lt;g:rate&gt;5.00&lt;/g:rate&gt;</code><br />
<code><br />
&lt;g:tax_ship&gt;y&lt;/g:tax_ship&gt;</code><br />
<code>&lt;/g:tax&gt;</code></div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
<p>&nbsp;</p>
<p><a name="shipping"></a>shipping [shipping]
<div>
<div>
<div>
<div>
<p>This attribute provides the specific shipping estimate for the product.<br />
Providing this attribute for an item overrides the global shipping settings you<br />
defined in your Google Merchant Center settings.</p>
<p>This attribute has four sub-attributes:</p>
<ul>
<li>country (required): The country to which an item will be<br />
delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166 country code</a>). The default value for this<br />
sub-attribute is your feed&#8217;s target country.</li>
<li>region (optional): The geographical region to which a delivery rate applies,<br />
e.g. in the US, the two-letter state abbreviation.</li>
<li>service (optional): The name of the shipping method.</li>
<li>price (required): Fixed delivery price.</li>
</ul>
<p>You can include this attribute up to 100 times per item to specify shipping<br />
cost for individual regions. If you decide to submit it explicitly for each part<br />
of the country, make sure to cover each region or to specify if the item has<br />
free shipping.</p>
<p><strong>Note</strong>: Please remember that<br />
you must only provide direct-to-consumer shipping rates, as per our <a href="answer.py?answer=188484">Program Policies</a>. Rates for<br />
other methods, like ship-to-store delivery, are not allowed.</p>
<p><strong>When to include: </strong>If you want<br />
to specify shipping cost for this item, or you want to override the default<br />
shipping cost specified in the Merchant Center settings. <a href="answer.py?answer=160162">Learn more.</a></p>
<p>&nbsp;</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Each shipping attribute group consists of four sub-attributes:</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Name</td>
<td>Requirement</td>
<td>Description</td>
<td>Examples</td>
</tr>
<tr>
<td>country</td>
<td>required</td>
<td>The country an item will ship to (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166</a> country code). The default value for this attribute<br />
is your feed&#8217;s target country.</td>
<td>AU</td>
</tr>
<tr>
<td>region</td>
<td>optional</td>
<td>The geographic region that a shipping rate applies to, e.g., in Australia,<br />
the three-letter state abbreviation.</td>
<td>NSW</td>
</tr>
<tr>
<td height="27">service</td>
<td>optional</td>
<td>N/A for Australia</td>
<td>Ground</td>
</tr>
<tr>
<td>price</td>
<td>required</td>
<td>Fixed shipping price</td>
<td>7.95</td>
</tr>
</tbody>
</table>
<p><strong>Note</strong>: You can submit<br />
multiple values for this attribute.</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>Separate each sub-attribute with a colon, and each shipping attribute group<br />
with a comma. Do not enclose sub-attribute values within quotations. All colons,<br />
even for blank values, are required, i.e., three colons are required.<br />
<code><br />
AU:::7.95<br />
AU:200*:Ground:7.95,AU:NSW:Ground:5.95<br />
</code></td>
</tr>
<tr>
<td>XML</td>
<td>The four sub-attributes are country, region, service, and price. Include<br />
each shipping attribute group as a separate attribute.</p>
<div><code>&lt;g:shipping&gt;</code><br />
<code><br />
&lt;g:country&gt;AU&lt;/g:country&gt;</code><br />
<code><br />
&lt;g:region&gt;NSW&lt;/g:region&gt;</code><br />
<code><br />
&lt;g:service&gt;Ground&lt;/g:service&gt;</code><br />
<code><br />
&lt;g:price&gt;5.95&lt;/g:price&gt;</code><br />
<code>&lt;/g:shipping&gt;</code></div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div>
<div>
<p>This attribute provides the specific shipping estimate for the<br />
product. Providing this attribute for an item overrides the global shipping<br />
settings you defined in your Google Merchant Center settings.</p>
<p>This attribute has four sub-attributes:</p>
<ul>
<li>country (required): The country to which an item will be<br />
delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166 country code</a>). The default value for this<br />
sub-attribute is your feed&#8217;s target country.</li>
<li>region (optional): The geographical region to which a delivery rate applies,<br />
e.g. in the US, the two-letter state abbreviation, ZIP code or ZIP code range,<br />
using * wildcard.</li>
<li>service (optional): The name of the shipping method.</li>
<li>price (required): Fixed delivery price.</li>
</ul>
<p>You can include this attribute up to 100 times per item to<br />
specify shipping cost for individual regions. If you decide to submit it<br />
explicitly for each part of the country, make sure to cover each region or to<br />
specify if the item has free shipping.</p>
<p><strong>Note</strong>: Please<br />
remember that you must only provide direct-to-consumer shipping rates, as per<br />
our <a href="answer.py?answer=188484">Program Policies</a>. Rates<br />
for other methods, like ship-to-store delivery, are not allowed.</p>
<p>&nbsp;</p>
<p><strong>When to include: </strong>If you want<br />
to specify shipping cost for this item, or you want to override the default<br />
shipping cost specified in the Merchant Center settings. <a href="answer.py?answer=160162">Learn more.</a></p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Each delivery attribute group consists of four sub-attributes:</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Name</td>
<td>Requirement</td>
<td>Description</td>
<td>Examples</td>
</tr>
<tr>
<td>country</td>
<td>required</td>
<td>The country to which an item will be delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166</a> country code). The default value for this attribute<br />
is your feed&#8217;s target country.</td>
<td>CN</td>
</tr>
<tr>
<td>region</td>
<td></td>
<td>The geographical region to which a shipping rate applies.</td>
<td></td>
</tr>
<tr>
<td height="27">service</td>
<td>optional</td>
<td>The service class or delivery speed</td>
<td>Standard</td>
</tr>
<tr>
<td>price</td>
<td>required</td>
<td>Fixed delivery price</td>
<td>7.95</td>
</tr>
</tbody>
</table>
<p><strong>Note</strong>: You can submit multiple<br />
values for this attribute.</td>
</tr>
<tr>
<td>Text/Tab-delimited</td>
<td>Separate each sub-attribute with a colon and each delivery attribute group<br />
with a comma. Do not enclose sub-attribute values within quotations. All colons,<br />
even for blank values, are required, i.e. three colons are required.<br />
<code><br />
CN::0:<br />
CN::Standard:8.25,CN::926*:8.75<br />
</code></td>
</tr>
<tr>
<td>XML</td>
<td>The three sub-attributes are country, service and price. Include each<br />
delivery attribute group as a separate attribute.</p>
<div><code>&lt;g:shipping&gt;</code><br />
<code><br />
&lt;g:country&gt;CN&lt;/g:country&gt;</code><br />
<code><br />
&lt;g:region&gt;MA&lt;/g:region&gt;</code><br />
<code><br />
&lt;g:service&gt;Standard&lt;/g:service&gt;</code><br />
<code><br />
&lt;g:price&gt;5.95&lt;/g:price&gt;</code><br />
<code>&lt;/g:shipping&gt;</code></div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div>
<div>
<p>This attribute provides the specific shipping estimate for the<br />
product. Providing this attribute for an item overrides the global shipping<br />
settings you defined in your Google Merchant Center settings.</p>
<p>This attribute has four sub-attributes:</p>
<ul>
<li>country (required): The country to which an item will be<br />
delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166 country code</a>). The default value for this<br />
sub-attribute is your feed&#8217;s target country.</li>
<li>region (optional): The geographical region to which a delivery rate applies,<br />
e.g. in the US, the two-letter state abbreviation, ZIP code or ZIP code range,<br />
using * wildcard.</li>
<li>service (optional): The name of the shipping method.</li>
<li>price (required): Fixed delivery price.</li>
</ul>
<p>You can include this attribute up to 100 times per item to<br />
specify shipping cost for individual regions. If you decide to submit it<br />
explicitly for each part of the country, make sure to cover each region or to<br />
specify if the item has free shipping.</p>
<p><strong>Note</strong>: Please<br />
remember that you must only provide direct-to-consumer shipping rates, as per<br />
our <a href="answer.py?answer=188484">Program Policies</a>. Rates<br />
for other methods, like ship-to-store delivery, are not allowed.</p>
<p>&nbsp;</p>
<p><strong>When to include: </strong>If you want<br />
to specify shipping cost for this item, or you want to override the default<br />
shipping cost specified in the Merchant Center settings. <a href="answer.py?answer=160162">Learn more.</a></p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Each delivery attribute group consists of four sub-attributes:</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Name</td>
<td>Requirement</td>
<td>Description</td>
<td>Examples</td>
</tr>
<tr>
<td>country</td>
<td>required</td>
<td>The country to which an item will be delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166</a> country code). The default value for this attribute<br />
is your feed&#8217;s target country.</td>
<td>JP</td>
</tr>
<tr>
<td>region</td>
<td></td>
<td>The geographical region to which a shipping rate applies. JIS X 0401 (the<br />
national local government code), defined in the county code.</td>
<td></td>
</tr>
<tr>
<td height="27">service</td>
<td>optional</td>
<td>The service class or delivery speed</td>
<td>Standard</td>
</tr>
<tr>
<td>price</td>
<td>required</td>
<td>Fixed delivery price</td>
<td>1000</td>
</tr>
</tbody>
</table>
<p><strong>Note</strong>: You can submit multiple<br />
values for this attribute.</td>
</tr>
<tr>
<td>Text/Tab-delimited</td>
<td>Separate each sub-attribute with a colon and each delivery attribute group<br />
with a comma. Do not enclose sub-attribute values within quotations. All colons,<br />
even for blank values, are required, i.e. three colons are required.<br />
<code><br />
JP:::1000<br />
JP:01::1000,JP:02::1200<br />
</code></td>
</tr>
<tr>
<td>XML</td>
<td>The three sub-attributes are country, service and price. Include each<br />
delivery attribute group as a separate attribute.</p>
<div><code>&lt;g:shipping&gt;</code><br />
<code><br />
&lt;g:country&gt;JP&lt;/g:country&gt;</code><br />
<code><br />
&lt;g:region&gt;01&lt;/g:region&gt;</code><br />
<code><br />
&lt;g:service&gt;Standard&lt;/g:service&gt;</code><br />
<code><br />
&lt;g:price&gt;1000&lt;/g:price&gt;</code><br />
<code>&lt;/g:shipping&gt;</code></div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div>
<div>
<p>This attribute provides the specific shipping estimate for the<br />
product. Providing this attribute for an item overrides the global shipping<br />
settings you defined in your Google Merchant Center settings.</p>
<p>This attribute has four sub-attributes:</p>
<ul>
<li>country (required): The country to which an item will be<br />
delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166 country code</a>). The default value for this<br />
sub-attribute is your feed&#8217;s target country.</li>
<li>region (optional): The geographical region to which a delivery rate applies,<br />
e.g. in the US, the two-letter state abbreviation, ZIP code or ZIP code range,<br />
using * wildcard.</li>
<li>service (optional): The name of the shipping method.</li>
<li>price (required): Fixed delivery price.</li>
</ul>
<p>You can include this attribute up to 100 times per item to<br />
specify shipping cost for individual regions. If you decide to submit it<br />
explicitly for each part of the country, make sure to cover each region or to<br />
specify if the item has free shipping.</p>
<p><strong>Note</strong>: Please<br />
remember that you must only provide direct-to-consumer shipping rates, as per<br />
our <a href="answer.py?answer=188484">Program Policies</a>. Rates<br />
for other methods, like ship-to-store delivery, are not allowed.</p>
<p>&nbsp;</p>
<p><strong>When to include: </strong>If you want<br />
to specify shipping cost for this item, or you want to override the default<br />
shipping cost specified in the Merchant Center settings. <a href="answer.py?answer=160162">Learn more.</a></p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Each delivery attribute group consists of three sub-attributes:</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Name</td>
<td>Requirement</td>
<td>Description</td>
<td>Examples</td>
</tr>
<tr>
<td>country</td>
<td>required</td>
<td>The country to which an item will be delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166</a> country code). The default value for this attribute<br />
is your feed&#8217;s target country.</td>
<td>FR</td>
</tr>
<tr>
<td>region</td>
<td><strong>Not used in the UK, Germany, France, Italy, Spain or the<br />
Netherlands.</strong></td>
<td></td>
<td></td>
</tr>
<tr>
<td height="27">service</td>
<td>optional</td>
<td>The service class or delivery speed</td>
<td>Standard</td>
</tr>
<tr>
<td>price</td>
<td>required</td>
<td>Fixed delivery price</td>
<td>10.00</td>
</tr>
</tbody>
</table>
<p><strong>Note</strong>: You can submit<br />
multiple values for this attribute.</td>
</tr>
<tr>
<td>Text/Tab-delimited</td>
<td>Separate each sub-attribute with a colon and each delivery attribute group<br />
with a comma. Do not enclose sub-attribute values within quotations. All colons,<br />
even for blank values, are required, i.e. three colons are required.<br />
<code><br />
FR:::10.00<br />
FR::Standard:2.95,FR::Standard:10.00<br />
</code></td>
</tr>
<tr>
<td>XML</td>
<td>The three sub-attributes are country, service and price. Include each<br />
delivery attribute group as a separate attribute.</p>
<div><code>&lt;g:shipping&gt;</code><br />
<code><br />
&lt;g:country&gt;FR&lt;/g:country&gt;</code><br />
<code><br />
&lt;g:service&gt;Standard&lt;/g:service&gt;</code><br />
<code><br />
&lt;g:price&gt;5.95&lt;/g:price&gt;</code><br />
<code>&lt;/g:shipping&gt;</code></div>
</td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>For feeds targeting the US, UK, Germany and France, it is required to<br />
provide shipping costs for every item, either by specifying the global default<br />
shipping costs in the Merchant Center settings, or by providing this attribute.<br />
If you do not provide shipping costs using one of these methods for each item,<br />
your items won’t show up in Product Search results.</li>
</ul>
</div>
</div>
<div>
<div>
<p>This attribute provides the specific shipping estimate for the<br />
product. Providing this attribute for an item overrides the global shipping<br />
settings you defined in your Google Merchant Center settings.</p>
<p>This attribute has four sub-attributes:</p>
<ul>
<li>country (required): The country to which an item will be<br />
delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166 country code</a>). The default value for this<br />
sub-attribute is your feed&#8217;s target country.</li>
<li>region (optional): The geographical region to which a delivery rate applies,<br />
e.g. in the US, the two-letter state abbreviation, ZIP code or ZIP code range,<br />
using * wildcard.</li>
<li>service (optional): The name of the shipping method.</li>
<li>price (required): Fixed delivery price.</li>
</ul>
<p>You can include this attribute up to 100 times per item to<br />
specify shipping cost for individual regions. If you decide to submit it<br />
explicitly for each part of the country, make sure to cover each region or to<br />
specify if the item has free shipping.</p>
<p><strong>Note</strong>: Please<br />
remember that you must only provide direct-to-consumer shipping rates, as per<br />
our <a href="answer.py?answer=188484">Program Policies</a>. Rates<br />
for other methods, like ship-to-store delivery, are not allowed.</p>
<p>&nbsp;</p>
<p><strong>When to include: </strong>If you want<br />
to specify shipping cost for this item, or you want to override the default<br />
shipping cost specified in the Merchant Center settings. <a href="answer.py?answer=160162">Learn more.</a></p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Each delivery attribute group consists of three sub-attributes:</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Name</td>
<td>Requirement</td>
<td>Description</td>
<td>Examples</td>
</tr>
<tr>
<td>country</td>
<td>required</td>
<td>The country to which an item will be delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166</a> country code). The default value for this attribute<br />
is your feed&#8217;s target country.</td>
<td>GB</td>
</tr>
<tr>
<td>region</td>
<td><strong>Not used in the UK, Germany, France, Italy, Spain or the<br />
Netherlands.</strong></td>
<td></td>
<td></td>
</tr>
<tr>
<td height="27">service</td>
<td>optional</td>
<td>The service class or delivery speed</td>
<td>Standard</td>
</tr>
<tr>
<td>price</td>
<td>required</td>
<td>Fixed delivery price</td>
<td>10.00</td>
</tr>
</tbody>
</table>
<p><strong>Note</strong>: You can submit<br />
multiple values for this attribute.</td>
</tr>
<tr>
<td>Text/Tab-delimited</td>
<td>Separate each sub-attribute with a colon and each delivery attribute group<br />
with a comma. Do not enclose sub-attribute values within quotations. All colons,<br />
even for blank values, are required, i.e. three colons are required.<br />
<code><br />
DE:::10.00<br />
DE::Standard:2.95,DE::Standard:10.00<br />
</code></td>
</tr>
<tr>
<td>XML</td>
<td>The three sub-attributes are country, service and price. Include each<br />
delivery attribute group as a separate attribute.</p>
<div><code>&lt;g:shipping&gt;</code><br />
<code><br />
&lt;g:country&gt;DE&lt;/g:country&gt;</code><br />
<code><br />
&lt;g:service&gt;Standard&lt;/g:service&gt;</code><br />
<code><br />
&lt;g:price&gt;5.95&lt;/g:price&gt;</code><br />
<code>&lt;/g:shipping&gt;</code></div>
</td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>For feeds targeting the US, UK, Germany and France, it is required to<br />
provide shipping costs for every item, either by specifying the global default<br />
shipping costs in the Merchant Center settings, or by providing this attribute.<br />
If you do not provide shipping costs using one of these methods for each item,<br />
your items won’t show up in Product Search results.</li>
</ul>
</div>
</div>
<div>
<div>
<p>This attribute provides the specific shipping estimate for the<br />
product. Providing this attribute for an item overrides the global shipping<br />
settings you defined in your Google Merchant Center settings.</p>
<p>This attribute has four sub-attributes:</p>
<ul>
<li>country (required): The country to which an item will be<br />
delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166 country code</a>). The default value for this<br />
sub-attribute is your feed&#8217;s target country.</li>
<li>region (optional): The geographical region to which a delivery rate applies,<br />
e.g. in the US, the two-letter state abbreviation, ZIP code or ZIP code range,<br />
using * wildcard.</li>
<li>service (optional): The name of the shipping method.</li>
<li>price (required): Fixed delivery price.</li>
</ul>
<p>You can include this attribute up to 100 times per item to<br />
specify shipping cost for individual regions. If you decide to submit it<br />
explicitly for each part of the country, make sure to cover each region or to<br />
specify if the item has free shipping.</p>
<p><strong>Note</strong>: Please<br />
remember that you must only provide direct-to-consumer shipping rates, as per<br />
our <a href="answer.py?answer=188484">Program Policies</a>. Rates<br />
for other methods, like ship-to-store delivery, are not allowed.</p>
<p>&nbsp;</p>
<p><strong>When to include: </strong>If you want<br />
to specify shipping cost for this item, or you want to override the default<br />
shipping cost specified in the Merchant Center settings. <a href="answer.py?answer=160162">Learn more.</a></p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Each delivery attribute group consists of three sub-attributes:</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Name</td>
<td>Requirement</td>
<td>Description</td>
<td>Examples</td>
</tr>
<tr>
<td>country</td>
<td>required</td>
<td>The country to which an item will be delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166</a> country code). The default value for this attribute<br />
is your feed&#8217;s target country.</td>
<td>GB</td>
</tr>
<tr>
<td>region</td>
<td><strong>Not used in the UK, Germany, France, Italy, Spain or the<br />
Netherlands.</strong></td>
<td></td>
<td></td>
</tr>
<tr>
<td height="27">service</td>
<td>optional</td>
<td>The service class or delivery speed</td>
<td>Standard</td>
</tr>
<tr>
<td>price</td>
<td>required</td>
<td>Fixed delivery price</td>
<td>10.00</td>
</tr>
</tbody>
</table>
<p><strong>Note</strong>: You can submit<br />
multiple values for this attribute.</td>
</tr>
<tr>
<td>Text/Tab-delimited</td>
<td>Separate each sub-attribute with a colon and each delivery attribute group<br />
with a comma. Do not enclose sub-attribute values within quotations. All colons,<br />
even for blank values, are required, i.e. three colons are required.<br />
<code><br />
NL:::10.00<br />
NL::Standard:2.95,NL::Standard:10.00<br />
</code></td>
</tr>
<tr>
<td>XML</td>
<td>The three sub-attributes are country, service and price. Include each<br />
delivery attribute group as a separate attribute.</p>
<div><code>&lt;g:shipping&gt;</code><br />
<code><br />
&lt;g:country&gt;NL&lt;/g:country&gt;</code><br />
<code><br />
&lt;g:service&gt;Standard&lt;/g:service&gt;</code><br />
<code><br />
&lt;g:price&gt;5.95&lt;/g:price&gt;</code><br />
<code>&lt;/g:shipping&gt;</code></div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div>
<div>
<p>This attribute provides the specific shipping estimate for the<br />
product. Providing this attribute for an item overrides the global shipping<br />
settings you defined in your Google Merchant Center settings.</p>
<p>This attribute has four sub-attributes:</p>
<ul>
<li>country (required): The country to which an item will be<br />
delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166 country code</a>). The default value for this<br />
sub-attribute is your feed&#8217;s target country.</li>
<li>region (optional): The geographical region to which a delivery rate applies,<br />
e.g. in the US, the two-letter state abbreviation, ZIP code or ZIP code range,<br />
using * wildcard.</li>
<li>service (optional): The name of the shipping method.</li>
<li>price (required): Fixed delivery price.</li>
</ul>
<p>You can include this attribute up to 100 times per item to<br />
specify shipping cost for individual regions. If you decide to submit it<br />
explicitly for each part of the country, make sure to cover each region or to<br />
specify if the item has free shipping.</p>
<p><strong>Note</strong>: Please<br />
remember that you must only provide direct-to-consumer shipping rates, as per<br />
our <a href="answer.py?answer=188484">Program Policies</a>. Rates<br />
for other methods, like ship-to-store delivery, are not allowed.</p>
<p>&nbsp;</p>
<p><strong>When to include: </strong>If you want<br />
to specify shipping cost for this item, or you want to override the default<br />
shipping cost specified in the Merchant Center settings. <a href="answer.py?answer=160162">Learn more.</a></p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Each delivery attribute group consists of three sub-attributes:</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Name</td>
<td>Requirement</td>
<td>Description</td>
<td>Examples</td>
</tr>
<tr>
<td>country</td>
<td>required</td>
<td>The country to which an item will be delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166</a> country code). The default value for this attribute<br />
is your feed&#8217;s target country.</td>
<td>GB</td>
</tr>
<tr>
<td>region</td>
<td><strong>Not used in the UK, Germany, France, Italy, Spain or the<br />
Netherlands.</strong></td>
<td></td>
<td></td>
</tr>
<tr>
<td height="27">service</td>
<td>optional</td>
<td>The service class or delivery speed</td>
<td>Standard</td>
</tr>
<tr>
<td>price</td>
<td>required</td>
<td>Fixed delivery price</td>
<td>10.00</td>
</tr>
</tbody>
</table>
<p><strong>Note</strong>: You can submit<br />
multiple values for this attribute.</td>
</tr>
<tr>
<td>Text/Tab-delimited</td>
<td>Separate each sub-attribute with a colon and each delivery attribute group<br />
with a comma. Do not enclose sub-attribute values within quotations. All colons,<br />
even for blank values, are required, i.e. three colons are required.<br />
<code><br />
ES:::10.00<br />
ES::Standard:2.95,ES::Standard:10.00<br />
</code></td>
</tr>
<tr>
<td>XML</td>
<td>The three sub-attributes are country, service and price. Include each<br />
delivery attribute group as a separate attribute.</p>
<div><code>&lt;g:shipping&gt;</code><br />
<code><br />
&lt;g:country&gt;ES&lt;/g:country&gt;</code><br />
<code><br />
&lt;g:service&gt;Standard&lt;/g:service&gt;</code><br />
<code><br />
&lt;g:price&gt;5.95&lt;/g:price&gt;</code><br />
<code>&lt;/g:shipping&gt;</code></div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div>
<div>
<p>This attribute provides the specific shipping estimate for the<br />
product. Providing this attribute for an item overrides the global shipping<br />
settings you defined in your Google Merchant Center settings.</p>
<p>This attribute has four sub-attributes:</p>
<ul>
<li>country (required): The country to which an item will be<br />
delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166 country code</a>). The default value for this<br />
sub-attribute is your feed&#8217;s target country.</li>
<li>region (optional): The geographical region to which a delivery rate applies,<br />
e.g. in the US, the two-letter state abbreviation, ZIP code or ZIP code range,<br />
using * wildcard.</li>
<li>service (optional): The name of the shipping method.</li>
<li>price (required): Fixed delivery price.</li>
</ul>
<p>You can include this attribute up to 100 times per item to<br />
specify shipping cost for individual regions. If you decide to submit it<br />
explicitly for each part of the country, make sure to cover each region or to<br />
specify if the item has free shipping.</p>
<p><strong>Note</strong>: Please<br />
remember that you must only provide direct-to-consumer shipping rates, as per<br />
our <a href="answer.py?answer=188484">Program Policies</a>. Rates<br />
for other methods, like ship-to-store delivery, are not allowed.</p>
<p>&nbsp;</p>
<p><strong>When to include: </strong>If you want<br />
to specify shipping cost for this item, or you want to override the default<br />
shipping cost specified in the Merchant Center settings. <a href="answer.py?answer=160162">Learn more.</a></p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Each delivery attribute group consists of three sub-attributes:</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Name</td>
<td>Requirement</td>
<td>Description</td>
<td>Examples</td>
</tr>
<tr>
<td>country</td>
<td>required</td>
<td>The country to which an item will be delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166</a> country code). The default value for this attribute<br />
is your feed&#8217;s target country.</td>
<td>GB</td>
</tr>
<tr>
<td>region</td>
<td><strong>Not used in the UK, Germany, France, Italy, Spain or the<br />
Netherlands.</strong></td>
<td></td>
<td></td>
</tr>
<tr>
<td height="27">service</td>
<td>optional</td>
<td>The service class or delivery speed</td>
<td>Standard</td>
</tr>
<tr>
<td>price</td>
<td>required</td>
<td>Fixed delivery price</td>
<td>10.00</td>
</tr>
</tbody>
</table>
<p><strong>Note</strong>: You can submit<br />
multiple values for this attribute.</td>
</tr>
<tr>
<td>Text/Tab-delimited</td>
<td>Separate each sub-attribute with a colon and each delivery attribute group<br />
with a comma. Do not enclose sub-attribute values within quotations. All colons,<br />
even for blank values, are required, i.e. three colons are required.<br />
<code><br />
IT:::10.00<br />
IT::Standard:2.95,IT::Standard:10.00<br />
</code></td>
</tr>
<tr>
<td>XML</td>
<td>The three sub-attributes are country, service and price. Include each<br />
delivery attribute group as a separate attribute.</p>
<div><code>&lt;g:shipping&gt;</code><br />
<code><br />
&lt;g:country&gt;IT&lt;/g:country&gt;</code><br />
<code><br />
&lt;g:service&gt;Standard&lt;/g:service&gt;</code><br />
<code><br />
&lt;g:price&gt;5.95&lt;/g:price&gt;</code><br />
<code>&lt;/g:shipping&gt;</code></div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div>
<div>
<p>This attribute provides the specific shipping estimate for the<br />
product. Providing this attribute for an item overrides the global shipping<br />
settings you defined in your Google Merchant Center settings.</p>
<p>This attribute has four sub-attributes:</p>
<ul>
<li>country (required): The country to which an item will be<br />
delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166 country code</a>). The default value for this<br />
sub-attribute is your feed&#8217;s target country.</li>
<li>region (optional): The geographical region to which a delivery rate applies,<br />
e.g. in the US, the two-letter state abbreviation, ZIP code or ZIP code range,<br />
using * wildcard.</li>
<li>service (optional): The name of the shipping method.</li>
<li>price (required): Fixed delivery price.</li>
</ul>
<p>You can include this attribute up to 100 times per item to<br />
specify shipping cost for individual regions. If you decide to submit it<br />
explicitly for each part of the country, make sure to cover each region or to<br />
specify if the item has free shipping.</p>
<p><strong>Note</strong>: Please<br />
remember that you must only provide direct-to-consumer shipping rates, as per<br />
our <a href="answer.py?answer=188484">Program Policies</a>. Rates<br />
for other methods, like ship-to-store delivery, are not allowed.</p>
<p>&nbsp;</p>
<p><strong>When to include: </strong>If you want<br />
to specify shipping cost for this item, or you want to override the default<br />
shipping cost specified in the Merchant Center settings. <a href="answer.py?answer=160162">Learn more.</a></p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Each delivery attribute group consists of three sub-attributes:</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Name</td>
<td>Requirement</td>
<td>Description</td>
<td>Examples</td>
</tr>
<tr>
<td>country</td>
<td>required</td>
<td>The country to which an item will be delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166</a> country code). The default value for this attribute<br />
is your feed&#8217;s target country.</td>
<td>GB</td>
</tr>
<tr>
<td>region</td>
<td><strong>Not used in the UK, Germany, France, Italy, Spain or the<br />
Netherlands.</strong></td>
<td></td>
<td></td>
</tr>
<tr>
<td height="27">service</td>
<td>optional</td>
<td>The service class or delivery speed</td>
<td>Courier</td>
</tr>
<tr>
<td>price</td>
<td>required</td>
<td>Fixed delivery price</td>
<td>10.00</td>
</tr>
</tbody>
</table>
<p><strong>Note</strong>: You can submit<br />
multiple values for this attribute.</td>
</tr>
<tr>
<td>Text/Tab-delimited</td>
<td>Separate each sub-attribute with a colon and each delivery attribute group<br />
with a comma. Do not enclose sub-attribute values within quotations. All colons,<br />
even for blank values, are required, i.e. three colons are required.<br />
<code><br />
GB:::10.00<br />
GB::Royal<br />
Mail:2.95,GB::Courier:10.00<br />
</code></td>
</tr>
<tr>
<td>XML</td>
<td>The three sub-attributes are country, service and price. Include each<br />
delivery attribute group as a separate attribute.</p>
<div><code>&lt;g:shipping&gt;</code><br />
<code><br />
&lt;g:country&gt;GB&lt;/g:country&gt;</code><br />
<code>   &lt;g:service&gt;Royal<br />
Mail&lt;/g:service&gt;</code><br />
<code><br />
&lt;g:price&gt;10.00&lt;/g:price&gt;</code><br />
<code>&lt;/g:shipping&gt;</code></div>
</td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>For feeds targeting the US, UK, Germany and France, it is required to<br />
provide shipping costs for every item, either by specifying the global default<br />
shipping costs in the Merchant Center settings, or by providing this attribute.<br />
If you do not provide shipping costs using one of these methods for each item,<br />
your items won’t show up in Product Search results.</li>
</ul>
</div>
</div>
<div>
<div>
<p>This attribute provides the specific shipping estimate for the<br />
product. Providing this attribute for an item overrides the global shipping<br />
settings you defined in your Google Merchant Center settings.</p>
<p>This attribute has four sub-attributes:</p>
<ul>
<li>country (required): The country to which an item will be<br />
delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166 country code</a>). The default value for this<br />
sub-attribute is your feed&#8217;s target country.</li>
<li>region (optional): The geographical region to which a delivery rate applies,<br />
e.g. in the US, the two-letter state abbreviation, ZIP code or ZIP code range,<br />
using * wildcard.</li>
<li>service (optional): The name of the shipping method.</li>
<li>price (required): Fixed delivery price.</li>
</ul>
<p>You can include this attribute up to 100 times per item to<br />
specify shipping cost for individual regions. If you decide to submit it<br />
explicitly for each part of the country, make sure to cover each region or to<br />
specify if the item has free shipping.</p>
<p><strong>Note</strong>: Please<br />
remember that you must only provide direct-to-consumer shipping rates, as per<br />
our <a href="answer.py?answer=188484">Program Policies</a>. Rates<br />
for other methods, like ship-to-store delivery, are not allowed.</p>
<p>&nbsp;</p>
<p><strong>When to include: </strong>If you want<br />
to specify shipping cost for this item, or you want to override the default<br />
shipping cost specified in the Merchant Center settings. <a href="answer.py?answer=160162">Learn more.</a></p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Each delivery attribute group consists of four sub-attributes:</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Name</td>
<td>Requirement</td>
<td>Description</td>
<td>Examples</td>
</tr>
<tr>
<td>country</td>
<td>required</td>
<td>The country to which an item will be delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166</a> country code). The default value for this attribute<br />
is your feed&#8217;s target country.</td>
<td>US</td>
</tr>
<tr>
<td>region</td>
<td>optional</td>
<td>The geographical region to which a delivery rate applies, e.g. in the US,<br />
the two-letter state abbreviation, ZIP code or ZIP code range, using * wildcard.</td>
<td>MA</td>
</tr>
<tr>
<td height="27">service</td>
<td>optional</td>
<td>The service class or delivery speed</td>
<td>Ground</td>
</tr>
<tr>
<td>price</td>
<td>required</td>
<td>Fixed delivery price</td>
<td>7.95</td>
</tr>
</tbody>
</table>
<p><strong>Note</strong>: You can submit<br />
multiple values for this attribute.</td>
</tr>
<tr>
<td>Text/Tab-delimited</td>
<td>Separate each sub-attribute with a colon and each delivery attribute group<br />
with a comma. Do not enclose sub-attribute values within quotations. All colons,<br />
even for blank values, are required, i.e. three colons are required.<br />
<code><br />
US:::7.95<br />
US:024*:Ground:7.95,US:MA:Ground:5.95<br />
</code></td>
</tr>
<tr>
<td>XML</td>
<td>The four sub-attributes are country, region, service and price. Include each<br />
delivery attribute group as a separate attribute.</p>
<div><code>&lt;g:shipping&gt;</code><br />
<code><br />
&lt;g:country&gt;US&lt;/g:country&gt;</code><br />
<code><br />
&lt;g:region&gt;MA&lt;/g:region&gt;</code><br />
<code><br />
&lt;g:service&gt;Ground&lt;/g:service&gt;</code><br />
<code><br />
&lt;g:price&gt;5.95&lt;/g:price&gt;</code><br />
<code>&lt;/g:shipping&gt;</code></div>
</td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>For feeds targeting the US, UK, Germany and France, it is required to<br />
provide shipping costs for every item, either by specifying the global default<br />
shipping costs in the Merchant Center settings, or by providing this attribute.<br />
If you do not provide shipping costs using one of these methods for each item,<br />
your items won’t show up in Product Search results.</li>
</ul>
</div>
</div>
<div>
<div>
<p>This attribute provides the specific shipping estimate for the<br />
product. Providing this attribute for an item overrides the global shipping<br />
settings you defined in your Google Merchant Center settings.</p>
<p>This attribute has four sub-attributes:</p>
<ul>
<li>country (required): The country to which an item will be<br />
delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166 country code</a>). The default value for this<br />
sub-attribute is your feed&#8217;s target country.</li>
<li>region (optional): The geographical region to which a delivery rate applies,<br />
e.g. in the US, the two-letter state abbreviation, ZIP code or ZIP code range,<br />
using * wildcard.</li>
<li>service (optional): The name of the shipping method.</li>
<li>price (required): Fixed delivery price.</li>
</ul>
<p>You can include this attribute up to 100 times per item to<br />
specify shipping cost for individual regions. If you decide to submit it<br />
explicitly for each part of the country, make sure to cover each region or to<br />
specify if the item has free shipping.</p>
<p><strong>Note</strong>: Please<br />
remember that you must only provide direct-to-consumer shipping rates, as per<br />
our <a href="answer.py?answer=188484">Program Policies</a>. Rates<br />
for other methods, like ship-to-store delivery, are not allowed.</p>
<p>&nbsp;</p>
<p><strong>When to include: </strong>If you want<br />
to specify shipping cost for this item, or you want to override the default<br />
shipping cost specified in the Merchant Center settings. <a href="answer.py?answer=">Learn more.</a></p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Each delivery attribute group consists of four sub-attributes:</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Name</td>
<td>Requirement</td>
<td>Description</td>
<td>Examples</td>
</tr>
<tr>
<td>country</td>
<td>required</td>
<td>The country to which an item will be delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166</a> country code). The default value for this attribute<br />
is your feed&#8217;s target country.</td>
<td>US</td>
</tr>
<tr>
<td>region</td>
<td>optional</td>
<td>The geographical region to which a delivery rate applies, e.g. in the US,<br />
the two-letter state abbreviation, ZIP code or ZIP code range, using * wildcard.</td>
<td>MA</td>
</tr>
<tr>
<td height="27">service</td>
<td>optional</td>
<td>The service class or delivery speed</td>
<td>Ground</td>
</tr>
<tr>
<td>price</td>
<td>required</td>
<td>Fixed delivery price</td>
<td>7.95</td>
</tr>
</tbody>
</table>
<p><strong>Note</strong>: You can submit<br />
multiple values for this attribute.</td>
</tr>
<tr>
<td>Text/Tab-delimited</td>
<td>Separate each sub-attribute with a colon and each delivery attribute group<br />
with a comma. Do not enclose sub-attribute values within quotations. All colons,<br />
even for blank values, are required, i.e. three colons are required.<br />
<code><br />
BR:::7.95<br />
BR:024*:Ground:7.95,BR:MA:Ground:5.95<br />
</code></td>
</tr>
<tr>
<td>XML</td>
<td>The four sub-attributes are country, region, service and price. Include each<br />
delivery attribute group as a separate attribute.</p>
<div><code>&lt;g:shipping&gt;</code><br />
<code><br />
&lt;g:country&gt;BR&lt;/g:country&gt;</code><br />
<code><br />
&lt;g:region&gt;MA&lt;/g:region&gt;</code><br />
<code><br />
&lt;g:service&gt;Ground&lt;/g:service&gt;</code><br />
<code><br />
&lt;g:price&gt;5.95&lt;/g:price&gt;</code><br />
<code>&lt;/g:shipping&gt;</code></div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div>
<div>
<p>This attribute provides the specific shipping estimate for the<br />
product. Providing this attribute for an item overrides the global shipping<br />
settings you defined in your Google Merchant Center settings.</p>
<p>This attribute has four sub-attributes:</p>
<ul>
<li>country (required): The country to which an item will be<br />
delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166 country code</a>). The default value for this<br />
sub-attribute is your feed&#8217;s target country.</li>
<li>region (optional): The geographical region to which a delivery rate applies,<br />
e.g. in the US, the two-letter state abbreviation, ZIP code or ZIP code range,<br />
using * wildcard.</li>
<li>service (optional): The name of the shipping method.</li>
<li>price (required): Fixed delivery price.</li>
</ul>
<p>You can include this attribute up to 100 times per item to<br />
specify shipping cost for individual regions. If you decide to submit it<br />
explicitly for each part of the country, make sure to cover each region or to<br />
specify if the item has free shipping.</p>
<p><strong>Note</strong>: Please<br />
remember that you must only provide direct-to-consumer shipping rates, as per<br />
our <a href="answer.py?answer=188484">Program Policies</a>. Rates<br />
for other methods, like ship-to-store delivery, are not allowed.</p>
<p>&nbsp;</p>
<p><strong>When to include: </strong>If you want<br />
to specify shipping cost for this item, or you want to override the default<br />
shipping cost specified in the Merchant Center settings. <a href="answer.py?answer=">Learn more.</a></p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Each delivery attribute group consists of four sub-attributes:</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Name</td>
<td>Requirement</td>
<td>Description</td>
<td>Examples</td>
</tr>
<tr>
<td>country</td>
<td>required</td>
<td>The country to which an item will be delivered (as an <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm">ISO 3166</a> country code). The default value for this attribute<br />
is your feed&#8217;s target country.</td>
<td>US</td>
</tr>
<tr>
<td>region</td>
<td>optional</td>
<td>The geographical region to which a delivery rate applies, e.g. in the US,<br />
the two-letter state abbreviation, ZIP code or ZIP code range, using * wildcard.</td>
<td>MA</td>
</tr>
<tr>
<td height="27">service</td>
<td>optional</td>
<td>The service class or delivery speed</td>
<td>Ground</td>
</tr>
<tr>
<td>price</td>
<td>required</td>
<td>Fixed delivery price</td>
<td>7.95</td>
</tr>
</tbody>
</table>
<p><strong>Note</strong>: You can submit<br />
multiple values for this attribute.</td>
</tr>
<tr>
<td>Text/Tab-delimited</td>
<td>Separate each sub-attribute with a colon and each delivery attribute group<br />
with a comma. Do not enclose sub-attribute values within quotations. All colons,<br />
even for blank values, are required, i.e. three colons are required.<br />
<code><br />
CH:::7.95<br />
CH:024*:Ground:7.95,CH:MA:Ground:5.95<br />
</code></td>
</tr>
<tr>
<td>XML</td>
<td>The four sub-attributes are country, region, service and price. Include each<br />
delivery attribute group as a separate attribute.</p>
<div><code>&lt;g:shipping&gt;</code><br />
<code><br />
&lt;g:country&gt;CH&lt;/g:country&gt;</code><br />
<code><br />
&lt;g:region&gt;MA&lt;/g:region&gt;</code><br />
<code><br />
&lt;g:service&gt;Ground&lt;/g:service&gt;</code><br />
<code><br />
&lt;g:price&gt;5.95&lt;/g:price&gt;</code><br />
<code>&lt;/g:shipping&gt;</code></div>
</td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>For feeds targeting the US, UK, Germany and France, it is required to<br />
provide shipping costs for every item, either by specifying the global defaultshipping costs in the Merchant Center settings, or by providing this attribute.<br />
If you do not provide shipping costs using one of these methods for each item,<br />
your items won’t show up in Product Search results.</li>
</ul>
</div>
</div>
</div>
</div>
<p>&nbsp;</p>
<p><a name="shipping_weight"></a>shipping weight [shipping_weight] -<br />
Weight of the item for shipping</p>
<div>
<div>
<p>This is the weight of the product used to calculate the shipping cost of the<br />
item. If you have specified a global shipping rule that is dependent on shipping<br />
weight, this attribute will be used to calculate the shipping cost of the item<br />
automatically.</p>
<p><strong>When to include:</strong> Required if you have set up a shipping rule<br />
in the Merchant Center that is based on weight.</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>We accept only the following units of weight: lb, pound, oz, ounce, g, gram,<br />
kg, kilogram.</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>3 kilograms</td>
</tr>
<tr>
<td>XML</td>
<td>&#8216;&lt;g:shipping_weight&gt;3<br />
kilograms&lt;/g:shipping_weight&gt;&#8217;</td>
</tr>
</tbody>
</table>
<p><strong>Important:</strong></p>
<ul>
<li>The weight must include a number and a unit of weight. We accept the<br />
following units: lb, pound, oz, ounce, g, gram, kg,<br />
kilogram.</li>
</ul>
</div>
</div>
<h2>7. Nearby Stores (US &amp; UK only)</h2>
<p>If you are a multi-channel retailer with physical presence,<br />
Product Search can show your store locations next to your products. If the user<br />
is looking at one of your products and has specified a location close to one of<br />
your stores, Product Search will show your store(s) on a map. We will display<br />
the phone number in case the user wants to check availability of the item, and<br />
the user can get driving directions to find your store easily.</p>
<p>To enable this feature, you need to submit<br />
your store locations through Google Places. <a href="answer.py?answer=1101441">Learn more.</a> Once you have provided your store locations, you<br />
may specify if an item is only available for purchase online and not in your<br />
physical store by providing the attribute below.</p>
<p>&nbsp;</p>
<p><a name="online_only"></a>online only [online_only] &#8211; Whether an<br />
item is available for purchase only online</p>
<div>
<div>
<div>
<div>This<br />
attribute is only available for feeds targeting the United States or United<br />
Kingdom.</div>
</div>
<div>
<div>This<br />
attribute is only available for feeds targeting the United States or United<br />
Kingdom.</div>
</div>
<div>
<div>This<br />
attribute is only available for feeds targeting the United States or United<br />
Kingdom.</div>
</div>
<div>
<div>This<br />
attribute is only available for feeds targeting the United States or United<br />
Kingdom.</div>
</div>
<div>
<div>This<br />
attribute is only available for feeds targeting the United States or United<br />
Kingdom.</div>
</div>
<div>
<div>This<br />
attribute is only available for feeds targeting the United States or United<br />
Kingdom.</div>
</div>
<div>
<div>This<br />
attribute is only available for feeds targeting the United States or United<br />
Kingdom.</div>
</div>
<div>
<div>This<br />
attribute is only available for feeds targeting the United States or United<br />
Kingdom.</div>
</div>
<div>
<div>This<br />
attribute is only available for feeds targeting the United States or United<br />
Kingdom.</div>
</div>
<div>
<div>This<br />
attribute is only available for feeds targeting the United States or United<br />
Kingdom.</div>
</div>
<div>
<div>
<p>This is used to indicate if you have a product that is only available online<br />
and not in your physical store.</p>
<p>There are only two accepted values:</p>
<ul>
<li>&#8216;y&#8217;: if any item is not available in your store to purchase.</li>
<li>&#8216;n&#8217;: if a customer can buy the posted item at your physical location &#8211; this<br />
is the default assumption.</li>
</ul>
<p><strong>When to include:</strong> Required if you&#8217;ve submitted your store<br />
locations, and you have items that you sell online but not in your physical<br />
stores.</p>
<table border="1" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td>Type</td>
<td>Boolean: y or n</td>
</tr>
<tr>
<td>Text/Tab delimited</td>
<td>y</td>
</tr>
<tr>
<td>XML</td>
<td><code>&lt;g:online_only&gt;y&lt;/g:online_only&gt;</code></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.unrealstudio.com/seo/google-base-products-feed-specification/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Steve P. Jobs, 1955-2011 &#8211; Apple’s Visionary Redefined Digital Age</title>
		<link>http://www.unrealstudio.com/seo/steve-p-jobs-1955-2011</link>
		<comments>http://www.unrealstudio.com/seo/steve-p-jobs-1955-2011#comments</comments>
		<pubDate>Thu, 06 Oct 2011 15:01:18 +0000</pubDate>
		<dc:creator>newyorkseo</dc:creator>
				<category><![CDATA[Website Marketing Tips]]></category>
		<category><![CDATA[apple ceo steven jobs]]></category>
		<category><![CDATA[steve jobs]]></category>

		<guid isPermaLink="false">http://www.unrealstudio.com/?p=574</guid>
		<description><![CDATA[Steven P. Jobs, the visionary co-founder of Apple who helped usher in the era of personal computers and then led a cultural transformation in the way music, movies and mobile communications were experienced in the digital age, died Wednesday. He was 56. The death was announced by [...]]]></description>
			<content:encoded><![CDATA[<p><a title="More articles about Steven P. Jobs." href="http://topics.nytimes.com/top/reference/timestopics/people/j/steven_p_jobs/index.html?inline=nyt-per">Steven P. Jobs</a>, the visionary co-founder of <a title="More information about Apple Incorporated" href="http://topics.nytimes.com/top/news/business/companies/apple_computer_inc/index.html?inline=nyt-org">Apple</a> who helped usher in the era of personal computers and then led a cultural transformation in the way music, movies and mobile communications were experienced in the digital age, died Wednesday. He was 56.</p>
<p>The death was announced by Apple, the company Mr. Jobs and his high school friend Stephen Wozniak started in 1976 in a suburban California garage.</p>
<p>A friend of the family said that Mr. Jobs died of complications from pancreatic cancer, with which he waged a long and public struggle, remaining the face of the company even as he underwent treatment. He continued to introduce new products for a global market in his trademark blue jeans even as he grew gaunt and frail.</p>
<p>He underwent surgery in 2004, received a liver transplant in 2009 and took three medical leaves of absence as Apple’s chief executive before stepping down in August and turning over the helm to Timothy D. Cook, the chief operating officer. When he left, he was still engaged in the company’s affairs, negotiating with another Silicon Valley executive only weeks earlier.</p>
<p>“I have always said that if there ever came a day when I could no longer meet my duties and expectations as Apple’s C.E.O., I would be the first to let you know,” Mr. Jobs said in a letter released by the company. “Unfortunately, that day has come.”</p>
<p>By then, having mastered digital technology and capitalized on his intuitive marketing sense, Mr. Jobs had largely come to define the personal computer industry and an array of digital consumer and entertainment businesses centered on the Internet. He had also become a very rich man, worth an estimated $8.3 billion.</p>
<p>Tributes to Mr. Jobs flowed quickly on Wednesday evening, in formal statements and in the flow of social networks, with President Obama, technology industry leaders and legions of Apple fans weighing in.</p>
<p>A Twitter user named Matt Galligan wrote: “R.I.P. Steve Jobs. You touched an ugly world of technology and made it beautiful.”</p>
<p>Eight years after founding Apple, Mr. Jobs led the team that designed the Macintosh computer, a breakthrough in making personal computers easier to use. After a 12-year separation from the company, prompted by a bitter falling-out with his chief executive, John Sculley, he returned in 1997 to oversee the creation of one innovative digital device after another — the <a title="Recent and archival news about the iPod." href="http://topics.nytimes.com/top/reference/timestopics/subjects/i/ipod/index.html?inline=nyt-classifier">iPod</a>, the <a title="Recent and archival news about the iPhone." href="http://topics.nytimes.com/top/reference/timestopics/subjects/i/iphone/index.html?inline=nyt-classifier">iPhone</a> and the <a title="More articles about iPad." href="http://topics.nytimes.com/top/reference/timestopics/subjects/i/ipad/index.html?inline=nyt-classifier">iPad</a>. These transformed not only product categories like music players and cellphones but also entire industries, like music and mobile communications.</p>
<p>During his years outside Apple, he bought a tiny computer graphics spinoff from the director George Lucas and built a team of computer scientists, artists and animators that became Pixar Animation Studios.</p>
<p>Starting with “Toy Story” in 1995, Pixar produced a string of hit movies, won several Academy Awards for artistic and technological excellence, and made the full-length computer-animated film a mainstream art form enjoyed by children and adults worldwide.</p>
<p>Mr. Jobs was neither a hardware engineer nor a software programmer, nor did he think of himself as a manager. He considered himself a technology leader, choosing the best people possible, encouraging and prodding them, and making the final call on product design.</p>
<p>It was an executive style that had evolved. In his early years at Apple, his meddling in tiny details maddened colleagues, and his criticism could be caustic and even humiliating. But he grew to elicit extraordinary loyalty.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.unrealstudio.com/seo/steve-p-jobs-1955-2011/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Google Panda Update &#8211; October 2011 Google Update</title>
		<link>http://www.unrealstudio.com/seo/google-panda-update</link>
		<comments>http://www.unrealstudio.com/seo/google-panda-update#comments</comments>
		<pubDate>Sat, 01 Oct 2011 13:24:42 +0000</pubDate>
		<dc:creator>newyorkseo</dc:creator>
				<category><![CDATA[Search Engine Optmization Tips]]></category>
		<category><![CDATA[google algo updates]]></category>
		<category><![CDATA[google algorithm]]></category>
		<category><![CDATA[Google Panda Update]]></category>
		<category><![CDATA[New Google Panda Update]]></category>

		<guid isPermaLink="false">http://www.unrealstudio.com/?p=553</guid>
		<description><![CDATA[Google has confirmed to WebProNews that an iteration of the controversial Panda update was launched this week. When asked directly if this occurred, a Google spokesperson told us, “yes,” then offered the following canned statement: “We’re continuing to iterate on our Panda algorithm as part of our [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignright" title="Panda Update" src="/wp-content/uploads/2011/10/google-panda-update.jpg" alt="" width="264" height="222" />Google has confirmed to WebProNews that an iteration of the controversial Panda update was launched this week. When asked directly if this occurred, a Google spokesperson told us, “yes,” then offered the following canned statement:</p>
<p><em>“We’re continuing to iterate on our Panda algorithm as part of our commitment to returning high-quality sites to Google users. This most recent update is one of the roughly 500 changes we make to our ranking algorithms each year.”</em></p>
<p>While Google did not say a specific day, one webmaster <a href="http://www.webpronews.com/daniweb-panda-2011-09">reported</a> that her site was hit on Wednesday, September 28th. That was Dani Horowtiz, who runs Daniweb, a Panda victim we’ve discussed several times before, as the site had managed a 110% Panda recovery before getting hit this week.</p>
<p>Search Engine Land is <a href="http://searchengineland.com/confirmed-google-panda-2-4-update-arrived-this-week-95222">reporting</a> that while Google “declined to share any specifics” about what kinds of pages were being targeted, unnamed sources said the update rolled out on Tuesday. The blog is calling this version 2.3.</p>
<p>Some webmasters <a href="http://www.webpronews.com/google-panda-2011-09">thought</a> maybe a Panda update had rolled out earlier this month. Search Engine Land editor Barry Schwartz <a href="http://www.seroundtable.com/google-panda-25-14051.html">asked if Panda 2.5 had hit</a> (personally, I’m not bothering much trying to keep track of the numbers). The answer turned out to be no, as Google told him there was no update taking place. According to Search Engine Land now, this latest update is actually the first true Panda update in about 10 weeks.</p>
<p>Since then, Google announced that it is <a href="http://www.webpronews.com/google-algorithm-scrapers-2011-08">testing algorithmic changes</a> for scraper sites (blog scrapers in particular). The company also released a video giving an inside look at how Google handles search algorithm tweaks:</p>
<p>&nbsp;</p>
<p><object style="width: 640px; height: 390px;" width="640" height="360" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowScriptAccess" value="always" /><param name="src" value="http://www.youtube.com/v/J5RZOU6vK4Q?version=3" /><param name="allowfullscreen" value="true" /><param name="allowscriptaccess" value="always" /><embed style="width: 640px; height: 390px;" width="640" height="360" type="application/x-shockwave-flash" src="http://www.youtube.com/v/J5RZOU6vK4Q?version=3" allowFullScreen="true" allowScriptAccess="always" allowfullscreen="true" allowscriptaccess="always" /></object></p>
]]></content:encoded>
			<wfw:commentRss>http://www.unrealstudio.com/seo/google-panda-update/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Improved handling of URLs with parameters</title>
		<link>http://www.unrealstudio.com/seo/improved-handling-urls-parameters</link>
		<comments>http://www.unrealstudio.com/seo/improved-handling-urls-parameters#comments</comments>
		<pubDate>Mon, 08 Aug 2011 18:46:18 +0000</pubDate>
		<dc:creator>newyorkseo</dc:creator>
				<category><![CDATA[Google Analytics]]></category>
		<category><![CDATA[Search Engine Optmization Tips]]></category>
		<category><![CDATA[Improved handling of URLs with parameters]]></category>
		<category><![CDATA[itemId Specifies Every URL]]></category>
		<category><![CDATA[Only crawl URLs with value=x]]></category>
		<category><![CDATA[page Paginates Every URL]]></category>
		<category><![CDATA[Site configuration]]></category>
		<category><![CDATA[URL Parameters helps you control which URLs]]></category>

		<guid isPermaLink="false">http://www.unrealstudio.com/?p=491</guid>
		<description><![CDATA[You may have noticed that the Parameter Handling feature disappeared from the Site configuration > Settings section of Webmaster Tools. Fear not; you can now find it under its new name, URL Parameters! Along with renaming it, we refreshed and improved the feature. We hope you’ll find [...]]]></description>
			<content:encoded><![CDATA[<p><img alt="" src="http://2.bp.blogspot.com/-_xJrN1KUdCc/Tiil9_5EWlI/AAAAAAAAAh4/-FVnqKXzxS8/s400/url-parameters.png" title="URL Parameters" class="alignleft" width="400" height="241" />You may have noticed that the Parameter Handling feature disappeared from the Site configuration > Settings section of Webmaster Tools. Fear not; you can now find it under its new name, URL Parameters! Along with renaming it, we refreshed and improved the feature. We hope you’ll find it even more useful. Configuration of URL parameters made in the old version of the feature will be automatically visible in the new version. Before we reveal all the cool things you can do with URL parameters now, let us remind you (or introduce, if you are new to this feature) of the purpose of this feature and when it may come in handy.</p>
<p>When to use<br />
URL Parameters helps you control which URLs on your site should be crawled by Googlebot, depending on the parameters that appear in these URLs. This functionality provides a simple way to prevent crawling duplicate content on your site. Now, your site can be crawled more effectively, reducing your bandwidth usage and likely allowing more unique content from your site to be indexed. If you suspect that Googlebot&#8217;s crawl coverage of the content on your site could be improved, using this feature can be a good idea. But with great power comes great responsibility! You should only use this feature if you&#8217;re sure about the behavior of URL parameters on your site. Otherwise you might mistakenly prevent some URLs from being crawled, making their content no longer accessible to Googlebot.</p>
<p>A lot more to do<br />
Okay, let’s talk about what’s new and improved. To begin with, in addition to assigning a crawl action to an individual parameter, you can now also describe the behavior of the parameter. You start by telling us whether or not the parameter changes the content of the page. If the parameter doesn’t affect the page’s content then your work is done; Googlebot will choose URLs with a representative value of this parameter and will crawl the URLs with this value. Since the parameter doesn’t change the content, any value chosen is equally good. However, if the parameter does change the content of a page, you can now assign one of four possible ways for Google to crawl URLs with this parameter:<br />
•Let Googlebot decide<br />
•Every URL<br />
•Only crawl URLs with value=x<br />
•No URLs<br />
We also added the ability to provide your own specific value to be used, with the “Only URLs with value=x” option; you’re no longer restricted to the list of values that we provide. Optionally, you can also tell us exactly what the parameter does&#8211;whether it sorts, paginates, determines content, etc. One last improvement is that for every parameter, we’ll try to show you a sample of example URLs from your site that Googlebot crawled which contain that particular parameter.</p>
<p>Of the four crawl options listed above, “No URLs” is new and deserves special attention. This option is the most restrictive and, for any given URL, takes precedence over settings of other parameters in that URL. This means that if the URL contains a parameter that is set to the “No URLs” option, this URL will never be crawled, even if other parameters in the URL are set to “Every URL.” You should be careful when using this option. The second most restrictive setting is “Only URLs with value=x.”</p>
<p>Feature in use<br />
Now let’s do something fun and exercise our brains on an example. </p>
<p>- &#8211; -<br />
Once upon a time there was an online store, fairyclothes.example.com. The store’s website used parameters in its URLs, and the same content could be reached through multiple URLs. One day the store owner noticed, that too many redundant URLs could be preventing Googlebot from crawling the site thoroughly. So he sent his assistant CuriousQuestionAsker to The GreatWebWizard to get advice on using the URL parameters feature to reduce the duplicate content crawled by Googlebot. The Great WebWizard was famous for his wisdom. He looked at the URL parameters and proposed the following configuration:</p>
<p>Parameter name Effect on content? What should Googlebot crawl?<br />
trackingId None One representative URL<br />
sortOrder Sorts Only URLs with value = ‘lowToHigh’<br />
sortBy Sorts Only URLs with value = ‘price’<br />
filterByColor Narrows No URLs<br />
itemId Specifies Every URL<br />
page Paginates Every URL </p>
<p>The CuriousQuestionAsker couldn’t avoid his nature and started asking questions:</p>
<p>CuriousQuestionAsker: You’ve instructed Googlebot to choose a representative URL for trackingId (value to be chosen by Googlebot). Why not select the Only URLs with value=x option and choose the value myself?<br />
Great WebWizard: While crawling the web Googlebot encountered the following URLs that link to your site:<br />
1.fairyclothes.example.com/skirts/?trackingId=aaa123<br />
2.fairyclothes.example.com/skirts/?trackingId=aaa124<br />
3.fairyclothes.example.com/trousers/?trackingId=aaa125<br />
Imagine that you were to tell Googebot to only crawl URLs where “trackingId=aaa125”. In that case Googlebot would not crawl URLs 1 and 2 as neither of them has the value aaa125 for trackingId. Their content would neither be crawled nor indexed and none of your inventory of fine skirts would show up in Google’s search results. No, for this case choosing a representative URL is the way to go. Why? Because that tells Googlebot that when it encounters two URLs on the web that differ only in this parameter (as URLs 1 and 2 above do) then it only needs to crawl one of them (either will do) and it will still get all the content. In the example above two URLs will be crawled; either 1 &#038; 3, or 2 &#038; 3. Not a single skirt or trouser will be lost.</p>
<p>CuriousQuestionAsker: What about the sortOrder parameter? I don’t care if the items are listed in ascending or descending order. Why not let Google select a representative value?<br />
Great WebWizard: As Googlebot continues to crawl it may find the following URLs:</p>
<p>1.fairyclothes.example.com/skirts/?page=1&#038;sortBy=price&#038;sortOrder=’lowToHigh’<br />
2.fairyclothes.example.com/skirts/?page=1&#038;sortBy=price&#038;sortOrder=’highToLow’<br />
3.fairyclothes.example.com/skirts/?page=2&#038;sortBy=price&#038;sortOrder=’lowToHigh’<br />
4.fairyclothes.example.com/skirts/?page=2&#038;sortBy=price&#038;sortOrder=’ highToLow’<br />
Notice how the first pair of URLs (1 &#038; 2) differs only in the value of the sortOrder parameter as do URLs in the second pair (3 &#038; 4). However, URLs 1 and 2 will produce different content: the first showing the least expensive of your skirts while the second showing the priciest. That should be your first hint that using a single representative value is not a good choice for this situation. Moreover, if you let Googlebot choose a single representative from among a set of URLs that differ only in their sortOrder parameter it might choose a different value each time. In the example above, from the first pair of URLs, URL 1 might be chosen (sortOrder=’lowToHigh’). Whereas from the second pair URL 4 might be picked (sortOrder=’ highToLow’). If that were to happen Googlebot would crawl only the least expensive skirts (twice):<br />
•fairyclothes.example.com/skirts/?page=1&#038;sortBy=price&#038;sortOrder=’lowToHigh’<br />
•fairyclothes.example.com/skirts/?page=2&#038;sortBy=price&#038;sortOrder=’ highToLow’<br />
Your most expensive skirts would not be crawled at all! When dealing with sorting parameters consistency is key. Always sort the same way.</p>
<p>CuriousQuestionAsker: How about the sortBy value?<br />
Great WebWizard: This is very similar to the sortOrder attribute. You want the crawled URLs of your listing to be sorted consistently throughout all the pages, otherwise some of the items may not be visible to Googlebot. However, you should be careful which value you choose. If you sell books as well as shoes in your store, it would be better not to select the value ‘title’ since URLs pointing to shoes never contain ‘sortBy=title’, so they will not be crawled. Likewise setting ‘sortBy=size’ works well for crawling shoes, but not for crawling books. Keep in mind that parameters configuration has influence throughout the whole site.</p>
<p>CuriousQuestionAsker: Why not crawl URLs with parameter filterByColor?<br />
Great WebWizard: Imagine that you have a three-page list of skirts. Some of the skirts are blue, some of them are red and others are green.</p>
<p>•fairyclothes.example.com/skirts/?page=1<br />
•fairyclothes.example.com/skirts/?page=2<br />
•fairyclothes.example.com/skirts/?page=3<br />
This list is filterable. When a user selects a color, she gets two pages of blue skirts:<br />
•fairyclothes.example.com/skirts/?page=1&#038;flterByColor=blue<br />
•fairyclothes.example.com/skirts/?page=2&#038;flterByColor=blue<br />
They seem like new pages (the set of items are different from all other pages), but there is actually no new content on them, since all the blue skirts were already included in the original three pages. There’s no need to crawl URLs that narrow the content by color, since the content served on those URLs was already crawled. There is one important thing to notice here: before you disallow some URLs from being crawled by selecting the “No URLs” option, make sure that Googlebot can access the content in another way. Considering our example, Googlebot needs to be able to find the first three links on your site, and there should be no settings that prevent crawling them.</p>
<p>- &#8211; -</p>
<p>If your site has URL parameters that are potentially creating duplicate content issues then you should check out the new URL Parameters feature in Webmaster Tools. Let us know what you think or if you have any questions post them to the Webmaster Help Forum.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.unrealstudio.com/seo/improved-handling-urls-parameters/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Preview the latest Google +1 button changes</title>
		<link>http://www.unrealstudio.com/seo/preview-latest-google-1-button</link>
		<comments>http://www.unrealstudio.com/seo/preview-latest-google-1-button#comments</comments>
		<pubDate>Mon, 08 Aug 2011 18:44:02 +0000</pubDate>
		<dc:creator>newyorkseo</dc:creator>
				<category><![CDATA[Search Engine Optmization Tips]]></category>
		<category><![CDATA[Google +1]]></category>
		<category><![CDATA[Google +1 button changes]]></category>

		<guid isPermaLink="false">http://www.unrealstudio.com/?p=487</guid>
		<description><![CDATA[Want to test the latest +1 features? Today we’re introducing a new option for webmasters who want to be the first to know about changes to the +1 button. Enroll in the Google+ Platform Preview, available globally, to test updates before they launch to all users on [...]]]></description>
			<content:encoded><![CDATA[<p>Want to test the latest +1 features? Today we’re introducing a new option for webmasters who want to be the first to know about changes to the +1 button. Enroll in the Google+ Platform Preview, available globally, to test updates before they launch to all users on your site. When you’re logged into the account you’ve enrolled with and you visit a page with the +1 button, you’ll see the latest preview release.</p>
<p>If you join now, you’ll be able to test the first set of updates we’ve released to Platform Preview: hover and confirmation bubbles. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.unrealstudio.com/seo/preview-latest-google-1-button/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

