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.

4 min readSume
All posts

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.

Sume media URL properties from the docs, read 2026-09-30.
PropertyWhat the docs say
Hostmedia.sume.com over HTTPS
ExpiryDoes not expire; expires_at is null
Cache headerpublic, max-age=31536000, immutable
AccessPublic to anyone holding the URL
Content typeFor 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

Related posts

More in Use cases

All Use cases posts

Written by Sume