Encapsulates all the listings in the feed. This is the document root tag of the XML file. Acts a container for data shared b/w in listings in the feed. As of 2009/04, this is just coupons. The language used in this feed. The value must be an ISO 639 lowercase 2-letter language code (http://www.w3.org/WAI/ER/IG/ert/iso639.htm#2letter). For example English is en, French is fr. The datum in use for geographic coordinates. Currently supported values: TOKYO, WGS84 If this tag is absent, WGS84 is assumed. Encapsulates all the information related to a single business. Unique ID of the listing on your site. The name of the business. Address of the business, including street number, street name, town/city, state/province/region, and postal code. Example: 1600 Amphitheatre Parkway, Mountain View, CA 94043 The type of address data provided. A particular component of an address. Example: 1600 Amphitheatre Parkway The type of address component provided. Example: addr1 The country that this listing is located in. The value must be a ISO 3116 uppercase 2-letter country code (http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html). For example, United States is US and Canada is CA. The latitude that corresponds to the location of the listing. For example, the latitude for 1600 Amphitheatre Parkway, Mountain View, CA 94043 is 37.423738. The longitude that corresponds to the location of the listing. For example, the latitude for 1600 Amphitheatre Parkway, Mountain View, CA 94043 is -122.090101. Flags about the location of the listing. Additional information about the geocode. Indicates that the latlong of the business was verified / moved to the right place. The phone number of the business. The type of the phone number. Main voice telephone number. Toll free telephone number. Fax telephone number. Telecommunications Device for the Deaf telephone number. Mobile telephone number. This attribute is specifically for compliance with regulations in Switzerland. According to Swiss law, businesses can request that their phone numbers must not be used for cold calls. Direct marketers must honor this request. YP providers must mark these number in their directories. The business does not want to receive cold calls on this number. The business does not object to cold calls on this number. This attribute is specifically for compliance with regulations in Switzerland. According to Swiss law, premium rate numbers must be labelled with its per minute cost. If the attribute exists, then its value must conform to the format "(CHF x.xx/Min.)", for example "(CHF 1.19/Min.)". The whole feed will be rejected if it contains even a single premium_rate_label that does not conform to the format. The category that the listing belongs to (based on your site's taxonomy). Example: Restaurants - Chinese One listing can contain any number of categories in any number of languages. Defines the language of the current category. If it is missing then the global language is used (defined in listings -> language). It is a good practice to leave out this attribute if all the categories are in the same language. Encapsulates all the content relevant to a listing. Encapsulates a block of text about the listing such as a description or a restaurant menu. The type of the text. If the contents are a general description of the business. If the contents are an offer or coupon. If the contents are are a restaurant menu. Encapsulates a single review of the listing. The type of the review. Review was written by a member of your staff. Review was written by a user of your site. Encapsulates an image relevant to the listing. The image type. The URL of the full-sized image The width of the image The height of the image Encapsulates a set of attributes about the listing. All attributes must be displayed on a single page on your site. If you have multiple pages that contain attributes, then include each page as a separate attributes tag. A single piece of structured information about the listing. For example, if the name is Business Hours then the value can be Mon-Fri 9am-5pm. If the name is Payment Types Accepted, then the value can be Cash, Visa, Mastercard. Use the names and values that appear on your site. The name of the field displayed on your site. The importance of the fact, which may effect the order in which facts are displayed in search results. A single piece of structured information about the listing, which should be hidden from users, because it is used for some internal purpose. The name of the hidden field. The URL of the page on your site that contains the content. We will link the teaser on Google Local to this page. The URL of the mobile page that contains the content. The name of mobile operator. The markup language of mobile website. A short summary of the content. The name of the author of the content. The value can either be a user name or a full name in the format "Firstname Lastname". The entire text of a review or description of the listing. Can contain escaped HTML The official website of the business. An email address associated with a business listing. If applicable, the rating score associated with the review. The value should reflect how the rating appears on your site. If there are multiple ratings for a single review, then use a separate rating tag for each rating. Type of the rating such as "Service" or "Food Quality". If there is only one rating score in the review, then name may be omitted. The date the listing or piece of content was created. Structured coupon information. A URL to fetch a PNG, JPG, or GIF image to appear in the coupon. The image should be 120x120, but will be proportionately resized if it is larger than this. Whether the coupon can be discovered by search. Setting this value to false means that the content will not be included in the index. This allows the provider some control of how the coupon is promoted. E.g, they might be excluded from the index, but accessible via ads. Defines data about the coupon feed provider. The name of the business as it should appear on the coupon. This is useful when coupons are shared between related businesses, but the business name on the coupon should not differ. This is printed on the coupon, and is used for clerks to recognize the offer and enter it into a point of sale system. Unique coupon id. Coupon elements from the same coupon provider must have different coupon id. Refers to another coupon in the feed, one that is defined earlier in the feed file. The idref value must match the id of an earlier defined coupon. A coupon may have an idref, an id or both. Having an id without an idref indicates that the coupon is standalone, and does not inherit fields from any other coupon. Having an idref without an id indicates the coupon inherits its fields from the referenced coupon, and keeps the id of the referred coupon. Having both means that the coupon inherits its fields, but uses the new id. When an idref is used, the referenced coupon must be in either the shared content or the current listing. Succinct summary of offer and major restrictions. For example: "$5 off large pizza". The offer is required for all coupons, though this is not enforced by the XSD because coupons may be defined by reference to other coupons, in which case the offer does not need to be supplied. Detailed descriptions of the coupon restrictions. The first day on which the coupon can be used. The coupon will not be displayed before this date. The last day on which the coupon can be used. The coupon will not be displayed after this date. The last date on which the coupon can be presented. It is optional. This will be printed on the coupon. It is optional. The number of days after printing that a coupon is valid. It is optional. If the coupon can't be redeemed from a PC, this field must be 'no' . Default value is 'yes'. If the coupon can't be redeemed from a mobile phone, this field must be 'no'. Default value is 'yes'. Information about the organization providing coupon information. This is typically only provided by third party providers who are providing listings coupons, and wish to apply their own branding to coupons. The name of coupon provider organization. The URL for the logo of your organization. This should be a GIF, JPG, or PNG image, and is allowed to be up to 100 pixels wide and 21 pixels high. It may not contain animation. The URL of the website for the coupon provider organization. Supported barcode types. Each type has restrictions on the type and amount of data that can be encoded. At most two barcodes are allowed for each coupon. In addition, there is a limit on the total amount of data that can be encoded in barcodes on a coupon. This limit depends on the the rendering style of the coupon, but is currently set at 32 bytes. UPC-A barcode data. This consists of a total of 11 or 12 decimal digits. The optional last digit is a check digit. If it is not supplied then we will calculate it. EAN-13 barcode data. This consists of a total of 12 or 13 decimal digits, with the first two digits being a number system that corresponds to coupons in the appropriate locale. The last digit is an optional check digit (if not supplied, we will supply it). EAN-128 barcode data, also known as GS1-128. The specification of these is beyond the scope of this document, and the supplier should refer to the UCC standard. Formats 1-4 are supported. Code 128 barcode data. The payload consists of up to 32 ascii characters. Code 39 barcode data using up to 20 characters from a restricted character set. No checksum is required in the data. Retailer's club card for coupon redemption. This is an experimental feature, and is not to be used by LEC feed partners without express agreement from Google. Display name of the club card URL for the logo of the club card. Message text for call to action to add to club card (e.g. "Add to Card") URL for handling user's action to add coupon to club card. URL for the store logo. Club card id. Refers to another club card in the feed, one that is defined earlier in the feed file. A club card may have an idref, an id or both. Having an id without an idref indicates that the card is standalone, and does not inherit fields from any other card. Having an idref without an id indicates the card inherits its fields from the referenced card, and keeps the id of the referred card. Having both means that the card inherits its fields, but uses the new id. When an idref is used, the referenced card must be in either the shared content or the current listing.