FREEFirst project with us? Your landing page design is on the house.See the offer

Chapter 5 of 6

Fix in place, render on the server, or rebuild

Three paths, a decision table, Webflow vs Astro for the rebuild, and what a rebuild keeps.

6 min readUpdated 2026-11-16
All chaptersChapter 5 of 6
  1. 01What AI builders get right and what they leave out
  2. 02The 20 minute check: can Google and AI assistants read it?
  3. 03SEO basics most AI-built sites miss
  4. 04Speed and phones
  5. 05Fix in place, render on the server, or rebuild
  6. 06Moving to the new site without losing traffic

The short answer

You have three paths. Fix in place when your pages already render as HTML and the gaps are titles, sitemap, images and scripts. Render on the server when the content is good but drawn by JavaScript, and your tool or framework offers server rendering you can switch to. Rebuild when rendering, editing and speed are all problems at once, or when every copy change needs a developer or a new prompt.

For a marketing site, the rebuild is usually in Webflow if your team wants to edit visually and publish without code, or in Astro if you want the most speed and control, with a CMS such as Sanity for editing. Either way, the design you like stays.

Path 1: fix in place

This is the cheapest path, and often enough. It fits when chapter 2 showed your words in the first HTML.

  • Write a title and description for every page, in the first HTML.
  • Add or repair the sitemap, robots.txt and canonical tags.
  • Resize images and set their width and height.
  • Remove extra scripts.
  • Turn button-style navigation into real links.

The risk is drift. Each prompt can undo an earlier fix. Keep a short checklist from chapter 3 and run it after every change. If you find yourself re-fixing the same thing, that is a sign for path 3.

Path 2: render on the server

This fits when the content and design are right but the first HTML is empty. You keep the tool and change how pages are served.

  • Lovable. Its SEO page says new apps already use server rendering, and older React and Vite projects can be upgraded to TanStack Start. Publish again after upgrading, then rerun the chapter 2 test.
  • v0 and other Next.js projects. Check that marketing pages do not fetch their main content in the browser after load. Move that data fetching to the server.
  • Exported React apps. Moving to a framework that renders on the server is real development work. Price it against a rebuild before you start.

Google's JavaScript SEO guide still calls server-side rendering or pre-rendering a great idea, because it makes the site faster for people and crawlers, and because not all bots can run JavaScript. Server rendering fixes the reading problem. It does not fix editing. Your team still changes copy through the tool.

Path 3: rebuild

A rebuild means the pages are built again on a platform made for marketing sites. It is not a redesign: the look stays. What changes:

  • Every page is HTML with the words, links and headings in it.
  • Copy, blog posts, case studies and FAQs move into a CMS your team edits.
  • Titles, descriptions, social images, schema and the sitemap are set per page.
  • Forms, analytics and your CRM are connected again and tested.
  • Every URL that changes gets a 301 redirect (chapter 6).

It costs more up front than a fix. It costs less over a year if your team edits the site often, because nobody has to prompt or code a copy change again.

The decision table

What you foundTeam edits copy often?Best path
Words in first HTML, a few SEO gapsNoFix in place
Words in first HTML, a few SEO gapsYes, and it is painfulRebuild
Empty first HTML, tool offers server renderingNoRender on the server
Empty first HTML, tool offers server renderingYesRebuild, or render now and rebuild later
Empty first HTML, no server rendering optionEitherRebuild
Slow on phones even with good HTMLEitherFix in place first, rebuild if the main scripts cannot go
Site has logins, accounts or saved dataEitherSplit: marketing pages rebuilt, app handled as app work

Decision rule Count how many of these are true: content not in the first HTML, titles set by script, copy changes need a prompt, phone LCP over 2.5 seconds. With one, fix it. With three or more, rebuilding is usually cheaper than patching.

Webflow or Astro for the rebuild

Both publish pages as HTML. Pick by who edits and what the site needs to do.

QuestionWebflowAstro (with a CMS such as Sanity)
Who edits?Marketers, visually, on the pageMarketers in a CMS, developers in code
HostingManaged by WebflowOn your own account with a host of your choice
JavaScriptWebflow's site scripts, plus what you addServer rendering first, with less client-side JavaScript by default
Redirects301 redirects in site settings, on a paid planIn your host's config file
Custom code and dataCustom code embeds, CMS, integrationsAny code, any data source
Best forTeams that want to change pages without a developerTeams that want top speed and full control

If you are unsure, read our Webflow vs Astro comparison and Webflow vs AI site builders. Both are good homes for a site that started in an AI tool.

What a rebuild costs and takes

Our rebuild prices follow our normal prices: a single landing page is $500, and a website of up to 5 pages starts from $2,500. Larger sites start from $3,000. First-time clients get $500 off projects of $2,000 or more. You get a fixed quote before we start, and 30 days of support after launch for safe changes and fixes.

To get a useful quote from anyone, bring:

  • The live URL and the list of pages (your sitemap or a crawl).
  • Your chapter 2 results.
  • Which parts must stay exactly as they are, and which can change.
  • Forms, integrations and tracking that must keep working.
  • Who will edit the site after launch.

See the AI-built site rebuild page for how we run it, or MVP development if your site is really an app.

Takeaways

What to remember from chapter 5.

  • Fix in place when the words are already in the first HTML and the gaps are SEO basics.
  • Render on the server when content is right but drawn by JavaScript and your tool supports it.
  • Rebuild when rendering, editing and speed are all problems, or every copy change needs a prompt.
  • Webflow suits teams that edit visually. Astro suits teams that want top speed and full control.
  • A rebuild keeps the design. It changes how pages are built, edited and served.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.