How to embed TrainingOS SCORM in WordPress

Who this is for

This guide fits two common setups: a portfolio or marketing site where you want reviewers to launch your hosted module from a WordPress page, and lightweight course delivery where WordPress is the front door but you do not want to run a full LMS inside WordPress.

WordPress excels at content, SEO, and design flexibility; it is not always the simplest place to host packaged SCORM. TrainingOS hosts your published package, gives you a stable HTTPS launch URL, and handles the player—WordPress stays your CMS.

Prerequisites

Publish your module from your authoring tool, upload the package to TrainingOS, and confirm the launch URL works when opened directly in a browser (not only from inside WordPress). Fix playback issues there first.

Your WordPress site should use HTTPS. Mixed HTTP pages embedding HTTPS players can trigger browser warnings; align both sides on secure URLs before you wire buttons or iframes.

Why TrainingOS plus WordPress works

TrainingOS (via Allure Connect when configured) hosts the ZIP and serves the player; you copy one URL into WordPress. You do not need a SCORM plugin for showcase or link-out delivery—you need a reliable link or embed.

If your goal is compliance-grade tracking inside WordPress, you may eventually want an LMS or a dedicated plugin. For portfolio demos and many training launches, a button or iframe to your hosted URL is enough.

Option A: Button or text link

In the Block Editor, add a Button block or a paragraph with a styled link. Paste your TrainingOS public course or portfolio URL. Use CTA copy such as “Launch the module” or “Open the demo”—avoid pasting a naked URL as the visible label.

Set the link to open in a new tab. Full-screen or dedicated-tab playback matches how most Storyline, Rise, and Captivate packages expect audio, completion, and bookmarking to behave.

Option B: iframe embed

Add a Custom HTML block and paste an iframe whose src is your TrainingOS launch URL. Use width="100%", a height of at least 600px (often 700–800px for tall players), and allow="fullscreen" when your authoring tool needs it.

Preview on mobile: themes with narrow content columns can make iframes feel cramped; increase height or switch to the link-out pattern for small screens.

Link vs iframe: when to choose which

Prefer a new-tab link when security plugins, corporate browsers, or theme constraints make iframes flaky, or when you want an LMS-like “launch in full window” feel with fewer surprises.

Prefer an iframe when you need the module to feel part of a single page—course landing pages, long-form articles with an inline demo, or when you control the theme and have verified iframe support.

WordPress-specific troubleshooting

Security and firewall plugins (Wordfence, iThemes, etc.) sometimes block iframes or external scripts. Whitelist your TrainingOS hostname in iframe or content-security settings, or fall back to opening the module in a new tab.

Page builders and “sanitize HTML” options may strip iframe tags from blocks. If the iframe disappears after save, use a block or widget that explicitly allows raw HTML, or use the link pattern.

Caching plugins (WP Rocket, LiteSpeed, etc.) can cache a page that embeds an iframe aggressively. Exclude the page from full-page cache during testing, or use a “don’t cache this page” rule if the player updates often.

Checklist before you publish

Test while logged out in an incognito window so you see what learners see. Confirm audio, completion, and resume if your package relies on them.

If you use an iframe, verify it after a theme or plugin update—updates sometimes tighten allowed HTML.

Common questions

Do I need a SCORM plugin? Not for hosted TrainingOS playback via link or iframe. Plugins matter when you want SCORM data stored inside WordPress itself.

Why does my iframe show a blank box? Often CSP, a security plugin, or a stripped Custom HTML block. Check the browser console for blocked-frame errors and try the new-tab link to confirm the URL works.