Merchant Center "Video not processed": use a raw MP4 URL
Fix Merchant's "Video not processed" by submitting a URL to a raw video file, not a page with a player. A media.sume.com MP4 URL is a direct file link.

For "Video not processed" in Merchant Center, Google says to make sure the URL points to a raw video file, not a landing page containing a video player. A Sume video result gives you a media.sume.com HTTPS URL for the file itself, which fits that description.
Google's steps are from its "Video not processed" Help page, read 2026-09-30. Sume's URL behavior is from Runs and Structured output.
What does Google say to try?
The page lists four fixes: check the URL format and video_link requirements, point to a raw video file rather than a page with a player, use YouTube URLs if you do not host videos directly, and change the filename and URL when the video changes.
Is a Sume video URL a raw file?
Yes, as the docs describe it: each artifact in a result has a url and a content_type such as video/mp4, and media URLs are durable media.sume.com HTTPS URLs. Give Merchant that artifact url, not a link to a page in your own app that embeds it.
| Property | What the docs say |
|---|---|
| Host | media.sume.com over HTTPS |
| Expiry | Does not expire; expires_at is null |
| Cache header | public, max-age=31536000, immutable |
| Access | Public to anyone holding the URL |
| Content type | For example video/mp4 |
Why does public access matter here?
Google's video_link page says Googlebot must reach the video without logins or special permissions. A URL that is public to anyone holding it meets that, and it also means anyone with the link can fetch the video, so do not use it for private footage.
What if it still fails?
Recheck the file against the attribute limits: length, ratio, resolution and size. See cutting to length.
Sources
- Runs
- Structured output
- Google Merchant Center: Video not processed (read 2026-09-30)
- [Google Merchant Center: video link [video_link] (read 2026-09-30)](https://support.google.com/merchants/answer/15216925)
Related posts
More in Use cases
- Google Play preview video length: the first 30 seconds
Play Console says only the first 30 seconds of a preview video autoplays. Trim a lead 30-second cut, and review its opening stills, with Sume.
- HeyGen look packs vs Sume: a new avatar per look
HeyGen's POST /v3/avatars/looks adds looks to an avatar. Sume has no look-pack endpoint: make one avatar per look and steer the scene with a prompt.
- Listing video with an AI avatar: HeyGen for Real Estate, and Sume
HeyGen launched a real estate offer for listing videos. With Sume you can build one from an avatar, a property photo as the scene and a 4-60 second script.
- Hinglish text to speech API: romanized Hindi with language hi
For romanized Hindi or Hinglish on Sume TTS, send language `hi` even though the text is Latin script, and pin a Sonic model id on the Router.
Written by Sume