+ SERVICE · MIGRATION

WordPress to Astro

WordPress to Astro without losing the SEO.

A migration path that keeps every URL, redirect, schema, and editorial flow — and trades 40 plugins for a static site that ships in milliseconds. Content team keeps editing. Stack disappears.

STACK

Astro · MDX · Cloudflare

CONTENT

Markdown · Sanity · Decap

ENGAGEMENT

Fixed scope · 4–8 wk

TEAM

2 engineers · 1 SEO lead

+ THE BRIEF

Most WordPress sites are 70% editorial pages, 30% scaffolding, and 100% slow. We move the editorial — posts, taxonomies, redirects, schema, sitemap, OG cards, the whole crawl surface — to Astro. Same URLs, same author flow, none of the plugins.

+ WHAT YOU GET
  • Full-content migration: posts, pages, taxonomies, ACF fields, custom post types.

  • Every URL preserved. 301 map signed off by your SEO lead before cut-over.

  • Astro static build with islands only where they earn it.

  • Editorial workflow on Decap, Sanity, or plain Markdown — your call.

  • Lighthouse 100 / 100 / 100 / 100 budget on the top 50 pages.

  • Cut-over runbook and a rollback path that takes 60 seconds.

+ CAPABILITIES

Inside the engagement.

  • 01

    Content extraction

    WP REST + custom SQL exporters. Posts, pages, ACF, CPTs, taxonomies, media — everything serialised to Markdown with front-matter, deterministic and re-runnable.

  • 02

    URL & redirect map

    A 1:1 URL map signed off before any code ships. Every legacy permalink resolves; every redirect chain collapses to a single hop.

  • 03

    SEO continuity

    Schema.org JSON-LD, OG, sitemap, robots, canonicals, hreflang — all carried over. We diff against the old site weekly through cut-over.

  • 04

    Editorial UX

    Decap (open-source, free) for solo editors. Sanity for teams. Plain Markdown + GitHub PRs for engineering teams. We pick once and stick to it.

  • 05

    Forms & comments

    Cloudflare Workers or Resend for forms. Giscus or Cusdis for comments. No PHP. No spam queue.

  • 06

    Edge & search

    Cloudflare Pages or Vercel. Pagefind or Algolia for search. Image optimisation through Cloudinary or Astro's own pipeline.

+ THE STACK

The migration toolchain.

Tested on sites with 40 to 8,000 posts. The bigger the archive, the more these tools earn their keep.

  • + BUILD
    Astro 4+MDXViteTypeScript
  • + CONTENT

    Decap CMSSanityMarkdownWP REST

  • + EDGE

    Cloudflare PagesWorkersR2Vercel

  • + SEO
    Schema.orgSitemapPagefindPlausible
+ HOW WE RUN IT

From kickoff to handover.

  • 01

    Audit & URL map

    We crawl the live WordPress site, inventory every URL, every plugin, every author quirk. You get a one-page audit and a signed-off 301 map. Nothing else moves until that’s green.

    Crawl reportURL mapPlugin inventory
    WEEK 1
  • 02

    Content export

    A reproducible export script pulls posts, ACF fields, CPTs, and media into Markdown. Editors review the diff against staging. We re-run until the diff is empty.

    Export scriptMarkdown corpusMedia bucket
    WEEK 2
  • 03

    Astro build

    Templates, layouts, islands, search, schema, OG cards. We build against the migrated content from day one — no Lorem Ipsum.

    Astro repoStaging URLLighthouse budget
    WEEK 3–5
  • 04

    Cut-over + monitor

    DNS swap on a Tuesday. We watch GSC and analytics for two weeks; nothing rolls back. Editorial team trained on the new flow before we leave.

    Cut-over runbookRollback pathEditor training
    Week 6–8
100/100
Lighthouse score
<80ms
Median TTFB at edge
0
URLs lost in migration
-96%
Hosting cost vs. WP
+ FAQ

Things teams ask before they sign.

Anything else? Email us.

+ START A PROJECT

Leave WordPress on your own terms.

Tell us your URL and your post count. We’ll send a one-page audit and a fee letter within three working days.

+ AVERAGE REPLY4 hours · weekdays+ FIRST CALL30 min · with a founder+ NDAOn request