CartVisualCreate account

Why Is Google Showing a Website Screenshot Below My Demand Gen Video?

Demand Gen landing-page previews are a separate creative optimization that can display a captured destination screenshot below the video; review the Final URL setting rather than replacing the video.

Published · By CartVisual editorial team

Find the source of the unexpected image

A merchant approves a product demonstration with a clean final frame. After reviewing a Demand Gen placement, they notice a screenshot of the store below the video and assume that Google inserted an extra frame into the uploaded file. Google documents a separate landing-page preview feature that captures the Final URL destination and can display that screenshot beneath the video ad. The video footage and landing-page screenshot have different owners.

First identify whether the unwanted visual is part of the encoded MP4, an uploaded image asset, or the separately generated landing-page preview. Inspect the original video file and the actual ad preview. If the screenshot is external to the video, regenerating the MP4 is unlikely to address the setting.

Inspect the documented Demand Gen control

Google’s current guidance says landing-page previews are enabled by default for new Demand Gen campaigns. In the Video ad builder, the Final URL card includes a checkbox for showing a screenshot of the landing page, and the account owner can opt out there. Creative optimizations also lists landing-page previews among the controls to review.

Do not transfer this to Performance Max as a universal campaign setting. The cited route is Demand Gen. Record the exact account interface, ad identity, Final URL and checkbox state rather than claiming that an editor changed it. Google says screenshots receive manual review and may be recaptured after site changes.

Fictional product launch

A fictional merchant advertises a navy travel case. The approved video ends on the navy case, but the destination page has a large seasonal banner featuring a red case. A landing-page screenshot could therefore communicate a conflicting color even when the video file itself is correct. The merchant has two decisions: repair the destination so it accurately represents the advertised variant, and decide whether the screenshot feature belongs in the campaign.

If the page is accurate but the screenshot is not wanted, the documented opt-out is the relevant setting. If the page itself is wrong, disabling the screenshot does not fix the buyer’s destination. Use the ad-to-landing promise guide to verify the selected offer. No Google Ads campaign or screenshot was generated for this example.

Distinguish review and serving states

An enabled checkbox does not establish that a particular screenshot is approved or serving. Google describes manual review and potential recapture after destination changes. Inspect the actual ad preview and account state. If a screenshot reflects an older page version, record the observed image, URL and time before attributing the discrepancy to the video asset.

The old-variant image transition guide concerns Merchant Center image processing, not this Demand Gen screenshot surface. Keep those platform mechanisms separate.

Finish with a two-surface proof

The release record should name the video revision and the Final URL separately. Check the video for accurate product content, then check the landing page and any preview screenshot for consistent offer, variant, price context and brand presentation. If the screenshot is unwanted, the authorized account owner should confirm the documented opt-out.

Hold when the ad promises a variant the landing page does not offer, or when the current screenshot state is unknown. An approved video file alone does not establish approval of the separately generated page preview. CartVisual does not control Google Ads creative optimizations.

Sources

Scope and evidence

Prepared by CartVisual with AI assistance and checked against the listed sources. Demand Gen-specific; screenshot capture, approval and recapture are Google-controlled and not tested here.

Related decisions

Explore the AI product video generator workflow