SoundCloud feed widget for any website.

SoundCloud was founded in Berlin in 2007 by Alexander Ljung and Eric Wahlforss, and nearly two decades later it remains the cultural home of independent music in a way no DSP has replicated. Spotify, Apple Music, and Tidal all sit behind a distributor wall. You upload to DistroKid or TuneCore, you wait 48 to 72 hours for review, your track lives in a curated catalog optimized for algorithmic playlisting, and your fans listen inside an app whose recommendation engine wants to send them to the next stream after yours. SoundCloud works the opposite way. Anyone can upload anything in under a minute. Tracks live on a permalink that is yours forever. The waveform is a visual signature in the same way an album cover is. The Repost button is how scenes form: a respected curator reshares an unknown producer and that producer wakes up with a thousand new plays. None of that exists on Spotify in the same form. For producers, beatmakers, hyperpop artists, footwork DJs, lo-fi beat curators, ambient composers, and basically every genre that started underground and is still finding its mainstream foothold, SoundCloud is the source of truth. Your website might be where you sell beats or take bookings, but SoundCloud is where the work lives. Embedding the SoundCloud feed on your own site is how you connect the two without losing the visitor to soundcloud.com's recommendation graph.

SoundCloud exposes four distinct primitives through its public API and each maps to a different job. A single track embed is what you get from the native iframe code on any SoundCloud track page. It is fine for one-off embeds (a hero release on a launch landing page, a beat preview on a product page, a single mix on your booking page), but it does not grow on its own and you maintain it by hand every time you upload. A playlist embed (SoundCloud calls these Sets in some contexts) pulls every track in a SoundCloud playlist, respects the playlist sort order, and auto-includes new tracks as you add them. This is the right primitive for beat tapes, label compilations, podcast seasons, course modules, and any curated set where you want editorial control. A user feed pulls every public upload from a SoundCloud profile, in chronological order. This is the right primitive for an indie artist's homepage, a producer's beat showcase, or any place where the latest upload should always be the first thing visitors see. The fourth and most underused primitive is the reposts feed: every track the user has reshared via the SoundCloud Repost button. Reposts are how scenes signal taste. A label that reposts five emerging producers is doing curation that is more valuable than any algorithmic playlist, and embedding that reposts feed on the label site turns the label page into a discovery surface. Poper supports all four primitives from the same widget config, so you can switch source types without re-embedding the snippet on your site. Picking correctly at the start saves you a re-embed cycle later.

SoundCloud retired its v1 API and the legacy client_id-only authentication model and now requires OAuth 2.1 with PKCE for all read access on the v2 API. This was a real shift. For years, dozens of widget tools relied on the unauthenticated client_id flow, which let any site read public SoundCloud data without the user signing in. Most of those widgets broke when SoundCloud tightened the policy, which is why a search for SoundCloud widgets in 2026 turns up many tools that quietly stopped working. The current correct flow is Sign in with SoundCloud (OAuth 2.1 with PKCE), which authenticates the connection in 30 seconds and returns a refresh token that the widget rotates automatically. Read scope is the minimum necessary for embedding tracks, playlists, and user feeds, so the OAuth consent screen is short and trustworthy. Rate limits on v2 are generous for embedding workloads. The current published limits are 15,000 requests per app per 24 hours plus per-IP throttles that mostly affect scraping use cases. A typical Poper SoundCloud widget syncing a single profile every 6 hours costs about 4 requests per day, which is well under any limit you will encounter. For multi-artist aggregations or higher-frequency Pro syncs we batch and cache aggressively at the global CDN edge so visitors to your site never hit the SoundCloud API directly. The v2 API also exposes the rich metadata SoundCloud is known for: comments with timestamp positions on the waveform, play counts per track, reposts counts, like counts, the user's followers and following totals, and the genre and tags taxonomy that powers SoundCloud's discovery surfaces. Poper renders this metadata in the widget by default so the embed feels like SoundCloud, not like a stripped-down shell.

Embedding audio and ranking audio are two completely different things. A SoundCloud iframe by itself is invisible to Google's audio index because Google cannot crawl what is inside an iframe. To be eligible for audio rich results, voice search inclusion via Google Assistant, and music carousel placement when someone searches for an artist or track name, your page needs Schema.org MusicRecording structured data for each track. The required fields are name, byArtist (which itself is a MusicGroup or Person), inAlbum (when the track belongs to a release), duration in ISO 8601 format, and url. Strongly recommended fields include datePublished, genre, isrcCode for label-released tracks, and an associated MusicAlbum or MusicPlaylist schema linking the tracks together. Most SoundCloud widgets emit none of this. Poper auto-injects a complete MusicRecording JSON-LD block for every track in the feed, populated from the SoundCloud API v2 response, so the audio you embed is immediately eligible for Google's music carousel and audio rich results. Validate with Google's Rich Results Test on any page where the widget is embedded. Beyond Google, MusicRecording JSON-LD is also consumed by Spotify Open Graph crawlers (yes, a track on your site can be picked up as a related work to the Spotify version), Bing Audio Search, and increasingly by AI search engines like Perplexity that build audio answer cards directly from MusicRecording markup. The schema investment also unlocks the most underused SEO opportunity in independent music: long-tail track-name queries. Searches like 'song name + artist name', 'mix name + DJ name', and 'beat name + producer name' are dominated by SoundCloud and YouTube because those are where the audio lives. Embedding the SoundCloud track on your own site with proper MusicRecording schema means your site becomes a third option in those SERPs, and your domain (rather than soundcloud.com) gets the click and the brand association.

The official SoundCloud iframe is one of the heavier audio embeds you can put on a page. A single embedded track pulls roughly 400KB of JavaScript, sets several third-party cookies, blocks the main thread during load, and frequently regresses Largest Contentful Paint by 800ms to 1.5 seconds depending on the visitor's connection. Embed five tracks as standard iframes and you can lose 15 to 20 Lighthouse points before any other code on the page runs. The fix is the lite-player pattern, the same approach that works for YouTube and Vimeo. Poper renders only the waveform thumbnail (pulled from SoundCloud's own CDN) and a play button overlay (under 8KB per track) on initial page view. The full SoundCloud iframe loads only when the visitor clicks play. Visitors who scroll past the widget pay nothing in performance cost. Visitors who click play see the full official SoundCloud player with comments, scrubbing, and the recognizable waveform interaction. Mobile playback in particular benefits from this pattern. SoundCloud's iframe is large enough that on a slow 3G connection it can take 4 to 6 seconds to become interactive, which means a mobile visitor who taps the play button sees a long delay before audio starts. With the lite-player pattern Poper preloads the iframe in the background as soon as the user shows intent (hover on desktop, viewport entry on mobile), so the iframe is ready by the time the visitor decides to play. There are three additional optimizations Poper applies on top of lite mode. First, waveform images are converted to WebP on the fly through our edge layer, which typically halves their weight versus the default PNG. Second, the play-button overlay uses a single inline SVG instead of an image request, which saves a round trip per track. Third, when the visitor clicks play, the iframe loads with autoplay enabled so the audio starts the instant the player is ready, not after the visitor has to click play a second time. The combined result is that a page with twelve embedded SoundCloud tracks in lite mode often outperforms a page with two embedded tracks in standard iframe mode on every Core Web Vitals metric. SoundCloud Pro+ creators get a small bonus from this approach: the higher-bitrate streams that come with the Pro+ tier are noticeable in the player only if the player loads fast enough to start streaming before the visitor moves on, and lite mode buys you that head start. If page speed matters to your SEO, this is the single biggest reason to choose carefully which SoundCloud widget you embed.