

Migrating a review site to Astro
A review site from WordPress to Astro: ratings, reader votes, comments and old URLs, in 4 days.
Move the website you already have to Astro and a CMS built around your business.
Your content, your URLs and years of SEO work come with it.
The problem
None of this is an argument against WordPress. It is what one particular installation turns into after a few years of adding to it.
Each one solved something real on the day it was installed. Together they are what you now update, test and hope nothing breaks.
The theme, the page builder and their libraries load on every page, whether that page uses them or not.
Core, theme and plugin updates arrive when they arrive, and each one is a small risk somebody has to carry.
The admin covers everything the web can be, which is why it rarely fits the handful of things your team actually does.
Key promise
The expensive version of leaving WordPress is the one where everything starts at a blank screen: the text is rewritten, the images are re-uploaded, the URLs change and the site spends six months earning back what it already had.
Start with the website you already have. Your pages, posts, images and addresses are the input, not a thing to be recreated later. What changes is what sits underneath them.
Keep what matters. Replace what doesn't. The content, the structure and the addresses stay. The plugin stack, the page builder and the theme are what get left behind — and I don't migrate complexity: anything rebuilt is rebuilt because it earns its place.
What a visitor reads stays the same. What the browser downloads, and what you maintain, does not.
A stack where each layer depends on the one under it.
A static front end and a content model that belongs to you.
Scope
Content preserved. URLs mapped. Functionality rebuilt.
Pages, posts, categories and tags, with their structure — headings, lists, tables and embeds intact.
The image library, re-encoded to modern formats and sized for the layouts that use it.
Titles, descriptions, canonical tags, structured data and the sitemap, plus a redirect for every address that changes.
Forms, search, filtering, galleries and member-only areas — rebuilt as part of the site rather than bolted on.
Analytics, tag manager and consent, reconnected and verified against the events you already report on.
Newsletter, CRM, booking, payments — whatever the site talks to keeps talking to it.
SEO
Nobody can promise a migration with no movement in the rankings, and anyone who does is selling you something. What can be done is to remove the reasons a migration usually causes it — almost always the same handful, and all of them avoidable with a plan made before anything moves.
The mapping is written first, checked against the live site, and verified again after launch against Search Console and the server logs.
Every address on the current site is listed and matched to its new one before the rebuild starts.
Anything that does move is redirected permanently, so links and rankings follow it.
Titles and descriptions come across as they are, unless a page is being rewritten anyway.
One canonical address per page, so the two versions of a site never compete during the switch.
Regenerated from the new site and submitted, rather than carried over by hand.
Article, breadcrumb, product and FAQ markup rebuilt from the content itself.
Rewritten to their new targets, so the migration does not leave the site linking to its own redirects.
Staging stays closed to crawlers, production opens on launch day — checked, not assumed.
Custom CMS
A general-purpose admin panel has to be ready for every website there has ever been. Yours has to be good at the five things your team does every week — publishing a post, swapping a photo, changing a price, adding a case study, updating a page in two languages.
This is not a product mock-up: the screenshots are a CMS I built and run for client sites, with a block-based page builder, translations, media and deployments in one place. See how it is put together.
The fields your content actually has, and no settings page anyone has to be told to ignore.
Content stored as data rather than as markup, so it can be reused, translated and rendered anywhere.
Roles, review and publishing that match how your team already works, not the other way round.
The same content, reachable by AI tooling over MCP under the same permissions as the panel itself.
Which one fits depends on how much of the current site you want to keep. Every path is quoted after the assessment.
The site you have, on a new foundation. The visual design stays; everything under it changes.
The move and the redesign you have been postponing, done in one pass instead of two projects.
For sites that are doing real work: shops, member areas, multilingual content, integrations.
Process
Nothing moves until the map exists, and nothing launches until the new site has been checked against the old one.
Audit
What the site is made of: pages and their addresses, plugins and what each one is load-bearing for, content structure, integrations, traffic.
Plan
The URL map, the content model, what gets rebuilt and what gets dropped — written down and agreed before any code is written.
Rebuild
The new front end in Astro and the CMS around your content model, on a staging domain closed to crawlers.
Migrate & verify
Content and media moved, redirects in place, then the new site checked page by page against the old one.
Launch
DNS switched, sitemap submitted, redirects and indexing watched in Search Console for the weeks that follow.
Start here
Send me your website. I'll look at the current WordPress setup and tell you what moving to Astro would actually involve — including the case where the honest answer is that it isn't worth it yet.
No sales deck. No generic audit. Just a practical look at your website.
What the site loads today, and how much of it is the stack rather than the content.
What is installed, what is load-bearing, and what would need rebuilding.
How the content is stored now, and what it would look like as structured data.
Addresses, metadata and structured data — what has to be mapped before anything moves.
Forms, search, shop, logins, integrations: what the site does beyond publishing pages.
Which of the three paths fits, roughly how long it takes, and what it would cost.
The website address is the only thing I really need — everything else I can read from the site itself.
Case study
A hobby blog about the VW Polo has had its articles in WordPress from the start, and since March 2023 readers get static HTML built with Astro. See the full case study.
Read from the WordPress REST API in the browser, posted through the site's own endpoint.
Measured on the live site, compressed, plus ~53 KB of JavaScript shared across the whole site.
WordPress as the CMS
From day one. Articles, photos and addresses live in the CMS, not in a theme.
A Vue 2 front end
An app in the browser fetched each article from the WordPress API.
March 2023: Astro
Static HTML from the same content. The author's panel did not change.
Today: Astro 7
Five major framework versions, taken as ordinary upgrades, with no rewrite.
Performance
WordPress assembles a page on every visit. A static page is built when you publish, so the server hands over a finished file. This is what that changed on two sites I moved; how I measured is in the write-ups on moving a review site and a blog.
+212%
Pages in Google's index
169 to 527
+54 pts
PageSpeed score
45 to 99
−88%
Time to main content (LCP)
14.6 s to 1.8 s
−97%
Page weight
4.4 MB to 114 KB
−94%
Requests
164 to 10
Pages in the index: Google Search Console, 13 November 2026 (the day of the switch) and 16 November 2026. The rest is one review page on mobile. PageSpeed Insights: WordPress on 9 November, a single run; Astro on 18 November, the median of 3 runs. Weight and requests: Lighthouse, median of 3 runs.


A review site from WordPress to Astro: ratings, reader votes, comments and old URLs, in 4 days.

Droida.pl, a site reviewing Android games and apps, grown over the years: from Foundation 5 and a custom CMS, via WordPress, to Astro.


WordPress → static Astro without losing a URL. Same posts and ads, 2,299 URLs without a miss, faster.

Polo.blue, a bilingual blog about the VW Polo: repairs, mods and part numbers. Headless WordPress for writing, a static site in Astro.
FAQ
No. The faithful migration path rebuilds the design you have, so the change is invisible to visitors and the site simply stops running on WordPress. A redesign is worth folding in when you were going to do one anyway — doing both at once costs less than doing them a year apart.
It moves. Pages, posts, categories, tags and the media library are exported from WordPress and imported into the new content model, with their structure intact. Nothing is retyped, and nothing depends on you copying and pasting it.
Each one gets looked at during the audit and lands in one of three buckets: rebuilt as part of the site (forms, search, galleries), replaced by something the platform does natively (caching, image optimisation, sitemaps), or dropped because nothing on the site still uses it. I don't migrate complexity.
Yes — that is what the CMS is for. The difference is that it holds the things your site actually has, so editing a page means filling in fields rather than fighting a page builder. If your team is comfortable in the WordPress admin, keeping WordPress as a headless CMS is also an option.
Any migration carries risk, and nobody can honestly promise rankings hold. What I can do is remove the usual causes: every address mapped before the rebuild, 301 redirects for anything that moves, metadata and structured data carried over, sitemap resubmitted, and Search Console watched after launch so anything that does slip is caught in days rather than months.
Yes. Languages are part of the content model rather than a plugin, so each language has its own addresses, its own sitemap entries and hreflang tags linking the versions. This site runs the same way, in English and Polish.
You can. In a headless setup your team keeps the WordPress admin it knows and the front end is rebuilt in Astro, reading content over the REST API. It is a smaller change and a good fit when the admin is not the problem — the frontend is. That path is covered on the WordPress Rescue page.
It depends on how much the site does, which is exactly what the assessment establishes. A brochure site with a few dozen pages is a different project from a shop with member accounts, and I would rather tell you which one you have before either of us commits to a date.
The new site has been running on a staging domain and checked page by page before that day arrives. Launch is a DNS switch, the sitemap submitted, and the redirects verified against the live site. If something is wrong, the old site is still there to switch back to.
Tell me in a few sentences what you need. I'll reply within 24 hours.
Free quote · no obligation

I learn your business, customers and goals. We set scope and timeline.
I prepare a mockup you approve before implementation.
I code the site, test it across devices and apply your feedback.
Domain, SSL, hosting — and I'm available after launch too.