A listing page often shows a summary of each item, while the full detail lives on the item's own page. Nested scraping follows the link for each item and pulls fields from that detail page too.
When you need it
Use nested pages when the data you want is not on the list. For example, a property listings page might show price and address, but bedrooms, floor area, and the full description only appear when you open a specific listing.
How it works
When the assistant detects that each item links to its own page, it can open those pages and suggest extra fields from them. Your scraper then captures both the list-level fields and the detail-page fields for every item.
Setting it up
In the setup wizard, tell the assistant which fields come from the detail page: "open each listing and also grab the floor area and the full description." It analyses an item's page and proposes those fields, testing them against the real page like any other field.
Nested scraping visits one extra page per item, so runs take longer and use more of your plan's allowance than a list-only scraper. Only add detail-page fields you actually need.