> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/list-advertise/google/list-items-on-google-shopping/rules-to-meet-google-shoppings-requirements.md).

# Rules to meet Google Shopping’s requirements

Google Shopping has specific requirements for listing your products. In Channable, the [**Quality** step](/list-advertise/list-on-channels/set-up-a-feed/set-up-a-feed-quality-step.md) of setting up a feed indicates how your product data meets these requirements.

Use these rules to meet Google’s requirements so that you can improve the quality of your feed and list your products successfully.

{% hint style="success" %}
**Tip:** [Rules](/manage-improve-product-data/rules-bulk-edit-and-enrich/rules-in-channable.md) help you to improve your feed quality and meet the requirements of your chosen export channel.
{% endhint %}

### **Exclude items with invalid Global Trade Item Numbers (GTINs)**

Google Shopping requires products to have valid GTINs. To ensure all your products have valid GTINs, create a rule using 'exclude' that filters out products with invalid GTINs. This rule requires that you have a GTIN or EAN field in your product data.

<figure><img src="https://content.gitbook.com/content/F8GepmoSonQRG6RnHOxJ/blobs/MigV3uVbpfXePmIAFY40/27528533008018" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Note:** Make sure your internal data field for GTIN or EAN codes is set to type GTIN in your project fields settings ( **Setup > Project fields**).
{% endhint %}

### **Exclude items without an image link**

Google Shopping requires all products to have a working image link. Use 'exclude' to remove products that don't have an image link.

<figure><img src="https://content.gitbook.com/content/F8GepmoSonQRG6RnHOxJ/blobs/eQ1BUIRo9cIqqURWNYPH/27528525618322" alt=""><figcaption></figcaption></figure>

### **Remove HTML tags from descriptions**

Google Shopping does not allow HTML tags in product descriptions. Use the [modify text action](/manage-improve-product-data/rules-bulk-edit-and-enrich/how-to-use-actions-then-in-rules/rule-action-modify-text.md) to remove the HTML.

<figure><img src="https://content.gitbook.com/content/F8GepmoSonQRG6RnHOxJ/blobs/zCi8poHho6SucF3c5nPe/27528533012114" alt=""><figcaption></figcaption></figure>

### **Set out of stock items to unavailable**

Google Shopping requires the field availability. Create this rule to update the availability status of items in your feed, so that out of stock items are not listed as ‘available’.

<figure><img src="https://content.gitbook.com/content/F8GepmoSonQRG6RnHOxJ/blobs/VeTLs6PCZLB9tbhL8PLB/27528533016466" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Note:** Do not exclude products that are out of stock, as Google Shopping works with the availability status of the products.
{% endhint %}

### **Trim titles to maximum allowed length**

Google Shopping has a maximum length for product titles. Create a rule to edit your titles to make sure that they meet this length requirement.

<figure><img src="https://content.gitbook.com/content/F8GepmoSonQRG6RnHOxJ/blobs/WOlwC0PtWuJ8LJlCFNmi/27528533017234" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Note:** 'Trim on words' breaks up the sentence by cutting out complete words when the maximum number of words is reached. This method leaves the words intact. Use the option 'trim directly' to break off a word when the maximum character length has been reached.
{% endhint %}

### **Use cases for rules for Google Shopping**

|                 |                                                            |                                                                                                                                                                                                |
| --------------- | ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Data Action** | **Purpose**                                                | **Example**                                                                                                                                                                                    |
| **Transform**   | Adapt your data to meet Google's specific format needs.    | <p>- Change the value <strong>'available'</strong> to <strong>'in\_stock'</strong>.<br>- Change value of items with stock value <strong>'0'</strong> to <strong>'out\_of\_stock'.</strong></p> |
| **Enrich**      | Fill in missing data for a more complete product listing.  | <p>- Take color value from a title and add it to a newly created <strong>'color'</strong> field.<br>- Add a <em>brand</em> value to your title.</p>                                            |
| **Filter**      | Remove unsuitable products from your Google Shopping feed. | Remove products with an invalid GTIN or missing image link.                                                                                                                                    |
| **Filter**      | Remove products you don't want to list on Google Shopping. | Remove items with a low margin that you don't want to advertise.                                                                                                                               |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpcenter.channable.com/list-advertise/google/list-items-on-google-shopping/rules-to-meet-google-shoppings-requirements.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.