> 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/css/readme/free-listings.md).

# Free Listings

Show eligible products across Google without paying for ads with Channable CSS.

Free Listings are a Google Shopping feature that allows eligible products to appear across Google without paid advertising.

They're a great way to drive shoppers to your online store from Google Search, Shopping, Images, Maps, Lens, YouTube, and other Google surfaces at no additional cost to your business.

#### Benefits of Free Listings

Free Listings can help you:

* Reach shoppers without an additional advertising budget.
* Show product details, including price and availability, in Google results.
* Increase visibility alongside paid Shopping ads.

Google uses your product data to match eligible products with relevant shopper searches. Free Listings do not guarantee product visibility.

#### Free Listings with Channable CSS

Channable CSS lets you use Channable as your Comparison Shopping Service for Free Listings in Europe. Select Channable CSS in Google Merchant Center to use it for this destination.

{% hint style="info" %}
Free Listings can only be enabled for one CSS per unique website domain. 
{% endhint %}

<br>


---

# 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/css/readme/free-listings.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.