VCEDC YouTube Video Hosting Strategy
Overview
During the October 2025 staging review, the team resolved longstanding confusion about how VCEDC videos are hosted and surfaced a clear path forward: discontinue the SiteCast licensed landing page and embed all videos directly from the official VCEDC YouTube channel. This decision simplifies the video workflow, improves site performance, and eliminates a paid service that was never meaningfully integrated with the website.
See the source meeting: [1].
The Problem: SiteCast Confusion
VCEDC had been paying for a SiteCast service — a licensed landing page built by a previous vendor (Brad) that pulled VCEDC's YouTube playlists into a branded, website-like interface. Key facts that caused confusion:
- SiteCast is not connected to the VCEDC website in any way — it is a completely separate, standalone landing page.
- The videos on SiteCast already live on YouTube; SiteCast simply re-presented them in a branded wrapper.
- SiteCast used a specialized YouTube integration that is specific to that vendor's license and cannot be transferred or replicated elsewhere.
- The SiteCast page uses outdated VCEDC branding (old logo, old tagline) and is inconsistent with the current brand.
- The page was never linked from the VCEDC website and was not part of the user journey.
Bottom line: SiteCast was a paid service providing no meaningful value to the new website build.
The Decision
| Item | Decision |
|---|---|
| SiteCast | Discontinue at end of contract (end of year) |
| Video hosting | Embed all videos from the official VCEDC YouTube channel |
| YouTube access | AAG (Melissa) to have full channel access |
| Old/outdated videos | Set to "unlisted" — removes from public feed without breaking existing links |
Rationale
Performance
Embedding from YouTube rather than hosting video files directly on the WordPress site is critical for VCEDC's audience. Vilas County has areas with slow internet connectivity. Self-hosted video files would cause long load times or failed playback for many users. YouTube handles adaptive streaming and CDN delivery automatically.
Simplicity
All videos already exist on YouTube. There is no migration required — the content is already there. The new website simply needs to embed the correct YouTube links.
No Content Loss
Discontinuing SiteCast does not affect the videos themselves. The YouTube channel remains intact. Any videos that should no longer appear publicly can be set to "unlisted," which preserves the video and any existing links while removing it from the public channel feed.
Implementation Notes
- YouTube channel name: Vilas County EDC (search discoverability was noted as an issue — the channel did not surface when searching "Vilas County Economic Development")
- Embed method: Standard YouTube embed within WordPress pages; the YouTube player can be configured to suppress "watch next" recommendations
- Past Programs page: A new dedicated page will house recorded past events, embedded from YouTube. The Events page will link to it. See [2].
- Access: Tracey Pilsner (VCEDC) to confirm AAG has full YouTube channel access; if blocked, Tracey will walk Kathy through granting it.
Action Items
- [ ] Confirm AAG (Melissa) has full VCEDC YouTube channel access — Tracey Pilsner
- [ ] Set outdated/irrelevant videos to "unlisted" on the VCEDC YouTube channel — Melissa Cusumano
- [ ] Update YouTube channel banner to reflect current branding — Melissa Cusumano
- [ ] Create Past Programs page and embed VCEDC YouTube recordings — Melissa Cusumano
- [ ] Add link from Events page to Past Programs page — Melissa Cusumano
Generalizable Insight
For small-org websites in low-bandwidth regions, always offload video to a platform like YouTube or Vimeo. Self-hosted video is a common mistake that degrades performance for the exact audiences these organizations serve. YouTube embeds also provide free CDN delivery, adaptive bitrate streaming, and a familiar playback interface — with the added benefit that the content library is maintained independently of the website CMS.
Related
- [3]
- [4]
- [5]