scrape-webpage

Extract webpage content, metadata, and images for CMS migration.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/mhaack/sewjaland --skill scrape-webpage-mhaack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scrape-webpage
Source: https://github.com/mhaack/sewjaland/tree/main/.claude/skills/scrape-webpage
Command: npx skills add https://github.com/mhaack/sewjaland --skill scrape-webpage-mhaack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, sharp, and includes scripts (resource) components.

What problem does it solve?

Scrape-Webpage helps teams migrating content from web pages to a CMS by extracting page content, metadata, and images, and preparing migration-ready artifacts including local images and cleaned HTML.

Core Features & Use Cases

  • Extracts page metadata (title, description, Open Graph, JSON-LD) for SEO preservation during migration.
  • Downloads all visible images, converts non-PNG/JPG formats to PNG, and maps original URLs to local paths for offline CMS imports.
  • Produces cleaned HTML with preserved attributes and with image references replaced by local paths, ready for import.
  • Generates structured document paths and related file names (MD, plain HTML) for CMS-compatible structure.
  • Use Case: You are migrating a large set of pages to AEM Edge Delivery Services and need a reproducible pipeline that yields import-ready assets and data.

Quick Start

Run the analyze-webpage script on a target URL to generate migration-ready artifacts in the output directory.

Frequently Asked Questions about scrape-webpage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract webpage content and images for CMS migration?

Scraping webpage metadata for migration requires extracting title, description, Open Graph, and JSON-LD data. This Skill captures these SEO fields directly from live URLs to ensure search ranking signals are preserved during AEM Edge Delivery Services imports.

Does this webpage scraper handle lazy-loaded images?

Yes, robust handling for lazy-loading is supported during image capture. The Skill uses Playwright to interact with the page, ensuring all visible images load before downloading and converting them to PNG for CMS pipelines.

Can I use Playwright and Sharp to prepare import-ready HTML and images?

Webpage scraping for migration requires a live target URL and an output directory. Running the analyze-webpage script fetches the page, extracts metadata, downloads images, and generates structured document paths and related file names for CMS-compatible structure.

What is the best way to download and normalize webpage images for offline CMS imports?

The best way is to capture all visible images, convert non-PNG/JPG formats to PNG, and map original URLs to local paths. This generates offline-ready assets and cleaned HTML with replaced image references suitable for AEM Edge Delivery Services.

How do I generate structured document paths for AEM Edge Delivery Services imports?

Image format normalization during webpage scraping converts non-PNG/JPG formats to PNG using Sharp. This ensures all downloaded images are uniformly formatted and correctly mapped to local paths before CMS pipeline execution.