Web Block Detector FAQs

Question 1

Does it work with modern JavaScript frameworks and SPAs?

Accepted Answer

Yes, it utilizes Puppeteer's networkidle2 condition and includes a built-in delay to ensure that dynamic content, CSS animations, and layout shifts have settled before analysis begins.

Question 2

Can it filter out navigation menus and footers?

Accepted Answer

Yes, the skill includes specific exclusion rules that filter out non-content elements like NAV, HEADER, and FOOTER tags, as well as fixed or sticky UI elements.

Question 3

How are the generated CSS selectors kept stable?

Accepted Answer

The skill follows a strict priority order for selector generation, preferring unique IDs and specific class combinations over brittle paths like nth-of-type, ensuring they remain valid even if the page content updates.

Question 4

How does Block Detector identify page sections?

Accepted Answer

It uses a tiered strategy that first checks for semantic HTML elements, then scans for common class patterns, looks for CMS-specific data attributes, and finally falls back to layout-based heuristics.

Question 5

What kind of metadata does the skill extract for each block?

Accepted Answer

For every detected block, it captures the visual bounding box, CSS selector, HTML snippets, text content, and boolean flags for headings, images, and links.

Web Block Detector

Key Features

Use Cases

Web Block Detector

Key Features

Use Cases