Aggregator channel (handle)
Input URL
https://www.youtube.com/@WPRSSAggregatorExpected feed
https://www.youtube.com/feeds/videos.xml?channel_id=UCRrmBF3pEXUQCNmq8uALD6gTest in finderRSS by platform
The feed is hidden and tied to the channel ID rather than the handle.
Quick answer
https://www.youtube.com/feeds/videos.xml?channel_id=[channel-id]Context
YouTube has exposed Atom feeds for channels since the Google Data API era and still publishes them today. The feed URL has never been advertised in the UI, and the switch to @handles in 2022 made it harder to find because handles don't appear in the feed URL. The underlying channel ID, a 24-character identifier starting with UC, is what the feed actually needs.
https://www.youtube.com/feeds/videos.xml?channel_id=[channel-id]https://www.youtube.com/feeds/videos.xml?channel_id=UCRrmBF3pEXUQCNmq8uALD6gRSS finder
Test a YouTube URL here to get the same feed analysis, import verdict, and live Aggregator-style preview as the main Feed Finder.
Gotchas
Examples
Input URL
https://www.youtube.com/@WPRSSAggregatorExpected feed
https://www.youtube.com/feeds/videos.xml?channel_id=UCRrmBF3pEXUQCNmq8uALD6gTest in finderInput URL
https://www.youtube.com/channel/UCRrmBF3pEXUQCNmq8uALD6gExpected feed
https://www.youtube.com/feeds/videos.xml?channel_id=UCRrmBF3pEXUQCNmq8uALD6gTest in finderInput URL
https://www.youtube.com/playlist?list=PLhwNNB2ZOH8WsSiyMbNpAXUw49ViF6V3pExpected feed
https://www.youtube.com/feeds/videos.xml?playlist_id=PLhwNNB2ZOH8WsSiyMbNpAXUw49ViF6V3pTest in finderFAQ
Yes. YouTube exposes Atom feeds for channels at /feeds/videos.xml?channel_id=[id]. The feed URL uses the channel ID, not the handle or custom URL. The endpoint went through a stretch of intermittent 404s starting December 2025; as of May 2026 it is back to normal, though server-side requests from cloud IPs can still flake.
Two common reasons. First, datacenter IPs (Vercel, AWS) get 500/404 responses even when the channel is fine, the same URL works from a browser or a normal WordPress host. Second, the endpoint went through a stretch of recurring 404 windows starting December 2025; the community-maintained uptime monitor at stats.uptimerobot.com/v6szxXApfC/802909356 tracks recent dips. The URL format itself has not changed. If you do hit a flake, point your RSS reader or Aggregator at https://piped.video/feed/[channel_id] until YouTube's endpoint returns.
Two reliable ways. First, paste the channel URL into Feed Finder, it resolves handles, /c/, and /user/ paths to the underlying UC... channel ID automatically. Second, open the channel page in a browser, view source (Ctrl+U or Cmd+Option+U), and search for `"channelId"`, the value next to it is the 24-character UC... ID. Channel IDs always start with UC and are stable, the channel handle (the @-prefixed name) can change without affecting the feed URL.
Use https://www.youtube.com/feeds/videos.xml?playlist_id=[ID] where [ID] is the playlist's PL... or UU... identifier (the value of the list= query parameter in the playlist URL). Like channel feeds, playlist feeds expose the most recent ~15 videos as Atom and update automatically when new videos are added.
YouTube caps channel feeds at roughly the 15 most recent uploads. This is a platform limitation. There is no standard RSS way to request older videos; the YouTube Data API v3 or a third-party bridge is the only path to older content.
Live streams and premieres typically appear in the feed only after they end and become regular videos. Scheduled streams are not in the feed until they go live.
Yes. Use the detected channel RSS URL as the source feed. Aggregator's display options can render the video inline in WordPress rather than just linking out.