Iframes and Embedded Widgets: Effects on SEO and Speed

Short answer: Content shown in an iframe belongs to the page that is framed, not to the page that embeds it, so search engines may index it under its own address and may not count it for your page. Use iframes for maps, videos, forms and widgets where that is acceptable, but keep important text on your own page, lazy-load frames below the fold, limit the number of frames and secure them with the right attributes and headers.

An iframe is a window inside a page that shows another page. It is a convenient way to embed a map, a video player, a booking form, a calendar or a chat tool without building them yourself. It is also a common source of problems: missing text, slow loading, layout jumps, privacy questions and security risks. This guide explains how search engines see embedded content and gives practical rules for using it well. It is related to the topic of third-party scripts and speed, since many embeds bring scripts of their own.

How search engines treat iframe content

A search engine that processes a page can load the framed page too, but it generally treats the framed content as part of the other address. The words inside a frame are therefore associated with the source page and not necessarily with the page that embeds it. If the source is blocked from crawling, the content cannot be read at all. This is why a page that is mostly an iframe, such as a price list shown from another system, may appear nearly empty to search. The lesson is simple: do not rely on a frame to carry text that you want to rank for.

When iframes are a good choice

Embeds suit content whose value is interactive or visual and whose text is not needed for search. Maps showing a location, video players, calendars, payment forms and surveys are typical. For these, an iframe is fast to set up and keeps the heavy logic with the provider. The page around the embed carries the meaning: a clear heading, a description of what the visitor can do and, for a map, the address in text. This approach is also the basis of the guide to video SEO with embedded videos.

When to avoid iframes

Avoid iframes for the main content of a page: articles, product descriptions, prices, reviews or documentation that you want to be found. If a tool displays your catalogue in a frame, the products may not rank on your site, and the framed address may even compete with your page. Where you currently embed such content, consider replacing the frame with content in your own page, or load the data from the provider and render it as text. If that is not possible, provide a text summary and links to the full pages next to the frame.

Keep important text and links outside

Put the heading, the introduction, the key facts and the calls to action in the page itself. Add a short description of what the embed shows, so that visitors and crawlers understand it even before the frame loads. Give the frame a title attribute that describes it, which helps screen reader users and gives machines a clue. Provide a plain link to the source, for example to open a large map or to view the video on its own page. These steps cost little and keep the page useful if the frame fails.

Speed and layout

Each iframe loads a full page with its own scripts, styles and images, which can be heavy. A few embeds on one page add up quickly. Use lazy loading for frames below the first screen so that they load only when needed, and consider a click-to-load placeholder for heavy players and maps: show an image with a play button, and load the real frame after a click. Set the width and height or an aspect ratio so that the page does not jump when the frame appears, which affects layout shift as described in the CLS guide. Test the page with and without embeds to see their cost.

Security and privacy attributes

Frames bring other parties into your page. Use the sandbox attribute to limit what the framed page can do, allowing only the features you need. Set the allow attribute carefully for features such as fullscreen. Use the referrer policy to limit the information sent to the provider. Check what cookies and trackers the embed sets, and make sure that your consent tools handle them, since some embeds load tracking before the visitor agrees. Choose providers with a good record and a privacy-friendly mode where one exists.

Preventing your own pages from being framed

The same technology can be used against you. If other sites can frame your pages, attackers may trick visitors into clicking on hidden buttons. Protect your pages with a header that controls who may frame them, using either the older frame options header or the content security policy directive for frame ancestors. Allow framing only for sites that you control or trust, and leave it off for the rest. This is a security matter, but it also keeps copies of your pages from appearing inside other people’s sites.

Check how the page appears to search tools

Use the URL Inspection tool and look at the rendered page and the page text. Check whether the content you care about appears, and whether the frame loads at all, since some providers block automated fetching. Compare the result with what a visitor sees. If the embed fails for crawlers, make sure that the surrounding text still makes sense. For frames that you control, make sure the framed address is not blocked in robots.txt, and decide whether it should be indexed or marked noindex, so that framed fragments do not appear as separate results.

Review your embeds once or twice a year. Providers change their products, shut down services or change their loading behaviour, and old embeds can break or slow down pages. Remove embeds that nobody uses, replace those that have heavy alternatives, and check that links to providers still work. A short inventory of every embed, with its purpose and its owner, makes the review quick.

Accessibility deserves a check as well. A frame needs a descriptive title, keyboard access to its controls and sufficient contrast, and the focus must not become trapped inside it. If the framed content is a form, make sure that error messages are announced and that the page around it explains how to complete the form. Many embedded tools fall short here, so test them with the keyboard and with a screen reader before you rely on them.

Finally, remember that an embed is a dependency. If the provider has an outage, your page shows a blank rectangle. Provide a fallback message and a link, and avoid using embeds for essential steps such as paying or contacting you, unless you have an alternative route. A resilient page works even when third-party content does not.

Consider three common cases. First, a restaurant embeds a map and a booking form. The map is harmless, provided that the address and the opening hours are written as text on the page. The booking form is more important: if it fails to load, customers cannot reserve, so the page should show a phone number and an email link beside it. Second, a software company embeds a documentation portal in a frame on its main site. The articles in the portal are indexed under the portal address, and the main site’s help page has almost no text. The company decides to publish the documentation directly under its own domain, which concentrates search value in one place. Third, a publisher embeds social posts. Each embed loads scripts and images from another company, so the publisher replaces most of them with a quoted text and a link, keeping a few where the original format matters.

Another point is analytics. Events inside a frame, such as a click on a button in an embedded form, do not appear in your analytics unless the provider sends them to your tracking or you use a messaging method between the frame and the page. If conversions are measured through an embedded tool, check how the results reach your reports. Many sites discover that a large share of their conversions is invisible because the form lives in a frame that their tracking cannot see.

If you are unsure whether to keep an embed, test the page without it. Compare the loading time, the interaction speed and the behaviour of visitors. Sometimes a simple link to the provider’s page is better than a frame, because it loads nothing until the visitor chooses it. For long, rarely used content, such as a map of ten locations, a link to a full map may serve people better than a large frame that every visitor must download.

Site SEO AI Audit crawls your site and checks page weight, status codes, headings, titles, structured data, broken links and mixed content, so you can see which pages are heavy and whether key content is present in the page itself. It does not test the behaviour or security of third-party embeds. The first audit of up to 200 pages is free; larger sites can see the pricing page.

The bottom line

Use iframes for maps, videos and tools, keep key text and links in your own page, lazy-load heavy frames, secure them with attributes and headers, and review them regularly.

FAQ

Does Google index content in iframes?

It can read framed pages, but the content generally belongs to the framed address, not to the embedding page.

Are iframes bad for SEO?

Not when used for maps, videos and widgets. They are a problem when they carry the main content.

Should I lazy-load iframes?

Yes, for frames below the first screen. Keep a fixed size to avoid layout shifts.

How do I stop others framing my pages?

Send a frame-ancestors policy or a frame options header that allows only trusted sites.

What if my embed does not load for crawlers?

Make sure the surrounding text explains the content and offer a plain link to the source.