How to optimize your videos for Google Discover (2026)

Last verified · 2026-09-19 · by Moe Ameen

The steps

1. Decide which path your video takes into Discover. There are two, and they need different work. Native platform video — mostly YouTube and YouTube Shorts — is surfaced in Discover as video cards and Shorts carousels tuned to a user's interests, so the optimization is a strong, on-topic video with a clean title and thumbnail on a channel Google can clearly classify. The second path is a video embedded on a page you own (a blog post or watch page), which Google finds in the rendered HTML and can surface as a card if the page is indexed and meets Discover's policies. If you control a website, do both: the owned page gives you direct control over the hero image, headline, and surrounding text that Discover rewards.
2. Meet the technical eligibility bar for the watch page. For the owned-page path, make sure Google can actually find and index the video. Embed it with a standard video, iframe, embed, or object element so it appears in the rendered HTML — confirm with the URL inspection tool — not hidden behind a click or a fragment that only loads on interaction. The page should feature that single video as its primary content rather than burying it, and the video must not be paywalled. Add VideoObject structured data with a unique name, description, and thumbnailUrl, keep that metadata consistent with the actual video, and serve the video from a stable URL so Google can fetch its bytes.
3. Package the hero image to Google's published spec. Every Discover card is an image card, so the hero image is a primary factor, not a finishing touch — a card with weak imagery often does not surface at all. Google's guidance is specific: use a high-quality original image at least 1200 pixels wide, in a 16:9 aspect ratio that matches how cards render, and enable the max-image-preview:large meta setting sitewide so Google can show a large preview. Declare the preferred image through og:image or schema markup. Avoid generic stock and heavily text-laden graphics; an original image that reads at a glance beats a busy one every time.
4. Set a stable, high-quality video thumbnail. The video needs its own thumbnail, and Google gives you several ways to declare a stable one: the poster attribute on the video element, thumbnailUrl in VideoObject structured data, video:thumbnail_loc in a video sitemap, or og:video:image. Use a supported format, keep the URL consistently reachable at one address, and make sure the thumbnail is unique per video. On the YouTube path this is your custom thumbnail — the same discipline applies: it has to earn a tap in a scroll, not just label the video.
5. Write a headline that earns a tap without clickbait. In Discover the title has to stop a thumb mid-scroll for someone who was not searching for it — a harder job than a search-results title. Google threads a specific needle: headlines should capture the essence of the content and spark interest, but must not use clickbait, sensationalism, or exaggerated details to manufacture engagement. Curiosity the content pays off is rewarded; over-promising is exactly what Discover's policies demote. Write the specific, honest version of the interesting thing, and make sure the video delivers on it.
6. Publish fresh and stay on one clear topic. Discover is organized around current interests and leans toward recently published content far more than evergreen search does, so cadence is a real lever — a steady stream of recent, on-topic videos gives the feed many matchable candidates, while occasional posting gives it few. Just as important is topical consistency: a channel or site with a clear, coherent subject is one Google can confidently classify and match to the right interest cluster. Refreshing a strong older piece can help too, but the durable move is regular, on-topic publishing rather than one perfect video and a long silence.
7. Get page experience right on mobile. Discover is a mobile-first surface, and page experience is part of eligibility, not just search. Make the watch page fast and clean on a phone, keep Core Web Vitals healthy, and avoid intrusive interstitials that get between the reader and the video. A slow or cluttered page is a reason for the feed to pass you over even when the content and imagery are strong — remove that reason.
8. Build supporting coverage so you can appear inside a topic overview. Google's September 2026 test adds a "Dive deeper" button that opens an AI-generated topic overview, starting on video cards, linking out to related stories, community reactions, and original reporting. To be one of those linked sources rather than summarized past, own the topic across formats — the video plus a supporting article, follow-up posts, and coverage that gives an AI summarizer something credible to cite. One clip alone is easy to bypass; a topic you cover with depth is the thing an overview points to.
9. Track Discover performance and iterate on the package. Use the Discover report in Google Search Console (it appears once your site gets Discover traffic) to see which pieces the feed surfaced and how they performed. Because there is no ranking to read, you are looking for patterns: which topics, hero images, and headlines earned impressions and taps. Then iterate the package — test a different hero image or a sharper headline on your next piece — rather than expecting to tune one asset into the feed. You are improving your odds across many candidates, not optimizing a single position.

Common gotchas

• You cannot submit a video to Discover or guarantee it appears — there is no submission, no ranking, and no slot to buy. Any tool or service that promises Discover placement is misleading you; Google states outright that eligibility is not appearance.
• Discover traffic is volatile by design. It rises and falls with shifting user interests and Search updates, so a spike or a drop is often the feed changing, not your page — don't overreact to a single week.
• A video buried on a page full of unrelated content usually won't qualify. The watch page should feature that single video as its primary content, and the video must be in the rendered HTML, not loaded only on a click.
• Weak or missing imagery is the quiet killer. A card without a strong 1200px 16:9 image often simply doesn't surface, no matter how good the video is — and generic stock underperforms original images.
• Clickbait and sensationalized headlines can get you demoted in Discover specifically. The policy targets exactly the exaggerated, curiosity-gap titles that work elsewhere — the honest-but-interesting version is the safe one.
• The topic-overviews test can summarize a topic in-feed so a reader never taps any single video. Being one clip on a subject is easy to bypass; being one of several credible pieces on it is how you get linked instead.

Where Kompozy fits

This checklist has a bottleneck, and it's not the technical setup — it's supply. Steps 3, 5, and 7 want an original 1200px 16:9 hero and a tap-worthy thumbnail for every video; step 6 wants a steady stream of on-topic pieces because Discover leans hard on freshness; step 8 wants supporting written coverage on the same subject. Producing that whole package repeatedly, by hand, is where most creators optimize one video perfectly and then let the pipeline run dry — which is the one thing Discover punishes, because an empty pipeline gives the feed nothing recent to match.

Kompozy is a full AI content generation and multi-platform publishing engine, and it manufactures the exact assets this workflow needs. For the video itself: Clipped Shorts cut from long-form and captioned Persona Shorts fronted by a face-locked avatar, for the native YouTube and Shorts path Discover surfaces first. For the image-card factor in steps 3 and 4: Photo Posts and Infographic Photo scenes generated on-brand rather than pulled from generic stock, sized to serve as the 1200px 16:9 hero and the thumbnail — and because it produces variations, you get the multiple hero and headline options step 9 wants to test rather than shooting one and hoping. For the owned watch page and the topic-overview coverage in steps 2 and 8: Blog Articles that give a video a proper indexed home with surrounding text, plus newsletters and social posts that build the topical footprint an overview links to. A Persona Brief keeps voice and subject consistent so a week of output reads as one clear topic — the exact signal step 6 needs Google to classify — and HyperFrames renders every hero image, card, and thumbnail pixel-consistent so a high volume of Discover-spec assets looks deliberate.

The freshness lever in step 6 is Autopilot: it schedules and publishes the whole set across eight social platforms plus blog and email from one queue behind a per-post review gate, so the feed gets a steady supply of recent, on-topic candidates instead of one hand-built piece a month. Be clear on the boundary — Kompozy cannot submit a video to Discover, guarantee the feed surfaces it, or control Google's indexing, because no tool can; steps 1, 8's topic choice, and the iterate-on-what-worked judgment in step 9 stay yours. What it removes is the production tax that makes consistent, Discover-spec video packaging impossible to sustain by hand. Starter ($99/mo, 5,500 credits) fits a solo creator keeping one channel and blog fed; Pro ($299/mo, 18,000 credits) sustains a creator or small team packaging video to Discover's spec across every platform; Enterprise is custom for agencies running this across many brands.

Frequently asked questions

Related tutorials

• How to optimize YouTube videos for AI search (2026)
• How to design a YouTube thumbnail for long-form views (2026)
• How to make content visible to AI search (2026)
• How to future-proof your content for Google spam updates and AI Overviews (2026)

← All how-to guides · Get Started