Hitivi · Field Notes
Meta Title and Description for Video Pages: Write, Publish and Check
For OTT and broadcaster programme pages: what the title and description each do, how to publish and verify them, and when to fix the page before rewriting tags.
Brand promotion: this article introduces Guangsuan's Google SEO services for video and programme pages.
If you run an OTT catalogue or broadcaster catch-up site, each programme, series and episode page needs one clear entry in search. The entry has two small fields with different jobs. Get the jobs mixed and every page in a season starts to read the same. This guide separates the title task from the description task, then gives a publish check you can repeat for one show page at a time.
What the title does and what the description does
In this guide, meta title means the HTML title element in the head, also shown in the browser tab. Meta description means the separate description tag in the same head. The H1 is the visible main heading on the page. The title link and snippet are what a searcher sees in results, generated by Google for that result context.
| Item | Where it appears | What to check |
|---|---|---|
| Title element | HTML head, browser tab | Names this exact video page and its distinction |
| H1 | Visible page body | States the same programme topic for a visitor already on the page |
| Meta description | HTML head | Gives an accurate, useful summary of scope |
| Title link and snippet | Search result | Text generated by Google for that query, kept, shortened or replaced |
They help describe a page, but Google generates the search result title and snippet using multiple sources. Your saved text is not a promise of exactly what a searcher will see. Snippets primarily come from page content and may use the meta description when it describes the page better. A snippet can vary with the query.
For a video page, use this split. The title answers: which programme, which series or episode, and what form is on this page. The description answers: what coverage is inside, who it suits, and what to check next. The H1 can phrase the same programme topic in page language. Different wording between title and H1 is acceptable when both describe the same task. A different topic is not acceptable.
Write from the actual page, not from a keyword list
Start with the reader task. A series landing page must separate the series from other series. An episode page must separate that episode from its siblings. A genre shelf must describe the range it contains and how choosing starts.
The following are hypothetical teaching examples with no ranking test behind them. Vague: Shows. Clearer: Nordic crime series S2: episode list and synopsis on this page. Vague: Watch now. Clearer: Episode 4 recap: guest cast and where it sits in S2. A matching description for the episode page could be: Lists synopsis, runtime position in the season, guest cast shown below, and next-episode link. Check the cast table before citing it. That sentence only works when those blocks exist on the page.
Use the main topic naturally, with enough distinguishing detail to separate this page from neighbouring pages. Do not stack title variants or force every keyword into the first words. Keep a brand suffix short at the end when added. Do not add tested, free, or download unless the page supplies a test record, an offer, or a file. Remove an ended season offer or an unconfirmed certificate before saving.
Length without a fixed rule
Google specifies no fixed length limit for title text or meta descriptions in the cited guides. Displayed results are truncated as needed, usually to fit device width, and the same count takes different room across scripts, fonts and capitals. Treat counters as drafting aids, not pass or fail thresholds.
A workable order for an OTT desk: remove repetition and empty modifiers, place the programme plus series or episode distinction early enough to survive shortening, keep essential conditions close to the claim, and read the sentence aloud. Then check the live result on a phone and on a desktop. A preview tool estimates layout. It cannot determine which wording Google will choose for every query, country and device.
Publish through the real field and inspect the output
Identify which CMS field or template owns title and description. Check whether a theme or plugin appends the brand or overrides the saved value. Save the intended values, refresh relevant caches, and fetch the public URL. Inspect the complete HTML head and rendered DOM. Confirm there is one intended title and one description, not conflicting output from multiple plugins. Compare them with the visible H1 and actual body. Check the final URL, canonical and indexing controls. A metadata edit is not a reason to change a useful existing URL.
Where you have access, inspect later crawled or indexed information and separately observe the real search result under recorded conditions. Browser DevTools can read the current document, for example with document.title and the description and H1 queries. Search Console URL Inspection provides indexed information and a live test of the page; its rendered screenshot is not a tool for previewing the final search title or snippet.
- Save through the correct SEO field, then view page source to confirm a single title and a single description.
- Compare saved title with visible H1 and body promise for the same episode or series.
- View the live result signed out on phone and desktop, and record query, device, date, headline shown and URL.
- Keep old text, release time and test setup so later comparison uses matching dates, countries, devices and query scopes.
When Google shows different wording, fix the page first in these cases
First check the current public page, the last known crawl and the particular result you observed. Look for a stale year, a vague or repeated title, mismatched headings, language differences or a body that does not deliver the title's promise. Fix the underlying mismatch instead of adding more versions of the same keyword.
Check in this order. Open public HTML and confirm single output. A theme, extension, cache copy or browser script can double, append or replace values. Place the saved title beside the visible H1. When they point to different subjects, decide which subject is correct first. For a snippet that skips the description, read the passage Google picked for that query and ask whether body text answers that query more directly and whether the description accurately summarizes scope.
A shortened title may reflect available space. Neither a shortened title nor a different snippet alone proves a penalty. Changes require recrawling and reprocessing and can take days to weeks to be reflected; that is not a deadline or a guarantee that the preferred text will be used. Metadata cannot repair an incomplete answer. When the body lacks the synopsis, cast table or season navigation it promises, complete the body before polishing headlines again.
Where Guangsuan fits
Guangsuan provides Google SEO services that join technical work, content building and link resources. For field definitions and publish checks, see Guangsuan's guide to meta titles and descriptions. For the broader scope of technical checks, content and links, see Guangsuan's Google SEO service. For how headlines are assembled from titles, headings and other cues, see Google's documentation on influencing title links.
FAQ
Is the title element the same as the H1? No. One lives in the head for tabs and results, the other stands on the page for visitors. Keep the same programme subject even when phrasing differs.
Does the description decide the snippet? No. Google may keep it, may take body copy instead, and may vary it by query. Write it as a faithful summary.
What length should I aim for? No universal total exists. Keep programme and episode distinction early, then read the live phone and desktop results.