What changed: Google says access to the Content API for Shopping continues until August 18, 2026, after which the API will be shut down. The replacement is Merchant API. Google does not publish an exact shutdown time or timezone, so treat August 18 as an urgent migration deadline without claiming that every old endpoint is already unavailable.
This matters beyond engineering. Content API integrations can sit underneath product uploads, inventory updates, diagnostics, reports, local inventory and Google Ads Scripts. If that connection stops working, the marketing symptom may be stale product data or missing automation rather than an obvious “API migration” alert.
I reviewed Google’s Merchant Center announcement, the Google Ads developer notice and the current migration documentation on August 18, 2026. This guide separates what Google confirms from what store owners, agencies and developers still need to verify in their own setup. It complements DMT’s broader Google Ads automation guide; it does not replace campaign-level bidding or targeting checks.
What is Merchant API, and what does Google confirm?
- Merchant API is now the primary programmatic interface for managing Merchant Center accounts and product data across organic and advertising experiences.
- Google says it will provide access to Content API for Shopping until August 18, 2026, after which Content API will be shut down.
- Google Ads Scripts added Merchant API as an Advanced API, giving script users a migration path away from the retiring Content API service.
- Merchant API is a redesign, not a drop-in hostname swap. It uses modular sub-APIs, resource names, explicit data sources and different product-management methods.
- Google warns that full backward compatibility is not guaranteed for similar features because fields and method availability can differ.
The unknown is equally important: Google’s cited pages do not specify an hour or timezone for shutdown. They also do not prove that a particular merchant account, script or endpoint has failed. Check your integration and logs directly. Do not turn the calendar date into an unsupported account-level outage claim.
First decide whether your store is actually affected
| Current product-data setup | Likely responsibility | Immediate check |
|---|---|---|
Custom code calling shoppingcontent.googleapis.com or Content API v2.1 | Your engineering or integration owner | Inventory every method, credential, job and dependent report; map each to Merchant API. |
| Google Ads Script using the Content API Advanced API | Script owner or agency | Open the script, identify Content API calls and test the Merchant API Advanced API replacement. |
| Shopify using the Google & YouTube app | Technology provider, according to Google’s example | Confirm the app is current and healthy; do not rebuild a provider-managed integration without evidence. |
| Another ecommerce platform, feed tool or agency connector | Provider or contracted integration owner | Request written migration status, affected surfaces, testing evidence and support escalation details. |
| Scheduled file feed or autofeed with no API calls | Feed owner | Confirm there is truly no hidden API dependency for inventory, diagnostics, reports or supplemental data. |
Google explicitly says merchants using a third-party technology partner to sync product data, such as the Google & YouTube app on Shopify, do not need to perform the API migration themselves because the provider handles it. That is not a universal promise for every plugin or feed vendor. Treat it as a reason to verify ownership, not a reason to ignore the deadline.
Merchant API migration checklist
1. Build an endpoint and workflow inventory
Search code, Apps Script projects, server jobs, cloud functions and vendor documentation for Content API hostnames, client libraries and v2.1 resource names. List the business workflow behind each call: product insertion, product status, account management, inventory, reports, promotions, data sources or notifications.
Do not inventory only the daily product upload. A migration can appear successful while diagnostics, local inventory or a reporting job remains tied to the old API. Assign an owner and validation result to every workflow.
2. Map Content API methods to Merchant API sub-APIs
Merchant API is modular. Google recommends identifying the features you need and prioritising Accounts, Products, Data sources and Reports, adjusted for the integration. Inventory-heavy businesses may need the Inventories sub-API earlier. The new request structure includes the sub-API, version, resource name and method rather than reusing the old Content API path.
This is the same operational principle behind DMT’s production-control guide for AI workflows: map dependencies first, then migrate one bounded surface at a time with observable checks.
3. Register the Google Cloud project
Google’s migration guide requires a link between the Google Cloud project and the primary Merchant Center account through Developer Registration. This is a one-time registration for each Cloud project used with Merchant API. Confirm that the right Merchant Center account, Cloud project and responsible developer email are linked before blaming method or data errors.
4. Redesign product writes around ProductInput and Product
In Merchant API, ProductInput is used to insert, update and delete submitted product data. The read-only Product resource represents Google’s processed result, including product status and issues. The old separate productstatuses service is removed; status information is included with the processed product.
Every product-input write now requires an explicit dataSource. This creates more control, but it also creates a failure mode: sending a product to the wrong primary source can move it away from the existing source and its rules. Google calls this “offer stealing.” Backfill the correct data-source name for each product and verify source ownership before updates or deletes.
5. Preserve product identity
Keep the same offerId for the same product. Google warns that changing it can lose product history. Merchant API also changes identifiers from colon-delimited Content API IDs to resource names using components such as content language, feed label and offer ID, separated with tildes. The channel segment is no longer part of the Merchant API product identifier.
Prefer the returned name value rather than manually constructing resource names. Product identifiers containing reserved characters may require unpadded base64url encoding. Test edge-case SKUs, not only clean alphanumeric examples.
6. Replace custom batches and validate throughput
Merchant API does not support Content API’s customBatch method. Google directs developers to asynchronous calls or HTTP batching, and its client libraries default to gRPC. That changes error handling, retry behaviour and throughput assumptions. Load-test with realistic catalog sizes, preserve per-item error visibility and confirm that retry logic cannot duplicate or overwrite product inputs.
7. Test business journeys, not just HTTP success
- Insert or update a controlled product input.
- Read the processed product and inspect product-status issues.
- Verify price, availability, image, landing-page URL, feed label and target destinations.
- Confirm the intended data source owns the product.
- Run inventory, reporting, account and diagnostics workflows that depend on the integration.
- Compare counts and a sample of identifiers between old evidence and the Merchant API result.
- Monitor Merchant Center diagnostics, application logs, error ratios and job completion.
An HTTP 200 proves only that a request succeeded. It does not prove that the product is eligible, current or attached to the correct source. For measurement hygiene after the feed layer is stable, use DMT’s Search Console platform-property guide to keep organic discovery analysis separate from Merchant Center/API health.
Key technical changes to include in migration QA
| Area | Content API pattern | Merchant API pattern | QA risk |
|---|---|---|---|
| Base URL | shoppingcontent.googleapis.com/content/v2.1 | merchantapi.googleapis.com/{SUB_API}/{VERSION} | A hostname-only replacement misses resource and method changes. |
| Product writes | products.insert/update/delete | productInputs.insert/patch/delete | Writing to the wrong resource or assuming old update semantics. |
| Processed status | Separate productstatuses service | Status included in read-only Product | Old diagnostics job silently stops. |
| Data source | Implicit Content API source could be created | Explicit dataSource required for writes | Wrong source can move an offer and change rules. |
| Product ID | Colon-delimited ID including channel | Resource name; tilde-delimited product part; no channel segment | Broken lookups, reserved-character errors or duplicate identity. |
| Batching | customBatch | Async calls or HTTP batching | Throughput, retries and per-item errors change. |
| Price type | Decimal string plus currency | amountMicros plus currencyCode | Unit conversion or field-mapping errors. |
What marketers should monitor after migration
- Freshness: Are price, availability and inventory timestamps moving as expected?
- Coverage: Do product and processed-status counts match the intended catalog scope?
- Diagnostics: Have new item issues, destination exclusions or disapprovals appeared?
- Ownership: Are products attached to the intended primary and supplemental data sources?
- Automation: Are every scheduled job, Google Ads Script and report completing without legacy calls?
- Change log: Can the team trace which sub-API, method and catalog segment moved in each release?
Do not diagnose campaign performance from an API migration alone. Product-data disruption can affect eligibility and freshness, but changes in spend or return can also come from bidding, targets, auctions and budgets. Review those separately with the current Google Ads target-bidding checklist and the Google Ads language-targeting migration guide.
A safe rollout plan when the deadline has arrived
If migration is incomplete, avoid a blind full-catalog cutover. Google recommends testing methods, validating simple user journeys, implementing one sub-API or method at a time, rolling out to a small business segment and monitoring continuously. Prioritise the paths that keep products accurate and diagnosable, then move lower-risk reporting or ancillary features with the same evidence trail.
- Freeze unrelated feed and catalog changes so failures remain attributable.
- Snapshot job success, product counts, data-source mappings and representative SKUs.
- Migrate a controlled segment with the correct Merchant API sub-APIs.
- Compare submitted inputs, processed products, issues and destination status.
- Expand only after error ratios and business checks remain stable.
- Keep a rollback or containment path for your own code, but do not assume Google’s retired API will remain available as that fallback.
The pattern is similar to DMT’s Imagen API migration checklist: inventory exact dependencies, preserve a baseline, test replacements and record what the vendor has not confirmed. The product domain differs, but the release discipline is the same.
Frequently asked questions
Is Content API for Shopping already shut down?
Google says access continues until August 18, 2026 and that the API will be shut down after that date. The cited pages do not give an exact time or timezone. Check your calls and logs rather than claiming universal shutdown from the date alone.
Do Shopify merchants need to migrate code?
Google specifically says merchants using a third-party partner such as the Google & YouTube app on Shopify do not need to perform the API migration because the provider handles it. Confirm that the correct app is connected and healthy. Do not generalise this statement to every Shopify app or custom connector.
Are file feeds and autofeeds affected?
Merchant API can complement file and autofeed upload methods. A store using only those methods may not depend on Content API for its main upload. Still audit hidden API dependencies for inventory, reports, status, supplemental data or automation before declaring the store unaffected.
Can I just change the API hostname?
No. Merchant API changes resource structure, versions, methods, identifiers, data-source requirements, product/status handling, price fields and batching. Treat it as a mapped migration with tests, not a string replacement.
