You have a video ready and a page where it belongs. The next step looks simple: copy something from the video service and paste it into your website. But a video URL, an embed snippet and an uploaded file are different inputs. Putting the right one in the wrong editor field can leave you with a link, visible code or an empty space.
To embed video on a website, first identify what your editor accepts. Use a supported-provider video URL in a URL-based embed block, or put the provider’s supplied HTML into an appropriate HTML area. Then save the page and test the result outside the editor. The installation is not finished just because a preview looks correct.
Choose the correct input before you start
Look at the field you are filling in, not just the name of the video service. These are three different routes:
- Video URL: A link to the video on its provider’s site. Use it when the website editor explicitly supports embedding from that provider through a URL field.
- Embed HTML: A snippet supplied for placing the player on another page. Use the editor’s supported HTML or code-embedding area, following the provider’s instructions.
- Video file: The media itself. An upload control is asking for a file, not a watch-page link. Uploading is a separate workflow from the hosted-video embedding covered here.
Do not manually turn a watch-page URL into supposed embed code. Retrieve the actual code from the provider, or use your editor’s documented URL-based route. This keeps installation decisions separate from guesses about how the player works.
Prepare the source and the destination page
Before editing, confirm which video version should appear and who should be able to watch it. Keep the source page available so you can compare it with the embedded result. Also identify the exact page section that will receive the player.
Work in a draft or staging page where possible. Save a copy of the existing section before replacing anything. If the site uses a page builder, establish which editor actually owns that section; pasting into a different editing surface can make later maintenance confusing.
Write down the input type you are using. “Provider video URL in an Embed block” is a clearer handoff note than “video added.” It tells the next editor where to investigate if the source changes.
Embed a supported video URL in WordPress
WordPress’s block editor supports URL-based embedding from services including YouTube and Vimeo. Its official embedding documentation distinguishes this from uploading the media to WordPress.
- Open the intended post or page in the block editor.
- Add an Embed block, or the supported provider’s dedicated embed block.
- Paste the video URL into the block’s URL field and complete its embed action.
- Save the draft and inspect the page preview.
This route depends on provider support. A block accepting YouTube URLs does not establish that it accepts every video service’s URL. If you have been supplied HTML instead, use the HTML route below rather than pasting the snippet into a URL field.
Use supplied embed HTML when that is the intended route
Get the snippet from the player or hosting provider you intend to display. For example, YouTube’s desktop procedure is to open the video, choose Share, choose Embed and copy the supplied HTML. That sequence is documented in YouTube’s embedding guidance; it is not a universal menu sequence for other players.
In WordPress, add a Custom HTML block and enter the supplied markup using its editing interface. Preview the result, save, then reopen the saved page. Other website editors may provide a different HTML insertion area; use their documented method.
Permissions matter. The WordPress Custom HTML documentation explains that users without the required capability can have disallowed markup, including script and iframe tags, removed when saving. If code disappears, ask the site administrator to check the supported installation route. Do not disable site protections simply to make a snippet persist.
Copy the complete supplied snippet without adding settings from an unrelated tutorial. If it needs adjustment, make one documented change at a time and retain the original for comparison.
Where Vidzy fits into the embedding workflow
Vidzy’s embeddable video player works through HTML embedding and is compatible with WordPress. Users keep their video hosted on their existing provider.
Those capabilities do not mean a generic URL block will automatically recognize a Vidzy link. For a Vidzy installation, establish the actual embed instructions for your setup rather than adapting another provider’s snippet. This guide does not assume a particular Vidzy code format, plugin or sequence of dashboard buttons.
The same acceptance checks still apply: the intended player must appear on the saved page, the correct video must play, and the page must work for its intended audience.
Check the saved page, not only the editor
Run these checks before handing the page over for release. Treat them as acceptance criteria, not as claims that every player supplies the same controls.
- Correct source: Start playback and confirm the video is the intended version, not merely a familiar thumbnail.
- Audience access: Test under conditions representative of the intended viewer. For a public page, use a signed-out test environment when available; an administrator’s session is not a substitute.
- Basic interaction: Try starting and pausing playback, then test the controls offered by the chosen player.
- Narrow-screen layout: Check that the player stays inside its content column, with no clipping or horizontal scrolling. Inspect both the player and its surrounding section.
- Usability: Check that visible controls remain readable and operable. Review keyboard interaction and any available caption controls as part of the wider page review.
- Persistence: Reload the saved page and confirm the embed remains present.
A draft preview may require an editor login. If that prevents a representative access test, record the test as pending rather than claiming it passed. Use an approved staging arrangement or ask the person responsible for release to complete it.
Troubleshoot the symptom you actually see
The page shows a link or code instead of a player
Recheck the input and editor field first. A URL-based block and an HTML area serve different purposes. Compare what you pasted with the provider’s instructions before replacing the video or changing the whole page.
The embed disappears after saving
Compare the saved content with the original snippet. For WordPress, revisit the permission-dependent filtering described above. Bring the source instructions and the changed snippet to the administrator; that is more useful than repeatedly pasting the same code.
The player appears, but the video will not play
Record the exact error and check the provider’s source and embedding settings. YouTube, for example, allows owners to disable embedding, and its guidance describes restrictions for age-restricted videos. A source that opens for you is not sufficient evidence that it can play in the intended embedded context.
The player extends beyond the page
Inspect the content container and the provider’s sizing instructions. Ask the site maintainer to check how the embed fits the available width while preserving its proportions. Hiding the overflow can conceal controls; verify the complete player remains usable after any layout correction.
Leave a useful installation record
Record the destination page, source video, embedding method, person responsible for the source and checks still outstanding. If a later editor changes the source or surrounding layout, repeat the affected checks.
Start with one saved page. Confirm the input route, verify playback and fit, and document anything you could not test. That gives the person reviewing the page a concrete result to approve.