# Page indexed, video not indexed: understand the difference

A page and the video embedded in it are different objects. A transcript may be available as page text while the video is not indexed for video search. Start by naming the result you want to check; otherwise, a successful test can answer the wrong question.

## Four questions, four kinds of evidence

| Question | Useful observation | What it does not prove |
| --- | --- | --- |
| Is the transcript in the document? | An anonymous HTTP response and browser inspection | That a search engine has indexed it |
| Is this page in Google's index? | The indexed result in URL Inspection | That its video is indexed |
| Does the page emit the intended metadata? | Actual JSON-LD and a relevant validation result | A rich result or a search position |
| Has Google indexed a video here? | The video's indexed status in Search Console | That every passage is indexed or the page will rank |

Our [WordPress comparison](/blog/before-and-after-a-video-page-with-and-without-an-exposed-transcript/) supplies the first kind of evidence. Its screenshots and exports are not Search Console results.

## When the page and video have different outcomes

Google's video documentation distinguishes watch pages, where watching a video is the main purpose, from pages where a video supports another purpose. For video features, the video must be discoverable without requiring a preliminary user action, and its thumbnail and resources must meet the documented conditions.

An illustrated product page can therefore be useful without becoming a dedicated watch page. Do not remove useful text or duplicate a page merely to turn every embedded clip into a search-video candidate. First [choose the page's role](/guides/video-page-or-existing-page/).

## A concrete diagnosis

Consider a tutorial page that returns HTTP 200 and contains the full transcript. Its player is created only after the visitor presses a button. You can verify the text immediately; you must inspect the rendered player separately.

```html
<!-- Teaching example: this button is not yet a video element -->
<button type="button">Load the demonstration</button>
<section><h2>Transcript</h2><p>The explanation is already here.</p></section>
```

If a live inspection detects a video, record that as detection in that test. It does not establish that the video has entered the index. Conversely, a missing video result does not establish that the text is absent from the page.

## Choose the next check from the observation

1. **The page is unavailable or excluded.** Resolve access, status, indexing directives and canonical selection before interpreting a video report.
2. **The page is indexed but no video is detected.** Inspect the player, its loading trigger and the resources it references. Use the [player and cache guide](/guides/video-player-cache-performance/).
3. **The video is detected but not indexed.** Read the recorded reason and compare the page with the relevant video requirements. Avoid making several unrelated changes at once.
4. **Metadata is missing or inconsistent.** Check [VideoObject](/guides/videoobject-wordpress/) against the visible media and [the video sitemap](/guides/video-sitemap-wordpress/) against its host page.

## Keep a dated record

Record the exact URL, selected canonical, observation date, source of the result and the change you made. Use a separate row for the live test and the indexed state. This makes a later comparison meaningful even when Google's reports update at different times.

**Next step:** follow the [Search Console procedure](/guides/video-search-console/). If your first goal is simply to add the video's words to your site, begin with [the HTML transcript mechanism](/blog/why-visible-transcripts-improve-video-discoverability/).

## References

- [Google: video best practices](https://developers.google.com/search/docs/appearance/video).
- [Search Console: video indexing report](https://support.google.com/webmasters/answer/9495631).
- [Search Console: URL Inspection](https://support.google.com/webmasters/answer/9012289).

[Browse all resources](/resources/).
