How to Start a Faceless YouTube Channel With Golpo: Prompt, Script, and Own Narration
Start with an idea, an exact script, or your own voice. Golpo drafts or follows the narration, plans the scenes, designs them, narrates, syncs, and returns a finished explainer. Nine briefs show Prompt Mode, Script Mode, and Own Narration as a library you can open.

The practical answer: Start with an idea, an exact script, or your own voice. Golpo turns that source into a channel-ready explainer: it drafts or follows the narration, plans the scenes, designs the visuals, narrates, syncs picture and voice, and returns a finished video. You review the script before it renders, correct one frame if a label is wrong, and reuse the same channel style on the next episode.
A prompt asks Golpo to develop the narration from your topic and notes. Script Mode speaks the words you supply. Video Instructions direct the pictures. Voice Instructions direct a generated voice. Own Narration replaces that voice with your recording. They are different controls. Prompt Mode with script review is a full professional workflow. Choose the input by how much control that episode needs. The Prompt vs Script Mode guide covers the split. In the API, custom_script supplies narration. enable_script_only_mode generates a script and does not render that script as the video.
Fast start: one source-grounded pilot
Make the first episode from a question you can support with sources you already trust. Open the matching brief in the library below when you want a worked shape. Researching a 50-video niche is for the series you intend to sustain. It can wait until this pilot tells you the format is worth repeating.
- Source. One audience question plus the notes or document that support it. The everyday-logistics brief is a ready shape if you want a worked example.
- Mode. Use the selector below. A channel that cares about accuracy can stay in Prompt Mode and approve the draft.
- Settings. Sketch or Canvas, a duration, one voice, color if your plan includes it, and Edit script before creating video turned on.
- Script review. Read the draft against your notes. Remove anything the sources do not support. Then create the video.
- One correction. If a label or arrow is wrong, edit that frame in plain language. Frame editing changes the picture, not the narration. The editing guide shows the control.
- Reuse. Save the look as a Custom Style and make the next episode in the same series with that style and the same voice.
Open Golpo and make that pilot from the source you already have.
Choose the input
| What you have | Golpo workflow | What goes in the main input | Voice Instructions? |
|---|---|---|---|
| A topic, a brief, or research notes | Prompt Mode | A precise request telling Golpo what to explain and which notes to respect. Approve the draft before the video. | Yes, for generated narration, when your plan includes them |
| Final words that must be spoken | Script Mode | Narration only. About 1,050 characters per selected minute. Visual directions stay in Video Instructions. | Yes, for generated narration, when your plan includes them |
| An audio or video recording | Own Narration | Your uploaded or recorded audio or video. The recording sets the duration and the spoken language. | No. Re-record the line if the delivery is wrong. |
| A founder or instructor beside the explainer | Any of the above, plus AI Presenter | The same narration source. Turn on a stock presenter, or a presenter made from a selfie you are allowed to use. | Voice selection is separate from the presenter photo. Presenter API support is coming soon. |
Video Instructions are separate in all three narration workflows. They describe visual logic, continuity, text density, diagrams, colors, and things to avoid. Keep narration out of Video Instructions, and keep “speak slowly” out of Video Instructions. That sentence belongs in Voice Instructions, and only for generated speech.
Give the channel one look, one voice, and one scene map
The briefs below use built-in styles so the settings are easy to copy. To keep a channel recognizable, save one Custom Style from an image, a video, or a short description, then select it on the next episode. For the logistics show, that description can be a navy parcel, teal routes, and a cream field. Custom Style is on Business and above and on Pay As You Go, and API use also needs API access. It guides the pictures. It does not reproduce exact typography.
Use Custom Scenes when two ideas need their own frames. On the package episode, keep the network benefit in one scene and the delay trade-off in the next. Custom Scenes are on Growth and above and on Pay As You Go. You can move sentence boundaries inside the engine limit. The map does not rewrite the narration. Compact keeps a hub map together. Expanded gives a step-by-step handoff more room. Notebook is Compact-only. In the API, an unsuffixed style value selects Compact, and _legacy selects Expanded on the ten pre-Notebook styles. See Compact vs Expanded.
For dates and terms that must appear on screen, turn on on-screen text from script only. It is available on Canvas and Sketch. Golpo may show a subset of the script. It is not the caption track, and it does not verify the source. If you have a photo or clip you are allowed to use, Own Media places it inside the explainer. A generated tracking screen is not evidence of a carrier’s real interface. Own Media is on Business and above and on Pay As You Go.
Pick the voice the same way you pick the mode. A selected Golpo voice plus Voice Instructions directs generated delivery. An authorized Voice Clone generates new narration in a saved voice and needs permission. Own Narration uses a recording you supply. If a founder-led episode should show you beside the diagram, turn on AI Presenter. Layouts include side-by-side, circle, full-screen, and Auto. The presenter is synthetic. Create presenter episodes in the dashboard. Presenter API support is coming soon.
After the pilot is approved, later episodes can be queued through the Golpo API from Codex, Claude Code, GitHub Copilot, Cursor, or an MCP client, reusing the saved Custom Style. Scale includes API access. Business can add a paid API add-on. API Only is metered separately and does not include dashboard generation. YouTube upload, titles, and thumbnails stay in your pipeline.
Optional research: test a niche before you commit to a long series
Use this when you are choosing a series you plan to sustain. External research tools organize the decision. Make the first pilot from a question and sources you already have. The niche scorecard is the longer filter.
Find a niche with your own evidence
Do not begin with “What faceless niche has the highest RPM?” That question invites recycled lists, unstable revenue claims, and topics you may not be qualified to cover. Begin with an unfair advantage: experience, access, curiosity, a source base, or a way of explaining that you can sustain for 50 videos.
First, make an honest creator inventory
Write short answers to these questions before opening ChatGPT or Claude:
- What have I studied, built, repaired, managed, taught, researched, or lived through?
- Which questions do people repeatedly ask me?
- Which primary or credible sources can I access every week?
- Can Golpo explain this topic with processes, comparisons, maps, timelines, diagrams, or recurring characters?
- Which areas should I avoid because errors could harm people or require credentials I do not have?
- Can I list 30 genuinely different episode ideas without changing only the nouns?
Copy this niche-hypothesis prompt into ChatGPT or Claude
You are helping me generate hypotheses for an educational YouTube channel.
Do not claim that a niche is profitable, underserved, or trending without evidence I provide.
My real experience:
[paste 3-8 bullets]
Topics I can research for at least one year:
[paste list]
Sources or access I have:
[paste publications, datasets, books, professional experience, interviews, or archives]
Topics I will not cover:
[paste boundaries]
The videos will be faceless illustrated explainers made with Golpo. Strong formats include
processes, mechanisms, comparisons, maps, timelines, and worked examples.
Propose 10 narrow channel hypotheses. For each, give:
1. one specific audience;
2. one repeatable promise;
3. three recurring series;
4. ten materially different episode titles;
5. the evidence I must collect before choosing it;
6. accuracy, rights, and platform-policy risks;
7. why illustrated explanation fits—or does not fit.
Reject any hypothesis that depends on scraping other creators, reading articles aloud,
mass-producing interchangeable videos, impersonating an expert, or making unsupported
health, legal, financial, or political claims.
The output is a list of hypotheses, not research. Save the best three and investigate them yourself.
Do the evidence pass yourself
- Search YouTube like a viewer. Enter the main problem and several variations. Record the autocomplete phrases, not just the results you hoped to find.
- Review at least 20 relevant recent videos. Note title, channel size, publish date, views, format, angle, length, and what the video actually contributes. Do not conclude that one viral outlier proves a market.
- Read the comments. Capture repeated questions, corrections, requests for examples, and complaints about missing context. Ignore engagement bait.
- Test topic depth. Write 30 to 50 non-duplicate episodes across three series. If every title reduces to the same template, the niche is too thin.
- Audit sources. Identify at least three reliable source types you can use repeatedly. For example: official documentation, government data, peer-reviewed research, museum archives, standards bodies, or interviews with qualified practitioners.
- Check visual fit. Mark which ideas can be taught with a sequence, mechanism, comparison, map, timeline, or worked example. A niche built on celebrity clips or product footage may be a poor rights and format fit.
- Check business paths without inventing revenue. List plausible options such as ads, relevant affiliates, sponsorships, services, memberships, or a product. Verify eligibility, audience fit, and local rules; do not paste an assumed RPM into a forecast.
Paste your findings back into the model
I researched three YouTube channel hypotheses. Analyze only the evidence below.
If evidence is missing, mark it UNKNOWN. Do not fill gaps from memory.
HYPOTHESIS A:
[paste search phrases, 20-video notes, comment questions, source list, 30-topic test,
visual fit, risks, and business paths]
HYPOTHESIS B:
[paste findings]
HYPOTHESIS C:
[paste findings]
Score each from 1 to 5 on:
- clear recurring audience problem;
- evidence of current viewer interest;
- room for a distinct editorial contribution;
- 50-video topic depth;
- access to reliable sources;
- fit for illustrated explanation;
- manageable accuracy and rights risk;
- plausible business paths that do not depend only on ads.
For every score, quote the evidence from my notes. Then recommend one 3-video pilot.
Also give the strongest reason NOT to choose the winner.
This method uses AI as an analyst of evidence you collected. The niche scorecard goes deeper on defensibility, source burden, and format fit.
Write the channel operating brief when you are ready to name the show
When you are ready to name the show, reduce it to one page. Here is the operating brief for the logistics example. The other briefs in the library use the same kind of page with a different promise.
| Field | Exact example |
|---|---|
| Channel niche | Everyday logistics explained for curious adults |
| Promise | Understand the hidden systems that move ordinary things from one place to another |
| Audience | Non-specialists who enjoy practical systems, infrastructure, and business explanations |
| Series 1 | One object, end to end: parcels, groceries, luggage, waste, mail |
| Series 2 | Why the system behaves strangely: indirect routes, waiting, batching, bottlenecks |
| Series 3 | One mechanism in two minutes: barcodes, hubs, queues, cold chains, containers |
| Default format | Two-minute horizontal illustrated explainer |
| Editorial contribution | One researched mechanism, one concrete example, one limitation or trade-off in every episode |
| Visual system | Professional Clean, color on, one recurring navy parcel, simple route maps and process diagrams |
| Source rule | Keep a claim sheet; every number, date, quotation, and consequential claim gets a source before scripting |
This channel identity is narrow enough to be memorable but broad enough for multiple series. It also creates a repeatable visual language without making every episode interchangeable.
Nine briefs, as a library
The nine briefs below are examples you can copy. They are not a sequence you have to finish. Open the one that matches the source you have. Each one keeps the prompt or script, the Video Instructions, and the Voice Instructions in separate fields. The parcel, the Northstar project, and the water-tower note are hypothetical examples in this guide. In the Golpo fields, treat the names as the story’s own names so the narration stays on the explanation.
- Prompt: why a package takes an indirect route
- Prompt: why the Moon changes shape
- Prompt: how a Fresnel lens makes a lighthouse beam
- Script: why railroads needed time zones
- Script: why leaves change color
- Script: why bridges have gaps
- Own Narration: a client handoff checklist
- Own Narration: comparing fractions
- Own Narration: a three-column research note
Prompt Mode example 1 of 3: everyday logistics
Outcome: a two-minute horizontal episode called “Why Your Package Sometimes Travels in the Wrong Direction.” Use Prompt Mode when you have researched the subject but want Golpo to draft and structure the narration.
1. Validate the episode before opening Golpo
| Decision | Exact example |
|---|---|
| Audience question | Why does parcel tracking sometimes show a route that appears to move away from the destination? |
| Search phrases to inspect | “package went wrong direction,” “why packages go through hubs,” and carrier-name variations |
| Evidence to collect | Current search results, repeated viewer questions, official carrier explanations of sorting networks, and an operations source explaining hub-and-spoke networks |
| Original angle | Follow one hypothetical parcel and explain both the network benefit and the disruption trade-off |
| Claims deliberately excluded | No carrier-specific route, speed promise, cost saving, emissions claim, or delivery statistic without a direct source |
Create a claim sheet with four columns: claim, source URL, exact supporting passage, and wording allowed in the script. Do not paste a competing video's transcript into Golpo. Your sources should support the mechanism; your example and explanation should be your own.
Exact Prompt Mode configuration
| Golpo control | Set it to |
|---|---|
| Own Narration | Off |
| Script Mode | Off |
| Main prompt | Paste the prompt below |
| Engine | Golpo Sketch |
| Style | Professional Clean |
| Use color | On |
| Duration | 2 minutes |
| Orientation | Horizontal |
| Language | English |
| Display language | English |
| Voice | Female 1; reuse the same voice for the pilot |
| Pace | Fast |
| Background music | None for the first test |
| Edit script before creating video | On |
| Video Instructions | Paste the visual block below |
| Voice Instructions | Paste the delivery block below |
Main prompt: copy exactly, then replace the source notes
Create a two-minute educational explainer titled “Why Your Package Sometimes Travels
in the Wrong Direction.” The audience is curious adults with no logistics background.
Explain the hub-and-spoke idea in plain English: a parcel can move away from its final
destination because carriers consolidate many shipments through sorting hubs instead
of sending a separate direct vehicle for every origin-and-destination pair. Follow one
navy parcel from pickup, to local sorting, to a regional hub, to destination
sorting, and then delivery. Explain the operational benefit and one trade-off: shared
routes can improve network efficiency, but hubs can also create delay when disrupted.
Open with the apparent contradiction. Use one concrete journey. End with the takeaway
that the shortest-looking route is not always the route a network is designed to use.
Do not include statistics, named carriers, guaranteed delivery claims, or claims not
supported by the research notes below.
RESEARCH NOTES:
[Paste your verified notes and source summaries here. Include the source URL beside
each factual note. If the sources do not support a claim, leave it out.]
Video Instructions: paste into the Video Instructions field
Use one recurring navy parcel with a white label in every scene. Show the network as a
simple map with three labeled nodes: Local Depot, Regional Hub, Destination Depot.
Animate routes as clean arrows. Contrast a web of many direct routes with a simpler
hub-and-spoke diagram. Keep on-screen labels to five words or fewer. Use navy, teal,
cream, and amber. Prefer process diagrams and maps over decorative characters. Do not
show real carrier logos, branded uniforms, fake tracking interfaces, precise delivery
times, or maps that imply an actual carrier route. Finish on a five-step route recap.
Voice Instructions: paste into the Voice Instructions field
Curious, calm documentary narrator. Clear international English. Medium-fast delivery
with a brief pause after the opening question and before the final takeaway. Emphasize
“network” and “sorting hub.” Sound interested, not amazed. No sales tone, whispering,
shouting, exaggerated suspense, or motivational cadence.
2. Validate Golpo's draft before generation
With Edit script before creating video on, compare the draft sentence by sentence with the claim sheet. Remove invented numbers, named-carrier details, or claims that the shortest route is always inefficient. Confirm that the script explains a possible network design rather than pretending to reveal the actual route logic of every carrier.
3. Use this exact YouTube package
- Title: Why Your Package Sometimes Travels in the Wrong Direction
- Thumbnail: one navy parcel, a destination arrow pointing east, and a route bending west. Text: WRONG WAY?
- Description opening: “A parcel route can look inefficient when you view one shipment in isolation. This illustrated explainer follows one parcel through local sorting, a regional hub, destination sorting, and final delivery to show why shared networks sometimes use indirect paths.”
- Source block: list the official carrier-network and operations sources actually used; do not cite this guide as evidence for the logistics claims.
- CTA: “Next, see what actually happens inside a sorting hub.”
- Final QA: verify every arrow, remove real carrier branding, correct captions, and confirm the title does not promise that every unusual route has this explanation.
This is the complete Prompt Mode path: observed audience question → verified research notes → main prompt → Video Instructions → Voice Instructions → script approval → render review → YouTube package.
Prompt Mode example 2 of 3: beginner astronomy
Outcome: a two-minute episode called “Why the Moon Changes Shape.” This is a Prompt Mode example because NASA supplies a clear factual foundation and Golpo can organize it into a beginner-friendly explanation.
1. Research and editorial boundary
- Audience: adults and older students who confuse phases with Earth's shadow.
- Question: why does the illuminated part of the Moon appear to change during a month?
- Primary source: NASA's current Moon Phases explainer.
- Key facts to preserve: the Moon reflects sunlight; half is illuminated by the Sun; the phase seen from Earth changes with the Moon's position; ordinary phases are not caused by Earth's shadow.
- Boundary: do not introduce eclipse geometry, orbital-period numbers, or hemisphere-specific orientation unless separately sourced.
2. Exact Golpo configuration
- Own Narration: Off
- Script Mode: Off
- Engine: Golpo Sketch
- Style: Creative
- Use color: On
- Duration: 2 minutes
- Orientation: Horizontal
- Language / display language: English / English
- Voice: Female 1
- Pace: Fast
- Background music: None
- Edit script before creating video: On
3. Main Prompt
Create a two-minute beginner astronomy explainer titled “Why the Moon Changes Shape.”
Explain that the Moon does not make its own visible light; it reflects sunlight. The Sun
always illuminates half of the Moon, while the fraction of that illuminated half visible
from Earth changes as the Moon moves around Earth.
Correct the common misconception that ordinary Moon phases are caused by Earth's shadow.
Use one overhead spatial model with the Sun fixed on the left, Earth in the center, and
the Moon shown at new Moon, first quarter, full Moon, and third quarter positions. Pair
each position with the view from Earth.
Use only the NASA research notes pasted below. Do not introduce eclipse geometry, exact
orbital timing, astrology, hemisphere-specific tilt, or unsourced facts.
RESEARCH NOTES:
[Paste verified notes from https://science.nasa.gov/moon/moon-phases/ with the source URL
beside each note.]
4. Video Instructions
Keep one stable overhead diagram: yellow Sun on the left, blue Earth in the center, and
gray Moon moving through four labeled positions. Use parallel sunlight arrows. Beside
each orbital position, show a large circular Earth-view inset. Keep the Moon half-lit in
the space diagram while changing only the portion visible in the Earth-view inset. Use
labels of four words or fewer. Do not depict Earth's shadow touching the Moon during the
ordinary phase sequence. Do not add stars, zodiac symbols, spacecraft, or decorative
space scenes that obscure the geometry. End with four positions in one clean recap.
5. Voice Instructions
Patient science teacher. Clear English at a moderate pace. Pause after the misconception
question and before “The Sun always illuminates half of the Moon.” Emphasize “visible
from Earth.” No mystical tone, dramatic movie-trailer delivery, or childish voice.
6. Review and YouTube package
- Draft review: reject any line saying the Moon produces light or that Earth's shadow causes the monthly phase cycle.
- Title: Why the Moon Changes Shape (It Isn't Earth's Shadow)
- Thumbnail: four Moon phases surrounding one small Earth. Text: NOT A SHADOW
- Description opening: “The Moon is always half-lit by the Sun, but we see different portions of that illuminated half as the Moon moves around Earth. This visual model explains four familiar phases.”
- Source: link NASA's Moon Phases page.
- CTA: “Next, see what has to line up for a lunar eclipse.”
- Final QA: pause on all four diagrams, verify the lit side faces the Sun, correct phase labels, and check captions.
Prompt Mode example 3 of 3: lighthouse technology
Outcome: a two-minute history-of-technology episode called “How a Fresnel Lens Makes a Lighthouse Beam.” Prompt Mode works because the mechanism and history are grounded in a compact official source package.
1. Research and editorial boundary
- Audience: curious adults interested in how familiar technology works.
- Question: how can many thin glass sections direct lamp light into a useful lighthouse beam?
- Primary source: the U.S. National Park Service's Fresnel Lens explainer.
- Key facts: Augustin-Jean Fresnel developed the lighthouse lens design in the early 1820s; its prism sections bend and concentrate light; it is thinner than a conventional lens with comparable optical power.
- Boundary: avoid a universal visibility distance or efficiency percentage because lighthouse configurations differ.
2. Exact Golpo configuration
- Own Narration: Off
- Script Mode: Off
- Engine: Golpo Sketch
- Style: Infographics
- Use color: On
- Duration: 2 minutes
- Orientation: Horizontal
- Language / display language: English / English
- Voice: Female 1
- Pace: Fast
- Background music: None
- Edit script before creating video: On
3. Main Prompt
Create a two-minute illustrated explainer titled “How a Fresnel Lens Makes a Lighthouse
Beam.” Begin with a lamp sending light in many directions. Explain the problem with
making one large conventional lens: it would be thick and heavy. Then show how a Fresnel
lens divides the useful curved optical surface into thinner concentric sections and uses
prisms to bend and concentrate the lamp's light into a strong, directed beam.
Briefly identify Augustin-Jean Fresnel and the early-1820s lighthouse design. Keep the
focus on the optical idea, not a complete lighthouse history. Use only the National Park
Service research notes below. Do not give universal range, brightness, weight, or lives-
saved claims.
RESEARCH NOTES:
[Paste verified notes from https://www.nps.gov/articles/fresnellens.htm and retain the URL
beside each factual note.]
4. Video Instructions
Use a side-view optical diagram throughout. Start with one amber lamp and scattered rays.
Compare a thick conventional lens with a thinner stepped Fresnel profile. Magnify one
section to show a prism bending a ray toward the horizontal beam. Then assemble the
sections around the lamp into a simplified beehive-shaped lighthouse lens. Use amber for
light, cyan for glass, and navy for structure. Keep ray directions geometrically
consistent. Do not show impossible light bending, real lighthouse logos, unsupported
distance labels, or a photorealistic portrait of Fresnel. End with “lamp → prisms → beam.”
5. Voice Instructions
Curious engineering-museum narrator. Moderate pace with a short pause before the prism
close-up. Pronounce Fresnel as “fray-NEL.” Emphasize “thinner sections” and “directed
beam.” No heroic claims, nautical character voice, or exaggerated suspense.
6. Review and YouTube package
- Draft review: remove any unsupported claim that the lens magnifies the lamp's energy or guarantees a particular distance.
- Title: How a Fresnel Lens Makes a Lighthouse Beam
- Thumbnail: scattered rays entering a stepped lens and one beam leaving. Text: THIN LENS, BIG BEAM
- Description opening: “A Fresnel lens rearranges a large lens surface into thinner prism sections that direct lighthouse light into a concentrated beam. This episode shows the optical idea step by step.”
- Source: link the National Park Service explainer.
- CTA: “Next, see how rotating lenses created recognizable flash patterns.”
- Final QA: verify ray direction, terminology, pronunciation, dates, visual labels, and captions.
Script Mode example 1 of 3: history of ordinary systems
Outcome: a two-minute episode called “Why Railroads Needed Time Zones.” Script Mode is appropriate because the episode contains dates and historical claims that should not be improvised.
1. Validate the niche, question, and sources
| Decision | Exact example |
|---|---|
| Channel niche | The history of ordinary systems for viewers who want to know why modern standards exist |
| Channel promise | Explain one familiar standard through the problem, adoption, resistance, and consequence that shaped it |
| Episode question | Why did expanding rail travel make local town time difficult to coordinate? |
| Primary research set | The Smithsonian's Synchronizing Time collection and Time and Navigation timeline |
| Technical cross-check | NIST's archived World Time Scales history |
| Original contribution | Explain the coordination problem visually with two neighboring town clocks and one railway timetable |
Read the sources yourself and record the exact support for each historical statement. The example below uses only a small set of defensible claims: towns used local solar time; rail networks had to coordinate many regional times; North American railroads adopted a standardized railway-time system in 1883; and federal recognition followed in 1918.
Choose the duration first. Golpo currently allows up to 1,050 script characters per selected minute, so a two-minute selection provides up to 2,100 characters. The allowance is a ceiling, not a target.
Exact Script Mode configuration
| Golpo control | Set it to |
|---|---|
| Own Narration | Off |
| Script Mode | On |
| Duration | 2 minutes; set this before pasting the script |
| Script field | Paste only the approved narration below |
| Engine | Golpo Sketch |
| Style | Creative |
| Use color | On |
| Orientation | Horizontal |
| Language | English |
| Display language | English |
| Voice | Female 1 |
| Pace | Fast |
| Background music | None |
| Video Instructions | Paste the history visual block below |
| Voice Instructions | Paste the history delivery block below |
Exact two-minute script: paste into Script Mode
Before time zones, noon was local. A town could set its clock by the sun, so nearby
communities did not always show exactly the same time.
That was manageable when journeys and messages moved slowly. Railways changed the scale
of the problem. One timetable now had to coordinate trains, stations, crews, and
connections across many towns.
By the early 1880s, North American railroads were operating with nearly fifty regional
times. Reading a timetable could require knowing which railway time a station followed.
On November 18, 1883, most railroads in the United States and Canada adopted Standard
Railway Time. The system grouped locations into five zones, each with a uniform time.
Many cities followed, although the change also met resistance from people who preferred
local solar time.
The railroads did not instantly create one worldwide legal system. International and
government decisions developed separately, and the United States did not place standard
time into federal law until 1918.
The important change was coordination. A shared clock made timetables easier to connect
across a growing network. Time zones were not only about measuring the sun. They were
also a solution to moving people and information between places.
Video Instructions: paste into the Video Instructions field
Use a consistent 1880s illustrated railway-station setting. Begin with two neighboring
town clocks showing slightly different noon times beneath the same moving sun. Turn a
confusing timetable into a clean network diagram linking Town A, Junction, and Town B.
Then show a simplified map of North America divided into five broad railway-time zones.
Use period-appropriate clocks, trains, tickets, and typography without copying a modern
brand. Keep dates and labels large and readable. Distinguish local solar time, railway
standard time, the 1884 international conference, and 1918 federal law as separate
events. Do not show invented quotations, exact town-time differences, modern borders as
historical evidence, or photorealistic depictions of real people.
Voice Instructions: paste into the Voice Instructions field
Measured museum-documentary narrator. Clear English at a moderate pace. Pause briefly
after “Before time zones, noon was local,” before the date November 18, 1883, and before
the final sentence. Read 1883 as “eighteen eighty-three.” Curious and authoritative,
without nostalgia, theatrical suspense, or a sales tone.
2. Review and publish the history episode
- Script fidelity: compare every date and quantity against the Smithsonian and NIST sources. Do not let a visual imply that railroads alone created every modern national boundary.
- Title: Why Railroads Needed Time Zones
- Thumbnail: two station clocks showing different times above one train. Text: WHOSE NOON?
- Description opening: “Before standardized railway time, towns and railroads could keep different local times. This episode explains why a growing train network made that difficult—and what changed in North America in 1883.”
- Source block: link the Smithsonian Synchronizing Time collection, the Time and Navigation timeline, and the NIST history used above.
- CTA: “Next, see how the telegraph helped distant clocks agree.”
- Final QA: verify 1883, five zones, and 1918; check map labels; remove any unsupported costume, flag, or border detail; correct caption punctuation around dates.
This is the complete Script Mode path: audience question → primary-source ledger → approved narration → exact duration → Script Mode → Video Instructions → Voice Instructions → claim-by-claim render review → sourced YouTube package.
Script Mode example 2 of 3: seasonal tree science
Outcome: a two-minute episode called “Why Leaves Change Color.” Script Mode keeps chlorophyll, carotenoids, anthocyanins, daylight, temperature, and species differences from being flattened into an inaccurate one-line explanation.
1. Research and source ledger
- Audience: families, students, and curious adults looking for a plain-language seasonal explanation.
- Primary source: the U.S. National Park Service's current Learn About Fall Colors explainer.
- Claims to preserve: chlorophyll gives leaves much of their green appearance; yellow-orange carotenoids are present but often masked; chlorophyll breaks down in fall; anthocyanins contribute red and purple in some species; species and weather affect the display.
- Boundary: do not imply every leaf contains or produces the same pigment mix, or that cold alone causes all fall color.
2. Exact Golpo configuration
- Own Narration: Off
- Script Mode: On
- Duration: 2 minutes, selected before pasting
- Engine: Golpo Sketch
- Style: Creative
- Use color: On
- Orientation: Horizontal
- Language / display language: English / English
- Voice: Female 1
- Pace: Fast
- Background music: None
3. Exact script
Why does a green leaf turn yellow, orange, or red in autumn?
During spring and summer, leaves contain abundant chlorophyll. This green pigment helps
capture light energy for photosynthesis, and its color masks other pigments already in
the leaf, including yellow and orange carotenoids.
As days shorten and temperatures change, many deciduous trees stop renewing chlorophyll.
The chlorophyll breaks down, so the green fades and the carotenoids become easier to see.
Red and purple require another part of the story. In some species, pigments called
anthocyanins form in the leaf during autumn. Their amount can vary with the species,
sunlight, temperature, and other conditions.
That is why one tree may turn yellow while another becomes red, and why the same tree can
look different from one year to the next. Brown colors can also come from pigments and
tissues remaining as the leaf dies.
Fall color is not one dye replacing another overnight. It is a changing mixture: green
chlorophyll declines, yellow-orange pigments become visible, and some leaves add red or
purple pigments before they fall.
4. Video Instructions
Follow one branch containing three deciduous leaves. Begin with a cutaway of a
green leaf showing a dominant Chlorophyll layer over smaller Carotenoids. As the calendar
moves from summer to fall, reduce the green layer rather than repainting the leaf
instantly. Split into three outcomes: yellow-orange carotenoids visible, red-purple
anthocyanins present in some species, and brown tissue. Use green, yellow, orange, red,
purple, and brown consistently. Do not show pigment molecules as living characters, claim
all species follow one path, or state that frost alone causes the change. End with a
three-part pigment recap.
5. Voice Instructions
Warm science educator. Moderate pace. Pronounce chlorophyll clearly and anthocyanins as
“an-thoh-SY-uh-ninz.” Pause after the opening question and between the yellow-orange and
red-purple explanations. No nursery-story voice or claim that every tree behaves alike.
6. Review and YouTube package
- Title: Why Leaves Change Color in Autumn
- Thumbnail: one leaf divided green, yellow, and red. Text: WHAT CHANGED?
- Description opening: “Autumn color comes from changing leaf pigments—not one universal switch. This explainer follows chlorophyll, carotenoids, and anthocyanins through the seasonal transition.”
- Source: link the National Park Service explainer.
- CTA: “Next, see why some trees drop their leaves while others stay green.”
- Final QA: verify pigment names, avoid universal claims, inspect every color label, and correct captions.
Script Mode example 3 of 3: bridge engineering
Outcome: a two-minute episode called “Why Bridges Have Gaps.” Script Mode is appropriate because the explanation needs to distinguish thermal movement, expansion-joint purpose, joint limitations, and jointless designs.
1. Research and source ledger
- Audience: non-engineers curious about familiar infrastructure.
- Primary sources: FHWA guidance on bridge deck expansion joints and thermal expansion of concrete.
- Claims to preserve: materials change length with temperature; some bridge joints accommodate thermal movement; joints must also manage traffic and water; many agencies minimize joints because they can leak and require maintenance; some bridges use jointless or integral designs.
- Boundary: never use the video to diagnose a real bridge or imply that every visible crack or gap is intentional.
2. Exact Golpo configuration
- Own Narration: Off
- Script Mode: On
- Duration: 2 minutes, selected before pasting
- Engine: Golpo Sketch
- Style: Professional Clean
- Use color: On
- Orientation: Horizontal
- Language / display language: English / English
- Voice: Female 1
- Pace: Fast
- Background music: None
3. Exact script
That gap across a bridge deck may look unfinished. In many bridges, it is a designed
movement joint.
Bridge materials change length as temperature changes. The movement may be small for a
short piece, but across a long structure it has to be considered. Traffic, wind, and
other loads can add movement too.
An expansion-joint system creates a controlled location where parts of the bridge can
move relative to each other while vehicles continue across the deck. The joint also has
to help manage water and debris.
But joints are not maintenance-free. A damaged or leaking joint can expose nearby
concrete, steel, bearings, and supports to water and contaminants. That is one reason
bridge owners often try to minimize the number of joints.
Some bridges use continuous or jointless designs that accommodate movement through
other details, such as integral abutments. The correct design depends on the structure,
materials, length, climate, and engineering requirements.
So not every bridge needs the same gap, and not every visible crack is an expansion
joint. The useful idea is controlled movement: engineers give the structure a planned
way to respond as conditions change.
4. Video Instructions
Use one simplified side-view bridge and one deck close-up. Show a cool blue condition and
a warm amber condition with a subtle length change; do not exaggerate it into buckling.
Magnify one designed expansion joint with two deck edges, a sealed gap, traffic passing
above, and water directed away. Then compare Jointed Bridge and Jointless/Integral Design
without declaring either universally better. Use clean arrows labeled Thermal Movement.
Do not depict a real bridge, identify a crack as safe, provide inspection advice, or show
catastrophic collapse. End with “controlled movement, project-specific design.”
5. Voice Instructions
Calm civil-engineering educator speaking to non-engineers. Moderate pace with brief
pauses after “designed movement joint” and “not maintenance-free.” Emphasize “controlled
movement” and “project-specific.” No alarmist tone or suggestion that viewers can judge
bridge safety from appearance.
6. Review and YouTube package
- Title: Why Bridges Have Gaps
- Thumbnail: close-up of a clean deck joint with warm/cool arrows. Text: THE GAP IS PLANNED
- Description opening: “Many bridge-deck gaps are engineered joints that accommodate movement, but joints also introduce maintenance challenges. This video explains the trade-off without diagnosing any real structure.”
- Sources: link both FHWA references.
- CTA: “Next, see how a jointless bridge accommodates movement.”
- Final QA: verify engineering terminology, remove diagnostic language, confirm movement arrows, and correct captions.
Own Narration example 1 of 3: practical work systems
Outcome: a first-person episode called “My 3-Part Client Handoff Checklist.” Own Narration is appropriate because the value comes from the creator's real process and voice, not an AI persona pretending to have client experience.
1. Validate the channel and prepare the evidence
| Decision | Exact example |
|---|---|
| Channel niche | Simple operating systems for independent consultants and small service businesses |
| Audience question | What should a freelancer give a client when a project ends? |
| First-person evidence | Your own handoff checklist, redacted project notes, and recurring client questions you personally observed |
| External research | Inspect current YouTube results and comments for “client handoff checklist,” “freelance project handoff,” and “offboarding a client” |
| Boundary | Present this as your working process, not a universal legal, security, or contractual standard |
| Privacy rule | Do not show client names, private files, email addresses, account credentials, contract terms, or confidential screenshots |
Before recording, use the project name “Northstar Website Refresh” and filenames that are not a real client’s. The name is hypothetical in this guide. It gives the pictures a concrete project without exposing a client.
2. Record this complete narration
Use a quiet room and keep the microphone position fixed. Read in your normal professional voice. Record a clean take as an audio file, or use Golpo's microphone recorder.
I used to end a client project by sending one final email with a folder link. The work
was finished, but the handoff was not. Questions arrived later: Which file is final?
Who owns this account? What happens next month?
Now I use a three-part handoff.
First: files. One clearly named final folder contains the approved deliverables, source
files the agreement includes, and a short index explaining what each item is.
Second: ownership. I list each account or tool, who controls it, and the agreed transfer
step. I never place passwords inside the handoff document.
Third: next actions. I write what the client should do next, what I will still do, and
the date any support period ends.
This is my process, not a universal rule. Adapt it to your contract, security needs,
and the kind of work you deliver.
Before your next project closes, check three things: files, ownership, and next actions.
Exact Own Narration configuration
| Golpo control | Set it to |
|---|---|
| Own Narration | On |
| Input | Upload the clean audio file, or choose microphone recording and record the script above |
| Script Mode | Do not use; the recording supplies the narration |
| Duration | No manual value; Golpo derives it from the recording |
| Spoken language | No translation setting; the recording supplies the spoken language |
| Engine | Golpo Sketch |
| Style | Dry Erase |
| Use color | On |
| Orientation | Horizontal |
| Pace | Normal |
| Background music | None |
| Voice selection | Not applicable |
| Voice Instructions | Not applicable; do not paste anything |
| Video Instructions | Paste the client-handoff visual block below |
| Rights confirmation | Confirm only if you own the recording or have explicit permission to use it |
Video Instructions: paste into the Video Instructions field
Use the project “Northstar Website Refresh.” Begin with a cluttered
email and an unlabeled folder, then reorganize the handoff into three columns: Files,
Ownership, Next Actions. Under Files, show a Final Deliverables folder, an included source
folder, and a one-page index. Under Ownership, show accounts moving from Consultant to
Client without displaying passwords or real interfaces. Under Next Actions, show two
owners and one support-end date on a simple timeline. Use navy, green, cream, and coral.
Keep labels to five words or fewer. Do not show real logos, client data, email addresses,
credentials, contracts, financial amounts, or promises that this process meets every
legal or security requirement. Finish with a three-box checklist.
Voice Instructions: leave the field unused. Own Narration uses the delivery in your recording. If you dislike the pacing or emphasis, re-record the line; do not try to correct your voice with AI Voice Instructions.
3. Review and publish the Own Narration episode
- Audio review: listen for clipped words and long pauses. Confirm that “this is my process” remains in the final narration.
- Privacy review: inspect every generated label and inserted asset for accidental client information. Use only the Northstar project named in this brief.
- Title: My 3-Part Client Handoff Checklist
- Thumbnail: one messy folder turning into three clean boxes. Text: FILES · OWNER · NEXT
- Description opening: “This is the three-part handoff I use to close consulting projects: organize the final files, document account ownership, and make the next actions explicit. Adapt it to your own contract, security requirements, and deliverables.”
- CTA: “Next, build the one-page project index that goes inside the final folder.”
- Final QA: correct captions, confirm the disclaimer is present, remove confidential details, and make sure the visual never shows passwords inside the handoff.
If you upload a video rather than audio, choose Audio in Video when you want only its audio, or Picture in Picture when you want the presenter visible. The Own Narration guide covers upload and layout controls in detail.
This is the complete Own Narration path: personal evidence → a project name that is not a real client → recorded narration → Own Narration upload → Video Instructions → audio and privacy review → YouTube package.
Own Narration example 2 of 3: a teacher's fraction method
Outcome: a two-minute teaching episode called “How I Compare Fractions Visually.” Own Narration lets the teacher preserve their real classroom phrasing while Golpo supplies consistent diagrams.
1. Validate the lesson
- Channel niche: short visual math lessons for parents, tutors, and upper-elementary learners.
- Lesson objective: compare three-fourths and five-eighths by representing equal-sized wholes.
- Teacher evidence: use your own explanation and examples; check the arithmetic before recording.
- Boundary: state that the wholes must be the same size. Do not teach “the larger numerator wins” as a general rule.
- Accessibility: narration must identify every important difference instead of relying on color alone.
2. Record this narration
When students compare three-fourths and five-eighths, I do not start with a shortcut. I
start with two equal-sized bars.
The first bar is divided into four equal parts, and I shade three. The second is divided
into eight equal parts, and I shade five.
The pieces are different sizes, so the numerators alone do not settle the comparison.
I redraw three-fourths in eighths. Each fourth becomes two eighths, so three-fourths is
the same amount as six-eighths.
Now the comparison is direct: six-eighths is greater than five-eighths. Therefore,
three-fourths is greater than five-eighths.
The important condition is that both bars represent the same-sized whole. If the wholes
are different sizes, the picture does not support the comparison.
My check has three steps: use equal wholes, rename the fractions with a common
denominator, and compare the number of equal-sized parts.
3. Exact Golpo configuration
- Own Narration: On
- Input: record with the microphone, or upload your clean audio recording
- Script Mode: Do not use
- Duration: automatic from the recording
- Engine: Golpo Sketch
- Style: Crayon
- Use color: On
- Orientation: Horizontal
- Pace: Normal
- Background music: None
- Voice selection: Not applicable
- Voice Instructions: Not applicable; leave unused
- Rights confirmation: confirm only for a recording you own or have permission to use
4. Video Instructions
Use two identical horizontal fraction bars labeled A and B. Keep both wholes exactly the
same total width. Divide A into four equal sections and shade three blue. Divide B into
eight equal sections and shade five orange. When the narration renames three-fourths,
split each fourth in A into two without changing the shaded area, producing six blue
eighths. Then compare six-eighths and five-eighths with one-section outlines. Display the
symbols 3/4 = 6/8 > 5/8 only after the visual transformation. Use patterns as well as
color for accessibility. Do not change bar size, use pizza slices, add unrelated
characters, or imply the numerator-only shortcut works.
5. Review and YouTube package
- Math review: count every partition and shaded part; verify equal whole sizes throughout.
- Title: How I Compare Fractions Visually: 3/4 vs 5/8
- Thumbnail: two equal bars, with six blue eighths versus five orange eighths. Text: WHICH IS BIGGER?
- Description opening: “This visual lesson compares three-fourths and five-eighths by converting both amounts to equal-sized eighths. The key is to begin with equal wholes.”
- CTA: “Next, use the same model to compare two-thirds and three-fifths.”
- Final QA: check arithmetic, spoken fractions, visual partitions, accessible patterns, captions, and reading order.
Own Narration example 3 of 3: a creator's research-note system
Outcome: a first-person episode called “The 3-Column Research Note I Use Before Every Video.” It demonstrates how a faceless creator can make the channel visibly original without claiming that one system is universal.
1. Validate the episode
- Channel niche: transparent research and production systems for educational creators.
- Audience question: how do I stop losing the connection between a claim, its source, and the visual that will explain it?
- Evidence: your own blank template and one hypothetical worked example.
- Boundary: present it as your workflow, not a substitute for legal review, academic citation rules, or subject-matter expertise.
- Privacy: use the episode “How City Water Towers Work.” The source card in this brief is hypothetical. Show no private research accounts or unpublished client material.
2. Record this narration
Before I script an educational video, I build one note with three columns: Claim, Source,
and Visual.
The Claim column contains one sentence I may say. If the sentence contains a date,
number, quotation, comparison, or cause, I make it specific enough to check.
The Source column contains the exact page and the passage that supports the claim. A link
by itself is not enough, because I need to know what the source actually proves.
The Visual column answers a different question: what should the viewer understand here?
For a process, I use steps. For a comparison, I use two aligned examples. For change over
time, I use a timeline.
If a claim has no source, it does not enter the script. If a visual implies more than the
source supports, I simplify the visual.
This is my production check: can I trace the words, evidence, and picture before I ask a
video tool to generate anything?
3. Exact Golpo configuration
- Own Narration: On
- Input: upload a clean audio recording, or record with the microphone
- Script Mode: Do not use
- Duration: automatic from the recording
- Engine: Golpo Sketch
- Style: Professional Clean
- Use color: On
- Orientation: Horizontal
- Pace: Normal
- Background music: None
- Voice selection: Not applicable
- Voice Instructions: Not applicable; leave unused
- Rights confirmation: confirm only for your own or authorized recording
4. Video Instructions
Show one recurring research sheet with three large columns: Claim, Source, Visual. Use the
episode “How City Water Towers Work.” In Claim, place one short sentence. In
Source, show an agency page card plus one highlighted supporting line;
do not invent a real URL or agency logo. In Visual, convert the supported mechanism into
a simple tank-and-pipe process diagram. Use navy for claims, green for evidence, and
amber for visuals. Animate a trace line across all three columns. When a source is
missing, stop the claim before it reaches the script. Do not show private browser tabs,
real account names, fake quotations, or claims that this workflow guarantees accuracy.
5. Review and YouTube package
- Process review: the source card in this brief is hypothetical. It must not look like a real citation. The narration should keep the workflow in the first person.
- Title: The 3-Column Research Note I Use Before Every Video
- Thumbnail: one sheet divided into Claim, Source, and Visual. Text: DON'T LOSE THE SOURCE
- Description opening: “My pre-script research note keeps each claim connected to its supporting passage and intended visual. This episode shows the three columns with one worked example.”
- CTA: “Next, turn the completed note into a Script Mode narration.”
- Final QA: remove private data, check the disclaimer, correct captions, and confirm no invented source appears real.
What belongs in Video Instructions
Good Video Instructions define a repeatable visual grammar. They do not retell the entire script. Use this order:
- Continuity: the recurring character, object, place, or system that should remain recognizable.
- Visual logic: maps for movement, timelines for chronology, diagrams for mechanisms, side-by-side frames for comparisons.
- Text rules: maximum label length, essential terms, and whether fake interfaces are forbidden.
- Palette and style: a few colors and the selected Golpo style, not a paragraph of art jargon.
- Exclusions: logos, unsupported numbers, real-person likenesses, confusing decoration, or sensitive imagery.
- Ending: a recap, decision path, checklist, or other useful final visual.
Avoid instructions such as “make it viral,” “add engaging B-roll,” or “use cinematic shots.” They do not tell an illustrated explainer what knowledge to visualize. The Video Instructions guide provides more patterns.
What belongs in Voice Instructions
Voice Instructions should define delivery, not content. Use:
- persona: documentary narrator, teacher, technical trainer, storyteller;
- tone: calm, analytical, warm, serious, playful;
- pace: measured, medium-fast, deliberate;
- pauses: after the hook, before a conclusion, between steps;
- emphasis and pronunciation: only for terms that genuinely need it;
- negative constraints: no sales tone, shouting, forced excitement, or melodrama.
Do not ask the voice to sound exactly like a real person. If you need a consistent version of your own voice, use Golpo's consent-based voice-cloning workflow where available. Otherwise, select one built-in voice and keep it consistent across the pilot. See the Voice Instructions guide.
The next two episodes in the same series
Pick one brief from the library and produce the next two episodes in that same series, with the same saved Custom Style and the same voice, so a viewer can see the promise.
| Channel tested | Episode 1 from this guide | Episode 2 | Episode 3 |
|---|---|---|---|
| Everyday logistics | Why Your Package Sometimes Travels in the Wrong Direction | What Happens Inside a Sorting Hub? | How a Cold Chain Keeps Food Cold |
| Beginner astronomy | Why the Moon Changes Shape | What Causes a Lunar Eclipse? | Why the Moon Rises Later Each Day |
| Lighthouse technology | How a Fresnel Lens Makes a Lighthouse Beam | How Rotating Lenses Created Flash Patterns | Why Lighthouse Lenses Came in Different Orders |
| History of ordinary systems | Why Railroads Needed Time Zones | How the Telegraph Synchronized Clocks | Why Railway Watches Became Safety Tools |
| Seasonal tree science | Why Leaves Change Color in Autumn | Why Some Trees Stay Green | How Trees Prepare to Drop Leaves |
| Everyday bridge engineering | Why Bridges Have Gaps | How Jointless Bridges Move | Why Bridge Bearings Matter |
| Practical work systems | My 3-Part Client Handoff Checklist | The One-Page Project Index I Give Clients | How I Define a Support Cutoff |
| Visual math teaching | How I Compare Fractions Visually | Comparing Two-Thirds and Three-Fifths | Why Equal Wholes Matter |
| Creator research systems | The 3-Column Research Note I Use Before Every Video | How I Turn Sources Into a Script | My Final Claim-Checking Pass |
Publish the three pilots close enough together that a new viewer can understand the channel. Do not scale merely because generation is fast. First review whether the episodes deliver different lessons, whether comments reveal useful next questions, whether the source burden is sustainable, and whether the opening and packaging can improve without becoming misleading.
Review the render before YouTube
- Watch once without pausing. Does the explanation answer the title's promise? Is any section confusing or slow?
- Compare the audio to the approved input. In Script Mode, confirm no sentence, number, proper noun, or qualification changed. In Own Narration, listen for room noise, clipped words, and long silences.
- Inspect every scene. Check routes, labels, diagrams, dates, symbols, continuity, and unintended implications. A polished image can still be factually wrong.
- Correct one frame. If the logistics map labels the hub wrong, edit that label in plain language. The first edited version is free across sessions until finalized. Frame editing is on all paid plans, and a later 2-minute edited version is charged 2 credits for that version. It does not change the narration. See the Golpo editing guide.
- Check rights. Use only music, recordings, images, video, logos, quotations, and other media you own or are allowed to use.
- Export and caption. Download when your plan permits, upload to YouTube, and correct the automatic captions against the final audio.
YouTube packaging: title, thumbnail, description, and CTA
Golpo produces the video asset; YouTube packaging remains a separate editorial job.
- Title: promise the actual explanation. Example: “Why Your Package Sometimes Travels the Wrong Way.”
- Thumbnail: show one contradiction, not six small scenes. Example: one navy parcel, a destination arrow pointing east, and the route bending west. Suggested text: “WRONG WAY?”
- Description: summarize the mechanism in two useful sentences, then list sources and any relevant disclosure. Do not keyword-stuff.
- Chapters: use them when the video is long enough to contain distinct sections.
- CTA: point to the next related question. “Next, see how a sorting hub decides where the parcel goes” is stronger than three unrelated asks.
- Captions: correct terminology and proper nouns manually.
Originality, AI, and monetization boundaries
Faceless presentation is not itself the problem. YouTube's current monetization rules expect original and authentic value and can reject channels whose videos are generic, repetitive, mass-produced, or minimally transformed. The policy also specifically warns about generic AI templates and AI personas delivering advice on sensitive topics such as health, law, finance, or politics. Read the current YouTube channel monetization policies before choosing or scaling a niche.
Your editorial contribution should be visible in every episode: original research, a distinct explanation, a worked example, primary-source interpretation, practitioner experience, a comparison, or a clearly argued point of view. Changing the subject nouns inside one reusable script is not enough.
YouTube also asks creators to disclose meaningfully altered or synthetic content when it appears realistic—for example, depicting a real person saying something they did not say or a realistic event that did not happen. Unrealistic illustration and production assistance may be treated differently. Use the current altered or synthetic content guidance when uploading. A disclosure does not replace permission, copyright review, or fact-checking.
Pre-publish checklist for every episode
- The title and thumbnail match what the video actually delivers.
- The hook creates curiosity without inventing danger, income, urgency, or certainty.
- Every statistic, date, quotation, causal claim, and recommendation is verified.
- The narration contains no prompt fragments, stage directions, or source URLs.
- Video Instructions do not contradict the script.
- The selected orientation is Horizontal for the main YouTube episode; Vertical is used only for a deliberately rewritten Short.
- On-screen text is readable on a phone.
- AI pronunciation, captions, route arrows, timelines, and labels are correct.
- Inserted media and narration are cleared for use.
- Required disclosures are added in YouTube.
- The description contains source links and the CTA leads to a genuinely related next video.
FAQ
What is the difference between a Golpo prompt, script, Video Instructions, and Voice Instructions?
A prompt gives Golpo the topic and asks it to develop the narration. You review that draft before the video is created. Script Mode supplies the exact words to narrate. Video Instructions control the visual treatment. Voice Instructions control generated delivery and do not apply when Own Narration is enabled. In the API, custom_script supplies narration. enable_script_only_mode generates a script and does not render that script as the video.
Which Golpo workflow should a new YouTube channel use?
Choose by the control that episode needs. Prompt Mode, with Edit script before creating video, is a professional way to turn a sourced idea into a finished explainer. Script Mode is for wording that must be spoken exactly. Own Narration is for a recording that should drive the pictures. A channel does not become more serious by leaving Prompt Mode.
Can ChatGPT or Claude choose a profitable niche for me?
They can organize hypotheses and score research you provide. They should not invent demand, competitor, or revenue evidence. Verify current searches, channels, comments, sources, and business models yourself when you are choosing a series to sustain. Make the first pilot from a question and sources you already have.
Do Voice Instructions work with Own Narration?
No. Own Narration uses the supplied recording, so voice selection and Voice Instructions do not apply. Video Instructions still direct the generated visuals. An authorized Voice Clone is a different control: it generates new narration in a saved voice and needs permission. Voice Clone is on Business and above and on Pay As You Go.
Can a faceless AI-assisted YouTube channel be monetized?
It can be eligible if it meets YouTube's current requirements and policies. The channel still needs original, authentic value. Repetitive, mass-produced, misleading, or minimally transformed content can be ineligible. A finished Golpo video does not by itself establish monetization.
Can I use the same video for Shorts?
Make a separate vertical version with one self-contained promise. Author it for the vertical frame. Creator and higher plans currently include vertical video. Check the pricing page for current availability.
Does Golpo publish directly to YouTube?
Golpo creates the video. You handle the upload, title, thumbnail, description, captions, chapters, disclosures, scheduling, comments, and analytics. After a pilot is approved, the API can generate later episodes from Codex, Claude Code, GitHub Copilot, Cursor, or an MCP client. Publishing stays in your pipeline. Presenter API support is coming soon.
Related guides
- Best Faceless YouTube Niches for Educational Channels — score a niche, then prototype the explanation.
- Complete Golpo AI Tutorial — dashboard controls from creation to Library.
- Script to Video in Minutes — character limits, script preparation, and fidelity review.
- Golpo Own Narration Guide — upload audio or video, or record with a microphone or webcam.
- Video Instructions in Golpo — direct the pictures without putting those words in the narration.
- Voice Instructions in Golpo — direct tone, pace, emphasis, and pronunciation of generated narration.
- Every Golpo Video Style — compare built-in styles before you save a Custom Style.
- Run Multiple YouTube Channels — one desk, a saved style and voice per show, and a separate publication review.
Make one pilot
Make one source-grounded pilot now. Choose Prompt Mode, Script Mode, or Own Narration because of the control that episode needs. If you already have notes on one audience question, start there in Golpo. Approve the script, correct one label if a frame is wrong, and reuse the saved style on the next episode in that series.
Tags


