Review the use of iFrames

An iFrame embeds another HTML page inside your page. In Webflow, you'll typically use them for third-party tools — a booking calendar, a form, a video player, a map. They work fine for users. The issue is that their content is largely invisible to Google.

Google can crawl some iFrame content, but it does so inconsistently, and the content inside an iFrame is usually attributed to the source URL, not your page. If the most substantive content on your page lives inside an iFrame, that page can look thin to Google even if it's genuinely useful.

The review before going live is straightforward: open each page, find every iFrame, and ask three questions.

Is the iFrame loading content I want indexed? If yes, consider whether that content can also exist as real text on the page — a description, a summary, supporting copy around the embed. The embedded tool provides the function; the page text provides the SEO value. A booking widget surrounded by a paragraph explaining what you offer is a better page than a booking widget alone.

Is the iFrame slowing the page down? iFrames loading external scripts on page load add render-blocking overhead and can affect your Core Web Vitals. Check PageSpeed Insights on any page with an iFrame. If the impact is significant, add a loading="lazy" attribute to defer the iFrame until the user scrolls near it — a simple fix available in Webflow's embed settings.

Is the iFrame visible on mobile? Some iFrames have fixed dimensions and don't adapt to smaller screens. Open your Webflow preview in mobile view and verify. A calendar or form tool that overflows the viewport on mobile is both a UX problem and a ranking factor — Google uses mobile-first indexing.

A specific case worth checking: embedded Google Maps. The Maps iFrame is one of the heaviest third-party scripts you can load. If it's on your homepage or a high-traffic page, consider a click-to-load approach — show a static image until the user clicks, then load the iFrame. It significantly reduces page weight without removing functionality.

You don't need to remove all iFrames. Most are fine. The goal is to know what each one is loading, how it affects your page speed, and whether you've compensated for its SEO limitations with real on-page text.