Education publisher · Malaysia · 2025

Seventeen years of archive, moved whole.

A parenting resource with posts going back to 2008, and the old ones still earning search traffic. The replatform had to keep all of it.

A woman reading a long article on a tablet at a kitchen table in the morning
Archive moved

Every year since 2008 came across

17 years
Old URLs

A redirect per address, not a wildcard

One by one
Booking

Google Calendar in the template

On the article
Hands picking a time slot on a phone booking screen

The problem

An education publisher built around one author's expertise, with a blog archive running from 2008 to today. That archive was the asset: old posts still answered the questions parents type at night, and a careless migration would have dropped their addresses and the traffic with them. The site itself had aged past the point where the content was comfortable to read on a phone.

What we did

A full WordPress redesign and rebuild, then the migration: the entire post archive brought across, a redirect written for every old URL rather than a wildcard rule, images relinked in the body instead of left pointing at the old host, categories collapsed into topics a parent would recognise, and Google Calendar booking built into the template so a consultation is one tap from the article that prompted it.

The result

The archive came across whole and the old addresses still resolve, so the search traffic the site had earned over seventeen years survived the replatform. Booking sits on the page that answers the question, instead of two clicks away on a contact form.

Inside the work
01The archive by year, as a shape. We show relative volume rather than a post count, because the count is not ours to publish unverified.
03Booking on the page that earned the visit. The archive brings a parent in; making them hunt for a contact form after that is the leak.
02A redirect written per URL. A catch-all rule sends seventeen years of specific pages to a homepage that answers none of them, and the traffic goes with it.
04The checklist we worked through. The last line, crawling the old sitemap after launch, is the one people skip and the only one that proves the rest worked.

Diagrams we drew from the measurement report, on a plain document background. No screenshots of the live site, and no client named: this was delivered white-label for another agency, so the name is not ours to share.

How the method ran
01Find

Read what the archive was actually doing: which old posts still pulled traffic, and on what addresses.

02Point

Decided the migration was the project and the redesign was the easy half, then wrote the URL map before any design.

03Build

Rebuilt the site, moved the archive whole, redirected every address, and put booking in the template.

04Prove

Crawled the old sitemap after launch and checked each entry resolves to the post it should.

Want the same numbers on your own site?

Thirty minutes, no pitch. You give us the URL when you book, we run your PageSpeed score and the AI visibility test before we speak, and you keep the findings. This case stays unnamed: it was freelance work for another agency, so the name is not ours to give.