Skip to content
SiteBienfait
Free website check
Guides · Migration

WordPress to Astro: what changes

By Ismael · Reviewed

Moving from WordPress to Astro changes how pages are produced, not what a search engine is allowed to index. SiteBienfait treats the platform swap as a URL and content migration first. Google Search Central, updated 2026-03-04, documents that Googlebot queues pages for crawling and for rendering, so a statically generated HTML page removes one dependency from that pipeline.

What changes when WordPress is replaced with Astro?

WordPress assembles each page when it is requested, using PHP, a database and whatever plugins are active. Astro builds every page ahead of time into static HTML. The database leaves the delivery path, which removes a class of failures: a database outage, an exhausted PHP process or a plugin update cannot take a static page down.

The editorial experience changes with it. Posts and pages live in markdown or in a headless content source, and a publish is a build rather than a database write. That is a workflow change the site owner feels on day one, so it belongs in the migration plan, not in a footnote.

What breaks first in the move?

URLs, media paths, forms and the sitemap are the usual failures. WordPress permalinks are easy to preserve for pages and posts, but category archives, tag archives, author archives, feeds and pagination are generated by the platform and often disappear without a decision. Media URLs change when the uploads directory is restructured.

Google Search Central, updated 2026-08-20, frames the fix: prepare a mapping from current URLs to their new destinations before configuring redirects, and keep it reviewed. A plugin-generated sitemap also has to be replaced by a generated one, then resubmitted, per Google Search Central’s sitemap guidance updated 2026-07-08.

Which URLs must be preserved?

Every URL with links or impressions deserves a destination. That is the honest threshold. Start with the pages that appear in the XML sitemap and the pages that earned clicks or links in the previous year, then decide for each one whether it is kept, moved, merged or removed.

When the CMS changes and the layout changes at the same time, the audit gets harder. Google Search Central, updated 2026-08-20, advises splitting a move into smaller steps and changing one thing at a time, precisely because a combined change makes it impossible to tell which change caused a fluctuation.

What needs checking in the new build?

Titles, descriptions, canonicals, sitemap entries, structured data and internal links. Static output makes these inspectable before launch: open the built HTML and read the tag, instead of trusting a plugin. Google Search Central, updated 2026-07-10, recommends a self-referencing canonical that names the final URL.

Also check what the old site rendered with JavaScript or through plugins: sliders, embeds, booking widgets, chat scripts. Each becomes a deliberate choice — a component, an iframe or a removed feature — rather than something that silently stops working.

What is the sequence that keeps search stable?

Freeze the URL list, build the redirect map, build the new site on the same paths where possible, verify the tags in the built HTML, launch, then monitor both old and new URLs in Search Console. Keep the redirects in place for at least a year, as Google Search Central states in guidance updated 2026-08-20.

Search Console settings survive the platform change because they belong to the verified property, not to WordPress. The work is to re-verify the variants, submit the new sitemap and confirm the redirects resolve to the intended pages.

SiteBienfait’s migration route runs the WordPress-to-static move as a sequence of approved change sets, with the URL contract checked before deployment. The redirect map checker is a fast way to compare the old permalink list with the new route list before any redirect rule is written. The method for the map itself is in building a 301 redirect map from a crawl.

Sources

Questions

01 Does moving from WordPress to Astro change the URLs?

It does not have to. A path can be preserved when the new build keeps the same permalinks. When the information architecture changes, the move becomes a site move with a redirect map, which Google Search Central covers in guidance updated 2026-08-20.

02 Does Google still render JavaScript on an Astro site?

Google Search runs JavaScript with an evergreen version of Chromium, according to Google Search Central's JavaScript guidance updated 2026-03-04. Static Astro pages reduce the dependency on that rendering step because the HTML arrives complete.

03 What replaces WordPress plugins?

Most plugins become build-time code, a third-party embed or a small service. Forms, search, comments and analytics need a decision before the move, because each one previously ran inside the old platform.

All guides