YouTube feed widget for any website.

YouTube exposes three distinct primitives through its public API and each maps to a different job. A single video embed is what you get from the native iframe code on any YouTube watch page. It is fine for one-off embeds (a hero video on a landing page, a product demo on a product page, a VSL above the fold), but it cannot grow on its own and you maintain it by hand every time you publish. A playlist feed pulls every video in a YouTube playlist (PLxxxxx ID), respects the playlist sort order, and auto-includes new videos you add to the playlist. This is the right primitive for tutorial libraries, course modules, customer testimonial walls, and any curated set where you want editorial control. A channel feed pulls every public upload from a channel via the channel's uploads playlist (every YouTube channel has a hidden uploads playlist with ID UU + the rest of the channel ID). This is the right primitive for a creator's homepage, a podcast show page, or any place where the latest content should always be the first thing visitors see. There is also a fourth, less-known option: search feeds, which let you pull every public video matching a keyword query across all of YouTube. Search feeds are useful for brand-mention monitoring and for industry-news walls, but they cost 100 quota units per call versus 1 for the playlist or channel approach, so most teams stick to channels and playlists. Poper supports all three primary primitives (and search as an opt-in for higher-tier plans) from the same widget config so you can switch between them without re-embedding the snippet on your site. Picking correctly at the start saves you a re-embed cycle later.

Every YouTube widget on the market is rate-limited by the same thing: the YouTube Data API v3 free quota of 10,000 units per project per day. Different API calls cost different amounts of quota. A simple search.list call costs 100 units, a videos.list call costs 1 unit, and a playlistItems.list call costs 1 unit. A naive widget that uses search.list to fetch a channel feed will hit the daily quota after about 100 sync runs, which is why so many free YouTube widgets show stale or empty feeds by mid-afternoon. Poper avoids search.list entirely. We resolve channel handles to channel IDs once at connect time, then use the channel's uploads playlist with playlistItems.list (1 unit per page) plus a single batched videos.list call (1 unit per video page) to fetch metadata. The result is roughly 50x more headroom than a search-based widget, plus we cache responses at the global CDN edge so visitors to your site never hit the YouTube API directly. You can request a quota increase from Google for free, but you should not need to.

YouTube Shorts are vertical videos 60 seconds or shorter, served through a different player surface and a different recommendation graph than regular YouTube videos. The YouTube Data API v3 returns Shorts in the same response shape as regular videos, but most widget builders never noticed and just render every video as a 16:9 landscape thumbnail. The result is a stretched or letterboxed Shorts thumbnail in your feed and a playback experience that ignores the vertical format. Poper detects Shorts (videos with 9:16 aspect ratio and duration under 61 seconds) and renders them in a dedicated 9:16 thumbnail mode with optional vertical autoplay. We also offer a separate Shorts-only feed type for creator pages that want a TikTok-style wall, and a mixed mode that lets you blend Shorts and long-form into one chronological feed without the layout breaking. Worth knowing: the official YouTube oEmbed endpoint at youtube.com/oembed is still useful for fetching titles and thumbnails of single videos without using API quota, but it does not return playlists or channel feeds and Google now downranks oEmbed-only embeds because they lack structured data. Poper combines oEmbed for instant single-video metadata with the YouTube Data API for playlist and channel sync. There are a few other format gotchas worth flagging. Live streams (videos with liveBroadcastContent: live) need a slightly different player config to avoid showing a stale thumbnail after the stream ends. Premieres behave like scheduled videos until they go live, then convert to regular videos. Member-only videos are not exposed through the public API at all, which means no widget can embed them outside of YouTube itself. Region-blocked videos return a privacyStatus of unlisted in some markets and require server-side IP detection to handle gracefully. Poper handles every one of these edge cases automatically so you do not have to read the YouTube Data API reference docs to ship.

Embedding videos and ranking videos are two completely different things. A YouTube iframe by itself is invisible to Google's video index because Google cannot crawl what is inside an iframe. To be eligible for the video carousel that appears at the top of many search results pages, and to get the rich video thumbnail next to your organic listing, your page needs Schema.org VideoObject structured data for each video. The required fields are name, description, thumbnailUrl (at multiple resolutions for Discover compatibility), uploadDate (ISO 8601), and duration (also ISO 8601, like PT4M30S). Strongly recommended fields include contentUrl, embedUrl, and interactionStatistic for view counts. Most YouTube widgets emit none of this. Poper auto-injects a complete VideoObject JSON-LD block for every video in the feed, populated from the YouTube Data API response, so the videos you embed are immediately eligible for video carousel placement. Validate with Google's Rich Results Test on any page where the widget is embedded. There is a second tier of optional VideoObject fields worth populating when you have the data: hasPart for chapter markers (which produces the chapter timeline directly in the SERP video preview), transcript for searchable captions, and learningResourceType for educational videos. Poper pulls chapter markers from the video description automatically when they follow YouTube's official format (timestamp followed by chapter title) and pulls captions from the YouTube auto-caption track when available. The result is that a page with the Poper YouTube widget embedded ships richer structured data than the YouTube watch page itself, because YouTube's own watch page does not emit VideoObject for the embedded video either. Beyond Google, VideoObject is also consumed by Bing Video, DuckDuckGo, and increasingly by AI search engines like Perplexity that build their video answer cards directly from VideoObject markup. The same JSON-LD investment pays off in five different surfaces.

The default YouTube iframe is one of the heaviest single resources you can put on a page. A single embedded video pulls roughly 600KB of JavaScript, sets several third-party cookies, blocks the main thread during load, and frequently regresses Largest Contentful Paint by 1 to 2 seconds. Embed five videos as standard iframes and you can lose 20 Lighthouse points before any other code runs. The fix is the lite-player pattern: render only the thumbnail and a play button overlay (under 5KB per video) on initial load, and only swap in the real iframe when the visitor clicks play. Google itself published a lite-youtube-embed reference component making the same point. Poper ships lite mode as the default, so all the videos you embed cost you no more LCP than the same number of static images. Visitors who click see the full player, full chromecast and quality controls included. Visitors who scroll past pay nothing. The performance difference between lite mode and standard iframe embeds is the difference between a 90+ Lighthouse score and a 60. There are three additional optimizations Poper applies on top of lite mode. First, thumbnails are served from i.ytimg.com (YouTube's own CDN) and converted to WebP on the fly through our edge layer, which typically halves thumbnail weight versus the default JPEG. Second, the play-button overlay uses a single inline SVG instead of an image request, which saves a round trip per video. Third, when a visitor does click play, the iframe is loaded with the youtube-nocookie.com privacy-enhanced domain, which avoids dropping advertising cookies until after playback starts and helps with GDPR consent requirements in the EU. The combined result is that a page with twelve embedded videos in lite mode often outperforms a page with two embedded videos in standard mode on every Core Web Vitals metric. If page speed matters to your SEO, this is the single biggest reason to choose carefully which YouTube widget you embed.