Iframes and Embedded Content: What Google Indexes

Most websites embed something from somewhere else. A YouTube video on the homepage. A Google Map on the contact page. A booking widget, a review carousel, an Instagram feed, a HubSpot form. Business owners usually ask me one of two things about these: “Does Google count the embedded content as part of my page?” and “Are these embeds slowing my site down?”

The answers are “sometimes” and “very often.” Most embeds are delivered through an iframe, which is a window on your page that loads another web page inside it. Google can look through that window, but what it does with the content depends on a few rules that most site owners never hear about.

Let me explain how Google handles iframes, who gets credit for embedded content, what each common type of embed means for SEO and speed, and how to control indexing from either side of the iframe. In brief: don’t rely on an iframe to carry content you want to rank for, and don’t let embeds load before people need them.

How Google handles iframes in 2026

An iframe is a piece of HTML that says, “show this other URL here.” It looks like this:

<iframe src="https://www.youtube.com/embed/VIDEO_ID" title="How we install a heat pump" width="560" height="315"></iframe>

The page that contains the iframe is the parent page. The page loaded inside it is the framed page. They are two separate URLs.

When Google renders your page (runs it in a browser like a visitor would), it can also load the framed page. Google’s John Mueller described the general approach in a Reddit thread, as reported by Search Engine Journal in April 2023:

“Google does try to crawl iframed content and include it in the indexed page, if it’s allowed. It’s not always trivial though.”

— John Mueller, as quoted by Search Engine Journal, Google on iframes and SEO

He repeated the idea in Google’s December 2023 SEO office hours, saying that “our systems would try to associate the sub-page’s content as a part of the primary page for indexing.” And in the same Reddit thread, his practical advice for content that must be indexed with your page was to include it directly rather than relying on iframes.

So the honest picture is this: Google tries to fold iframe content into the parent page, but it isn’t guaranteed. If a paragraph matters for rankings, put it in your own HTML. If you are new to how rendering works, our lesson on JavaScript SEO explains it in simple terms, and our longer JavaScript SEO guide goes deeper.

Whose page gets credit for embedded content?

This is where it gets interesting. Because the framed URL is a separate page, the same content can be connected to two places: your parent page and the original source.

An agency test lab provides some useful evidence here. Search Engine Land published the results in September 2022: Bastian Grimm of Peak Ace tested parent pages that framed content from other URLs. The findings, in plain words:

• The parent page could rank for text that only existed inside the iframe.
• It made no difference whether the framed page was on the same domain, a subdomain or another domain.
• If the framed page had a noindex rule (in a meta tag or an HTTP header), the parent page could not rank for that content.
• If the framed URL was blocked in robots.txt, the parent page also could not rank for it.

That was one agency’s test from 2022, so I treat it as direction, not hard science. But it lines up with what Google has said since. Here is how I summarize who usually “owns” what:

Embed type	Where the content lives	Who usually benefits in search
YouTube or Vimeo video	On the video platform	Both: the platform’s watch page, and your page if the video is its main content
Google Map	On Google Maps	Google Maps; your page gains little text value
Social post (Instagram, X, TikTok)	On the social network	Mostly the social platform
Review widget	On the review platform	Often the review platform, unless reviews are also in your HTML
Form or booking tool	On the form provider	Nobody, in search terms; it is functional content
Your own content framed from another URL	On your other URL	Possibly both, which can look like duplicate content

The last row matters for publishers. If you frame your own pages (for example, a calculator on /tools/calc/ framed into ten blog posts), the framed URL can get indexed by itself as a thin, bare page. I will show you how to stop that later in this guide.

Video embeds and the watch page rule

Video is where embeds matter most for SEO. Google’s video SEO best practices confirm it can find videos in a <video>, <embed>, <iframe> or <object> element. And on third-party players like YouTube:

“Google may index the video both on your web page and on the third-party platform’s equivalent page.”

— Google Search Central, Video SEO best practices

The catch is the watch page rule. Google only indexes a video for your page when the page’s main purpose is to show that single video. Google gives examples of pages that are not watch pages: a blog post that reviews an embedded video, a product page with a 360° product video, and a movie review with an embedded trailer.

So a 2,000-word blog post with a YouTube video halfway down will usually appear as a normal text result, not a video result. That is fine. It just means the video’s search value goes mostly to YouTube, while your page gets the engagement benefit.

If you want your own page to show up as a video result:

1. Create a dedicated page where the video is the main content, near the top, not hidden behind tabs or clicks.
2. Give it a unique title and description that match the video.
3. Add VideoObject structured data with name, description, thumbnail and upload date.
4. List it in a video sitemap, or include video details in your normal sitemap.
5. Check the rendered HTML in the URL Inspection tool to confirm the player loads for Googlebot.
6. Watch the Video indexing report in Search Console for indexed and non-indexed videos.

Google also notes that being on a watch page doesn’t guarantee indexing. Our full video SEO guide covers the rest.

Social embeds

Instagram, TikTok and X embeds are useful for showing social proof, but they bring little search value to your page. The text inside them lives on the social platform, and the embed scripts are often heavy. If a social post contains something important, like a customer quote, I suggest writing it into your page as text and using the embed only as a visual extra.

Maps, forms and widgets: what they cost and what they give

Many business pages carry three or four third-party widgets. Each one deserves a quick “is this worth it?” check.

Google Maps. A map embed helps visitors find you, but it doesn’t make your page rank locally by itself. Your address in plain text, your Google Business Profile and consistent citations do that work. I go into detail in does embedding a Google Map help local SEO? One cost note: Google’s Maps Embed API documentation says the API “is free to use with unlimited requests,” though an API key is required.

Forms and booking tools. Embedded forms from HubSpot, Typeform, Calendly and similar tools are fine for SEO, because nobody needs a form to rank. But keep the important words outside the iframe. Your heading, your explanation of what happens after someone books and your trust signals should all be in your own HTML. Our guide to contact page SEO covers what belongs there.

Review widgets. These often load reviews in an iframe or with JavaScript from the review platform. Visitors see them, but Google may credit the text to the review site. If reviews matter to your page, consider showing a selection as real HTML text on the page as well.

Chat widgets. These don’t affect indexing at all, but they are some of the heaviest scripts on many sites.

The performance cost of embeds, in numbers

This is where embeds do the most damage. Every iframe loads a whole second web page, with its own scripts, styles and fonts. web.dev’s guide to third-party embed best practices notes that many popular embeds include over 100 KB of JavaScript, sometimes up to 2 MB.

Its iframe lazy-loading article gives these figures for what lazy loading can save on the first page load:

Embed	Figure reported by web.dev
YouTube player	About 500 KB saved on initial load
Spotify player	514 KB saved on initial load
Instagram post	About 100 KB saved on initial load
Facebook Like button	About 215 KB loaded by default, 197 KB of it JavaScript
Chrome.com offscreen YouTube embed	Time to Interactive reduced by 10 seconds after lazy loading

Those numbers come straight from web.dev, and the article was last updated in September 2024, so treat them as a guide to scale rather than today’s exact weights.

Embeds hurt in three ways:

• Slower loading. Extra downloads compete with your own images and text, which can delay Largest Contentful Paint.
• Slower interaction. Heavy embed scripts keep the browser busy, which can hurt Interaction to Next Paint. Our guide to third-party scripts explains how to find the worst offenders.
• Layout shift. web.dev notes that embeds which load without fixed dimensions push content around. Always set width and height, or use a CSS aspect ratio, as I explain in our guide to Cumulative Layout Shift. And make sure fixed-width iframes don’t break your mobile layout; see the viewport meta tag guide for the mobile basics.

Lazy loading embeds and using facades

There are two simple fixes for embed weight, and you can use both.

Native lazy loading. Add loading="lazy" to iframes below the fold:

<iframe src="https://www.youtube.com/embed/VIDEO_ID" loading="lazy" title="Heat pump installation walkthrough" width="560" height="315"></iframe>

web.dev lists browser support for iframe lazy loading as Chrome 77, Edge 79, Firefox 121 and Safari 16.4. It also points out that leaving the attribute out is the same as loading eagerly. Don’t lazy-load an iframe at the very top of the page, because that delays the thing people came to see. Our lazy loading guide covers the SEO side.

Facades. A facade is a lightweight placeholder, usually a thumbnail image and a play button, that loads the real embed only when someone clicks. web.dev says the lite-youtube-embed facade “looks like the real player but is 224 times faster.” Chrome’s Lighthouse facade documentation lists options such as lite-youtube-embed and lite-vimeo-embed for video, and react-live-chat-loader for chat widgets. Note that the Lighthouse audit that flagged missing facades was removed in Lighthouse 13, so you won’t see that warning anymore, but the technique still works.

For maps, web.dev suggests a static map image where the map doesn’t need to be interactive, perhaps linked to Google Maps for directions.

An example: a service page with four embeds (hypothetical)

This is an example to show the thinking, not real data. Imagine a heating company’s service page with a YouTube video at the top, a Google Map at the bottom, a review widget in the middle and a chat bubble. Using web.dev’s rough figures, the YouTube player alone is around 500 KB. Add a map, a review widget and a chat script, and it is easy to imagine the embeds outweighing the page’s own content several times over.

A sensible plan: replace the video with a facade, swap the map for a static image linking to directions, lazy-load the review widget and load the chat bubble only after the user scrolls or after a few seconds. Then compare PageSpeed results and conversions before and after, using the approach in my guide on measuring on-page SEO changes.

Blocking or allowing indexing of iframe sources

Sometimes you control the framed page, and you want to decide how Google treats it. There are three common situations.

Your goal	What to use	Where it goes
Keep the framed page out of results, but let its content count on pages that embed it	noindex, indexifembedded	Robots meta tag or X-Robots-Tag header on the framed page
Keep the framed content out of search completely	noindex alone	On the framed page
Stop other sites from framing your pages at all	Content-Security-Policy: frame-ancestors (and X-Frame-Options for older browsers)	HTTP response header

The first option is the one most people don’t know about. Google added the indexifembedded rule in January 2022. Its robots meta tag documentation says it lets Google index a page’s content when it is embedded in another page “through iframes or similar HTML tags,” in spite of a noindex rule, and that it only has an effect when combined with noindex. In practice, the framed page would carry:

<meta name="robots" content="noindex, indexifembedded">

This suits embeddable tools, calculators and media players that you don’t want indexed as bare standalone pages. For more on noindex itself, see our noindex tag guide.

The third option is about protection, not SEO. MDN describes the frame-ancestors directive as setting which parents may embed a page, and notes it can’t be set in a meta tag. frame-ancestors 'self' allows only your own site to frame your pages.

Accessibility for every iframe

One small thing applies to every embed: give each iframe a title attribute that says what it is. W3C technique H64 explains that the title “provides a label for the frame so users can determine which frame to enter and explore in detail.” “YouTube video player” is better than nothing; “Video: how we install a heat pump” is better still.

Questions site owners ask about iframes and SEO

Does Google index content inside an iframe?

Often, yes. Google tries to associate iframe content with the parent page when it is allowed to crawl it, but this isn’t guaranteed. Put anything important for rankings in your own HTML.

Does embedding a YouTube video help my page rank?

Not directly. It can improve engagement, but your page is only treated as a video result when the video is its main content. Otherwise the video’s search value mostly stays with YouTube.

Will a noindexed iframe source hurt my page?

Your page won’t be penalized, but it likely won’t get credit for that content. Use noindex, indexifembedded on the source if you want the content to count on embedding pages.

Should I lazy-load every iframe?

Every iframe below the fold, yes. Not the one at the very top of the page, because that delays the main content people came to see.

Are iframes bad for SEO?

No. They are a normal way to add maps, videos and forms. The problems come from relying on them for important content and from their performance cost.

Auditing the embeds on your own site this week

Here is my short checklist. List every embed on your top 20 pages. Ask whether each one is needed. Move important text out of iframes and into your own HTML. Add loading="lazy" and a clear title to every iframe below the fold, set width and height on all of them, and replace heavy video and map embeds with facades or static images where you can.

If you would like help finding the embeds and scripts slowing your site down, our page speed optimization team does this every week. Request a free quote and send us the pages that matter most.

Further reading on iframes SEO

• Click Depth: How Far Your Pages Sit from the Homepage
• Link and Image Title Attributes: Do They Help SEO?
• Does Bold Text Help SEO? Formatting for Skimmers

Sources for this iframes and embeds guide

1. Search Engine Journal: Google on iframes and SEO (April 2023)
2. Google Search Central: December 2023 SEO office hours
3. Search Engine Land: Technical SEO testing: How Googlebot handles iframes (September 2022)
4. Google Search Central: Video SEO best practices
5. Google Search Central: Robots meta tag specifications
6. web.dev: It’s time to lazy-load offscreen iframes
7. web.dev: Best practices for using third-party embeds
8. Chrome for Developers: Lazy load third-party resources with facades
9. Google Maps Platform: Maps Embed API usage and billing
10. MDN Web Docs: CSP frame-ancestors
11. W3C: H64 Using the title attribute of the iframe element