For companies whose WordPress site rarely changes. We move it to Astro: a static site built from ready HTML files, with no admin panel, PHP, database or plugins to update, and usually no server fees either. After that, a change is just a message, to an AI assistant in a chat or to us.
Leave your website address. We'll check what it runs on and how often its content changes, then tell you straight whether moving makes sense or WordPress is the better choice.
We'll look it over and get back to you on whether and how to move it.
Urgent? Call us: +48 726 220 596
01What it's about
WordPress assembles every page on the fly: on each visit the server pulls content from the database, runs the theme and plugins, and only then sends the page. Astro does this once, at publishing. It builds ready HTML pages from content stored in files, and the server simply serves them. The page you're reading works exactly like this.
Every page is a ready HTML file, loaded from the server closest to the visitor. There's no PHP, database or login panel on the server, so there's nothing to update and nothing for an attacker to take over.
We rebuild the site your customers know: the same pages, texts, photos and addresses, with a design refresh along the way if you want one. Any address we tidy up gets a 301 redirect, so links from Google, emails and directories keep working.
Texts go into Markdown files in a repository that keeps every version of the site. A Markdown file reads like plain text, so people and AI assistants can both edit it, and any change can be undone. Each page also gets a .md version at the same address, handy for AI assistants.
Example The version of this page for AI assistants: This page in Markdown
There's no admin panel, but changes don't wait for a developer. Describe the change in a chat with an AI assistant connected to the site's repository. The assistant prepares it on a preview site, and a person approves publishing. Or simply write to us.
02When it makes sense
We build plenty of WordPress sites and still think it's a great tool. So before suggesting a move, we look at who changes the content, how often and how they like to do it. Sometimes the better answer is a well-built WordPress site.
When content changes rarely
Services, case studies and contact details, with news every few weeks or less, usually added by one or two people. The site can still change; the change is just described in a chat or an email instead of clicked through in a panel. This is where moving pays off most: a fast site with nothing to update, and no more server bills.
When content changes often
Several people add news and posts every week, build new pages from blocks and want to see changes in the panel straight away. Then WordPress is the right place to stay: well secured, well organised and regularly updated, it works great. We build sites like that every day, on our own theme.
When the site sells or has accounts
A cart, customer accounts, bookings or search across thousands of products need a server. A site like that stays on WordPress or a shop platform, and the company pages next to it can move to Astro. We discuss this separately, for each specific site.
Not sure which case fits your site? Leave the address and after a review we'll tell you straight what makes sense. For a broader comparison of both technologies, see our post WordPress vs Astro.
03Benefits
The site looks the same. What changes is everything behind it: how fast it loads, how much upkeep it needs and what it costs. The numbers come from our own site after we moved it from WordPress to Astro.
Speed
Old themes and plugins add their own scripts and styles to every page. After the move only the code the site actually uses remains, photos switch to lighter formats, and the server doesn't assemble pages on every visit. We measure mobile speed before and after the move.
4 times lighter shared stylesheet on fluostudio.pl after the move: from 1.6 MB to about 400 KB
Security
When a serious hole turns up in PHP or a popular plugin (PHP2Shell in PHP itself, for example), WordPress sites wait for patches, and someone has to install them. A site made of ready files has no PHP, plugins or login panel, so those security warnings don't apply to it.
0 plugins, PHP and databases on the fluostudio.pl server
AI
More and more people ask AI assistants about companies and products. When moving a site we tidy up headings and markup, add structured data and llms.txt, and give every page a Markdown version that AI assistants read more easily. Here's how it looks on our site: each page next to its .md version, the one the assistant reads.
04Starting point
We hear these lines from companies whose site has run on WordPress for years while its content rarely changes. Under each one is what we do about it, with an example from our own website.
A website that needs no updates
WordPress, the theme and every plugin get fixes separately, and someone has to install them and check the site still works. After the move this work disappears: the site is a set of ready files, and the tools that build it don't run on the server, so they get updated calmly with the next round of changes.
What we do
An example from our website
fluostudio.pl
fluostudio.pl ran on WordPress for years. Today it's ready HTML files on Cloudflare's server network, and the forms run as small functions protected against bots.
How we moved fluostudio.plMoving without designing from zero
The move starts from the site you already have, with its design, content and Google traffic. We rebuild it in Astro page by page, and your team is needed mainly for sign-off. Anything you'd like refreshed along the way happens in the same step.
What we do
An example from our website
fluostudio.pl
When moving fluostudio.pl, we took the content, photos and addresses from the old site, so we didn't start from a blank page.
How we moved fluostudio.plThe same addresses and 301 redirects
Before anything changes, we list every address on the site along with its traffic from Search Console. Each old address either stays or gets a 301 redirect to its new place, and titles and descriptions move together with the content. All old addresses are tested before publishing.
What we do
An example from our website
fluostudio.pl
When we moved fluostudio.pl, the old pages stayed at their addresses, and over 140 redirect rules lead from old and retired addresses to the new ones.
How we moved fluostudio.plA light website without unnecessary code
Old themes and plugins load scripts and styles on every page, even where nothing uses them. When moving, we keep only the code the site uses, and save photos and videos in lighter formats.
What we do
Changes in plain words
The content sits in Markdown files that people and AI assistants can both read and edit. A change is described in an email or a chat, the assistant prepares it and shows it on a preview site, and a person approves publishing: your team or ours.
What we do
05Process
Five steps from site review to launch. A typical company website takes 2–3 weeks from accepting the offer, and your team is needed mainly for sign-off.
What it involves
We check how many pages and how much content the site has, which plugins, forms and integrations it uses, and who changes it and how often. We list the addresses and traffic from Search Console, and agree on scope and timing in a short call. If it turns out WordPress is the better choice, we say so right away.
Why it matters
Features that need a server and content that changes daily come out at this stage, before any work starts.
What it involves
Every old address gets a place: the same address after the move, or a 301 redirect. That includes attachments, categories, author pages, RSS feeds and the sitemaps that SEO plugins leave behind.
Why it matters
Links to your site live in Google, emails, directories and partner sites. With the map, every one of them still leads somewhere.
What it involves
We move content from the WordPress database into Markdown files and rebuild the design in Astro from the same photos and typefaces. Forms get small functions protected against bots, the consent banner, Tag Manager and GA4 keep the same events as before, and structured data, llms.txt and .md versions of the pages come on top.
Why it matters
Well-organised content in files is easy to review, compare and change. Every later change builds on it, including those made through an AI assistant.
What it involves
The new version first runs as a preview site at a separate address, visible only to your team and ours. We compare screenshots of every page with the old version, test forms and phones, and collect fixes on one list.
Why it matters
Differences are easiest to catch before launch, before customers see them.
What it involves
We publish the new version with a fallback plan: the old site stays with your hosting provider as a copy until the account is closed, and switching back takes a few minutes. For the first 30 days we keep an eye on Search Console, forms and GA4 events.
Why it matters
Launch is the moment when something can go wrong. With a fallback plan, any mistake can be undone in minutes.
06Our website
We moved our own website from WordPress to Astro: services, case studies, the blog and the glossary. fluostudio.pl now runs on ready HTML files on Cloudflare, with a separate preview site. Forms are handled by small functions protected against bots, and the consent banner, Tag Manager and GA4 have the same events as before the move.
07Changes after the move
No WordPress panel needed. The content sits in files an AI assistant reads as well as a person does, and every change goes through a preview. It's how we update fluostudio.pl today.
In a chat, an email or a ticket, the way you'd write to a colleague. Photos, a data file or a screenshot can go along with it.
An assistant connected to the site's repository finds the right files and makes the change. Each change is a separate version that can be undone at any time.
The change lands on the preview site first, visible only to your team and ours. It looks exactly as it will on the live site.
The change goes live only after approval, from your side or ours, as agreed. Publishing takes a few minutes.
Rather have someone else handle the changes? Under our ongoing care, we make them for you. And if the content starts changing every week, going back to a panel is easy: Markdown files can be imported into WordPress.
08Questions
Astro is a free, open-source site generator. From content in Markdown files and components (the reusable parts of a page) it builds ready HTML, CSS and JavaScript files. The server simply serves them, so it needs no PHP or database. fluostudio.pl runs on Astro today.
Yes. “Static” describes how the server delivers the site, not what's on it. Animations, videos and even 3D scenes work, and forms are handled by small functions protected against bots. Only a cart, customer accounts and bookings need a server.
Describe the change in plain words, in a chat with an AI assistant or in an email to us. It goes to the preview site first, and a person approves publishing: your team or ours. If the content later starts changing often and the team wants a panel to click through, going back to WordPress is possible, since content in Markdown files can be imported into it.
No. Send us the change by email and we'll make it. If your team would rather do it themselves, we connect the site's repository to the AI assistant you already use, agree who approves publishing, and show how to work with it.
We do everything that's in our hands: the same addresses, 301 redirects from the old ones, titles and descriptions moved together with the content, and a test of all old addresses before publishing. In the first weeks we check Search Console daily. We're responsible for correct redirects and indexing. Nobody can honestly guarantee the rankings themselves, because they also depend on competitors and changes at Google.
Yes. Submissions go where they go today, with bot protection and a log of every submission from the last 30 days. The consent banner moves over or gets replaced with a lighter one, and Tag Manager and GA4 get the same events, so reports from before and after the move can be compared.
The domain and email stay where they are and remain yours. We only change the website's DNS records; the email records stay untouched. If the domain sits with your hosting provider together with the site, we help set up the records there or transfer it.
Yes. Until the account with your previous hosting provider is closed, a copy of the site stays there, and switching back means changing one DNS record. Even after that, nothing ties you to us: the content is in Markdown files that can be imported into WordPress or another system.
The content sits in Markdown files in a repository, and Astro builds them into ordinary HTML, CSS and JavaScript files that can be hosted anywhere. We deploy them to a Cloudflare account that belongs to you. The code, content and repository are yours.
We prepare it so assistants can read it properly: clean headings, structured data, llms.txt and a Markdown version of every page. Standards in this area are still taking shape, and nobody can guarantee a place in assistants' answers, so what we promise is order and readability.
Yes, most of them, with a custom theme and no ready-made templates. It's a good choice when content changes often and the team wants to build pages from blocks in the panel themselves. More on the Websites page.
09Other websites
When content changes often or the site needs a new design, a new WordPress site with a panel set up for your team is the better start. That's how we build company websites, online shops, sites with configurators and landing pages.
"*" indicates required fields
Cookies
With your consent, we use Google Analytics and Hotjar to see how people use the site, and Google Ads to measure how well our ads work. Without consent, the site works just the same. You can change your choice at any time under “Cookie settings” in the footer. Details are in our privacy policy.
The fluo_zgoda cookie remembers this choice for 12 months. Cloudflare Turnstile protects the forms from bots.
Plausible counts visits without cookies or personal data, so it works regardless of this choice.
