- Use YouTube for a tutorial that answers a discoverable question on its own. Use the help center when readers need current button labels, role-specific exceptions or text they can copy.
- Check visibility on both the page and player. An unlisted video can still be forwarded by anyone with its link.
- When both destinations use the lesson, assign responsibility for updating the watch address and the written instructions.
A customer opens a ticket because the export button moved. They need the exact steps for their account today. Someone searching “how do I upload my first video?” has a different starting point. The right home for the tutorial depends on which reader you are serving.
Choose YouTube for the question people ask before they know your product
A self-contained explanation can make sense to someone browsing a public channel. Give it a title that names the task, demonstrate the whole path without private details and identify what viewers should be able to do afterward. Before promoting it, open the destination page and check its audience and playback.
For a concrete example, YouTube Creators publishes How to Upload Videos with YouTube Studio. The topic makes sense on its own and the viewer can follow it while using the product. If you prepare posts from ngram, its YouTube integration explains where to select the channel and visibility. The public tutorial here is an editorial example, not a claim that it was published through ngram.
Choose the destination by the reader's starting point
A customer who already opened a support ticket needs to find the new export control with their existing account. Start their help article with required permissions, the current navigation label and a screenshot or short demonstration of the export result. Put the exception for accounts without the control in text. A video alone is a poor home for a command or a support contact likely to change.
A viewer searching YouTube before choosing a product needs a different opening. They may not know what is being exported or why the report matters. Give the tutorial enough context to stand on its own. Name the task in the title, demonstrate a whole example and link to the current written instructions for product-specific details. A video that opens “as explained above” is not yet ready to stand alone on a channel.
Choose visibility separately from destination. An unlisted channel video can still be shared by anyone holding its link. A public help article containing an unlisted embed is still an accessible distribution path. For account-specific instructions, review permissions on both the page and player. Decide what the audience can access before writing the launch email.
Decide which version a viewer needs
| Reader | Primary destination | What must be available |
|---|---|---|
| Searching a general question from outside the product | YouTube | An introduction that makes sense without a surrounding article. |
| Customer following current product instructions | Help center | Exact steps, permission exceptions and copyable text. |
| Customer receiving a private account procedure | Controlled destination with appropriate access | Verified page and player permissions for the intended audience. |
Choose the help center for precise instructions and exceptions
A support article can put the clip next to the current button label, a command to copy and the rule for accounts that see a different screen. Use a video for the part readers need to recognize, then keep the searchable answer and any exceptions in plain text. The help-center video workflow explains how to choose that moment.
In this hosted example, the owner changes which version of a handoff lesson is live. The revised instruction plays through the original embed. That is useful when one help article should remain the destination after a screen or procedure changes.
Use both when each version earns its place
YouTube’s written upload guide links its public tutorial and explains details that are easier to scan in writing. A support team can make a similar choice: a public introduction answers the broad question, and the help article carries exact steps, exceptions and current links.
Name a maintainer for each destination. When a UI label changes, open the actual help article and the public video separately. A replaced hosted embed does not update a separate video uploaded to a channel. Use the sharing guide to distinguish an embedded player from an exported file uploaded elsewhere.
Separate the source owner from the distribution channel
Give one person ownership of the task instructions and another, if necessary, ownership of the channel upload. When the export screen changes, the source owner identifies the affected steps and approves the corrected example. The channel owner updates the public destination and finds the help article, playlist and emails that referenced the older video.
Test the audience boundary from both directions. A visitor who discovers the public tutorial should be able to reach a useful written guide. A customer coming from the help center should be able to finish the task without needing a subscription to the channel. If the article contains a restricted player, verify that its audience matches the page's intended readership.
This approach also makes removal easier. When an obsolete tutorial has no current audience, retire or redirect the placements your team controls and check the channel's visibility. A stale URL in an old onboarding email may matter more than the video project's internal status.
Maintain two placements without creating two competing answers
Check the current differences between private, unlisted and public access when deciding where to publish a support tutorial. YouTube’s privacy settings guide.
Sometimes the public tutorial and help article need the same cut. Keep the help article as the owner of exact steps and the YouTube description as a route to the current instructions. If the product changes substantially, check whether the existing channel upload can still teach the task. A new upload generally has a new watch address, so update every article that depended on the old one.
Use a simple test before distributing either version. Give a channel viewer no context and ask what task the tutorial teaches. Give a customer the help article and ask them to perform the task with their account. If the viewer understands the topic but the customer cannot finish, improve the written exception or record the missing screen. Success in one destination does not automatically establish success in the other.
You just read it. Now watch it.
ngram turns this post into a short explainer video: scenes, voiceover, and motion graphics included.






