Video SEO - Getting Videos Indexed and Featured in Search

Pedro Dias Last updated: 2025-12-10 ~15 min read

Technical requirements for video indexing, from page layout signals to byte range support and complete structured data markup.

Why video SEO is different

Video SEO operates under a stricter set of rules than standard page indexing. Google doesn't just check whether a video exists on a page—it evaluates whether the page genuinely functions as a video experience. This distinction matters because Google allocates video-specific search features (video carousels, video previews, key moments) only to pages that meet both technical and qualitative thresholds.

Many sites embed videos on pages and add schema markup, yet never appear in video search results. The reason is usually one of three gaps: the page doesn't look like a video watch page, the video file doesn't meet technical requirements, or the structured data is incomplete. These are fundamentally technical SEO challenges that require proper server configuration and markup implementation.

The qualitative test: Does your page look like a video page?

Before evaluating any technical signals, Google performs a qualitative assessment: does this page appear to be primarily about this video? This is a deliberate filter designed to prevent sites from gaming video search by sprinkling embedded videos onto unrelated content.

What Google looks for

A page that passes this qualitative test typically has:

Signal What it means Why it matters
Video above the fold The video player is visible without scrolling Signals the video is the primary content, not supplementary
Video as main content The page centres on the video experience Distinguishes watch pages from articles with embedded clips
Supporting context below Title, description, metadata appear under the video Mirrors the layout pattern of dedicated video platforms
Minimal competing content No dense text blocks or product grids dominating the viewport Reinforces that the video isn't just one element among many

Layout anti-patterns

These patterns typically prevent video indexing:

  • Videos in sidebars or footers: Relegated positioning signals supplementary content
  • Autoplay videos in hero sections: Often interpreted as decorative rather than content
  • Multiple videos competing on one page: Dilutes the "main content" signal
  • Videos behind accordions or tabs: Hidden-by-default content may not be indexed
  • Embedded videos within long-form articles: The article is the main content, not the video

Practical layout guidance

Structure your video watch pages like this:

Video watch page layout showing the video player prominently above the fold, with title, channel, upload date, and description below, followed by related videos
Optimal video watch page layout: video player dominates the viewport, with supporting metadata below.

The video player should occupy the dominant visual space. Think YouTube, Vimeo, or any streaming platform—that's the layout archetype Google expects.

Self-hosted video requirements

When you host videos yourself (rather than embedding from video-serving optimised platforms like Wistia, Vimeo or Flowplayer/Wowza), you must meet specific technical requirements. Google needs to access and parse your video files directly, which introduces constraints that third-party platforms handle automatically.

Byte range support (HTTP 206)

This is the most commonly missed requirement. Your server must support HTTP range requests, allowing clients (including Googlebot) to request specific portions of a video file.

Why it matters: Google doesn't download entire video files. It fetches specific byte ranges to:

  • Verify the video exists and is accessible
  • Extract keyframes for thumbnail generation
  • Analyse video content for understanding and indexing

Browsers, media players, and crawlers almost always request video using byte ranges. They do this to probe metadata (the moov atom containing duration and codec information), avoid downloading entire files, and support seeking and adaptive playback.

Understanding 200 vs 206 responses

A common point of confusion: should your server return 200 OK or 206 Partial Content? The answer is both, depending on the request:

Status code When to return it What it means
200 OK Client requests the entire resource (no Range header) Valid, compliant response for full file requests
206 Partial Content Client sends a Range header (e.g., Range: bytes=0-1023) Expected response when byte ranges are supported

The key is not which status code you always return, but whether your server correctly negotiates range requests. A properly configured video endpoint should:

  • Return Accept-Ranges: bytes header (advertising range support)
  • Return 206 Partial Content when a Range header is present
  • Return 200 OK when no Range header is present
  • Include correct Content-Range and Content-Length headers on 206 responses

Example of a correct range response:

Request:
GET /video.mp4 HTTP/1.1
Range: bytes=0-102399

Response:
HTTP/1.1 206 Partial Content
Accept-Ranges: bytes
Content-Range: bytes 0-102399/104857600
Content-Length: 102400
Content-Type: video/mp4

[102400 bytes of video data]

Headers your server must return for range requests:

Header Purpose Example
Accept-Ranges: bytes Declares support for byte range requests Accept-Ranges: bytes
Content-Range Specifies the byte range and total file size Content-Range: bytes 0-102399/104857600
Content-Length Size of the partial content being returned Content-Length: 102400

Testing byte range support

# Test if your server supports range requests
curl -I -H "Range: bytes=0-1023" https://example.com/video.mp4

# Expected: HTTP 206 Partial Content
# With Accept-Ranges and Content-Range headers

If your server returns 200 OK when you send a Range header, byte range requests aren't being honoured. This typically requires server configuration changes. Playback may still work, but seeking can break, progressive loading becomes inefficient, and crawlers may struggle to fetch video metadata cleanly.

Common misconfigurations to avoid

  • Ignoring Range headers: Always returning 200 OK regardless of the request
  • Forcing 206 without a Range header: Only return 206 when the client actually requests a range
  • Disabling range requests for caching simplicity: This breaks video seeking and crawler access
  • Buffering entire files before responding: Common with misconfigured serverless setups or reverse proxies
  • CDNs stripping Range headers: Some CDN configurations don't pass through range requests correctly

MP4 moov atom placement

For MP4 files, metadata placement affects both playback and crawling. The moov atom (movie atom) contains essential metadata: duration, codecs, track information, and the index needed to locate video frames.

The problem: By default, many encoding tools place the moov atom at the end of the file. This means players and crawlers must download the entire file—or make multiple requests—before they can access basic metadata.

The solution: Move the moov atom to the beginning of the file (often called "fast start" or "web optimised" encoding). This allows immediate access to metadata with a single range request.

How to check moov atom position:

# Using ffprobe (part of FFmpeg)
ffprobe -v error -show_entries format_tags=major_brand \
  -show_entries stream=codec_type,start_time \
  -of default=noprint_wrappers=1 video.mp4

# Using AtomicParsley
AtomicParsley video.mp4 -T
# Look for 'moov' - it should appear before 'mdat'

How to move the moov atom:

# Using FFmpeg
ffmpeg -i input.mp4 -c copy -movflags +faststart output.mp4

# Using qt-faststart (included with FFmpeg)
qt-faststart input.mp4 output.mp4

For large video libraries, ensure your encoding pipeline includes the faststart flag by default.

Video file accessibility

Beyond byte range support and moov atom placement, ensure:

  • Direct URL access: The video file URL should be directly accessible to Googlebot (no authentication, no JavaScript-only loading)
  • Stable URLs: Don't use expiring signed URLs or session-based paths that change
  • Correct MIME types: Serve videos with proper Content-Type headers (video/mp4, video/webm, etc.)
  • Reasonable response times: Videos hosted on slow servers may time out during crawling

CDN considerations

If using a CDN:

  • Verify the CDN preserves range request functionality
  • Some CDNs require explicit configuration to pass through Range headers
  • Test from multiple geographic locations to ensure consistent behaviour
  • Ensure the CDN doesn't cache error responses for valid video URLs

Complete VideoObject structured data

Structured data tells Google exactly what your video contains. Incomplete markup is the most common reason for videos failing to appear in rich results—even when the page layout and technical requirements are correct.

Required properties

These properties are mandatory for video rich results:

{
  "@context": "https://schema.org",
  "@type": "VideoObject",
  "name": "How to Configure Nginx for Video Streaming",
  "description": "Step-by-step guide to setting up Nginx with proper byte range support for self-hosted video content. Covers configuration, testing, and common pitfalls.",
  "thumbnailUrl": "https://example.com/thumbnails/nginx-video-guide.jpg",
  "uploadDate": "2025-12-10T09:00:00+00:00"
}
Property Requirements
name Descriptive title matching the visible page title
description Accurate summary of video content (not just keywords)
thumbnailUrl Accessible image URL; should match visible thumbnail
uploadDate ISO 8601 format with timezone

These properties significantly improve indexing and rich result eligibility:

{
  "@context": "https://schema.org",
  "@type": "VideoObject",
  "name": "How to Configure Nginx for Video Streaming",
  "description": "Step-by-step guide to setting up Nginx with proper byte range support for self-hosted video content. Covers configuration, testing, and common pitfalls.",
  "thumbnailUrl": "https://example.com/thumbnails/nginx-video-guide.jpg",
  "uploadDate": "2025-12-10T09:00:00+00:00",
  "duration": "PT8M32S",
  "contentUrl": "https://example.com/videos/nginx-streaming-guide.mp4",
  "embedUrl": "https://example.com/embed/nginx-streaming-guide",
  "interactionStatistic": {
    "@type": "InteractionCounter",
    "interactionType": { "@type": "WatchAction" },
    "userInteractionCount": 12847
  },
  "regionsAllowed": ["GB", "US", "CA", "AU", "DE", "FR"]
}
Property Purpose
duration ISO 8601 duration format (PT#H#M#S)
contentUrl Direct URL to the video file itself
embedUrl URL for embedding the video on other sites
interactionStatistic View counts, likes, or other engagement metrics
regionsAllowed ISO 3166-1 alpha-2 country codes where video is available

Properties for enhanced features

For key moments (video chapters) in search results:

{
  "@context": "https://schema.org",
  "@type": "VideoObject",
  "name": "Complete Guide to Video SEO",
  "description": "Everything you need to know about getting videos indexed in Google Search.",
  "thumbnailUrl": "https://example.com/thumb.jpg",
  "uploadDate": "2025-12-10T09:00:00+00:00",
  "duration": "PT15M42S",
  "contentUrl": "https://example.com/video.mp4",
  "hasPart": [
    {
      "@type": "Clip",
      "name": "Introduction to Video SEO",
      "startOffset": 0,
      "endOffset": 45,
      "url": "https://example.com/video-seo-guide#t=0"
    },
    {
      "@type": "Clip",
      "name": "Page Layout Requirements",
      "startOffset": 45,
      "endOffset": 180,
      "url": "https://example.com/video-seo-guide#t=45"
    },
    {
      "@type": "Clip",
      "name": "Structured Data Implementation",
      "startOffset": 180,
      "endOffset": 420,
      "url": "https://example.com/video-seo-guide#t=180"
    }
  ]
}

Complete production example

Here's a full implementation combining all elements:

{
  "@context": "https://schema.org",
  "@type": "VideoObject",
  "@id": "https://example.com/videos/nginx-streaming#video",
  "name": "How to Configure Nginx for Video Streaming",
  "description": "Step-by-step guide to setting up Nginx with proper byte range support for self-hosted video content. Covers configuration, testing, and common pitfalls.",
  "thumbnailUrl": [
    "https://example.com/thumbnails/nginx-guide-1x1.jpg",
    "https://example.com/thumbnails/nginx-guide-4x3.jpg",
    "https://example.com/thumbnails/nginx-guide-16x9.jpg"
  ],
  "uploadDate": "2025-12-10T09:00:00+00:00",
  "duration": "PT8M32S",
  "contentUrl": "https://example.com/videos/nginx-streaming-guide.mp4",
  "embedUrl": "https://example.com/embed/nginx-streaming-guide",
  "interactionStatistic": {
    "@type": "InteractionCounter",
    "interactionType": { "@type": "WatchAction" },
    "userInteractionCount": 12847
  },
  "author": {
    "@type": "Person",
    "name": "Pedro Dias",
    "url": "https://example.com/about"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Example Tech",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png"
    }
  },
  "inLanguage": "en-GB",
  "isFamilyFriendly": true
}

Common validation errors

Use Google's Rich Results Test to validate your markup. Common issues include:

Error Cause Fix
Missing required property Omitted name, description, thumbnailUrl, or uploadDate Add all required properties
Invalid duration format Using "8:32" instead of ISO 8601 Use PT#H#M#S format (PT8M32S)
Inaccessible thumbnailUrl Image blocked by robots.txt or requires auth Ensure public accessibility
contentUrl returns error Video file not accessible or wrong URL Verify direct URL access
Structured data doesn't match content Schema says one thing, page shows another Align markup with visible content

Monitoring video indexing

Track your video indexing status in Google Search Console:

  1. Video pages report: Shows indexed videos and any issues
  2. URL Inspection tool: Check individual video page status
  3. Performance report: Filter by "Video" search appearance

Look for these status messages:

  • "Video indexed": Successfully indexed and eligible for video results
  • "Google could not determine the prominent video": Page layout issue—video isn't the main content
  • "Video outside the viewport": Video is below the fold or hidden
  • "Invalid video URL": contentUrl or embedUrl not accessible

Video XML sitemaps

A dedicated video sitemap helps Google discover your video content more efficiently, especially for large sites or when videos are added dynamically. While not strictly required if your pages have proper structured data, video sitemaps provide an additional discovery signal and let you submit video-specific metadata directly.

Important: Your video XML sitemap and on-page JSON-LD structured data must be aligned. The title, description, thumbnail URL, duration, and publication date should match across both sources. Conflicting metadata can confuse search engines and may result in neither source being trusted.

When to use a video sitemap

Video sitemaps are particularly valuable when:

  • You have hundreds or thousands of video pages
  • Videos are added frequently and you want faster discovery
  • Your site architecture makes video pages hard to crawl naturally
  • You want to provide metadata that's difficult to express on the page itself

Video sitemap structure

A video sitemap extends the standard sitemap format with video-specific tags:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:video="http://www.google.com/schemas/sitemap-video/1.1">
  <url>
    <loc>https://example.com/videos/nginx-streaming-guide</loc>
    <video:video>
      <video:thumbnail_loc>https://example.com/thumbnails/nginx-guide.jpg</video:thumbnail_loc>
      <video:title>How to Configure Nginx for Video Streaming</video:title>
      <video:description>Step-by-step guide to setting up Nginx with proper byte range support for self-hosted video content.</video:description>
      <video:content_loc>https://example.com/videos/nginx-streaming-guide.mp4</video:content_loc>
      <video:duration>512</video:duration>
      <video:publication_date>2025-12-10T09:00:00+00:00</video:publication_date>
    </video:video>
  </url>
</urlset>

Required video sitemap tags

Tag Description
<video:thumbnail_loc> URL of the video thumbnail image
<video:title> Title of the video (max 100 characters)
<video:description> Description of the video (max 2048 characters)
Tag Description Format
<video:content_loc> Direct URL to the video file Must be accessible to Googlebot
<video:player_loc> URL of the embeddable player Alternative to content_loc
<video:duration> Video length Seconds (e.g., 512 for 8m32s)
<video:publication_date> When the video was published ISO 8601 format
<video:expiration_date> When the video will no longer be available ISO 8601 format
<video:family_friendly> Whether the video is suitable for all audiences yes or no
<video:restriction> Countries where video is allowed/denied Space-separated ISO 3166 codes
<video:live> Whether this is a live stream yes or no

Complete video sitemap example

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:video="http://www.google.com/schemas/sitemap-video/1.1">
  <url>
    <loc>https://example.com/videos/nginx-streaming-guide</loc>
    <video:video>
      <video:thumbnail_loc>https://example.com/thumbnails/nginx-guide.jpg</video:thumbnail_loc>
      <video:title>How to Configure Nginx for Video Streaming</video:title>
      <video:description>Step-by-step guide to setting up Nginx with proper byte range support for self-hosted video content. Covers configuration, testing, and common pitfalls.</video:description>
      <video:content_loc>https://example.com/videos/nginx-streaming-guide.mp4</video:content_loc>
      <video:duration>512</video:duration>
      <video:publication_date>2025-12-10T09:00:00+00:00</video:publication_date>
      <video:family_friendly>yes</video:family_friendly>
      <video:restriction relationship="allow">GB US CA AU DE FR</video:restriction>
    </video:video>
  </url>
  
  <url>
    <loc>https://example.com/videos/apache-video-config</loc>
    <video:video>
      <video:thumbnail_loc>https://example.com/thumbnails/apache-guide.jpg</video:thumbnail_loc>
      <video:title>Apache Configuration for Video Delivery</video:title>
      <video:description>Learn how to configure Apache HTTP Server for efficient video streaming with proper MIME types and byte range support.</video:description>
      <video:content_loc>https://example.com/videos/apache-video-config.mp4</video:content_loc>
      <video:duration>645</video:duration>
      <video:publication_date>2025-12-08T14:30:00+00:00</video:publication_date>
      <video:family_friendly>yes</video:family_friendly>
    </video:video>
  </url>
</urlset>

Best practices for video sitemaps

  • Keep it separate: Use a dedicated sitemap file (e.g., sitemap-video.xml) rather than mixing with your page sitemap
  • Reference in sitemap index: Include the video sitemap in your sitemap index file
  • One video per URL: If a page has multiple videos, create separate <video:video> blocks within the same <url> element
  • Keep it current: Update the sitemap when videos are added, removed, or modified
  • Match your structured data: Ensure sitemap metadata matches the VideoObject schema on the page
  • Validate before submitting: Use online XML validators to check for syntax errors
  • Submit to Search Console: After creating the sitemap, submit it via GSC for faster discovery

Referencing in your sitemap index

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://example.com/sitemap-pages.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://example.com/sitemap-video.xml</loc>
  </sitemap>
</sitemapindex>

Checklist for video SEO implementation

Before publishing a video page:

  • [ ] Video player is above the fold and visually dominant
  • [ ] Page layout mirrors a dedicated watch page, not an article with video
  • [ ] Server returns 206 Partial Content for range requests and 200 OK for full requests
  • [ ] MP4 files have moov atom at the start (fast start enabled)
  • [ ] Video URL is directly accessible (no auth, stable path)
  • [ ] Thumbnail is publicly accessible and matches displayed image
  • [ ] VideoObject schema includes all required properties
  • [ ] Duration is in ISO 8601 format
  • [ ] uploadDate includes timezone
  • [ ] Rich Results Test shows no errors
  • [ ] Video sitemap created and submitted (for sites with many videos)
  • [ ] Video appears in GSC Video pages report

Key takeaways

  1. Page layout determines eligibility: Google evaluates whether your page genuinely functions as a video watch page before considering technical signals
  2. Supporting byte range requests is mandatory: Your server must return 206 Partial Content for range requests and 200 OK for full requests—correct negotiation matters more than any single status code
  3. Moov atom placement affects discoverability: For MP4 files, ensure the moov atom is at the start of the file (fast start) so crawlers can access metadata without downloading the entire video
  4. VideoObject schema must be complete: Missing required properties (name, description, thumbnailUrl, uploadDate) prevent video rich results
  5. Video sitemaps complement but don't replace on-page markup: Use sitemaps for discovery at scale, but structured data on the page is required for rich results
  6. Alignment matters: Your sitemap, structured data, and visible page content should all contain matching metadata

Frequently asked questions

Will embedding a YouTube video help my page appear in video search results?

No. When you embed YouTube videos, Google shows the YouTube page in video results, not yours. To appear in video carousels with your own URL, you must host videos yourself and meet the technical requirements (byte range support, proper layout, complete schema markup).

What is HTTP 206 Partial Content and why does it matter?

HTTP 206 is the status code your server should return when a client sends a Range header, requesting specific portions of a file. When no Range header is present, 200 OK is correct. The key is proper negotiation: your server must honour range requests and return the appropriate status code for each scenario. Google uses range requests to fetch video segments for thumbnail generation and content analysis. If your server ignores Range headers and always returns 200 OK with the full file, self-hosted videos may not be indexed correctly.

Do I need both VideoObject schema and a video sitemap?

VideoObject schema on the page is required for video rich results. Video sitemaps are optional but recommended for sites with many videos—they help discovery but don't replace on-page structured data. Both should contain matching metadata.

Why isn't my video appearing in search results even with schema markup?

The most common reasons: (1) the page doesn't look like a video watch page (video below fold, competing content), (2) the video file doesn't support byte range requests, (3) schema is incomplete or doesn't match visible content. Check Search Console's Video pages report for specific issues.

Further reading

Your Brand, VISIVELY outstanding!