Check this page with an assistantOpens a chat asking it to summarise this article and name the evidence behind each claim.
Claude opens with the prompt on your clipboard: Anthropic does not support prefilled prompts on the web, and we would rather copy it than ship a button that drops it.
A Video Embed Is Not Yet a Video Search Destination
Google indexes videos from indexed watch pages: pages whose primary purpose is to let a user watch one video. A blog post, product page, or category can contain a useful video and rank as a normal result, but the embed alone does not make it eligible as the indexed video page.
This distinction explains many “video not indexed” reports. The player works for a visitor, VideoObject validates, and the thumbnail exists, but the page is an article with a supporting demonstration or a product page with a small carousel clip. Google’s current guidance treats those as non-watch pages.
Decide the content job first. If the video is the primary experience, publish a dedicated watch page. If it only clarifies another page, keep it there and optimize the main page honestly. It is fine for the same video to exist on both its watch page and a relevant supporting page.
The Five-Layer Eligibility Stack
| Layer | Requirement | Typical failure |
|---|---|---|
| Page | Discoverable, crawlable, indexed canonical URL | Page is noindex, duplicate, orphaned, or blocked |
| Watch experience | One prominent video is the page’s main purpose | Video is supplementary, hidden, or one of many equal items |
| Player/file | Google can identify and fetch supported video or player URLs | Login, firewall, expired URL, unsupported protocol |
| Thumbnail | Stable, accessible, valid representative image | Blocked, missing, generic, or shared incorrectly |
| Metadata | Consistent title, description, dates, duration, and URLs | HTML, schema, sitemap, and host disagree |
Fix the layers in order. Video markup cannot rescue an unindexed watch page. A perfect page cannot expose a player that Google cannot find. Search Console separates page indexing from video indexing for this reason.
Design the Watch Page Around Watching
- Use a unique page title and H1 that identify the specific video and the decision, skill, event, or story it contains.
- Place the player prominently in the initially rendered page instead of hiding it behind tabs, carousels, or user interaction.
- Provide a stable thumbnail that represents the actual video, works at search-result sizes, and remains crawlable.
- Add useful visible context such as a summary, chapters, speaker, date, resources, transcript, or related next steps.
- Offer captions and accessible controls so the content works without audio and with keyboard or assistive technology.
- Keep one canonical URL for the watch experience and link to it from relevant hubs, articles, products, and series pages.
A transcript should serve the viewer, not become a hidden keyword dump. Edit machine transcripts for names, technical terms, speaker changes, and punctuation. Use headings and chapters to make long material navigable, and preserve the relationship between the text and actual timeline.
Self-Hosted and Third-Party Players Can Both Work
| Choice | Advantage | Control to verify |
|---|---|---|
| Third-party host | Encoding, delivery, player, captions, platform discovery | Google can fetch the embed/player and the host permits indexing |
| Self-hosted video | Page experience, data, branding, and file ownership | Supported format, bandwidth, content URL, range requests, stability |
| Hybrid distribution | Platform reach plus an owned watch destination | Consistent metadata and clarity about the preferred page |
Google says a third-party video can be indexed on both your watch page and the host’s page when each qualifies. Do not assume the embed transfers the platform page’s visibility. Your page still needs its own value, metadata, links, indexability, and watch-page design.
Use VideoObject as an Accurate Metadata Layer
VideoObject can communicate the video name, description, thumbnail, upload date, duration, and the content or embed URL. Google can use this data for video features across the main results, Video mode, Images, and Discover. Required and recommended properties depend on the feature and must satisfy general structured-data policies.
Use contentUrl when Google can access the actual video file; use embedUrl for an embeddable player as documented. Keep the URLs stable and consistent with the player and video sitemap. Do not describe a different video, hide the marked-up player, or add values the viewer cannot verify.
Clip can identify manually defined key moments, whileSeekToAction can describe a URL pattern that deep-links into the timeline. The page must support seeking through the URL, and the feature requirements still apply. Chapters are navigation, not a guarantee of enhanced display.
Add a Video Sitemap When Discovery Matters
Google recommends video sitemaps and supports mRSS. A video sitemap entry associates the watch-page URL with a thumbnail, title, description, and either content or player URL. It can help expose recent or otherwise difficult-to-discover video content.
Every referenced file must remain accessible to Googlebot without login, robots blocking, or firewall denial. The sitemap title and description should match the visible watch page. Do not list incidental videos unrelated to the host page or treat the sitemap as a substitute for internal links.
The XML sitemap guide explains the canonical URL contract, accurate lastmod values, file limits, and Search Console submission layer.
Protect Performance and Accessibility
A heavy player can load scripts, trackers, fonts, and thumbnails before the visitor chooses to watch. Measure the watch template’s LCP, INP, CLS, total transfer, and interaction delay. Use a lightweight facade when appropriate, but ensure the video remains detectable in the rendered page and does not require an opaque interaction before Google can identify it.
Reserve player dimensions to prevent layout shift. Make controls keyboard accessible, label them clearly, preserve visible focus, and provide accurate captions. Give autoplaying media a user-controlled pause and avoid unexpected audio. A technically indexable video that excludes viewers is not a successful result.
Optimize the thumbnail as both a critical image and a search asset: representative composition, sufficient resolution, stable URL, appropriate format, explicit dimensions, and crawl access. The image SEO guide covers that delivery system.
Diagnose the Video Indexing Report in Order
Search Console’s Video indexing report covers indexed pages where Google detected a video. It distinguishes pages with an indexed video from pages where a video was detected but not indexed. It does not report the total number of unique videos, and Google indexes at most one video per page.
- Confirm the watch page itself is indexed and canonical.
- Open the reported reason and sample the listed URLs.
- Inspect the live page and rendered screenshot for player visibility.
- Compare detected video, thumbnail, and metadata URLs.
- Test structured data and direct crawler access to the thumbnail/player.
- Validate the fix on a small page set before changing the whole template.
Use the Videos search-appearance filter in Performance for impressions and clicks, then connect watch pages to completions, next-step clicks, leads, subscriptions, or purchases. View count alone cannot tell the business whether the video served its intended job.
Questions About Video SEO
- Does embedding a YouTube video help the page rank?
An embed is not a ranking shortcut. A relevant video can improve the page experience, but Google’s video indexing requires an indexed canonical watch page where watching the video is the main purpose. Google may also index the video on YouTube’s page. Build the page for its real user job rather than adding an unrelated player.
- Do I need a separate page for every video?
Create a dedicated watch page when video search visibility matters and the video deserves a standalone destination. Google says only videos on indexed watch pages are eligible for video indexing. A video can also appear on a product or article page as supporting content, but that page is not necessarily a video result candidate.
- Is VideoObject structured data required?
Google can understand some videos without it, but recommends VideoObject on watch pages because it supplies explicit title, description, thumbnail, dates, duration, and content or embed URLs. Markup must match the visible video and satisfy the video indexing and structured-data requirements.
- How do I know whether Google indexed my videos?
Use Search Console’s Video indexing report to see indexed pages containing an indexed video and reasons pages contain a video Google could not index. Inspect individual watch URLs for detected video details, and use the Videos search-appearance filter in Performance to monitor impressions and clicks.
Primary Sources Reviewed
- Google Search Central: Video SEO best practices
- Google Search Central: VideoObject structured data
- Google Search Central: Video sitemaps
- Google Search Console: Video indexing report
- Google Search Central: Core Web Vitals
Reviewed July 28, 2026. Video features, host capabilities, supported formats, and structured-data properties evolve; verify the current requirements before changing a player or video template.
