Webflow to Astro in 10 weeks

A healthier site, structured data generated automatically, and a marketing team that could keep publishing without waiting on design.

Role
Project lead
Company
TeamGantt
Timeline
About 10 weeks
Stack
Astro, Storyblok, Schema.org, SE Ranking
TeamGantt homepage after the Webflow to Astro migration

Context

TeamGantt's marketing site ran on Webflow. Crawl errors, oversized scripts and styles, missing metadata, duplicate titles and orphaned pages had piled up, and structured data covered only some pages. For a SaaS company whose traffic was almost all organic, that mattered.

Constraints

  • About ten weeks, planned and executed.
  • A full visual redesign alongside the migration.
  • Three teams: design, engineering and marketing, plus a tight launch date that forced some items onto a post-launch list.
  • A non-technical marketing team that had to keep publishing.

What I did

I led the project across design, engineering and marketing, and was accountable for the outcome.

I scoped the project and got the marketing team on board. I designed a system that generates valid Schema.org structured data automatically, so marketers never handle schema by hand. I also set up a new publishing model: marketers change content directly in Storyblok, while design and structural changes run through AI agents. After launch I ran the punch list of deferred items as a GitHub Issues backlog.

Outcome

155 to 1crawl errors
79 to 93SEO health score (SE Ranking)
340+ to 0pages with oversized or unminified JavaScript and CSS
Halfthe page weight of the old site
Every pagehas structured data, generated automatically

Launch started clean: no missing meta descriptions (from 48), duplicate titles (from 33), missing H1s (from 34) or orphaned pages (from 98), and an XML sitemap with no redirects or noindexed URLs.

Just as important, marketers no longer depend on design for routine page updates.