Why Your AI-Generated Videos Don't Show Up in Search

What Changed Is the Cost to Make — Not the Rules for Search

Generative AI that turns text or images into short videos has become practical, so even small teams can now add an explainer video to an article or a how-to clip to a product page.

Google's video best practices, however, set indexing conditions that do not care how a video was made: the watch page must be indexed and performing well in Search, the video must be embedded on the watch page and not hidden behind other elements, and it needs a valid thumbnail at a stable URL. Google also notes that an indexed watch page does not guarantee the video gets indexed.

So the real decision is not how to make the video but whether it deserves its own page that people search for. If it does, build a watch page. If it is only a supplement, embed it in the article and do not expect traffic from it as a video. Draw that line first.

What Counts as a Watch Page

Google defines a watch page as one whose main purpose is to show the user a single video. Pages where the video only complements the text do not count. Here are the examples Google gives.

What Happened on This Site: Rich Result "Valid," Video Not Indexed

Direbase once had a demo video on its home page, marked up with VideoObject. A later redesign removed the video section — but the VideoObject JSON-LD stayed behind.

When we checked Search Console in October 2026, URL Inspection reported the video rich result as valid, while the Video indexing report showed the home page videos (Japanese and English) as not indexed, with the reason "Video isn't on a watch page."

Two lessons. First, the rich result check is a syntax check; whether the video is indexed is decided separately. Second, marking up a video that is not on the page was itself against the general structured data guideline, "Don't mark up content that is not visible to readers of the page." Google also notes that rich results may not show when markup has errors the Rich Results Test can't catch or refers to content hidden from the user.

We removed the home page VideoObject alongside publishing this article. When a video goes, its structured data must go with it — an omission that becomes more likely the more often you swap in AI-generated videos.

How to Write VideoObject (Reflecting the September 24, 2026 Update)

On September 24, 2026, Google added the creator (or author) property to its VideoObject documentation and clarified the interaction types supported by interactionStatistic. Only three properties are required; the rest are recommended.

A minimal example for a watch page (values are fictional).

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "VideoObject",
  "name": "VideoObjectの書き方を90秒で",
  "description": "動画再生ページに必要な3つの必須プロパティを解説します。",
  "thumbnailUrl": "https://example.com/video/videoobject/thumb.jpg",
  "uploadDate": "2026-10-05T10:00:00+09:00",
  "duration": "PT1M30S",
  "contentUrl": "https://example.com/video/videoobject/main.mp4",
  "creator": {
    "@type": "Person",
    "name": "山田太郎",
    "url": "https://example.com/about"
  }
}
</script>

What to Watch for With AI-Generated Videos

• Don't mass-produce: Google's guidance on generative AI content (updated October 1, 2026) says generating many pages without adding value for users may violate its scaled content abuse policy. Rather than mechanically spinning up a watch page per video, limit it to videos worth finding on their own.
• Have a person check the metadata too: the same guidance asks for fact-checking AI-generated content, including titles, meta descriptions, and structured data. If AI wrote your VideoObject name or description, confirm it matches what the video actually shows.
• Avoid transparent thumbnails: Google requires at least 80% of the thumbnail's pixels to have an alpha value above 250 (essentially opaque). An AI-generated PNG with a transparent background used as-is will be rejected with the reason "Thumbnail is transparent."
• Don't hide the player behind a click: if the page shows a play-button image and only loads the player on click, the video is rejected with "Cannot determine video position and size." Load the player at its real size and position when the page loads.

For your first watch page, a quick route is to turn an article's key points into a short explainer with a text-to-video tool such as DomoAI. Whichever tool you use, the conditions above apply the same way.

Four Steps to Verify in Search Console

For measuring the effect of changes in Search Console, see how to verify SEO changes with Search Console. For structured data in general, see how to write structured data.

Check the Structured Data on Your Watch Page

Enter a URL to see which structured data types the page has and whether required fields are present for major types, including VideoObject. No sign-up required. Whether the video is treated as being on a watch page is something to confirm in Search Console using the steps above.

Related Tools

• Structured Data Check — JSON-LD types and required fields
• SEO Audit — structured data, basic SEO, and technical SEO in one pass
• AIO Readiness Check — how ready a page is to be cited by AI search

Sources (checked October 5, 2026)

• Google Search Central — Video SEO best practices
• Google Search Central — Video (VideoObject, Clip, BroadcastEvent) structured data
• Google Search Central — Latest documentation updates (2026-09-24 / 2026-10-01)
• Search Console Help — Video indexing report
• Google Search Central — General structured data guidelines
• Google Search Central — Guidance on using generative AI content