FeedMender

FeedMender/Errors/Video not processed

Common rejections

Video not processed

Google accepts up to ten video links per product, and a YouTube URL is fine. A link it cannot fetch and decode — most often a non-YouTube URL that points at a page instead of the video file — is reported as not processed.

Scan your feed for free

What Google requires

Up to ten links; a file, unless it is YouTube

video_link may repeat up to ten times per product. Every value starts http:// or https://. A YouTube URL is accepted as is; only when the URL is not a YouTube link does it have to point directly at a raw video file rather than a landing page with a player. Google reports a link it cannot fetch and decode as Video not processed.

What Google does

The video is refused, the listing stays flat

A non-YouTube link that resolves to a page rather than a file, or a value it cannot read, cannot be processed, and the product simply serves without that video. Nothing looks broken, so the richer media that lifts engagement quietly never appears.

How to fix it by hand

Use a YouTube URL, or point at the file

  • Keep to ten video links or fewer per product.
  • Use a YouTube URL as is, or, for another host, link straight to the raw video file, not a page with a player.
  • Encode any non-ASCII characters and keep each URL within the length limit.

What FeedMender checks today

6 checks apply, read from the scanner's registry

The scan reads the video URLs as strings: how many are sent — video_link_too_many fires only above ten — the scheme, the encoding, the length, and whether the field holds separators but no URL. FeedMender flags a non-YouTube URL when it has an explicit file extension outside the supported list; it does not fetch the URL, inspect its response, or prove whether an extensionless URL leads to a raw video or a player page.

  • video_link_too_manyat risk
  • video_link_not_a_fileat risk
  • video_link_invalidat risk
  • video_link_non_asciiat risk
  • video_link_too_longat risk
  • video_link_emptyat risk

What the scan does not check today: FeedMender does not fetch the URL, inspect the MIME type or video bytes, or prove that the video plays. An extensionless non-YouTube URL passes because its destination cannot be determined from the string alone.

The quicker way

Let the scan read the video links

Run the free scan and it flags the video links with an unsupported file extension, bad characters, an over-long URL, or more than ten per product. The scan to identify errors is free and shows every finding before you pay anything. You only pay for the fix.

Scan your feed