What does a WordPress to Astro migration involve?
A WordPress to Astro migration takes the content out of WordPress, rebuilds the design as Astro components, and serves the result as static pages from a CDN. Posts usually move to Sanity, for a friendly editor, or to Markdown files, for developer-run blogs. Every old URL is kept or redirected with a 301.
It is a bigger change than moving between two page builders, because the whole engine changes. That is also why the gains are bigger: no plugins, no database, and pages that are fast by default.
Is Astro a good fit for your site?
Astro is a great fit for content and marketing sites: company sites, blogs, docs, landing pages and resource libraries. It is a weaker fit if your site depends on many WordPress plugins for logged-in features, like memberships, complex stores or forums.
If editors need visual page building, WordPress to Webflow may suit you better. If you want speed and code ownership, Astro wins. We help you decide on the first call. See Astro vs WordPress for the long version.
Getting the content out of WordPress
We pull content through the WordPress REST API or a full export. That gives us posts, pages, authors, categories, tags, featured images and custom fields.
Then the clean-up starts:
- Gutenberg blocks become Portable Text or Markdown, with headings, lists and links kept
- Shortcodes and page builder markup are replaced with Astro components or removed
- Embeds like YouTube or tweets become light components
- Images in posts are downloaded, resized and re-linked
We compare counts at the end. Every post in WordPress has a match in the new site.
URL inventory and 301 redirects
WordPress creates many URL types: posts, pages, /category/ and /tag/ archives, /author/ pages, /page/2/ pagination, /?p=123 short links, attachment pages, feeds and files under /wp-content/uploads/. We list all of them from a crawl, your sitemaps, analytics and Search Console.
Post and page slugs are kept wherever possible, so most URLs do not change at all. The rest get a 301 to the closest match. Rules live at the host, like Vercel or Cloudflare Pages, so they return a true 301 status in one hop.
Carrying over SEO, page by page
SEO plugins hold a lot of hidden value. We export the title, meta description, canonical, social image and noindex setting for every post and page, then load them into matching fields in Sanity or front matter.
- Templates generate canonicals and Open Graph tags automatically
- JSON-LD schema covers Organization, Article, BreadcrumbList and FAQPage where it fits
- The XML sitemap is built from live, canonical pages only
- The RSS feed keeps its path if readers or tools use it
Images, forms and integrations
Your media library is often the heaviest part of a WordPress site. We move only the files that are used, resize them for each place they appear, and serve them in modern formats. Linked PDFs and downloads get redirects from their old upload paths.
Forms from Contact Form 7, Gravity Forms or WPForms are rebuilt to post to a form service, your CRM or a small serverless function. Newsletter sign-ups connect to Mailchimp or your email tool. Analytics, Tag Manager and consent are installed once in the layout, so every page has them.
Launch day DNS steps
- Lower the TTL on your DNS records a day ahead.
- Deploy the production build and attach your domain on the new host.
- On a call, update the A or CNAME records to the new host. Email (MX) records are not touched.
- Wait for SSL, then test redirects, forms, analytics and the sitemap on the live domain.
- Submit the sitemap in Google Search Console.
- Keep WordPress hosting running for a few weeks, then cancel it.
Monitoring and what can go wrong
We check Search Console daily for the first two weeks and weekly after that, until our 30 days of support end. We look for new 404s, pages leaving the index, and drops in clicks on top pages.
- Forgotten archives or attachments. The crawl finds them before launch.
- Shortcodes leaking into posts. Every post is checked after import.
- Missing SEO fields. Imported from the plugin data, not retyped.
- Redirect pages instead of 301s. Rules set at the host.
- Broken feed. RSS kept at the same path.






