embeds

An embed is a piece of one website shown inside another, usually through an iframe, a small window that loads content from somewhere else and displays it in place. A YouTube video on a blog post, a map on a contact page, a podcast player pulled in from Spotify, all of these are embeds. The content and the code behind it stay on the other service’s server; your page just opens a window onto it.

Embeds are a fast way to add functionality you have no interest in building yourself. Nobody should build their own video player or map from scratch for a single business site. The trouble starts when an embed is used as a substitute for a real page, rather than a supplement to one.

Why it matters to you

A page that is one embed and a couple of sentences of your own text is, to a search engine, a page with almost nothing on it. One site’s entire podcast, twenty-one episodes of it, existed as a single 264-word page built around embedded players. Search engines cannot read what plays inside those players, so as far as ranking goes, that page said almost nothing about any of the twenty-one conversations it represented. A competitor’s show, with far fewer sites linking to it, was outranking that page for individual guest names simply because it had built a real page per episode, with a transcript search engines could actually read.

For a visitor, an embed-heavy page can also be slow. Every embedded player is a separate request to another company’s server, with its own script to load before anything plays.

How I use it

I use embeds for what they are good at: a map, a single video, a booking widget from a service you already use, dropped into a page that otherwise has its own real content around it. I do not use an embed as the entire content of a page that deserves to rank on its own.

For something like a podcast, the fix is episode pages: a real page per episode, with a transcript, a summary and guest details written as actual text, and the audio or video player embedded underneath as a convenience, not as the substance of the page. The words carry the ranking weight; the embed just lets the visitor listen without leaving.

What it looks like in practice

Look at the source of a page with a heavy embed and you will find an iframe pointing to another domain, doing all the real work invisibly. On a page I have built around real content with an embed added for convenience, you will find that same iframe sitting underneath several paragraphs of actual text, a transcript, a summary, links to related pages, all of it readable and rankable on its own, whether or not a visitor ever presses play.