Editing, exporting and getting your video found
Researched and reviewed I checked it against primary sources. How I write these guides →
In this guide
Cut the video for clarity first, then add captions and on-screen text, export it and publish it on a page that gives it context. If a video matters for search, give it its own watch page with a title, description, transcript, proper thumbnail and VideoObject schema.
Most videos that flop weren't badly shot. They were cut too long, had no captions, and were dropped onto a page with no title, no context and no reason to press play.
This is my edit-to-publish routine for small teams, including the video SEO that helps people find it on your own website, not just on YouTube.
Cut before you finish
Effects, graphics and export settings come last. I start with two questions. What does the viewer need to understand first, and what can I remove so the idea arrives faster?
A better edit does more than shorten the timeline. It clears hesitation, removes repetition, puts things in the right order and lets the viewer move through the video without friction. If that layer is weak, polish can only do so much.
What to get right first depends on the kind of video.
| Video type | What tends to matter most first | What can stay simpler |
|---|---|---|
| Interview-led video | Clear editing rhythm, readable speaker identification, captions that support sound-off viewing, and enough pacing control to keep answers focused | Heavy graphics, flashy transitions, or overly stylised text treatments that distract from the speaker |
| Educational or explainer video | Clarity of structure, clean lower-screen text, strong subtitles, and a page layout that supports embedded viewing without confusion | Complex effects, decorative motion, or extra editing tricks that do not help understanding |
| Short branded piece | A tight cut, clear opening seconds, disciplined runtime, and a finished page context that supports the message rather than burying it | Long introductions, too many text layers, or a heavier edit than the idea actually needs |
| Social-first video | Fast visual clarity, subtitles for sound-off viewing, strong pacing, and a mobile-friendly editing workflow that keeps turnaround realistic | Desktop-level complexity, elaborate packaging, or stylistic extras that slow down production without improving attention |
| Website-first embedded video | Clear structure, useful captions, sensible runtime, and page-level context that improves discoverability and helps the video make sense in place | Over-editing, trend-led transitions, or visual choices that matter less than clarity and page usefulness |
Pacing that earns the runtime
A short video still drags if it repeats itself, and a longer one holds attention when every section has a job, so I judge the structure rather than the clock. There's more on that in how long should a video be.
Captions and on-screen text
A lot of people watch with the sound off (on a train, in an open-plan office, scrolling in bed), so I treat captions as part of the edit, not an extra at the end. They also make the video accessible and easier to follow for anyone splitting their attention. I cover open versus closed captions, fonts and how to check them in subtitles and captions for video.
On-screen names and titles do a different job. In interviews, explainers and training videos, a lower third tells the viewer who is speaking and why they should listen, and that small bit of context makes the whole piece feel more confident. Keep it short, keep it clear of the speaker's face, and leave it up long enough to read. There are design tips and common mistakes in lower thirds.
Publishing video on your own site
A video isn't finished when the export is done. If it lives on a website, the page around it is part of the viewing experience. The copy, the way the video is introduced and the context it sits in all affect whether people understand what they're watching, and whether search engines can read the page well enough to show it. Drop a good edit onto a bare page and it loses most of its impact.
Before I publish, I check that the page has each of these.
- The right host. YouTube, Vimeo or self-hosted each suit different jobs.
- A page of its own if the video matters for search (more on that below).
- A title and short description on the page itself, written for the person deciding whether to press play.
- A transcript below the video, so people can skim it and search engines can read what's said.
- A thumbnail that shows what the video is about, not a random frame.
VideoObjectschema, so search engines get the video's title, description, thumbnail and upload date.
One rule catches a lot of people out. Google shows video results for a watch page, which Google describes as a page whose main purpose is to show one video. A video added to a blog post or a service page to support the text isn't on a watch page, so it won't usually get a video result of its own. If a video matters for search, give it its own page with everything above. Google also needs a valid thumbnail before a video can appear in its video features. Once the page is live, the video indexing report in Google Search Console shows which of your watch pages have an indexed video. Google's video best practices have the detail, including video sitemaps and key moments (chapters).
Which editing tool for which job
If the project has layered audio, heavier graphics or a strict delivery spec, edit on a desktop (see best desktop video editing software). If it's phone-shot, quick-turnaround or social-first, a phone editor is faster and no compromise (see best video editing apps for phones). For a small team, the best workflow is the one you can repeat every week without it dragging.