wp-static-clone

Clone a live WordPress site into a static HTML deployment.

93|9|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/jdevalk/skills --skill wp-static-clone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wp-static-clone
Source: https://github.com/jdevalk/skills/tree/main/wp-static-clone
Command: npx skills add https://github.com/jdevalk/skills --skill wp-static-clone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Converts a live WordPress site into a static HTML clone that can be deployed on any static host, eliminating backend dependencies.

Core Features & Use Cases

  • Sitemap-driven URL discovery from sitemap_index.xml or sitemap.xml, producing a flat static output.
  • Single-shot wget scraping to ensure cross-page links are rewritten consistently.
  • Asset harvesting for long-tail resources missed by standard crawlers, with paths rewritten to root-relative.
  • Self-hosted Gravatars and removal/replacement of WordPress runtime components (forms, analytics) for privacy and performance.
  • Banner branding on the output and host-specific deployment recipes for Cloudflare Pages, Netlify, Vercel, or generic hosting.
  • Produces a drop-in static clone that requires no backend and no build step.

Quick Start

Use the wp-static-clone skill to clone a live WordPress site and deploy the result to a static host.

Frequently Asked Questions about wp-static-clone

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

FAQPage Schema
How do I convert a live WordPress site to static HTML?

Converting a live WordPress site to static HTML involves sitemap-driven URL discovery, single-pass scraping for asset collection, and rewriting cross-page links to be root-relative. This process strips the WordPress runtime and produces a deployable static clone.

Can I deploy a static WordPress clone to Cloudflare Pages or Netlify?

Yes, you can deploy a static WordPress clone to Cloudflare Pages, Netlify, Vercel, or generic static hosts. The cloning process generates host-specific deployment recipes, yielding a drop-in static output that requires no backend or build step.

Does converting WordPress to a static site remove tracking scripts and Gravatars?

Yes, converting WordPress to a static site removes and replaces runtime components like analytics for privacy. It also harvests self-hosted Gravatars, ensuring the static output preserves user privacy and eliminates external runtime dependencies.

What is the best way to scrape a WordPress site for offline access?

The best way to scrape a WordPress site for offline access is using a sitemap-driven single-pass wget scraper. This ensures cross-page links are rewritten consistently while collecting long-tail assets missed by standard crawlers into a flat static output.

What are the limitations of migrating a WordPress site to static HTML?

Migrating a WordPress site to static HTML limits dynamic backend features by stripping runtime components like forms and analytics. It relies on sitemap discovery and single-pass scraping, meaning content not linked in the sitemap or missed during asset collection will not be included.