A service page can contain a useful video without being a place people visit to watch that video.
That distinction changes the investigation when a publisher asks why its video is missing from search. An embedded player proves that a page contains a player. It leaves the page's purpose, the video's discovery path, and the assets behind it unresolved.
Start with the reader's task. Then inspect the relationship between the page, player, thumbnail, and media file. Record what each check establishes before moving to the next one.
The worksheet below is a proposed editorial investigation method. Every page scenario is fictional. Google's requirements come from its current documentation, checked on October 28, 2026. The examples describe public publishing decisions, with no private account inspection or measured search outcome.
Decide what the reader came to do
Consider two fictional pages from a business software publisher.
The first offers a tutorial called “Build a supplier approval queue.” A visitor arrives to watch someone demonstrate that task. The page presents one video, a short introduction, and supporting instructions. Watching is the main activity.
The second describes a supplier onboarding service. Its visitor compares scope, responsibilities, and delivery conditions. A short clip illustrates one step. Removing that clip would leave the service explanation largely intact.
Google's watch-page guidance identifies watching one video as the page's main purpose. It distinguishes that purpose from pages where video supplements other content. Treat the two fictional pages differently when planning an investigation.
Keep the service page useful for service evaluation. If a tutorial deserves its own viewing destination, give that destination a clear editorial purpose. Moving an embed above a heading does not establish why the page exists.
Write the intended task in one sentence: “The visitor watches a demonstration of supplier queue setup.” Ask an editor to compare that sentence with the actual page. A mismatch is a content decision to resolve before interpreting technical evidence.
Name the four resources before checking them
A video can involve several addresses. Put each one in the record under its own name.
| Resource | Role in the fictional tutorial | Evidence to collect |
|---|---|---|
| Watch page | The public tutorial destination | Exact page URL and visible purpose |
| Embedded player | The interface that presents this video | Element and player address, when applicable |
| Thumbnail | The still image representing the video | Image URL and observed image |
| Media file | The underlying video content | Media address supplied by the publishing system or host |
Google's video URL explanation separates the watch page, player, and actual video file. A player address is not evidence that you possess the file address. Keep the file field unknown when the host does not supply it.
For the fictional tutorial, the page might be https://example.com/watch/supplier-queue/. Its player might live at https://example.com/player/supplier-queue. Its thumbnail and media might use separate paths under the same host.
These are invented identifiers. They illustrate roles and are not working resources to test. On a real authorized audit, copy the actual emitted addresses. Avoid constructing a plausible media URL from a filename or a platform's public viewing link.
The inventory prevents a vague handoff such as “the video URL fails.” A developer needs to know which resource failed and what the request returned.
Inspect prominence through the page's purpose
Open the page as a viewer would encounter it. Identify the promised video and its position within the task.
In the fictional tutorial, the player appears with the tutorial title before the supporting notes. An editor can identify the intended video without choosing among several equally prominent recordings. This observation supports the page-purpose decision. It does not prove Google's assessment.
Google's indexing requirements also say the video cannot be hidden behind other elements. Check visibility separately from the page's editorial purpose. In a fictional tutorial, a persistent overlay covers the player even though the introduction promises a demonstration. Record the obstruction for investigation.
Now consider a fictional resource library containing six equal video cards. The page helps visitors select a recording. Record it as a selection destination. Google lists a category page with equally prominent videos among its non-watch-page examples in the same guidance.
A third scenario contains a full service explanation followed by a small demonstration. Record the demonstration as supporting material. Do not report that the service page is defective merely because its video has a different role.
Keep the broader B2B video marketing discussion separate from this diagnosis. Distribution planning and owned-site watch-page eligibility answer different questions. This review does not assess a YouTube channel or predict rankings.
Follow the discovery path before pressing play
Separate finding the video from starting playback. A visitor clicking a play control is one observation. Loading the entire embed only after an unrelated interaction is another.
Google's video discovery guidance identifies common embedding elements, including video and iframe. It warns against requiring user actions to load the video. For JavaScript-injected video, it calls for checking the rendered HTML through URL Inspection.
In a fictional page, a poster links to a modal that inserts the player only after a click. Record the initial state and the post-click state separately. Assign the developer to investigate how the published page exposes the video. “Plays on my laptop” leaves that discovery question open.
In another fictional page, an iframe exists when the page loads, while playback begins after the viewer presses play. Preserve that distinction in the evidence. The play button alone is not the same observation as an absent initial player.
Inspect the specific page and template version. A working tutorial template does not establish how an older service template loads its embed. Record a separate row when the publishing path differs.
If you cannot access the authorized inspection evidence, mark it unavailable. A browser observation should retain its narrower label.
Check access and stable assets separately
Review the page, thumbnail, and media delivery paths as separate resources. A public page can reference a restricted thumbnail. An editor's authenticated browser can conceal that difference.
For an intended public tutorial, inspect the published view without an editor session. Record any login prompt, unavailable resource, or content mismatch. Leave intentional private content private. A search review does not authorize changing its access policy.
Google's thumbnail guidance requires a valid, stable thumbnail accessible to Googlebot and Googlebot Images. Its stable URL guidance also explains the importance of stable media addresses for specific video features.
Suppose the fictional thumbnail comes from an editor preview link that expires. Assign the media owner to confirm its lifetime. Do not infer expiration from a query parameter alone. Record the provider's documented behavior or an observed change under the same check conditions.
For a third-party player, ask the host which media access options it supports. Keep that answer attached to the host and configuration checked. Avoid promising the publisher control over a resource it does not own.
Use the image explanation workflow when the thumbnail's meaning is unclear. File access and editorial accuracy need different evidence.
Keep page indexing and video indexing separate
An indexed page establishes a page-level state. It does not settle the video's state.
Google's video indexing requirements require an indexed watch page. They also state that the indexed page must perform well in Search before its video is considered for indexing. An indexed watch page does not guarantee video indexing.
That guidance supplies no numeric performance threshold for this worksheet. Do not invent one. Keep page evidence, video evidence, and the documentation's stated limits in separate fields.
In the fictional service scenario, a page-level indexed status can coexist with a supporting clip. Record both observations. Repeatedly changing video metadata would leave the page-purpose question unresolved.
For the tutorial, collect the dated page inspection and the dated video findings available to the authorized owner. If those observations conflict with a local browser check, preserve the conflict. Compare the inspected version and observation dates before proposing another change.
A completed technical review can establish that specific evidence has been collected and named problems have been addressed. It cannot establish a future search appearance. Keep that boundary in the acceptance note.
Use an eligibility evidence worksheet
Create one record per intended watch page. Add a second record when another page embeds the same video for a different purpose.
| Question | Evidence field | Decision or next action |
|---|---|---|
| Why does the viewer visit? | One-sentence task and page observation | Confirm watching is the main purpose, or classify supporting use |
| Which video is primary? | Visible title, player, surrounding content | Resolve competing videos or unclear purpose |
| Is the video visible? | Player view and any overlapping elements | Investigate an obscured player |
| How is the video discovered? | Initial element and rendered-page evidence | Investigate missing or interaction-dependent embed |
| Can the intended public audience reach it? | Session condition and observed response | Confirm restriction or investigate delivery |
| Which thumbnail represents it? | Exact URL, image, checked date | Confirm identity, accessibility, and stability |
| Which media or host serves it? | Known file address or provider limitation | Assign unknown delivery questions |
| What does page evidence show? | Dated authorized page inspection | Record state without inferring video state |
| What does video evidence show? | Dated findings or unavailable evidence | Assign the next supported investigation |
| Who closes the record? | Owner, evidence requested, review date | Keep unresolved questions visible |
Use descriptions instead of a percentage score. Eight completed fields do not cancel a blocked thumbnail. Mark each row observed, unresolved, or intentionally outside scope.
Work one fictional record to a decision
Return to the supplier queue tutorial. The editor confirms that watching the demonstration is the page's primary task. The developer observes an iframe in the initial page. The media owner finds that the player's thumbnail uses an expired preview asset.
The record contains three observations and one assigned delivery problem. The page's search status is unknown because no authorized inspection has been supplied. Leave that field unknown.
The proposed action is to replace the preview reference with the approved stable public thumbnail. The media owner provides the intended address. The developer updates the reference through the normal publishing review. The editor then checks that the still matches the tutorial.
The acceptance note records the updated page, thumbnail identity, observed access, and date. It leaves page and video indexing open for later evidence. No search result is implied by the successful thumbnail check.
For the service page using the same video, retain the supporting classification. Its reader still needs the service explanation. A separate tutorial destination need not turn every embed into a watch page.
Investigate in an order that preserves evidence
Start with purpose. Continue through resource identity, embed discovery, access, and stable assets. Then interpret the available page and video inspection evidence.
Use the technical SEO checklist for B2B websites for broader site questions. Keep this record attached to the specific video and publishing path.
After an approved change, repeat the affected checks. Retain the earlier observation so the next reviewer can see what changed. If the page now uses a different host, reopen the delivery questions instead of carrying forward the old answers.
Close the investigation with an owner and a defined next observation. A missing search appearance can remain unresolved after a correct local change. Record that limit plainly.
Keep the evidence attached to the resource.
Sources
- Google Search Central: Video SEO best practices. Watch-page purpose, embedding, indexing requirements, URL roles, thumbnails, and stable assets. Checked 2026.10.28. Worksheet fields and fictional decisions are proposed editorial methods.