Hitivi · Field Notes
Video Indexing Report vs. Page Indexing: What OTT Teams Should Check First
Brand promotion: this article introduces Guangsuan's GSI Google indexing promotion service. It is a vendor introduction, not an independent review or a customer story.
A broadcaster or OTT operator publishes a new episode page, checks that the player works, links it from the series page, and waits. Three weeks later the episode title still returns nothing in Google. The team calls that one problem, not indexed, but the evidence sits in at least two different reports, and those reports answer different questions.
Short answer
Before buying indexing help for episode or watch pages, settle three questions in order. Does Google know the URL, and can it fetch the page? If the page is indexed, did Google detect a video on it? If a video was detected, was that video indexed? A page that fails the first question needs an access or crawl repair, and promotion does not substitute for it. A page that passes the first question and still shows no detected video needs the player and the rendered HTML examined. Only when a page is reachable, indexable and linked, and Google still has not fetched it, does promoting discovery become a reasonable step. Even then, the indexing decision remains Google's.
Two reports, two questions
The Page indexing report and the Video indexing report are not two views of the same number. The first describes URLs on the property that Google has crawled and indexed. The second describes indexed pages where Google found a video, and gives a reason for each affected page. A page can be indexed with no video detected, and a video can be detected on a page that is not indexed. Neither report describes the other case.
| Source | What it describes | What it does not establish |
|---|---|---|
| Page indexing report | How many known URLs Google crawled and indexed, and why others were not | Whether a video was detected on a page, or whether a video was indexed |
| Video indexing report | Indexed pages where Google found a video, with the reason recorded for each affected page | A complete inventory of media files, or the status of pages where no video was detected |
| URL Inspection | The version Google has processed for one URL, plus a live test of what it can fetch now | That the tested version is indexed, or which URL Google will treat as canonical |
Guangsuan's English guide to video indexing issues makes the same separation. It notes that the Video indexing report covers indexed pages where Google found a video, and that the report is not a deduplicated inventory of media files. Google indexes at most one video per page, the same video can appear on several pages, and pages with no detected video are absent from the report. The last-crawled date shown there refers to the page, not to the video file.
Read the Video indexing report literally
Open the reported issue and one example URL, then write down five things for that page: the URL, the exact reason given, the crawl date, the selected video URL, and the thumbnail Google recorded. A reported video URL can be a player URL rather than a direct media file, so the field does not always name an MP4.
Three observations get confused, and each points to different work:
- The page is not indexed. The question is about discovery, crawl access, noindex, authentication and Google's selected canonical. Installing a different video plugin does not answer it.
- The page is indexed but no video is detected. The question is about the rendered HTML and whether a player element exists before any click or scroll. A poster image with a play icon is not a discoverable player.
- A video is detected but not indexed. The question is the stated watch-page, player, thumbnail or hosting issue. Different pages can fail for different reasons.
Detection is also separate from indexing. A page that appears in text search, a player that works for a visitor, and valid VideoObject markup are three observations, and none of them alone proves that Google has indexed the video or will show it for a particular query.
Then check the watch page itself
Fetch the exact URL signed out, and record the final status after redirects, the robots.txt rule that matches the path, any meta robots tag or X-Robots-Tag header, the declared canonical, and whether the player is present in the HTML that comes back.
Discovery by Google does not depend on the visitor pressing play. Google can find videos through common elements such as video, iframe, embed and object, but a JavaScript implementation needs its video element in the rendered HTML. Do not depend on clicking a poster, swiping or typing to create the video.
Keep the two controls apart. A robots.txt rule limits crawling and is not a dependable way to keep a known URL out of search. A page that should stay out of results needs a noindex directive on a page Google can fetch. Blocking the path and relying on the tag leaves the instruction unread.
For a series with many episodes, the sitemap and the internal links do different jobs. In a video sitemap, loc identifies the watch page, video:content_loc identifies the file and video:player_loc identifies the player. A particular filename or a sitemap submission does not override the video indexing requirements, so a sitemap entry is a discovery input rather than a promise.
Read the Search Console label for that URL
URL Inspection shows the version Google has processed, and its live test describes what Google can fetch now. That live test does not report the video's index status and does not predict which URL Google will select as canonical.
Read the status as written. 'Discovered – currently not indexed' means Google found the URL but has not crawled it yet. 'Crawled – currently not indexed' means the page was fetched but not placed in the index. Neither label identifies a cause by itself, and neither is evidence of a penalty. For a newly published episode, Google's own guidance notes that a new page or site can take a week or so to start being crawled and indexed, and that not every URL on a site should be expected in the index; the canonical pages are the target.
When promoting crawl is a reasonable next step
Crawl promotion fits one situation. The page returns the content the team expects, carries no noindex and no conflicting canonical, is linked from pages Google already knows, and Google still has not fetched it. Anything else is a page repair first.
Guangsuan publishes GSI as its own indexing promotion service. The page states that GSI (Google Speed Indexing) is Guangsuan's service name and not a Google product, an official partnership or a priority-indexing permission. The service works around the URLs a client submits, using Guangsuan's GPC crawler pool and related link structures to encourage discovery and crawling. Whether a URL is indexed, when that happens and how long it stays indexed remain Google's decision. The same page states plainly that submission is not indexing and indexing is not ranking.
Its listed precondition matches the checks above. A submitted URL should be reachable and free of obvious crawl blocks, noindex or duplicate-canonical problems, and the service does not replace content or technical repairs. The published package periods are service references affected by page quality, site status and Google's processing, not fixed completion dates. The GSI Google indexing service page sets out the flow, the URL conditions and the verification route.
What to prepare before asking for a quote
A promotion service can only work with the list it is given, so the list is the part the team controls. Build one row per URL, grouped by page type: series page, episode watch page, catch-up page, clip page.
| Field | What to record |
|---|---|
| URL | The exact address, including case, trailing slash and meaningful parameters |
| Page type | Series, episode watch page, catch-up window, clip or bonus content |
| Final status | The response after redirects, and the final destination |
| Canonical | The declared canonical, and the one Google selected where it differs |
| Indexability | robots rule, meta robots or header, login or geo restriction |
| Current state | Search Console status and crawl date where known |
| Purpose | The reader question the page is meant to answer |
| Owner | Who can approve a player, template or metadata change |
Two details are easy to omit and expensive to discover later. The canonical column should record the one Google selected where it differs from the one declared, because a watch page that points at a series page is not the URL being considered. The purpose column should name the reader question the page answers, which is what separates an episode page worth promoting from a template duplicate that should be consolidated instead.
How to verify what changed
Save the before state: the sitemap address and its response, the sampled URLs with status and canonical, and the current Search Console values with the date they were read. Then report three results separately. Whether URLs moved from discovered to crawled, whether they became indexed, and whether they started to earn impressions and clicks. The first can happen without the second, and the second without the third. Repeating a request for an unchanged URL does not make Google crawl it faster.
For the video layer, add a fourth line. Whether Google's Video indexing report now shows the page with a detected video, and whether that video is indexed. That line is not the same as the page being indexed, and it is not the same as the episode appearing for its title.
Where Guangsuan fits
Guangsuan's published material covers both halves of this check. The guide to Google video indexing issues walks through the report, the player, the thumbnail and the markup separately. The GSI page describes what crawl promotion covers once those checks pass. Neither page is a Google product, and neither promises an index entry, a thumbnail or a ranking.
Frequently asked questions
Should a new episode page appear in Google within a week?
Google's guidance says a new page or site can take a week or so to start being crawled and indexed, but that is a general observation, not a deadline for every URL. Check whether Google knows the URL before treating the delay as a fault.
The page is indexed, so why is the video missing from the Video indexing report?
A page with no detected video points at the player and the rendered HTML rather than at the index. Confirm that the video element is present before any interaction, rather than only appearing after a click or a scroll.
Can a robots.txt rule remove a watch page from search results?
A robots block limits crawling, and it is not a dependable way to remove a known URL from results. If a page must stay out of the index, the documented approach is to let Google fetch it and use a noindex directive.
Does GSI guarantee that an episode URL will be indexed?
No. Guangsuan states that the service promotes discovery and crawling around submitted URLs, while whether a URL is indexed, when, and for how long remains Google's decision. Scope, observation period and verification method are agreed before work starts.
What is the first thing to check when an episode page does not show up?
The exact URL, signed out. Confirm it returns the episode page without a redirect to another host, a login or a challenge screen, that it carries no noindex and no canonical pointing at the series page, and that the player is present in the returned HTML.