An `<iframe>` embeds another HTML document within the parent page. The embedded document has its own URL, cookies, and JavaScript context, and is subject to the same-origin policy — meaning the parent page's JavaScript cannot directly read the iframe's DOM if they differ in origin.
For scrapers, iframes present two challenges: the content must be fetched from a second URL (which may itself require authentication or anti-bot handling), and the relationship between the parent frame and embedded frames must be navigated correctly. Browser-based scrapers can switch frame context to interact with embedded content directly.
Common iframe use cases include embedded payment forms, third-party video players, map widgets, and ad units. Anti-bot systems sometimes serve challenge pages inside iframes so that the challenge logic is isolated from the host page's JavaScript.