How ConveyThis Migrated from WordPress to Astro Without Losing Speed or SEO

How ConveyThis moved conveythis.com from WordPress to Astro — 363+ pages, 99 redirects preserved, Lighthouse Performance 99, and Core Web Vitals in the green. The migration story, the results, and what it means for our users.
Get started
Learn more
No card details No commitment
G2 High Performer Spring 2023
G2 Easiest Setup Fall 2024
G2 Best Support Spring 2025

· Alex B · Blog

Summarize this post with: 8 min read
ChatGPT ChatGPT Perplexity Perplexity Grok Grok Google AI Google AI

At a glance: We moved 103 pages, 248 blog posts, 65 Help Center articles, 34 integration pages, and ~111 MB of media from WordPress to Astro. The new site generates 363+ pages in ~54 seconds, preserves 99 legacy redirects, and kept WordPress running for 30 days after cutover as a safety net.

Cartoon-style illustration of the ConveyThis team collaborating on a website migration project. The team plans, builds, and launches a new Astro-powered website within a 30-day deadline, celebrating improved performance, faster load times, and a successful transition from WordPress.

Why we replatformed

ConveyThis helps businesses publish and manage content in 200+ languages — and WordPress remains one of our most widely used platforms. Thousands of customers run ConveyThis on WordPress every day, and we continue to invest in that integration.

Our own marketing site lived on WordPress for years and served us well. As content and traffic grew, we needed faster builds, a lighter front end, and simpler deployments — so we moved conveythis.com to Astro. That was a deliberate platform upgrade for our site, not a cosmetic refresh, and not a statement about WordPress itself.

The migration was judged on four outcomes:

  • Speed — lighter pages and faster repeat loads
  • SEO continuity — URLs, redirects, metadata, and structured data preserved
  • Support usability — Help Center stays familiar, with better search
  • Operational reliability — predictable static builds instead of runtime plugin dependencies

What we migrated

Content typeVolumeWhy it mattered
Core website pages103Pricing, features, industries, use cases, legal — high-intent URLs that must not break
Blog posts248Years of organic traffic, backlinks, and indexed long-tail content
Help Center articles65Setup guides, billing, and translation workflows across four categories
Integration pages34WordPress, Shopify, Webflow, and other platform landing pages
Media library1,511 files (~111 MB)Images and assets referenced across the site
Legacy redirects99Renamed slugs, retired campaigns, and nginx rules from prior years

Build output: 363+ HTML pages in ~54 seconds · Export: May 6–7, 2026 · Fallback: WordPress origin live for 30 days post-cutover

How we ran the migration

Illustrated infographic showing the ConveyThis team migrating from WordPress to Astro, with a four-week timeline from Audit and Export through Build, Test, and Launch.

We treated the move as a controlled production cutover — not a one-click export.

PhaseWhat happened
1. Audit & exportContent inventory, URL map, plugin audit, media export from wp-content/uploads
2. Build & convertAstro setup, content pipelines, layout parity, integration templates
3. ValidateSEO checks, forms, Help search, redirects — 7 days staging soak + 5 days QA
4. CutoverDNS switch with rehearsed rollback; old origin kept as fallback

The guiding rule: visitors and search engines should not feel the platform change — only the performance improvement.

What was hardest — and how we solved it

Most WordPress migrations fail quietly: a missing redirect, blank page body, or broken form. These were our five main challenges and the fixes behind them.

ChallengeWhat we did
Page bodies in custom fields
103 pages; theme/ACF rendering, not the WP editor		enrich-pages-body.js — live-fetched rendered HTML from each published URL
SEO metadata on 313 content URLs
248 blog posts + 65 Help articles		enrich-posts-head.js — captured Rank Math titles, OG tags, and JSON-LD at export
99 redirects + locale URL patterns
Legacy /ar/..., /es/... paths		Migrated explicit rules to Caddy; pattern-based rewrites for language prefixes
Forms on a static site
Contact, enterprise, jobs — WP PHP endpoints		WpFormsBridge.astro + Node sidecar during transition
Help Center search
65 articles; users need fast answers		Same URLs and categories; Pagefind index scoped to KB content

If you are planning a similar move: export your redirect map before cutover, treat metadata and structured data as first-class assets (not just body copy), and list every form POST endpoint before going static. Missing any of these is the fastest way to lose traffic or leads after launch.

The results

Before and after

AreaWordPressAstro
Front endjQuery, Bootstrap, Vue site-wideZero JS by default; interactivity only where needed
DeploysPHP + MySQL; plugin update riskStatic build → rsync in ~54 s
Help CenterKB plugin scriptsSame structure; faster Pagefind search
SEORank Math per requestMetadata and JSON-LD baked at build time

The payoff is a leaner front end and deploys that finish in under a minute — without changing a single customer-facing URL.

Colorful scene of the ConveyThis team celebrating launch day with migration stats on screen and a green All Green status after moving to Astro.

The ConveyThis Help Center still covers the same workflows — same URLs, same four categories:

CategoryArticlesStart here
Getting Started20WordPress · Shopify · JavaScript
Translations Management30Visual editor · Glossary · Import/export
Pricing & Account8Plans, billing, GDPR
Account Management7Team access, DNS, domains

Bookmarks, support links, and in-app references all still work. What improved is load time and on-site search — users reach the right article faster.

Does this affect your ConveyThis setup?

No. ConveyThis connects to your site via plugin, app, or JavaScript snippet — regardless of whether you run WordPress, Astro, Shopify, or Webflow.

If you are replatforming your own site, four things are worth checking:

  1. URL structure — update custom URL rules and exclusions if paths change
  2. Existing translations — export and re-import before switching CMS; no need to start over
  3. Multilingual SEO — preserve hreflang, canonicals, and redirects; see our SEO guide
  4. DOM changes — re-check excluded pages and segments if your HTML structure shifts

Who made it happen

Five people owned distinct slices of a large project. The goal throughout was the same one we hold for customers: big scope, clean execution, nothing broken at cutover.

PersonOwned
Alex B.Product direction — kept the migration anchored to outcomes, not framework novelty
TimInfrastructure, CI/CD, cutover, forms, and the 30-day rollback plan
Kristina103 template pages — including ACF/theme content the database export missed
David248 blog posts — metadata, canonicals, and structured data continuity
Varia65 Help articles — familiar structure, faster KB search

The hardest part was never moving content — it was cutover night. Code can be fixed at 3 a.m.; DNS does not negotiate. We rehearsed rollback until the team could run it without hesitation.

— Tim

What stands out is how this team operated under pressure: ambitious scope, calm execution, and a foundation we are already building the next releases on.

— Alex B.

In platform work, the best compliment is a launch users barely notice. That is exactly what we aimed for.

Migration checklist

Planning a similar move? Work through this before cutover:

  • Full URL inventory — pages, posts, docs, integrations
  • Every 301/302 redirect documented and tested
  • SEO metadata and JSON-LD captured per URL, not just body HTML
  • All form endpoints identified; static-site POST plan in place
  • Media assets mirrored; broken image paths fixed in content
  • Staging soak before DNS switch (we used 7 + 5 days)
  • Old origin kept live as fallback (we used 30 days)
  • Help/docs URLs and search verified post-launch
  • Hreflang and locale URLs validated if the site is multilingual

What comes next

  • Complete form handling on Node and retire the WordPress bridge
  • Decommission the WordPress origin after the fallback window
  • Bring multilingual routing into Astro (some legacy locale patterns remain at the server today)
  • Refine analytics and consent configuration

This roadmap is about conveythis.com — our marketing site — not our product strategy. ConveyThis on WordPress is staying, growing, and remains a first-class integration for the customers who rely on it.

WordPress served ConveyThis well for many years. Astro is the foundation for what we build next.

Useful resources

Go global on a faster site

Whether you are replatforming or staying on your current CMS, ConveyThis adds multilingual pages without rebuilding your stack from scratch.

Start your free trial — setup takes minutes on WordPress, Shopify, Webflow, and 50+ other platforms.

Published June 11, 2026 · ConveyThis

Share: