Are iframes bad for SEO?

Not categorically. Google has been able to crawl and index iframed content for years, and content that loads inside an iframe can be associated with the parent page in many cases. The problems arise when the iframed content is the primary on-page content, when it is served from a host with weaker authority, or when it relies on JavaScript that the crawler does not execute. Iframes used for embeds (YouTube, Maps, Calendly) almost never cause SEO problems; iframes used as a layout primitive almost always do.

Will Google index text inside an iframe?

Sometimes. Google can crawl the iframe's source URL and may associate the rendered content with the parent page, but the association is weaker than text rendered directly in the parent document. If the iframed content is the page's primary content — long-form text, product listings, articles — you should serve it directly in the parent, not via iframe.

Do iframes affect Core Web Vitals?

Yes, materially. Iframes are render-blocking by default, count toward Largest Contentful Paint when they contain the LCP element, and are a common source of Cumulative Layout Shift when they load without reserved dimensions. Lazy-loading iframes (loading="lazy") and reserving width/height attributes are now baseline hygiene.

Can search engines follow links inside an iframe?

Yes, but the link equity flows to the iframe's host, not the parent page's host, unless the iframe and the parent share a hostname. This is why iframed widgets that contain author bylines or sponsor links are functionally invisible to the parent site's link graph.

Should I use an iframe to embed a YouTube video?

Yes — YouTube's iframe embed is the correct method, and it does not harm SEO. The video itself is hosted by Google and indexed independently; the parent page benefits from the topical association and from VideoObject schema if you mark it up.

What about iframing a third-party booking widget?

Acceptable for the booking widget, but do not let the iframe replace your own indexable content describing what the user can book. The widget is a conversion tool; the page around it is what gets discovered.

Do AI search engines handle iframes the same way as Google?

Mostly worse. Live-mode crawlers used by AI engines (GPTBot, PerplexityBot, ClaudeBot) do less rendering than Googlebot and are more likely to ignore iframed content entirely. If a sentence inside an iframe is the answer to a query, it is unlikely to be cited. Render that sentence in the parent document.

Is the loading="lazy" attribute on iframes a ranking signal?

Not directly. It improves Core Web Vitals scores by deferring offscreen iframe loading, which can improve LCP and reduce blocking. The signal is the resulting performance, not the attribute itself.

iframe SEO (2026): When iframes Wreck Indexation

What an iframe is, in search-engine terms

An <iframe> is an inline frame — an HTML element that loads another document inside the current page. The browser fetches the iframe's src URL, renders that document in its own isolated browsing context, and composites it into the layout of the parent. From the user's perspective the two pages look like one. From a search engine's perspective they are two distinct documents that happen to render together.

That distinction is the entire SEO story. Every question about iframe SEO eventually reduces to one underlying question: "is the content I want indexed reaching the parent document, or is it trapped in the iframe?"

How Google handles iframed content in 2026

Google is the most capable crawler on the open web at handling iframes. Googlebot will follow the iframe's src, fetch the embedded document, and in many cases associate that content with the parent page in addition to indexing it as a standalone URL. That is the optimistic version of the story. The pessimistic version, which we see far more often in audits, looks like this:

Iframe pattern	Indexation outcome	Common cause
YouTube / Vimeo embed	Fine — content indexed by the host, association preserved	Standard embed flow, well-understood by crawlers
Same-origin layout iframe	Sometimes associated, often not	Crawler treats it as a separate URL with its own ranking
Cross-origin booking widget	Iframed content not indexed with parent	Different host, no semantic association
JavaScript-injected iframe	Frequently not crawled at all	Crawler does not execute enough JS to discover the iframe
iframe whose src is X-Frame-Options blocked	Not indexed, often not detected	Browser hides the failure; crawler sees nothing
iframe used for primary article body	Catastrophic — article often not indexed at all	Anti-pattern; happens when CMS embeds article via iframe

AI search engines are a tier worse. The live-mode crawlers used by ChatGPT browsing, Perplexity, Claude, and Gemini do less rendering than Googlebot and have shorter timeouts. Anything that is not in the parent document's HTML response is at high risk of being invisible to them.

If the answer to the page's primary query is inside an iframe, expect to lose to a competitor whose answer is in the parent document. AI engines do not wait for your iframes to load.

— Martin Vassilev, Founder, Toronto SEO

When iframes wreck indexation

Article body inside an iframe
If a CMS or framework renders the article body via an iframe (most often a legacy WYSIWYG editor or a syndicated content widget), expect the article to either not be indexed or to rank materially worse than competitors.
Product listings inside an iframe
Some legacy ecommerce platforms embed the catalogue via iframe. Result: the products themselves rank, but the parent category page does not gain authority from them.
Author bylines and credentials inside an iframe
E-E-A-T signals depend on association. If the byline lives inside an iframe served from a different host, Google may not associate the author with the article.
FAQ content inside an iframe
Common with embedded help-centre widgets. The FAQ answers do not reach the parent document, FAQPage schema does not apply, and the page loses the rich-result eligibility.
Customer reviews inside an iframe
If reviews are embedded via a third-party widget that loads asynchronously, they may not be in the rendered HTML when the crawler captures the page. Plan for both server-side rendering of reviews and Review schema on the parent.
Pricing inside an iframe from a billing platform
Pricing is one of the most commercially valuable pieces of content on a SaaS marketing site. If it lives in an iframe, you have hidden it from search.

When iframes are safe (and the right tool)

There is a long list of cases where iframes are appropriate, well-supported, and have no negative SEO impact. The pattern is consistent: the iframed content is a tool or media object, not the primary content of the page.

Video embeds (YouTube, Vimeo, Wistia)

Standard, well-understood. Pair with VideoObject schema on the parent page.

Map embeds (Google Maps)

Fine. The map is a tool, not the content. Add a text address and LocalBusiness schema in the parent.

Booking and scheduling widgets

Calendly, Cal.com, SimplyBook embeds work well as long as you describe what is being booked in indexable text on the parent page.

Payment forms (Stripe, PayPal)

Required for PCI compliance — iframes are the correct architecture for payment surfaces. No SEO downside as long as the surrounding page is rich.

Interactive demos and sandboxes

CodeSandbox, Figma embeds, interactive product demos. The demo is a tool; describe it in the parent.

Third-party form embeds

HubSpot forms, Typeform, etc. Fine for the form itself; do not embed the entire landing page that way.

Modern alternatives to consider first

Before reaching for an iframe in 2026, the modern alternatives are usually better:

Server-side include or edge render
Compose the page on the server (or at the edge) so the browser receives a single document with all content present in the HTML response. Best for SEO, best for performance, best for crawler compatibility.
Reverse proxy
If two services need to live under one hostname, a reverse proxy is almost always a better answer than an iframe. Same SEO benefits as a single server, with operational separation preserved.
Web Components or framework islands
For interactive widgets, hydrating a web component or an island in the parent document keeps the content in the parent's HTML and the interactivity isolated.
API-driven server rendering
Pull data from the third-party API and render it on the server. The third-party owns the data; you own the SEO surface.

The iframe SEO debugging checklist

Run a Mobile-Friendly Test on the page and verify all primary content is in the rendered HTML.
View source (Ctrl-U) and search for the iframe's main content text. If it is not there, the iframe is hiding it.
Use the URL Inspection tool in Search Console and review the rendered HTML — not the live test, the indexed version.
Verify every iframe has explicit width and height attributes to avoid Cumulative Layout Shift.
Add loading="lazy" to every iframe that is not above the fold.
Check for X-Frame-Options or Content-Security-Policy headers on the iframe's src that would prevent loading.
If the iframe contains an answer to a query you want to rank for, move that answer into the parent document.
Validate the iframe's src URL also returns a sensible standalone response — it can and will be crawled directly.

The honest summary

iframes are a precision tool. Used for embeds and tools, they are invisible to your SEO performance. Used as a layout primitive for primary content, they silently destroy it. The 2026 reality is that AI engines are even less forgiving than Google, so anything you would not want to lose to an AI competitor needs to live in the parent document. When in doubt: render server-side, reserve dimensions, lazy-load anything offscreen, and treat iframes as the last option, not the first.

Frequently Asked Questions

The iframe questions we get asked most often during technical audits.

iframe SEO: When iframes Wreck Indexation (and When They Don't)