Replace a Merchant Center product video: new filename and URL
Google says video_link URLs must stay stable and never be reused for another video. Each Sume trim or filter returns a new artifact URL, so a re-cut fits.
Do not overwrite the file behind an existing video_link URL. Google says URLs must stay stable and not be reused for different videos, and to change a video, change its filename and URL. Sume helps by default: each trim or filter produces a new artf_ artifact with its own URL.
Google's rules are from its Help pages, read 2026-09-30; Sume's from Video trim and Structured output.
What does Google say about changing a video?
Two statements matter. The attribute page says URLs must remain stable and not be reused for different videos. The not-processed page says a changed video should get a new filename and URL.
How does Sume's URL behavior line up?
| Sume behavior | Why it helps |
|---|---|
Trim and filter results carry a new artf_ video_url, never the source | A re-cut cannot overwrite the old file |
| Served as immutable, one-year cache | An existing URL keeps pointing at the same bytes |
| Docs: "Store the URL against your own record" | You can keep the old URL until Merchant has the new one |
What is a safe replacement flow?
Re-cut or re-filter the source so Sume returns a new URL, store it on the product record, then update the video_link value in your feed. Leave the old file in place; nothing in the docs says it must be removed. If you re-run a request, reuse the same Idempotency-Key only for the same payload, and use a new key for a different cut, so you do not get the earlier job back by accident.
Can I keep two versions live?
video_link is a repeated field of up to 10 URLs per product, so an A/B pair of cuts fits. Give each cut its own trim request and its own key.
Sources
- Video trim
- Structured output
- [Google Merchant Center: video link [video_link] (read 2026-09-30)](https://support.google.com/merchants/answer/15216925)
- Google Merchant Center: Video not processed (read 2026-09-30)
Related posts
More in Use cases
- Google Merchant Center 16 MB and 64 megapixel image limits vs Sume
Google lists no image over 64 megapixels and no file over 16 MB. Sume's gpt-image-2.5 caps output at 8,294,400 pixels; file size is not published.
- Google Merchant Center image formats: which Sume output_format fits
Google lists JPEG, WebP, PNG, GIF, BMP and TIFF for product images. Sume's Image API lists png, jpeg, webp and svg; svg is not on Google's list.
- Google Merchant Center image rules: no watermark, price or CTA overlay
Google's image page bars promotional elements or content that covers the product. How to ask Sume's image API for a clean product image, and what to check.
- Merchant Center product video 720p minimum: what to request
Merchant Center video_link needs at least 720p (1280x720). Sume's generated video defaults to 720p; probe a file first, then conform with Video trim if needed.
Written by Sume