
URL inventory
Pages show traffic weight, revealing what earns before changes.

WordPress to Astro
Keep every post and URL. Lose the plugin updates and the slow pages. We rebuild your site in Astro, move or connect your content, and set up a workflow your team can run.

Nominated
Products Launched
Before we quote
Raised By Clients

WordPress to Astro
Keep every post and URL. Lose the plugin updates and the slow pages. We rebuild your site in Astro, move or connect your content, and set up a workflow your team can run.

Nominated
300+
Products Launched
Audit first
Before we quote
$1Bn+
Raised By Clients

WordPress to Astro
Keep every post and URL. Lose the plugin updates and the slow pages. We rebuild your site in Astro, move or connect your content, and set up a workflow your team can run.

Nominated
300+
Products Launched
Audit first
Before we quote
$1Bn+
Raised By Clients
To move from WordPress to Astro, we either export your posts into Markdown or a headless CMS, or keep WordPress as a headless CMS behind an Astro front end. Your theme is rebuilt as Astro components, and every URL is kept or redirected. The audit sets the scope, quote and schedule.
The Problem

The rankings go quietly
Redirects were missed, the URL structure did not match, and nobody knew which pages had traffic until they stopped.

You still can't edit it yourself
New platform, same problem. Every page still needs a developer, so nothing changes after launch.

Years of pages nobody will delete
Years of pages no one has authority to delete, and no record of which ones were actually earning anything.
The Problem

The rankings go quietly
Redirects were missed, the URL structure did not match, and nobody knew which pages had traffic until they stopped.

You still can't edit it yourself
New platform, same problem. Every page still needs a developer, so nothing changes after launch.

Years of pages nobody will delete
Years of pages no one has authority to delete, and no record of which ones were actually earning anything.
The Problem

The rankings go quietly
Redirects were missed, the URL structure did not match, and nobody knew which pages had traffic until they stopped.

You still can't edit it yourself
New platform, same problem. Every page still needs a developer, so nothing changes after launch.

Years of pages nobody will delete
Years of pages no one has authority to delete, and no record of which ones were actually earning anything.
The Problem

The rankings go quietly
Redirects were missed, the URL structure did not match, and nobody knew which pages had traffic until they stopped.

You still can't edit it yourself
New platform, same problem. Every page still needs a developer, so nothing changes after launch.

Years of pages nobody will delete
Years of pages no one has authority to delete, and no record of which ones were actually earning anything.
Theme & design
Rebuild your theme as Astro components.
Theme & design
Rebuild your theme as Astro components.
Posts & pages
Move to Markdown or a headless CMS, or keep WordPress headless.
Posts & pages
Move to Markdown or a headless CMS, or keep WordPress headless.
URLs & SEO
Keep permalinks and carry over titles, metas and schema.
URLs & SEO
Keep permalinks and carry over titles, metas and schema.
Forms & tracking
Move forms to a form service and reconnect analytics.
Forms & tracking
Move forms to a form service and reconnect analytics.
Plugins
Replace each plugin with code or a hosted service.
Plugins
Replace each plugin with code or a hosted service.
Commerce & accounts
Scope WooCommerce and members as a separate service.
Commerce & accounts
Scope WooCommerce and members as a separate service.
A good fit
Content-heavy sites with developers who want speed and fewer moving parts.
Consider alternatives
Teams that rely on WooCommerce, memberships or many editors in wp-admin.
Know the limits
Themes, PHP and plugins do not run in Astro. Each feature is rebuilt, replaced or kept in WordPress.
What is included
The audit comes first and its fee comes off the build. Everything below is in the price after that.

Pages show traffic weight, revealing what earns before changes.

Built and signed off before any page moves, then tested against the map.

Astro components in your own repo, with content in a headless CMS or Markdown.

Not copied across as it was. Collections structured for the people who will actually update them, with training before handover.

Rankings, crawl errors and redirect health after go-live. Migrations fail quietly in week three, so somebody should still be looking.
What is included
The audit comes first and its fee comes off the build. Everything below is in the price after that.

URL inventory
Pages show traffic weight, revealing what earns before changes.

The redirect map
Built and signed off before any page moves, then tested against the map.

The new build
Astro components in your own repo, with content in a headless CMS or Markdown.

CMS remodelled around your team
Not copied across as it was. Collections structured for the people who will actually update them, with training before handover.

30 days of monitoring
Rankings, crawl errors and redirect health after go-live. Migrations fail quietly in week three, so somebody should still be looking.
What is included
The audit comes first and its fee comes off the build. Everything below is in the price after that.

URL inventory
Pages show traffic weight, revealing what earns before changes.

The redirect map
Built and signed off before any page moves, then tested against the map.

The new build
Astro components in your own repo, with content in a headless CMS or Markdown.

CMS remodelled around your team
Not copied across as it was. Collections structured for the people who will actually update them, with training before handover.

30 days of monitoring
Rankings, crawl errors and redirect health after go-live. Migrations fail quietly in week three, so somebody should still be looking.
What is included
The audit comes first and its fee comes off the build. Everything below is in the price after that.

URL inventory
Pages show traffic weight, revealing what earns before changes.

The redirect map
Built and signed off before any page moves, then tested against the map.

The new build
Astro components in your own repo, with content in a headless CMS or Markdown.

CMS remodelled around your team
Not copied across as it was. Collections structured for the people who will actually update them, with training before handover.

30 days of monitoring
Rankings, crawl errors and redirect health after go-live. Migrations fail quietly in week three, so somebody should still be looking.



Cost & Timing
Your audit defines the pages, CMS and integrations. You get a clear quote and schedule before the build starts.
Cost & Timing
Your audit defines the pages, CMS and integrations. You get a clear quote and schedule before the build starts.
Cost & Timing
Your audit defines the pages, CMS and integrations. You get a clear quote and schedule before the build starts.
After Launch
We check redirects, forms and tracking, then monitor search signals and train your team. Support duration is agreed in your scope.
After Launch
We check redirects, forms and tracking, then monitor search signals and train your team. Support duration is agreed in your scope.
After Launch
We check redirects, forms and tracking, then monitor search signals and train your team. Support duration is agreed in your scope.
FAQs
We audit every URL, then either export posts into Markdown or a headless CMS, or keep WordPress as a headless CMS. The theme is rebuilt as Astro components and every permalink is kept or redirected.
Yes. Astro can read content from the WordPress REST API, so editors keep wp-admin while the public site is served by Astro. The audit compares this with moving content out completely.
Plugins do not run in Astro. SEO, forms and analytics plugins are replaced with built-in code or hosted services. Anything that cannot be replaced cleanly is flagged in the audit.
We keep your permalinks where possible and redirect any that change. Rankings can move during any migration, and no provider can guarantee them. Monitoring after launch reduces the risk.
Astro is built for content sites. It ships very little JavaScript by default, supports Markdown and headless CMSs natively, and deploys to most hosts.
It depends on post count, custom fields and plugins. The audit sets the scope, and we agree the schedule before the build starts.
FAQs
We audit every URL, then either export posts into Markdown or a headless CMS, or keep WordPress as a headless CMS. The theme is rebuilt as Astro components and every permalink is kept or redirected.
Yes. Astro can read content from the WordPress REST API, so editors keep wp-admin while the public site is served by Astro. The audit compares this with moving content out completely.
Plugins do not run in Astro. SEO, forms and analytics plugins are replaced with built-in code or hosted services. Anything that cannot be replaced cleanly is flagged in the audit.
We keep your permalinks where possible and redirect any that change. Rankings can move during any migration, and no provider can guarantee them. Monitoring after launch reduces the risk.
Astro is built for content sites. It ships very little JavaScript by default, supports Markdown and headless CMSs natively, and deploys to most hosts.
It depends on post count, custom fields and plugins. The audit sets the scope, and we agree the schedule before the build starts.
FAQs
We audit every URL, then either export posts into Markdown or a headless CMS, or keep WordPress as a headless CMS. The theme is rebuilt as Astro components and every permalink is kept or redirected.
Yes. Astro can read content from the WordPress REST API, so editors keep wp-admin while the public site is served by Astro. The audit compares this with moving content out completely.
Plugins do not run in Astro. SEO, forms and analytics plugins are replaced with built-in code or hosted services. Anything that cannot be replaced cleanly is flagged in the audit.
We keep your permalinks where possible and redirect any that change. Rankings can move during any migration, and no provider can guarantee them. Monitoring after launch reduces the risk.
Astro is built for content sites. It ships very little JavaScript by default, supports Markdown and headless CMSs natively, and deploys to most hosts.
It depends on post count, custom fields and plugins. The audit sets the scope, and we agree the schedule before the build starts.
FAQs
We audit every URL, then either export posts into Markdown or a headless CMS, or keep WordPress as a headless CMS. The theme is rebuilt as Astro components and every permalink is kept or redirected.
Yes. Astro can read content from the WordPress REST API, so editors keep wp-admin while the public site is served by Astro. The audit compares this with moving content out completely.
Plugins do not run in Astro. SEO, forms and analytics plugins are replaced with built-in code or hosted services. Anything that cannot be replaced cleanly is flagged in the audit.
We keep your permalinks where possible and redirect any that change. Rankings can move during any migration, and no provider can guarantee them. Monitoring after launch reduces the risk.
Astro is built for content sites. It ships very little JavaScript by default, supports Markdown and headless CMSs natively, and deploys to most hosts.
It depends on post count, custom fields and plugins. The audit sets the scope, and we agree the schedule before the build starts.
Your growth depends on shipping fast, iterating often, and keeping things moving.
Don’t need a call? Email harish@goodspeed.studio
Your growth depends on shipping fast, iterating often, and keeping things moving.
Don’t need a call? Email harish@goodspeed.studio
Your growth depends on shipping fast, iterating often, and keeping things moving.
Don’t need a call? Email harish@goodspeed.studio