Google opened a request form this week letting merchants ask for more time before the Content API for Shopping shuts down on August 18, 2026. The API is being replaced by the Merchant API, and merchants who miss the deadline without an approved extension face what Google calls service degradation. That degradation is not confined to paid campaigns. Google’s own notice says it can reach organic listings too.
The form, live now on the Merchant API documentation pages, asks applicants for an email address, a company or partner name, a website, the Google Cloud project IDs involved, and a written business justification. Applicants must also pick an extension date: October 15, 2026, or, for those needing more runway, December 31, 2026. Google says a support team will reach applicants at the email address they submit, a detail that signals review rather than automatic approval. Search Engine Roundtable first reported the live form on July 20, 2026.
Google’s own warning is explicit about the cost of doing nothing: “If you do not apply for an extension, your extension is not granted, or you exceed your approved extension date, you will experience service degradation. This will directly impact your API integration and may impact performance across both your advertising and organic experiences.” That line sits atop the Merchant API documentation, not buried in a support thread.
The phrase “organic experiences” is the detail most merchants will skip past. Google Shopping surfaces free product listings pulled from the same product feed data that also powers paid campaigns, and the Content API for Shopping has fed both surfaces for years. A merchant who treats the August cutoff as a PPC problem risks losing more than ad impressions. Free listings in the Shopping tab and in search results can degrade right alongside the paid feed.
Not every merchant needs to file. A team already running its catalog through the Merchant API, or one close to finishing that migration before August, gains nothing from the form and adds a review step that can stall on a missing project ID or a thin justification. The form is built for merchants with custom integrations, multi-market catalogs, or a dependency on a Content API endpoint the Merchant API has not yet replicated.
Assuming the extension will be approved is the riskier bet. Google frames the request as something its support team evaluates, not something the form guarantees on submission, and neither listed date functions as a default fallback. A merchant that files for the later date and treats it as secured, without confirmation back from Google, could still be running on a shut-off API on August 18 with no paid or organic Shopping presence to fall back on.
Any team still dependent on the Content API for Shopping should treat the next four weeks as a migration sprint, not a filing exercise: finish the Merchant API cutover wherever the integration allows it, and reserve the extension request for the catalogs that genuinely cannot move in time.
Search Engine Roundtable, reporting by Barry Schwartz, first covered the extension request form on July 20, 2026.
