# Moving a review site from WordPress to Astro: ratings, comments and old URLs

droida.pl, a site with reviews of Android games and apps, moved from WordPress to static Astro. Reviews, ratings, reader votes and comments moved with it.

**Canonical:** https://spoko.space/blog/wordpress-to-astro-migration-droida/  
**Language:** en  
**Published:** 2026-11-18  
**Tags:** WordPress, Astro, migration, Cloudflare Workers, Core Web Vitals  
**Category:** Engineering

---
**[droida.pl](https://droida.pl), a site with reviews of Android games and apps, moved from WordPress to static Astro in 4 days.** It now has 885 reviews and 252 posts. Editor ratings, reader votes and comments moved with them, with their dates and names, and there are 1,734 comments today. 798 of the 810 old URLs work, and the other 12 are mostly pages I chose not to move. In PageSpeed Insights on mobile the review page scores 99 (median of 3 runs); before the migration it scored 45.

In short:

- **A review is more than text.** It has ratings per criterion, reader votes and store links. That data moved as data, not as HTML.
- **The comments stayed on the site.** They moved to my comment system with their dates, names and replies.
- **A URL test against production caught a bug the local test missed.** 154 old image URLs ended in a 404.
- **The site is light.** A review weighs 114 KB instead of 4.4 MB.

I described the method, meaning the list of old URLs, the redirect test and the before-and-after measurement, in the [GSMX blog migration](https://spoko.space/blog/wordpress-to-astro-migration-gsmx/). It is the same here, so I will not repeat it. This article is about what was different on a review site.

## The starting point {#the-starting-point}

WordPress ran on PHP 7.4, which stopped getting security fixes long ago. Reviews were a separate post type from a plugin, and the theme added ratings and Google Play cards to them. There were also a few things that show well what such sites look like after years:

- **Two SEO plugins on at once**, AIOSEO and Yoast, each with its own titles and sitemap.
- **4,747 "author" accounts**, nearly all from automated spam sign-ups, and about 3,800 spam comments in the database.
- **21,179 media files (626 MB)**, of which 4,120 were WebP copies made by plugins next to the originals.
- **No HTML cache.** Every visit built the page in PHP from scratch.

Traffic was low, about 230 sessions a month. As with GSMX, the reason to migrate was not SEO but upkeep: an old PHP version, plugins to update and spam to clean up.

## Reviews are not posts: ratings and reader votes {#reviews-are-not-posts-ratings-and-reader-votes}

A plain post can move as text. A review also has data that the site shows separately, calculates with and passes to Google in structured data. That data moved into fields of every review:

**What every review has**

- **Editor rating** — The average of three criteria. For games: sound, graphics and gameplay. For apps: interface, ease of use and usefulness.
- **Reader votes** — Old WordPress votes merged with new ones into one average. A reader sees one rating, not two.
- **Store links** — A Google Play app card, generated at build time and refreshed every 30 days.

Ratings use a scale of 1 to 10, the same as the comment system where readers vote. I first moved them on a scale of 1 to 5, and on 17 November switched to 1–10: I multiplied every rating by 2, and the comment system converted its votes the same way.

In the `AggregateRating` structured data I count only reader votes, not the editor rating. That is Google's rule for aggregate ratings: they should come from many people, not from the review's author.

## Comments {#comments}

The comments moved to [aqimo](https://aqimo.pl), my comment system, which runs next to the static site. Today there are 1,734 comments on 420 pages under reviews and posts, nearly all of them moved from the old site.

Every comment kept its date, the author's name and its place in the thread. I did not move e-mail or IP addresses, because the new site does not need them. Links to authors' websites stayed only where, after a check, they still led to a working site. aqimo had no import before, so that had to be written first.

Comments and ratings are part of the static HTML, so they work without JavaScript and Google sees them. To get new comments and votes onto the site, a small Cloudflare Worker checks every 6 hours whether anything has arrived. If it has, it rebuilds the site. If not, it does nothing.

## Media in R2 {#media-in-r2}

Of the 626 MB of files, about 346 MB made it to the site: the originals the content actually uses, plus WebP variants in a few widths. The media are not in the repository but in Cloudflare R2 at `media.droida.pl`. That keeps the build fast and the repository small.

Every file got a safe name during the migration: lower case, no Polish letters, `.jpg` instead of `.jpeg`. That tidies the names, but it has a consequence I describe below.

## URLs: 810 old ones and a bug the local test missed {#urls-810-old-ones-and-a-bug-the-local-test-missed}

I took the list of old URLs from the WordPress sitemap: 810 URLs of reviews, posts, categories, tags and images. The redirects live in a `_redirects` file that a script generates. It now has 771 rules, and Cloudflare allows 2,000 static ones.

Before the cutover, the local test showed 794 of 810 URLs working. Five days after the cutover I repeated it against production and got 645. The difference was 154 image URLs, for example:

- old URL: `/img/2011/12/Castle-Of-Shadows-APK-Android-cover.jpg`
- file in R2: `2011/12/castle-of-shadows-apk-android-cover.jpg`

The general `/img/*` rule carried the old name with its capital letters over, and R2 is case-sensitive, so it answered 404. The local test missed it for two reasons. It checked files on a Windows disk, which is not case-sensitive, and since the move to R2 the local media folder was only a partial copy anyway.

The fix: every old image name that changed got its own rule to the new one. The test now checks files against the list of what is actually in R2, not against the disk. One rule with a Polish letter (`Zdjęcie-…png`) still did not work, because Cloudflare compares the encoded URL (`Zdj%C4%99cie`), so the script now writes every path encoded. After both fixes, 798 of 810 URLs work in production.

| URL | Count | Why |
| --- | --: | --- |
| Theme technical pages (login, sign-up, HTML sitemap) | 6 | The new site has no accounts and no such pages |
| Menu entries (`mega_menu`) | 2 | They were not content |
| Google Play plugin icons | 3 | The new app cards have their own icons |
| An image missing even from the WordPress backup | 1 | It cannot be restored |

The lesson is simple: repeat the redirect test against production, not only before the cutover. A file system on a computer and file storage in the cloud can differ in details a local test will not show.

## Speed {#speed}

The same method as on GSMX: the same 5 URLs before and after the migration. Before the migration I ran PageSpeed Insights once per URL, after it three times, and I give the median.

**PageSpeed Insights on mobile: WordPress and Astro**

| Page | Version | Score | Range of runs |
| --- | --- | --- | --- |
| Review | WordPress, 9 Nov | 45 |  |
| Review | Astro, 18 Nov | 99 | 92–100 |
| Home page | WordPress, 9 Nov | 67 |  |
| Home page | Astro, 18 Nov | 99 | 99–99 |
| Post | WordPress, 9 Nov | 70 |  |
| Post | Astro, 18 Nov | 100 | 100–100 |
| Category | WordPress, 9 Nov | 77 |  |
| Category | Astro, 18 Nov | 99 | 99–99 |
| Ranking | WordPress, 9 Nov | 87 |  |
| Ranking | Astro, 18 Nov | 99 | 99–99 |

Higher is better; 100 is the maximum.

On desktop every page scores 100 (median). The review page changed the most:

| | WordPress | Astro |
| --- | --: | --: |
| [LCP](https://spoko.space/glossary/lcp/) on mobile (PageSpeed Insights) | 14.6 s | 1.8–1.9 s |
| [CLS](https://spoko.space/glossary/cls/) on mobile | 0.495 | 0 |
| Page weight | 4.4 MB | 114 KB |
| Requests | 164 | 10 |
| DOM elements | 7,131 | 246 |

Weight, requests and DOM elements come from local Lighthouse (median of 3 runs, 9 and 14 November).

Two notes to read these numbers fairly. First, the WordPress score jumped around: in local measurements over several days the same review page usually scored 50–62, and single runs dropped much lower. The 45 from PageSpeed Insights is a single run. Second, droida.pl has no ads today, so its score is stable. On the [GSMX blog](https://spoko.space/blog/wordpress-to-astro-migration-gsmx/) AdSense ads stayed, and they decide whether the score is 85 or 100.

![PageSpeed Insights for a review on droida.pl after the migration, mobile: performance 99, LCP 1.8 s, Total Blocking Time 70 ms, CLS 0, no real-user data](https://spoko.space/_spoko/droida-astro-psi-recenzja-telefon.H4EN7aMq.webp "The review page after the migration, 18 November 2026")

One thing only showed up when measuring the new site. The home page first had a carousel of the latest reviews, and Lighthouse could not find the largest element in it, so it scored 0. I replaced the carousel with a plain grid of tiles, and the home page scores 99.

## After the migration: apps no longer in the store {#after-the-migration-apps-no-longer-in-the-store}

The oldest reviews are over ten years old, and Google Play has changed a lot since. I checked every Google Play link: of 859 apps, 676 are no longer in the store, mostly those from 2011–2015. The review stays, because it describes a game or app that existed, but the store button is greyed out and leads nowhere. The app cards check Google Play every 30 days, so when an app comes back or disappears, the site shows it after the next build.

## What I did not move {#what-i-did-not-move}

**What stayed in WordPress**

- **Tag pages** — There were over 400 of them. Old tag URLs lead to the list of reviews or to the blog.
- **Accounts and login** — Readers comment and vote in aqimo, so the site needs no accounts of its own.
- **Contact form** — Contact details for the editors are now on the page about the site.
- **PWA app** — Put off for later. The site is fast without it.

## Summary {#summary}

- droida.pl moved from WordPress to static Astro in 4 days, with 885 reviews, 252 posts and 1,734 comments.
- Ratings and reader votes moved as data, and I merged the old votes with new ones into one average.
- A URL test against production caught 154 broken image URLs that the local test missed. 798 of 810 old URLs work.
- PageSpeed Insights on mobile: a median of 99–100 instead of 45–87, and a review weighs 114 KB instead of 4.4 MB.

## Frequently Asked Questions {#faq}

### Can ratings and reader votes survive a move from WordPress to Astro? {#faq-can-ratings-and-reader-votes-survive-a-move-from-wordpress-to-astro}

Yes. On droida.pl the editor ratings moved as data in every review, and I merged the old reader votes with new ones from the comment system into one average. The site shows one reader rating, whether a vote was cast on the old site or the new one.

### What happens to comments when WordPress becomes a static site? {#faq-what-happens-to-comments-when-wordpress-becomes-a-static-site}

The comments moved to <a href="https://aqimo.pl">aqimo</a>, my comment system, with their original dates, names and replies, but without e-mail or IP addresses. They are part of the static HTML, and the site rebuilds when a new comment or vote arrives.

### Why did old image URLs pass the local test but return 404 in production? {#faq-why-did-old-image-urls-pass-the-local-test-but-return-404-in-production}

The migration renamed files to lower case, and Cloudflare R2 is case-sensitive. The local test checked files on a Windows disk, which is not. Only a test against production showed 154 broken URLs. Each one now has a rule to the new name.

### How long did the droida.pl migration take? {#faq-how-long-did-the-droidapl-migration-take}

Four days from analysis to cutover: analysis and the first scripts on 10 November 2026, the domain switch on the evening of 13 November. Fixes and new features went on for a few days after the cutover.


## Sources {#sources}

- [Cloudflare Workers: Static Assets redirects](https://developers.cloudflare.com/workers/static-assets/redirects/) — The _redirects format and its limits: 2,000 static and 100 dynamic rules.
- [Cloudflare R2](https://developers.cloudflare.com/r2/) — The storage that holds the site's media.
- [Cloudflare Workers: Cron Triggers](https://developers.cloudflare.com/workers/configuration/cron-triggers/) — The job that checks every 6 hours for new comments or votes.
- [Google: Review snippet structured data](https://developers.google.com/search/docs/appearance/structured-data/review-snippet) — Rules for AggregateRating and reader ratings.
- [Lighthouse: performance scoring](https://developer.chrome.com/docs/lighthouse/performance/performance-scoring) — Why a single run is not enough for a comparison.
