
A Merchant Center offer can remain approved while its optional product video is not eligible to serve. Google documents video-specific technical, policy and quality checks separately from the associated offer. Investigate the video_link asset and its diagnostic before rebuilding an otherwise correct product record.
Key Takeaways
- Offer approval does not certify every attached media asset.
- A video page URL and a raw video URL are not interchangeable.
- Correct the failed video stage and verify its own result.
Read the status at the right level
The official video-link specification says the attribute does not affect offer approval. The 2026 update likewise states that video policy or quality errors can stop the video without affecting its associated offer.
Record the product identifier, submitted video URL, exact message and observed offer status. Do not collapse approved product and usable video into a single green check. A new video may still be processing or have an issue even when the item itself remains available.
Verify the URL's actual role
Google accepts a YouTube URL for this attribute. For a non-YouTube route, the source requires a link directly to the raw video file rather than a landing page containing a player. A normal Vimeo viewing page or a store page with an embedded movie is therefore a different kind of address from the required raw-file route.
The URL also needs stable public accessibility for Googlebot without sign-in or special permission. Do not make confidential client footage public to satisfy a product-feed requirement. Choose an approved marketing asset and its appropriate hosting route.
Inspect the file rather than the export preset
The captured specification calls for a video between 6 and 240 seconds, within 500 MB, in a supported format and aspect ratio, with adequate resolution. Check the exact current specification before publishing. Sound is optional; adding narration is not a remedy for a broken URL.
Use the actual video-file verification guide to inspect the delivered movie. A prompt asking for a duration or a visible project setting is not proof of the final file's properties.
| Observed failure | Next evidence to inspect |
|---|---|
| URL inaccessible | Public media response and crawler access |
| Technical rejection | Actual movie duration, format and other reported property |
| Policy or quality issue | The specific asset diagnostic and movie content |
| Old video persists | Submitted URL, revision and processing state |
Keep the demonstration product-specific
The source recommends a video about the particular product, rather than a general company film. Use the testable-message brief to connect the demonstrated action with supported product facts. An attractive generated scene cannot verify performance or included accessories.
If replacing media, retain the reviewed previous asset and submit the intended new mapping. The product-image refresh diagnosis offers a useful separation of store, feed and fetch stages, although video timing and rules must come from the video specification.
Accept the repair when the submitted movie meets its requirements and the asset's actual diagnostic supports the result. Record serving evidence separately; a successful submission or approved offer is not a promise that a video will appear for every shopper.
Related tasks
- Why Does Google Still Show My Old Product Image After I Upload a New One?
- I requested 10 seconds in 16:9. How do I check the actual AI video file?
- How Do I Turn a Product Launch Brief Into a Testable AI Video Story?
Sources and scope
- Google Merchant Center: Video link: video_link is optional and does not affect offer approval. Non-YouTube links must reach raw video; accessibility, technical requirements and content rules apply to the asset.
- Google Merchant Center: Product data specification update 2026: Policy or quality errors can stop video serving without affecting the associated offer; related validation began June 30, 2026.
Based on both complete official sources captured October 29, 2026. No product, video, account diagnostic or serving event was tested. The triage table is proposed. The source's asset-specific review and recrawl wording is not converted into a guarantee of offer state, timing or exposure.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.