Pasting the Embed Into a CMS: HTML Blocks and Stripped Attributes

The partner documentation tells you to paste the embed code into the HTML editor of your page, blog post or CMS block. That sounds simple, and often is. But content systems are built to protect themselves from unknown HTML, and an iframe is exactly the kind of thing they filter. This post explains the usual problems, how to recognise them and what to look for in your own system.

The quick start has three steps: open the game in the catalog, switch to the HTML tab and press Copy, then paste the code into the HTML editor of your page and publish. The troubleshooting table adds a related warning: if the game area is blank, check that the code was pasted in an HTML block, not as plain text.

Symptom	Likely cause
You see the code on the page as text	It went into a text or visual block, which shows tags literally
The page shows nothing where the game should be	The system removed the iframe when saving
The game appears but is tiny or cut off	The wrapper's style attributes were stripped
Fullscreen, sound or controls do not work	The allow attribute was removed
It works for you but not for other users	Your account can use raw HTML, theirs cannot (rare for public pages, common in editing previews)
It works in the editor preview but not on the live page	A caching or security layer on the live site changes the output

The names differ between systems, but the ideas repeat. I cannot describe every platform here, and options change between versions, so use this as a list of things to search for in your system's settings:

• A "custom HTML" or "raw HTML" block or an HTML source view. This is where the code belongs.
• An embed or iframe block that asks for an address. It may accept only the src, in which case other attributes are lost. Check the result against the original snippet.
• User roles. Some systems let only administrators insert unfiltered HTML. An editor may see the code vanish.
• Security plugins and filters that remove iframes or attributes.
• Visual editors that rewrite the HTML when you switch modes. Paste the code in the HTML view last, save, and do not return to the visual mode for that block.

After you save, open the live page, find the frame and compare it with the original snippet. Look at: the src address, the allow value, the loading attribute, the wrapper's inline styles and the title. The terms say that you may not modify the embed in a way that removes the permissions the game needs, so a system that strips them silently puts you in a position you did not choose. The fix is to change the block type or the setting, not to accept the loss. See the allow attribute and what every part of the iframe code does.

If you embed games often, make a template: one block that holds the wrapper and iframe, with only the slug and title changing. This reduces the risk of typing mistakes and keeps all your embeds the same. Keep a copy of the original snippet next to it so you can compare after an upgrade.

CMS updates, theme changes and new plugins can alter how HTML is saved or displayed. After an update, open a page with a game and test it again. A monthly check of one page per template is enough. Our post on five embed problems and their fixes covers the cases that are not about your CMS, such as a Content-Security-Policy block.

Ask your CMS vendor or your developer how to insert a trusted iframe with its attributes intact. Do not try to bypass the security of your site with workarounds you do not understand. If you suspect the problem is on PlayKovo's side, write to [email protected] with the details from what to include in a message.