CartVisualCreate account

Why is Google Merchant Center rejecting my product video URL when it plays on my website?

First check Merchant Center's Needs attention details. A technical error, policy or quality issue, video under review, and missing public placement require different responses. The optional video_link attribute accepts YouTube video URLs or direct raw-video URLs from other hosts. Check the exact submitted value, Google's technical and media requirements, public crawler access, marketing rights and the actual video status. A playable website video does not establish acceptance. Video issues do not automatically disapprove the associated product offer.

Published · By CartVisual editorial team

Start with the actual Merchant Center status

Open Merchant Center's Needs attention section and identify the affected product, submitted video_link value, reported issue and observation date. Copy the exact Google diagnostic wording into your record. The categories below are this guide's troubleshooting groups, not a promise of literal status labels in every account. A missing placement alone does not establish rejection.

The video_link attribute is optional. Google reviews video eligibility separately from the associated offer. Distinguish a technical delivery problem from a policy or visual-quality issue; either can stop a video from serving without establishing that the whole offer was rejected.

Observed stateWhat it establishesNext decision
Technical errorGoogle reports a problem with the submitted video input or its technical acceptanceCheck the exact URL, format, accessibility and media properties
Policy or quality issueThe video has a separate content or presentation problemAddress the reported issue; a successful download is not approval
Under ReviewProcessing or review has not reached a final accepted statePreserve the submitted version and monitor the actual status
No visible placementThe seller has not observed the video where expectedCheck video status and serving separately; do not infer rejection

Apply Google's video_link acceptance contract

Use Google's current Video link specification to check the submitted feed and media file. The table summarizes documented checks; no example video has been submitted. Record actual values from the submitted feed and approved media file.

Acceptance fieldSource-based check
URL resourceYouTube URL, or a direct raw-video resource for another host
URL syntaxHTTP/HTTPS; ASCII and RFC 3986 compliant; at most 2,000 characters
Actual mediaGoogle lists MPG, MP4, WMV, AVI, MOV, FLV, MPEG-1 and MPEGPS
Duration and size6–240 seconds; maximum 500 MB
Encoded geometryMinimum resolution: 720p. Google says ratios should be 9:16, 16:9 or 1:1; preserve that qualification.
Rights and retrievalMarketing-use rights; public Googlebot access without login or blocking robots.txt rules
Hosting and qualityStable, non-expiring URL; footage not blurry or out of focus
Destination reviewShopping-policy compliance; audio is optional

Google places the listed ratios under Minimum requirements but uses qualified wording. Its 720p example is 1280 × 720; the retrieved page does not separately explain portrait pixel dimensions. Record the actual encoded geometry and investigate the destination diagnostic rather than inventing a portrait acceptance threshold.

Decide whether the submitted URL identifies the video

A website can play a clip through an HTML product page, an embedded player or a separate media resource. Google permits YouTube video URLs, but other hosts must supply the direct raw-video resource. For example, a hypothetical https://media.example.invalid/watch/kit player page is not equivalent to a hypothetical https://media.example.invalid/files/kit.mp4 raw-file address. Neither example has been tested or submitted.

Compare the actual feed value with the intended resource. If the address requires a personal session, returns an HTML login page or expires, resolve that delivery problem with the hosting owner. An anonymous browser check is preliminary evidence, not proof of Googlebot access. For the broader authenticated-download handoff, see the existing public-media delivery guide. For detailed crawler-response troubleshooting, see the existing Google image-crawler diagnostic.

Check the actual feed representation

Google accepts up to ten video_link values. Text data sources separate repeated URLs with commas; commas belonging inside a URL must be encoded as %2C. The following is an illustrative TSV record, not an executed upload. The space between the two column names and between the two values represents a tab:

id	video_link
KIT-EXAMPLE	https://media.example.invalid/kit%2Cfront.mp4,https://media.example.invalid/kit-side.mp4

The encoded comma belongs to the first filename; the unencoded comma separates two video values. The example addresses text-feed formatting only. XML uses repeated <g:video_link> elements, while Merchant API submissions must follow their own documented structure. Check the final exported row or request, not merely the value displayed inside a feed editor.

Keep one acceptance record for the actual submission

Download the video-delivery worksheet (CSV). It contains a clearly labelled illustrative row and a blank working row. Keep the item identifier, exported field value, media version, measured properties, rights/access evidence, reported issue, observation time and next action together. The worksheet records your evidence; it does not approve a video.

Route a technical finding to the relevant input or hosting owner. Route a policy or quality finding to the creative review. Keep an unresolved review pending. Regenerating the clip will not correct a wrong feed value, and changing a URL will not substantiate a visual claim.

When replacing a video, preserve the URL and review history

Google recommends submitting a new unique URL when video content changes. Its documentation says a new URL typically prompts a crawl within 24–72 hours, while detecting changed content at an unchanged URL can take up to six weeks. These are published estimates, not deadlines guaranteed for an account.

During review of a new URL, Google says the product video can remain Under Review and the previous video may continue serving until the replacement is processed. Keep a replacement record with the product identifier, previous URL, new URL, approved file versions, feed-update time, current video status and observed public result. The replacement video's review does not itself establish offer disapproval. Seeing the previous clip does not prove the replacement was rejected.

Keep CartVisual creation separate from Google delivery

CartVisual's product-video workflow supports planning, storyboard review, shot generation and inspection of a silent 720p assembled video. It does not automatically host a permanent public video URL or submit video_link to Merchant Center. The approved export still requires appropriate hosting, feed submission and destination-specific review.

Before delivery, check product accuracy as well as file acceptance. The reflection-continuity guide addresses visual fidelity, not URL validity. The Pinterest video-pin versus catalog-link guide covers a different platform contract; its file limits and publishing routes must not be transferred to Google.

Evidence boundary: The matrices, TSV row and replacement record are illustrative editorial tools. No Merchant Center account, live feed, crawler log or video approval was tested for this article. Passing a local checklist does not guarantee acceptance, placement, impressions or sales.

Sources

Scope and evidence

Prepared by CartVisual with AI assistance and checked against the listed sources. The official Google sources were reopened for this revision. Platform requirements may change after the recorded review date.,The portrait-resolution interpretation is not separately specified in the retrieved Google documentation; no alternate pixel threshold is asserted.,Google places the listed aspect ratios under Minimum requirements while using the word 'should'. This manuscript preserves that distinction without claiming a universal rejection outcome.,The diagnostic tables and feed row are hypothetical editorial aids, not results of an actual Merchant Center submission.,The supplied seven existing guide bodies and CartVisual feature-page text informed the duplication and capability boundaries. This does not establish a full-body comparison against every existing CartVisual guide.,No permanent hosting, direct Merchant Center integration, guaranteed approval or serving outcome is attributed to CartVisual.,A technically acceptable video can still have unresolved product-fidelity, licensing, policy or quality issues.

Related decisions

Explore the AI product video generator workflow