twimco.Let’s talk ↗︎
Menu
Field notes / Commerce

Google Merchant Center now takes product videos in the feed. Start with five products that need explaining

Some products sell themselves in a photo. Others need ten seconds of someone folding, pouring or zipping them. Google just added a place in your product feed for exactly that clip, with a few rules that will trip up the usual way stores host video.

Editorial engraving of a sunny ceramics studio where a potter films a mug on a turntable while an assistant takes notes beside a laptop.

Since about November 7, 2026, Google's Merchant Center product data specification lists an optional video_link attribute. It takes a YouTube URL or a direct link to a raw video file that Googlebot can fetch, 6 to 240 seconds long, 720p or better, with no black bars, and you must own the marketing rights. Google hasn't said where the videos will show. Start with a handful of products that are hard to understand from a photo, and check your video hosting before you send anything.

A new field in the feed

Google's Merchant Center product data specification now has an entry that wasn't there last week: Video Link, video_link. It's optional, and the description is one line, "Additional link to show a video of your product." AI Docs Watch, which tracks Google's documentation, caught the change between November 5 and November 7.

The rules under it are short and specific. You can give a YouTube URL, or a URL that points directly to a raw video file. Google spells out what it doesn't want: "It should not be a link to a landing page that contains the video player." The file has to be publicly reachable by Googlebot with no login and no robots.txt restriction. It should run between 6 and 240 seconds, stay under 500 MB, come in 9:16, 16:9 or 1:1, and be at least 720p. No blurry footage, no black bars. Sound is optional.

Two more lines matter for anyone using creator content. Merchants must own the licensing rights for marketing use, and Google won't pay creators anything. Any compensation is between you and them.

What Google hasn't said yet is where these videos will appear. Free listings, Shopping ads, AI Mode answers? The page doesn't say. That's a reason to start small, not a reason to wait.

Where most stores will get stuck

A product page with a player on it is not a video link. Google wants the file.

That one rule rules out the way a lot of stores handle video today. The clip lives in a theme section or an embedded player, served from a platform CDN or a video app, often through URLs that expire or check where the request came from. None of that is visible to the person who uploaded the video, and all of it can stop Googlebot.

The spec also notes the attribute isn't a Schema.org property, so the markup on your product page won't supply it. It has to go in the feed itself, or through the Content API or a feed app. If your Google feed comes from a Shopify app or a feed tool, check whether it can map a video field at all before you plan a shoot.

There's a quieter problem too: who owns the clip. In many teams the person who uploads product video is in marketing, the person who runs the feed is in ecommerce or an agency, and the person who controls the CDN is a developer. A field like this falls between all three. Before anything else, name one person who is responsible for every video_link value in the feed, and make sure they know where each file lives.

How the work moves

Why a clip gets rejected before anyone sees it

  1. The link

    Points at a page with a player instead of a YouTube URL or the raw file.

  2. The fetch

    Googlebot meets a login, an expiring signed URL, hotlink protection or a robots.txt block.

  3. The file

    Shorter than 6 seconds, longer than 240, over 500 MB, or under 720p.

  4. The frame

    Wrong aspect ratio or black bars around a clip recorded for another screen.

  5. The rights

    A creator clip with no written marketing licence behind it.

Illustrative check order built from Google's published video_link rules; not a measured result.
A product page with a player on it is not a video link. Google wants the file.

Pick five products, not five hundred

Don't add video to the whole catalog. Choose five products that are genuinely hard to understand from a photograph. A bag that converts into a backpack. A serum whose texture people ask about. A folding chair, a pour-over kettle, a jacket with a hidden hood. If customers keep asking how something works, or return it saying it wasn't what they expected, that product needs ten seconds of someone using it.

Look at the footage you already own before you plan a shoot. A lot of stores have short clips made for social media. Many are 9:16, which Google accepts, but check them for overlays, burned-in captions that cover the product, music you only licensed for one platform, and black bars from being reframed.

Keep each clip simple. Show the product being used, in real light, at a size people can judge. The first few seconds should show the thing the photo can't. Nobody needs a logo animation before the zip comes open.

For anything a creator made, find the agreement. If it doesn't clearly give you marketing rights beyond their own post, get that in writing before the clip goes in the feed.

Decision guide

Which products get a clip first

ConsiderationWorth a clip nowCan wait
What the photo missesMovement, texture, size in a hand, how it folds or fitsThe photo already says everything
Questions it causesThe same how-does-it-work question keeps arrivingFew pre-sale questions
Returns'Not what I expected' shows up in return reasonsReturns are about size or damage, not surprise
FootageYou already own a clean, short clipYou'd have to shoot from scratch
Decision framework: assess against your own catalog and returns.

Get the hosting right once

For each of the five clips, decide where the file lives. YouTube is the simplest path that meets the rules, and it's fine for most brands. If you'd rather host the file yourself, use a public URL that doesn't expire, isn't hotlink-protected and isn't blocked in robots.txt. Encode special characters; Google's example is replacing commas with %2C.

Then test it the way Google will. Open the URL in a private browser window. You should get the video file itself, not a page. If you have to sign in, accept cookies or click play on someone's player, Googlebot will have the same problem.

Add video_link to those five items, run the feed, and look at Merchant Center diagnostics for each product over the next few days. Write down what you sent and when. Google hasn't published how it will report video issues, so your own note is the record.

What to watch, and when to do more

Keep the first batch boring. A small, clean test tells you more than a big messy one, because when something is rejected you'll know which of five things went wrong. Five products, five clips, one hosting approach. Watch for disapprovals or warnings, and for any announcement about where videos show up. When you know that, you can decide whether video is worth a shoot day for the next twenty products.

Also decide what happens when a product changes. If the colourway is discontinued or the packaging is redesigned, the clip in the feed is now wrong. Put the video on the same checklist as photos when a product is updated, so an old clip doesn't keep showing a version you no longer sell.

Keep the product honest in the clip, too. The same specification section asks that images made with generative AI keep the metadata that says so. A clip that makes the product look better than it is will show up in your returns. We wrote about a related feed change when Google started taking product questions from the feed.

If you'd like help mapping video into your product feed, fixing hosting so Google can read it, or deciding which products deserve the effort, that is part of our ecommerce work. Talk to TWIMCO.

Related work: Nines Style

twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Paddle8 ↗︎