Websites
Migration to a static site with Astro
Your WordPress, Drupal or Joomla site rebuilt as a static site with Astro: the same addresses, content carried over as is, pages served as plain HTML from a CDN, and nothing left to update at night.
Who it is for
- An end-of-life WordPress, Drupal or Joomla site, slow, demanding security updates nobody applies.
- A company whose site must stay reachable everywhere, including behind networks that block third-party scripts.
- A team that wants to publish without depending on a vendor, with a rollback available at every publication.
What you receive
- Address inventory and redirect plan: every page receiving traffic or links keeps its address or is redirected with a 301.
- Content extracted and reproduced as is, checked page by page; design kept or improved, template by template.
- Static Astro site: single templates, pages that do not build if a title, a description or a canonical is missing.
- Images converted and resized at build time, self-hosted fonts, no third-party script that is not essential.
- Publishing chain: Git repository, preview before going live, automatic checks (dead links, sitemap, addresses), rollback in one command.
- Acceptance by crawl diff before and after, switch monitored for fourteen days, training.
How it goes
01
Inventory
Crawl of the current site, Search Console, list of pages not to break: the address contract is written before building.
02
Build
Content extraction, Astro templates, redirects, on a pre-production you visit.
03
Acceptance
Crawl diff page by page, address matrix, content fidelity check.
04
Switch
Go-live, redirects active, fourteen days of monitoring; the old site stays ready to come back.
Why Astro
HTML, not an application
Astro generates pages at build time and sends no JavaScript by default. The browser receives HTML and CSS: nothing to execute before displaying, nothing to attack on the server side.
Islands where needed
A form, a map, a calculator: only that component carries its code, loaded when it becomes visible. The rest of the page stays inert and fast.
Content under control
Content is validated by a schema: a page without a title, a description or a canonical does not build. What used to be checked by hand becomes impossible to forget.
No server to administer
The site is a folder of files served by a CDN: no database, no PHP, no plugin to patch. It deploys wherever you want, including on your current host.
Publishing is merging
Every change goes through a preview and automatic checks before going live, and every version stays restorable. Publishing an article in six months needs neither a local tool nor a vendor.
A CMS when you need one
Astro reads content from wherever it lives: Markdown files in the repository, or a headless CMS like Sanity for a team editing daily, with live preview and automatic rebuild at every publication.
What we have already done
This site is built that way, and so is our real-estate site, with Astro, across six languages and more than 3,000 addresses. Measurement of 3 September 2026 on this site’s home page, Lighthouse 12 in simulated mobile: 0 ms of main-thread blocking and 322 KB loaded in total. A Drupal 7 to Astro migration of 233 addresses, with accessibility from China and unchanged addresses, is under way for a Shanghai agency.
What it costs to run
A static site costs its hosting, often a few euros a month, and no licence. With Sanity, the free plan covers up to 20 users and the Growth plan costs $15 per user per month (prices checked on 3 September 2026).
Frequently asked questions
Will my rankings survive?
It is the first risk, and it is handled before building: address inventory, list of pages not to break, redirects set before the switch, crawl diff after. An address lost without a redirect is destroyed traffic: we do not switch until the matrix is green.
Can I still edit my site myself?
Yes. Either in the files, with an automatic preview and training, or in a headless CMS like Sanity, with visual editing and one-click publishing. The choice is made at scoping, depending on who publishes and how often.
Why Astro rather than Next.js or WordPress?
Because a content site does not need an application: Astro produces HTML, sends JavaScript only where a component needs it, and reads content from any source. We have used it on our own sites since 2025: a choice proven in operation, not a fashion preference.
What if my site must stay reachable from China?
A static site without third-party scripts is far more robust there: local fonts, no call to Google, deployment possible on the current host behind your CDN. That is the case of the migration under way for a Shanghai agency.