541.201.9965 Support_Email
Website
Contents
:
Search:
Home > Channels (Feeds) > Google Shopping > Google Shopping - Feed Fields

Google Shopping - Feed Fields

How DotFeed helps you to succeed when passing data to Google.

Please read Google's feed specification in detail here



Google field: "id"

How DotFeed behaves:
DotFeed will generate this for you. This field is (must be) unique and should not be touched. It is built from productID - variantID - size - color. The Product Mapping rule allows you to populate the "id" but this should be treated with immense care. Please let DotFeed build your "id".


Google field: "title"

How DotFeed behaves:
Defaults to Variant Name unless blank, in which case the Product Name is used. This needs thought, since some merchants (is this you?) have used variant names such as "pack of 2" or "16 oz". If you have done that, then realize that DotFeed will, by default, feed exactly that to Google. You can set a rule, easily, to concatenate your product name and your variant name.


Google field: "description"

How DotFeed behaves:
Defaults to the content that you have stored in the tab called "HTML-Free Description" (labeled "Product Feed" prior to version 9.5)  unless it's blank, in which case the product description is used. Beware - Google accepts, but doesn't translate, HTML. You need to create a description which is free of HTML for Google.


Google field: "google product category"

How DotFeed behaves:
Required for apparel industry, and ALWAYS recommended. DotFeed leaves this blank by default (so be sure to set up rules).


Google field: "product type"

How DotFeed behaves:
DotFeed will extract and feed this, using your category and sub-category names. On Google's instructions, only ten category paths can be fed, so we truncate after that.


Google field: "link"

How DotFeed behaves:
DotFeed pulls your product page URL, unless you are choosing to use mini-sites, in which case DotFeed will generate a URL for you. You can use rules to change the 'link' but it isn't recommended.


Google field: "mobile link"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content). As long as you are using AspDotNetStorefront's responsive design, or AspDotNetStorefront's mobile commerce engine, you won't need to use this output field.


Google field: "image link"

How DotFeed behaves:
DotFeed pulls the default image from your product page. (The "medium" image link is fed by default, and works regardless of filename override.) Please note that Google put a new set of image quality recommendations in place in Summer 2014 and you may want to check the quality of your images.


Google field: "additional image link"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content)


Google field: "condition"

How DotFeed behaves:
For every release of AspDotNetStorefront since 8.0.1.2, the storefront software gives you a product level field called "condition" which defaults to 'new'. DotFeed has nothing to collect for ML 8 version 8.0.1.2 and earlier, and so will leave this blank. Be sure to use the DotFeed rules engine to populate this mandatory field.


Google field: "availability"

How DotFeed behaves:
Please see our article here about inventory and it's availability setting. You can use rules to change the value - from September 30th 2014, Google accepts just three values: 'in stock', 'out of stock' and 'preorder'.


Google field: "availability date"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content)


Google field: "price"

How DotFeed behaves:
DotFeed pulls the list price of each product. If you are using a 'link' which is a mini-site, then you can safely use rules to change the selling price at Google - the mini-site will always reflect the price you are feeding, rather than your in-store price.


Google field: "sale price"

How DotFeed behaves:
DotFeed pulls the value from your 'sale price' - be careful to make sure that you don't have a zero value in the sale price field of your storefront - DotFeed is very literal and if you set a sale price of zero, then Google could easily end up selling your product free of charge!


Google field: "sale price effective date"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content). This is only necessary if you are planning a sale ahead of time. Format is very important, so please be sure to read Google's feed specs.


Google field: "brand"

How DotFeed behaves:
DotFeed will extract and feed this from the manufacturer field. Google says "don't use your company name unless you really are manufacturing the product."


Google field: "gtin"

How DotFeed behaves:
Since 9.4, AspDotNetStorefront has provided a variant-level facility for you to store a 'GTIN' - this is normally UPC / ISBN / EAN / JAN . Be very careful not to invent, or mis-type, a value. At all times, Google wants you to help them either: identify your product/bundle using a GTIN ; or identify it using a combo of Manufacturer and MPN; or claim that no unique identifier exists.


Google field: "mpn"

How DotFeed behaves:
DotFeed, by default, will populate this field with the product-level MPN concatenated with the variant-level MPN.


Google field: "identifier exists"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content). By default, DotFeed and Google assume 'TRUE' so if you are selling completely unique, hand-made items then remember to make a rule to insert FALSE.


Google field: "apparel"

How DotFeed behaves:
There are a number of important fields that are treated separately for items which are 'apparel'. Size and color, for example, are treated differently. Fields that should be fed for apparel items (but are not relevant for other item types) include: gender; age-group; size type; size system. None of these fields are populated from your store as a default, so you will need to use rules carefully to insert required data.


Google field: "item group id"

How DotFeed behaves:
This is an important way to connect, for Google, the 'items' that are generated out of variants and attributes. DotFeed will generate this for you and it is important that you do not change the auto-generated value.


Google field: "color"

How DotFeed behaves:
DotFeed will extract and feed this from attributes. If you are selling apparel items, but you are not using attributes, then you will need to use rules to populate the color value.


Google field: "material"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content)


Google field: "pattern"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content)


Google field: "size"

How DotFeed behaves:
DotFeed will extract and feed this from attributes. If you are selling apparel items, but you are not using attributes, then you will need to use rules to populate the color value.


Google field: "tax"

How DotFeed behaves:
You should set this up in the Google Merchant Center.


Google field: "shipping"

How DotFeed behaves:
It is recommended that you should set this up in the Google Merchant Center.


Google field: "shipping weight"

How DotFeed behaves:
DotFeed will extract and feed this from your AspDotNetStorefront 'weight' value, and will not use the attribute-level weight delta.


Google field: "shipping label"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content)


Google field: "multipack"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content)


Google field: "is bundle"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content)


Google field: "adult"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content)


Google field: "adwords grouping"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content)


Google field: "adwords labels"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content)


Google field: "adwords redirect"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content)


Google field: "custom label 0"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content)


Google field: "custom label 1"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content)


Google field: "custom label 2"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content)


Google field: "custom label 3"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content)


Google field: "custom label 4"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content)


Google field: "excluded destination"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content)


Google field: "expiration date"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content)

Google field: "promotion ID"

How DotFeed behaves:
DotFeed leaves this blank by default (so be sure to consider any rules you want to use to generate content)


See also


Was this information helpful?YesNo