WordPress integration
A WordPress social media widget, without another plugin.
The usual answer to anything on WordPress is to install a plugin, and the usual result is another thing to keep updated, another thing that breaks on a major release, and another set of database tables. A social media widget you paste in as HTML needs none of that.
Where it goes, by editor
WordPress is really several editors wearing the same badge, and where you paste the snippet depends on which one your site is using.
Block editor — Custom HTML block
Search for 'Custom HTML' in the block inserter, paste, done. The preview toggle inside the block renders it so you can check before publishing.
Classic editor — the Text tab
Switch from Visual to Text before pasting. The Visual tab will escape the script tag and you will get the code printed on your page as words.
Elementor, Divi, Beaver Builder — an HTML widget
Every major builder has one. Drop it where the wall belongs and paste in.
Sitewide — theme footer or a widget area
For a floating launcher or a footer strip, a Custom HTML widget in Appearance → Widgets puts it on every page at once.
Adding it to WordPress
- 1
Copy the snippet
From the feed's Embed dialog — a script tag and a div.
- 2
Add a Custom HTML block
In the block editor, click the + and search 'Custom HTML'. Paste the whole snippet, both lines, into the block.
- 3
Preview before publishing
The block has its own Preview toggle. If it renders there it will render live — and if it does not, that is a caching or security plugin, not a bad snippet.
- 4
Publish and clear your cache
Any caching plugin will serve the old page until you purge it. Do that before deciding it has not worked.
What trips people up on WordPress
Nearly every WordPress embed failure comes from something else on the site rather than the embed, and it is nearly always one of these four.
- Pasting into the Visual tab of the classic editor, which escapes the script and prints it as text. Use the Text tab
- Caching plugins serving a stale page. Purge after publishing, every time, before you conclude anything
- Optimisation plugins that defer, combine or minify third-party JavaScript. Exclude the embed script from those rules and it comes back
- Security plugins and locked-down hosts that strip script tags from post content for non-administrator authors. If it works for you and not for an editor colleague, that is why
WordPress questions
No, deliberately. A Custom HTML block does the same job with nothing to update, nothing to conflict with your other plugins, and no extra database tables. Plugins earn their keep when they need server-side hooks; an embed does not.
Other platforms
One snippet, then never again.
Build the feed, paste it into WordPress once, and it keeps itself current from then on.
Start free