Google Merchant Center · Status at source date: Account observation
Merchant Center product-video processing issue reported
A 13 October FeedArmy investigation reports that some submitted Merchant Center product videos remained in preview processing and did not appear playable on live Shopping listings.
What changed
FeedArmy’s 13 October investigation reports a bounded Merchant Center observation: in account checks by Emmanuel Flossie, product videos submitted through YouTube and self-hosted routes remained in preview processing. Thumbnails were visible, but videos were not playable on live Google Shopping listings. Flossie says he replicated an observation first made by Joey Bidner across multiple accounts in the sample. The 13 October date is the investigation date, not evidence of when the behaviour began.
For advertisers using product video, PMC suggests treating this as a testable delivery question, not confirmation of a platform-wide incident. Start with a small, documented set of affected and unaffected products. Record the Merchant Center account, product identifiers, target market, submission route, upload or submission time where available, preview status, thumbnail presence and observed live-listing result. Preserve dated screenshots or recordings of both the preview interface and the corresponding live surface.
Compare like with like before inferring a processing fault. Check whether the item is otherwise eligible and live, whether the video association is present, and whether differences align with product, account, market or surface. If practical, compare a YouTube-submitted example with a self-hosted example, while avoiding a conclusion from a single asset or one account. A result seen only in preview, only on a particular listing surface, or only for a subset of products should be reported at that level of scope.
Separate observed impact from hypothesised cause. Missing playback could reflect processing, but the supplied evidence does not establish whether feed configuration, policy, eligibility, a surface-specific condition or another factor explains any individual case. Do not state that feedback submission is a remedy; the source encourages it, but no verified fix, response or estimated resolution is available here.
Joey Bidner receives first-contributor credit because Flossie explicitly identifies his original observation. Flossie is credited separately for replication and the dated investigation. Joey’s original post and exact chronology have not been independently inspected, and no Google acknowledgement has been verified.
Why it matters for advertisers
It gives retail teams a bounded way to investigate product-video visibility while preserving the distinction between sampled observations and a confirmed broader issue.
What to check next
- Check preview status and live playback for a documented set of products.
- Record account, product, market, submission route and observation time.
- Check eligibility and video associations before inferring a processing fault.
Sources & contributor credit
- Original investigation · FeedArmy
Joey Bidner explicit original-observation credit reconfirmed in FeedArmy. Original post/chronology unresolved. Direct screenshot download HTTP403; story-media gap retained. No current global outage or Google acknowledgement verified.
- Discovery and distinct analysisEmmanuel Flossie
Post supplied through Markifact; export timestamp is not a launch date. Joey Bidner is expressly credited with original observation by Emmanuel Flossie; Emmanuel replicated it and wrote the dated investigation. Joey original post/priority not independently inspected.
Original creator unverified
Credits reflect the editor's latest changes. Original authorship has not been independently verified for this version.
Attribution evidence and limitations
Full attribution review pending.
A source link alone does not establish original authorship.
Original image and video creators have not yet been verified.
- Published on this site
- Article updated
This update reflects the dated source reporting. Availability may have changed. Further coverage of this same development will be added to this page.





