> 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/changelog/2026/july/google-shopping-automatic-migration-from-content-api-to-merchant-api-complete.md).

# Google Shopping: automatic migration from Content API to Merchant API complete

July 1, 2026

### What’s changed?

The automatic migration from Content API to Merchant API is now complete.

* New Google Shopping API channels now create a data source automatically on the first run.
* You no longer need to create a data source manually in Merchant Center beforehand.
* New data sources in Google use this format: `Channable API - {feed_label} - {target_language}`

### What you may still see in Google

You may still receive emails from Google about migrating from Content API.

Older data sources can also still appear as **Content API** in Google Merchant Center. This can show in both the data source name and the **Source** field, even when the channel already runs on Merchant API.

In both cases, **no action is needed**. Your Google Shopping API channel(s) should be on the Merchant API.

### How to verify your migration status

Use Channable as the source of truth for migration status.

1. In your Channable account, open **\[your project]** > **Channels**.
2. Click the **Settings** step for your \[**your Google Shopping channel]**.
3. At **Linked seller account**, click <i class="fa-pen-to-square">:pen-to-square:</i> **Edit**.
4. If your Google Shopping channel shows **Merchant API** with a <i class="fa-square-check">:square-check:</i>, your channel is migrated and working on the new API.

<figure><img src="https://199992526-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCelgbro04804WOVz6ZV0%2Fuploads%2F4FdEwSAopAfbzYE9yezM%2Fimage.png?alt=media&amp;token=f5a5e60c-3f19-4555-8870-3fc68fa4c94c" alt=""><figcaption></figcaption></figure>


---

# 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/changelog/2026/july/google-shopping-automatic-migration-from-content-api-to-merchant-api-complete.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.