Should you rebuild?
Rebuild when the platform is the problem: pages that load in 4+ seconds, an Elementor build nobody can safely edit, plugin conflicts, a mobile PageSpeed score in the 40s. Don't rebuild to change colours — that's a redesign, and you can do it on the current stack.
WordPress hosting + premium plugins + maintenance for a serious business site runs roughly USD 3,000–12,000/year. A Next.js/Astro site on a modern host is USD 0–240/year with no plugin overhead. And moving mobile PageSpeed from ~45 to ~95 typically tracks a 15–40% lift in organic visibility over 3–6 months.
What a rebuild costs in 2026
| Scope | Cost | Timeline |
|---|---|---|
| Simple site (brochure, blog) | from ~USD 2,000 | 2–6 weeks |
| Content site with custom layouts | USD 10,000–25,000 | 6–12 weeks |
| WooCommerce / complex functionality | USD 10,000–50,000+ | 6 weeks–6 months |
| DIY (your time) | hosting only, USD 0–240/yr | weeks of your evenings |
The single biggest cost driver is template count. A 50-page site with 22 unique Elementor layouts is 22 React components to design, build and test — not 50 pages of content to paste. Audit your layouts before you price anything.
The 7-step framework
- 1. Inventory — every URL, every unique layout, every form and integration. This is the real scope.
- 2. Decide the stack — Next.js or Astro for the front end; keep WordPress headless as the editor, or move to Sanity/Contentful/Strapi. Don't rebuild the CMS if the team is happy in WordPress.
- 3. Rebuild layouts as components — one per unique template, not per page. Content flows in from the CMS.
- 4. Migrate content — export, transform, import. Images to a CDN or the new host's asset pipeline.
- 5. Map redirects — every old URL to its new equivalent, 301. This is where SEO is won or lost.
- 6. Cut over — deploy, switch DNS, keep the old site reachable on a subdomain for a week as a reference.
- 7. Monitor — Search Console coverage, Core Web Vitals, 404s. Fix redirects for a month.
Migrate without losing your SEO
- 301-redirect every old URL — including trailing-slash and case variants — to the new one.
- Keep titles, meta descriptions and canonical tags identical unless you're deliberately improving them.
- Own the sitemap: generate it from the new site and submit it in Search Console on cutover day.
- Preserve structured data (Article, Product, Breadcrumb, Organization).
- Expect a small ranking dip for 1–3 weeks while Google recrawls; a clean migration recovers within weeks.
- Do not change the URL structure and the platform in the same release if you can avoid it.
Case study: rebuilding startdigitalnomad.com
This site is itself a rebuild in progress: legacy PHP content and an old theme, moved onto Next.js (App Router) with the historical database kept as the source of truth and articles rendered server-side. The lessons — redirect discipline, keeping the editor familiar, cutting force-dynamic pages over to ISR — are being written up here as they land.
DIY if you can code and the site is simple — the hosting savings alone pay back the evenings. Delegate if the site earns money and downtime or a botched redirect map would cost more than the fee. The grid: (site revenue) × (risk of getting it wrong) vs (agency cost).
- Next.js or Astro?
- Astro if the site is mostly content and marketing pages — simpler, ships less JavaScript. Next.js if you have app-like interactivity, auth, or a dashboard.
- Keep WordPress or move CMS?
- Keep it headless if the team writes in it happily — you get a fast front end without retraining anyone. Move only if WordPress itself is the pain.
- How long will rankings take to recover?
- A clean migration with full redirects: 1–3 weeks of wobble, back to baseline within a few weeks, then the speed gains compound over 3–6 months.
- Cheapest way to rebuild?
- DIY on Astro/Next.js with a static host and headless WordPress. Real cost is your time; cash cost approaches zero.