scrape-webpage

Scraping webpage content and images for an AEM migration involves extracting HTML, Open Graph data, JSON-LD, and local image assets into a structured metadata.json. This process requires Playwright for rendering and Sharp for image processing to produce migration-ready outputs.

Yes, webpage scraping with Playwright captures dynamic images and metadata by intercepting image requests during page load. It downloads images locally, maps them to the final HTML, and extracts Open Graph and JSON-LD metadata into a comprehensive metadata.json file.

The best way to extract Open Graph and JSON-LD metadata from a webpage is using an automated scraping script that renders the page with Playwright. This approach captures the fully rendered HTML, canonical URL, and structured metadata, outputting them in a structured metadata.json format.

To downscale and convert scraped webpage images to PNG, use the Sharp image processing library during the scraping workflow. As Playwright intercepts and downloads local image assets, Sharp processes them to ensure all images are properly formatted and optimized for migration pipelines.

Yes, you can use scraped HTML and image mappings for AEM Edge Delivery Services. The scraping process produces cleaned HTML with local image references and a comprehensive metadata.json bundle, which serves as a ready-to-migrate package for downstream AEM processing.

Yes, you need Node.js to run a webpage scraping script for migration. The script is executed via the command line using Node, and it relies on Playwright for browser rendering and Sharp for image processing to generate the final page-analysis bundle.