WordPress Part 3: Integrating Wordpress and Soundcloud

Audio can give a WordPress post something text alone cannot: the sound of an interview, the atmosphere of a live performance, or a guided explanation readers can follow while they work. SoundCloud provides a hosted player for that audio, so visitors can listen inside your post without first opening another website.

In this third part of our WordPress series, we’ll walk through the complete workflow: preparing an audio file, uploading it to SoundCloud, choosing sharing settings, and embedding the player in WordPress. We’ll cover both the block editor and the Classic Editor, plus the checks that help prevent an empty player or a broken listening experience.

This guide reflects WordPress and SoundCloud workflows as of 2020; tools, interfaces, and account limits may have changed since then.

How SoundCloud and WordPress Work Together

SoundCloud hosts and streams your audio. WordPress holds the article and displays a player that loads the track from SoundCloud. You are not copying the audio into your WordPress Media Library when you embed a SoundCloud track.

That separation has a few practical benefits:

Your WordPress hosting account does not have to store and serve the audio file.
Readers can play the recording alongside your notes, images, and links.
You can use the same SoundCloud track on multiple pages without uploading it again.

There is also a dependency: the embedded player needs the SoundCloud track to remain available. Deleting the track, changing its access settings, or removing the SoundCloud account can affect published posts that use it.

For a typical public track, WordPress can turn a SoundCloud URL into an embedded player automatically through its supported embed system, often called oEmbed. Copying iframe code is an alternative, not always a requirement.

Before You Start

You’ll need a SoundCloud account with available upload capacity, permission to edit a WordPress post, and an audio recording you have the right to publish. SoundCloud plan limits and WordPress hosting restrictions can affect the process, so check those before committing to a large audio library.

Prepare the recording

Listen to the exported file from beginning to end. Check for long stretches of silence, clipping, abrupt endings, and inconsistent volume. An embed cannot repair problems already present in the recording.

SoundCloud accepts common audio formats, including WAV and MP3. Use a high-quality source file when practical; converting a low-quality MP3 to WAV does not recover lost detail. Keep a local backup of the original recording and the final upload.

Choose a useful track title, too. “Interview: Planning a First Website” tells listeners much more than “final_audio_v4.” Add a description that explains the recording and credits contributors where appropriate.

Confirm your publishing rights

Only upload material you own or have permission to distribute. Music playing behind an interview can introduce rights issues even when you recorded the conversation yourself. Embedding a track does not remove those obligations.

If the audio contains sensitive information or participant interviews, confirm that publication is appropriate before uploading it to a third-party service.

Step 1: Upload Your Audio to SoundCloud

Sign in to SoundCloud and open the upload page using the Upload control.
Select your audio file, or drag it into the upload area if offered.
Enter the track title and description while the file uploads.
Add relevant artwork, a genre, and tags where useful.
Choose the track’s privacy setting and save the upload.
Wait for processing to finish, then play the track on its SoundCloud page.

Do not move straight from a successful upload message to publishing your WordPress post. Confirm that the track actually plays and that you uploaded the intended version.

Choose public or private deliberately

For a normal public blog post, a public SoundCloud track is usually the simplest choice. Readers should be able to access it without being signed in to your account.

A private track uses special sharing access, typically through a secret link. If you embed a private track using SoundCloud’s supported sharing controls, the player may depend on access information included in that link or embed code. Do not strip those parameters out while editing.

Private sharing is not the same as a members-only publishing system. Anyone who receives a usable secret link may be able to share it further. If you need restricted course or client content, evaluate access controls separately rather than relying on an obscure URL.

Step 2: Get the Track Link or Embed Code

Open the uploaded track’s page and choose Share. From here, decide which WordPress embedding method you want to use.

Option A: Copy the track URL

For the easiest integration, copy the public track’s page URL. It generally has this structure:

https://soundcloud.com/your-profile/your-track

Use the URL for the individual track, not a search result or your account dashboard. A profile URL will not necessarily produce the single-track player you intended.

This method works well with WordPress’s SoundCloud block and with automatic embeds in the Classic Editor.

Option B: Copy SoundCloud’s iframe code

In the sharing dialog, open the Embed tab if available. SoundCloud provides player options and generates HTML for the selected configuration.

Depending on the player and account, you may see choices for appearance, artwork, or other display settings. Preview the result before copying the code. Avoid automatic playback: it can interrupt readers, and browsers may block it anyway.

A simplified iframe has this general structure:

<iframe
  title="SoundCloud audio: Planning a First Website"
  width="100%"
  height="166"
  scrolling="no"
  frameborder="no"
  allow="autoplay"
  src="https://w.soundcloud.com/player/?url=https%3A//api.soundcloud.com/tracks/TRACK_ID&amp;auto_play=false">
</iframe>

This is an illustration, not a working embed: TRACK_ID is a placeholder. Copy the actual code supplied by SoundCloud instead of trying to reconstruct the player URL. Retain any access parameters required for private tracks.

The allow="autoplay" attribute grants a browser permission; it does not itself request automatic playback. The example explicitly sets auto_play=false.

Step 3: Embed the Track in the WordPress Block Editor

The block editor, introduced with WordPress 5.0, provides a straightforward way to embed supported services.

Use the SoundCloud block

Open the post you want to edit, or create a new post.
Place the cursor where the player should appear.
Select Add block and search for SoundCloud.
Insert the SoundCloud embed block.
Paste the track URL into the block’s URL field.
Select Embed and wait for the player preview.
Save the post as a draft and preview it on the front end.

You can also try pasting the track URL onto a new, empty line in the block editor. WordPress may recognize the supported URL and create the embed automatically. Using the dedicated block makes your intention explicit if automatic conversion does not happen.

Add a short introductory paragraph above the player. Explain what the recording contains and why a visitor should listen. Below it, include supporting notes or a transcript rather than leaving the player without context.

Use a Custom HTML block for iframe code

If you want SoundCloud’s generated player configuration, insert a Custom HTML block and paste the iframe code there. Use the block’s preview control, then check the full post preview.

Do not paste iframe markup into a Paragraph or Code block. Those blocks may display the markup as text rather than render the player.

Some WordPress environments remove iframes for security reasons. This can depend on your user permissions, a multisite configuration, hosting policies, or security tools. If the iframe disappears after saving, try the supported SoundCloud URL embed first. Do not weaken site-wide security merely to preserve one embed.

Step 4: Embed the Track in the Classic Editor

If your site uses the Classic Editor, you still have two options.

Embed a plain URL

Open the post in the Visual editor.
Put the SoundCloud track URL on a line by itself, with no surrounding text.
Press Enter and allow WordPress to resolve the embed.
Save and preview the post.

The URL should be plain text rather than a manually created hyperlink. If WordPress leaves it as a link, remove the hyperlink formatting and try again on a separate line.

Paste iframe code

Switch from the Visual tab to the Text tab.
Find the position where the player belongs.
Paste the embed code copied from SoundCloud.
Save the draft and preview the post.

In this editor, Text is the HTML-editing view. Pasting raw HTML into the Visual view may escape it or produce unwanted formatting. If switching between tabs alters the markup, make the final embed edit in Text view and verify the saved result.

Step 5: Test Before Publishing

A player appearing in the editor is only the first check. The published page uses your theme’s layout and may behave differently.

Play the recording. Confirm the correct track loads and that playback works beyond the opening seconds.
Test while signed out. Open the preview or published page in an appropriate signed-out session to check access from a visitor’s perspective. Draft previews may require authentication, so repeat this after publication.
Check a narrow screen. Look for horizontal overflow, cropped controls, and artwork that overwhelms the article.
Check player height. A compact audio player and a large visual player need different amounts of vertical space.
Test the surrounding content. Verify transcript links, downloads you intentionally provide, and the fallback SoundCloud link.

A width of 100% helps an iframe fit its container, but it does not guarantee that every theme and player configuration works perfectly on every device. Test rather than assuming responsiveness.

Common Problems and Practical Fixes

The URL stays as text or a hyperlink

Confirm that it is an individual SoundCloud track URL. In the block editor, use the SoundCloud block directly. In the Classic Editor, place the plain URL on its own line. If supported embeds fail across the site, ask your administrator to investigate plugins, outbound requests, or hosting restrictions.

The player appears, but the track is unavailable

Open the track link while signed out of SoundCloud. Check whether the upload is still processing, the track was deleted, or its privacy settings changed. For a private track, obtain fresh sharing code if its secret link was reset.

The embed vanishes after saving

WordPress may be filtering the iframe. Use the URL-based embed where possible, or ask the site administrator which embed methods your environment permits. Installing an arbitrary plugin is not the best first fix.

The player looks cramped or loads slowly

Try SoundCloud’s smaller player configuration and keep embeds inside the article’s normal content column. Avoid loading many players on a single archive page. Browser privacy extensions or network filtering can also block third-party players, so include a direct track link as a fallback.

Make the Audio Useful Beyond the Player

Provide a transcript for spoken content whenever possible. It helps readers who cannot hear the recording, cannot play audio in their current setting, or prefer to scan for a specific point. Brief episode notes are useful, but they are not a complete substitute for a transcript.

Remember that the player loads resources from a third-party service. Review how that fits your site’s privacy notice and any applicable consent requirements. A basic integration does not require a WordPress plugin; add one only when you have a specific need it solves.

Takeaway

Upload and verify your recording in SoundCloud, then use a WordPress SoundCloud block or standalone track URL for the simplest embed. Choose generated iframe code when you need its player options. Before publishing, test access, playback, and mobile layout, and give readers context, a transcript, and a fallback link so the post remains useful beyond the player.