# Recent changes to Onebox embedding for my site
**URL:** https://meta.discourse.org/t/recent-changes-to-onebox-embedding-for-my-site/393606
**Category:** Support
**Tags:** onebox
**Created:** [January 15, 2026, 11:10pm UTC](https://meta.discourse.org/t/recent-changes-to-onebox-embedding-for-my-site/393606 "2026-01-15T23:10:06Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@riknoll](https://meta.discourse.org/u/riknoll)
#### Post date: [January 15, 2026, 11:10pm UTC](https://meta.discourse.org/t/recent-changes-to-onebox-embedding-for-my-site/393606/1 "2026-01-15T23:10:06Z")
Hello there!
On our forum, we’ve seen some recent changes to how links to sites on our domain ([makecode.com](http://makecode.com)) are embedded by onebox. Previously, you got a little minimal preview like this:
However, we’re now seeing a more advanced embed where the actual site is hosted in an iframe when the same link is pasted into new posts:
Was there an update made in last few days to onebox and, if so, is there a way to revert to the old behavior? As far as we are aware, we haven’t made any recent changes on our side.
For reference:
- Here is a link to the post from the first image: [Falling blocks multitasking - Show & Tell - Microsoft MakeCode](https://forum.makecode.com/t/falling-blocks-multitasking/41508)
- Here is a link to the post from the second image: [Changes to link embeds - Forum Feedback - Microsoft MakeCode](https://forum.makecode.com/t/changes-to-link-embeds/41539)
- And here is the link that both posts are embedding: [falling blocks insanity](https://arcade.makecode.com/59736-39100-73400-75898)
---
### Author:  [@ToddZ](https://meta.discourse.org/u/ToddZ)
#### Post date: [January 15, 2026, 11:44pm UTC](https://meta.discourse.org/t/recent-changes-to-onebox-embedding-for-my-site/393606/2 "2026-01-15T23:44:40Z")
Your first post has pretty normal looking onebox code:
But your second post is doing something different with a `pxtoembed` class and an iframe:
Are you sure there have been no changes? I don’t know much about setting up iframing but there’s an admin setting for “Allowed onebox iframes” you might take a look at.
---
### Author:  [@riknoll](https://meta.discourse.org/u/riknoll)
#### Post date: [January 16, 2026, 12:07am UTC](https://meta.discourse.org/t/recent-changes-to-onebox-embedding-for-my-site/393606/3 "2026-01-16T00:07:56Z")
Thanks for taking a look! I’m fairly certain there have been no changes; I did take a look at that setting and it simply had the default value (“\*”). I just tried removing that wildcard and replacing it with a single domain (YouTube) but it doesn’t seem to have had any effect on the embed.
That pxtoembed class and iframe that you screenshotted come from the oembed endpoint that we link in the embedded page:
However that’s been there for years, I’m not sure why it suddenly started getting embedded today.
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [January 16, 2026, 9:42am UTC](https://meta.discourse.org/t/recent-changes-to-onebox-embedding-for-my-site/393606/4 "2026-01-16T09:42:08Z")
> [@riknoll](#):
>
> I just tried removing that wildcard and replacing it with a single domain (YouTube) but it doesn’t seem to have had any effect on the embed.
Did you try rebuilding the post’s HTML after that (Post 3 dots \> Admin wrench \> Rebuild HTML)?
---
### Author:  [@riknoll](https://meta.discourse.org/u/riknoll)
#### Post date: [January 16, 2026, 5:47pm UTC](https://meta.discourse.org/t/recent-changes-to-onebox-embedding-for-my-site/393606/5 "2026-01-16T17:47:49Z")
Just gave that a shot, but no dice! The embed is still there and still shows up when I create a new post with the same link.
---
### Author:  [@riknoll](https://meta.discourse.org/u/riknoll)
#### Post date: [January 16, 2026, 6:05pm UTC](https://meta.discourse.org/t/recent-changes-to-onebox-embedding-for-my-site/393606/6 "2026-01-16T18:05:11Z")
Alright, turns out there are two iframe settings in the Security section, and my domain was still added in the other one. I’ve now removed that one and it has at least prevented the issue for now! Still not sure why this suddenly started happening…