identify-page-structure

You can structure scraped webpage content for AEM imports by analyzing HTML scrapes, screenshots, and metadata to detect a two-level hierarchy of sections and content sequences, producing a neutral structural description for deterministic authoring workflows.

Mapping webpage sections and content sequences is best handled by surveying blocks and applying per-section sequencing to generate neutral output, which informs authoring choices without prematurely proposing specific blocks for the downstream import.

Yes, you can use HTML scrapes and screenshots to detect page structure for content migration. The analysis applies per-section sequencing and block surveying across these inputs to export neutral structural descriptions for downstream consumption.

To decompose a webpage into sections for block inventory workflows, you identify top-level sections and their internal content sequences, then export these neutral descriptions to integrate with page-decomposition and block-inventory processes.

No, the page structure analysis does not propose specific AEM blocks during the identification phase. It produces neutral section and sequence descriptions to inform authoring choices, leaving block proposals to downstream workflows.