The short answer

Video SEO for a publisher is mostly about meeting a short list of indexing requirements that Google documents, and then giving each video clean, consistent metadata. Google Search Central sets the core conditions: the watch page must be indexed, the video must be embedded on a watch page, it cannot be hidden behind other elements, and it needs a valid thumbnail at a stable URL. Google also says that an indexed page does not mean its video is indexed. Metadata reaches Google through VideoObject structured data, a video sitemap or Open Graph tags, and the same thumbnail URL should be used everywhere a video is described. Features such as video previews and key moments additionally need Google to be able to fetch the video file itself. The rest of this guide takes those requirements one at a time, with the decisions a newsroom, sports publisher or station group has to make for each.

Watch pages: the requirement most publishers miss

Google distinguishes between a watch page, whose main purpose is showing one video, and a page where the video is complementary to the rest of the content. Google lists video landing pages, TV episode players, news video pages, sports highlight pages and event clip pages as watch pages. Blog posts that review an embedded video, product pages with a product video, category pages listing several equally prominent videos and reviews with a trailer are not. Google says watch pages are required for video results, Video mode, key moments, the LIVE badge and other rich formats, and recommends a dedicated watch page for each video where it makes sense for the business, with a title and description unique to that video. The Search Console video indexing report shows the consequence: one of the listed reasons for a video not being indexed is that it is not on a watch page. For publishers this is the main structural decision. A story page with a video at the top of a long article is usually an article page, and it can still rank as a text result. If video search traffic matters, the video also needs its own page where it is the main content. Google allows the same video to appear on both.

Make sure Google can find the video

Google finds videos referenced by video, embed, iframe or object elements. Its best practices add several rules that catch publisher players. Do not load the video through a URL fragment, because Google Search does not generally support fragments. If the player is injected with JavaScript, check that the video appears in the rendered HTML in the URL inspection tool. Keep the HTML video container in the page even when a media API call fails. Do not rely on a swipe, click or typed input to load the video: the video indexing report lists cannot determine video position and size as a reason for non-indexing when the player is not present on page load, for example when a screenshot must be clicked to start playback. Videos behind a sign-in or subscription can still be indexed if the page carries paywall structured data. For videos hosted on YouTube, Vimeo or another platform and embedded on your page, Google may index the video on both your page and the host page, and still recommends structured data on your watch page.

Thumbnails, stable URLs and file access

Without a valid thumbnail, a video is not eligible for video features. Google accepts BMP, GIF, JPEG, PNG, WebP, SVG and AVIF thumbnails of at least 60 by 30 pixels, with larger preferred, and at least 80 percent of the pixels must have an alpha value above 250. Googlebot and Googlebot Images must be able to fetch the image, so it cannot be blocked by robots.txt or a login. The preferred thumbnail can be set with the poster attribute, the sitemap thumbnail tag, thumbnailUrl in structured data or og:video:image, and Google asks for the same URL in each place. Stability matters as much as format: Google warns that changing URLs, such as quickly expiring CDN links, can prevent indexing, and asks for one unique, stable thumbnail URL per video. The same applies to the video file. For video previews and key moments, Google needs to fetch the file, including a streaming URL such as an M3U8 playlist, so it should not be blocked by robots.txt or noindex. Google notes that both the watch page host and the streaming server need enough capacity for crawling. Publishers that want to protect media URLs can verify Googlebot before serving them.

VideoObject structured data

Google lists three required VideoObject properties: name, thumbnailUrl and uploadDate. Recommended properties include description, contentUrl, embedUrl, duration in ISO 8601 format, expires, interactionStatistic, regionsAllowed or ineligibleRegion, hasPart for Clip segments, potentialAction for SeekToAction and publication for live streams. contentUrl is the direct URL of the video file, not the page; embedUrl is the player URL and is the fallback when the file URL is not available. uploadDate should be the first publication time in ISO 8601 with a timezone. Name, description and thumbnail should be unique for every video and match what the page shows. The markup must sit on the page where users can watch the video. For live programming, a BroadcastEvent under publication with isLiveBroadcast, startDate and, once the stream ends, endDate is required for the LIVE badge, and Google asks publishers to notify it through the Indexing API when a stream starts, ends or its markup changes. Expiry deserves care for rights-limited clips: a past expires date removes the video from video results, and Google warns not to add one to videos that do not expire, because a wrong date can remove an available video.

Video sitemaps and mRSS

A video sitemap lists watch pages in loc entries, with a video:video element for each video on that page. Required tags are thumbnail_loc, title, description and either content_loc or player_loc; Google recommends content_loc where possible, and both must differ from the page URL. Titles and descriptions must be escaped or wrapped in CDATA and should match the page, with descriptions limited to 2,048 characters. Optional tags include duration from 1 to 28,800 seconds, expiration_date, publication_date, restriction for country rules, requires_subscription, live and up to 32 tags per video. Google lists category, gallery_loc, price and tvshow as deprecated, so older sitemap generators may need cleaning. Google says it recommends video sitemaps but also supports mRSS feeds, which suits publishers whose video platform already exports one. A sitemap does not replace structured data on the page: the two should carry the same title, description and thumbnail, and unrelated videos should not be listed against a page.

Where Minute-ly.com fits

The requirements above reward publishers that give each meaningful clip its own page, title, description and chapters, which is where the volume problem starts for a newsroom or league. Minute-ly.com's Video AI Engine connects live streams, broadcast feeds, VOD and video libraries and generates derivatives including highlights, summaries, chapters, previews and captions. Highlights are candidates for their own watch pages, summaries give editors a starting point for unique descriptions, and chapters with their source timecodes can feed Clip markup, as described in the guide to AI video chapters. Video Previews creates short previews from existing content for listing and article pages, which are not watch pages themselves but help readers decide which video to open. Outputs, editorial rules and delivery to the CMS or player are scoped for each workflow, and editors review generated text before it is published.

Checklist and monitoring

Decide which videos deserve a watch page and give each one a unique title and description. Load the player on page load with a standard video or iframe element, without fragments or click-to-load screenshots, and confirm it in the rendered HTML. Set one stable thumbnail URL per video in a supported format and use it in the poster, structured data, sitemap and Open Graph tags. Keep video files at stable URLs that Googlebot can fetch. Add VideoObject markup with name, thumbnailUrl and uploadDate, plus description, duration and contentUrl or embedUrl, and BroadcastEvent for live streams. Add expiry and region rules only where rights require them. List watch pages in a video sitemap or mRSS feed with matching metadata. Then watch three Search Console reports: the video indexing report, which counts indexed pages with a video and explains why others were not indexed; the video rich result report for markup errors; and the performance report filtered to the Videos search appearance.