# General optimizations

Optimizing your feed increases the chance of your products surfacing on various
Things to do surfaces. The general feed recommendations in this document is
applicable to all product types and across multiple surfaces.

In addition to the following recommendations, see also the following guides to
optimise for various product types and surfaces:

- [Attractions products optimization guide](https://developers.google.com/actions-center/verticals/things-to-do/guides/partner-integration/attractions-product-optimization)
- [Experiences products optimization guide](https://developers.google.com/actions-center/verticals/things-to-do/guides/partner-integration/experineces-product-optimization)
- [Operator booking module optimization guide](https://developers.google.com/actions-center/verticals/things-to-do/guides/partner-integration/obm-product-optimization)

## Provide the default adult price as the only price option

Supply the default price as the **only** price option for each product `Option`
for distinct geo criteria.

While the Things to do Feed Specification allows supplying multiple prices,
only the lowest matched price is used. To prevent accidentally displaying a
child price to users, you should only upload default adult ticket
prices.

## Provide the total price of group bookings

For products that require a minimum number of attendees (group bookings),
send Google the total price of the group booking (instead of the average single
person price).

## Provide the higher of the residence versus non-residence price

If a product has a resident price and non resident price, provide the
higher of the two prices. As a general principle, the price provided to Google
must be the price at which any adult is able to participate.

## Provide detailed product description

Google makes use of product descriptions in several ways including extracting
key information about the product as well as displaying it to the user on
certain surfaces. Writing an accurate product description improves the
chances the product is shown as well as conversions when the user clicks through
to see the details.

For more information see [Title and description guidelines](https://developers.google.com/actions-center/verticals/things-to-do/guides/partner-integration/title-guidelines).

## Localize languages to provide a better user experience

To offer a better user experience and improve click through rate, it is
recommended that you provide localized language strings.

## Treat zh-CN, zh-HK and zh-TW, zh-hans, zh-hant as separate languages

Due to differences in written character set and dialect, explicitly treat
*zh-CN* , *zh-HK* , *zh-TW* and *zh-SG* as independent languages. That is even in
the case where the same landing page is used for the different dialects,
provide separate entries for each language.

## Provide rating and other optional data to generate additional user interest

Optional informational fields such as `ratings` and `fulfillment_type` get
additional UI treatment on certain surfaces. Seeing these additional information
builds user trust, generates additional interest and improves the overall user
experience. It is recommended to include ratings if the data is
available.

The following fields are particularly important across multiple surfaces:

- `rating`
- `fulfillment_type`
- `confirmation_type`
- `related_media`

## Provide accurate POI \& product category

Points of interest information helps Things to do to more quickly and accurately
determine related points of interest of a product and thus decrease the chance
your product is incorrectly served. Product category similarly helps to
categorize your products more accurately and increase the chance your products
are shown when users browse experiences and other categorical searches.