← ClaudeAtlas

wordpress-to-webflowlisted

Rebuild a WordPress site in Webflow so it looks and behaves the same, keeps every URL that matters, and stays editable by the site's own team. Use this whenever someone wants to move, migrate, rebuild or recreate a WordPress site (WP Engine, ACF, Yoast, custom themes, page builders) in Webflow, import WordPress content into Webflow CMS, turn WordPress or host redirect rules into Webflow 301s, check a Webflow rebuild against the old site, add JSON-LD schema markup to a Webflow site, test that editors can add new CMS items, or plan the DNS cutover. Use it even when they ask about only one of those steps, and when they hit a Webflow API or MCP limit (Collection Lists, components, slots, redirects, sitemap) during any Webflow build.
seanbtw/wordpress-to-webflow · ★ 0 · Web & Frontend · score 72
Install: claude install-skill seanbtw/wordpress-to-webflow
# WordPress to Webflow A method for rebuilding a WordPress site in Webflow, written from a full migration (about 500 CMS items, 30 pages, 24 theme blocks), three follow-up schema jobs, a second site on the same theme (about 370 items, 37 pages) built with this kit in one overnight run, and a third (about 200 items, 38 pages) built unattended in about six and a half hours. It exists because the obvious way fails: rebuilding pages by eye from the live site gets the colours right and nearly everything else subtly wrong (breakpoints, spacing tiers, which element carries which rule, behaviour, URLs). The method below replaces looking with measuring. ## The method in five sentences 1. **Build from source, not by eye.** The WordPress theme and database are the specification. Run the backup locally and treat that copy as the reference for every comparison. 2. **Inventory before building.** Every page, post, field, option, asset, URL and SEO value goes into machine-readable files, and the acceptance counts are generated from them, never typed. 3. **Prove the risky parts small.** Settle component versus Collection List boundaries, body conversion, curation, filtering past 100 items, search, and a list of the template's own collection on a handful of real examples before building at scale. 4. **Import idempotently.** Identity is the WordPress id, not the slug, so the import can be rerun at cutover without duplicates. 5. **Verify by script, with evidence.** Differences are found by co