StackContext← Documentation

STRUCTURED EXTRACTION

Read the content
inside an embedded page.

Some sites display their useful content through an iframe hosted by another service. StackContext can now ask for access to that embedded site and include its readable text in your structured result.

How to use it ↓
EMBEDDED CONTENT

Parent page → iframe → structured JSON

Access is requested only when the top-level page has no readable text and an embedded page is present.

ON-DEMAND ACCESSRead the embedded siteOnly after you approve the browser prompt

HOW TO USE IT

Approve access when the browser asks.

Open the page you want to structure, then select Structure this page. If its content is embedded from another site, StackContext requests access to that specific embedded origin. Approve the prompt, and then it reads the available frame text, headings, and links.

01

Open the parent page

For example, a company careers page may embed its job board from a separate hiring platform.

02

Structure the page

StackContext first checks the top-level page and only falls back to frames when it cannot find readable text there.

03

Grant the targeted permission

The browser shows the embedded site that will be read. Declining leaves that embedded content out of the extraction.

WHAT IS INCLUDED

Readable page context.

StackContext combines the accessible frame’s text, headings, and links with the page context sent to your selected provider.

LIMITATIONS

Browser access still applies.

Content cannot be read if you decline the permission, if the browser blocks the frame, or if the iframe has no readable text. PDFs, browser settings pages, and extension pages are not supported.

Ready to structure
the whole page?

Install the latest StackContext extension, then structure the page in front of you.

Download Chrome / Chromium ↓Download Firefox ↓