The short answer
Before launch, list every URL the old site has, map each one to its new address, and set a permanent 301 redirect for every URL that changes. At launch, publish the new site on the same domain, check the redirects, and submit the new sitemap in Search Console. After launch, watch Search Console for errors and keep the redirects for at least a year.
That is Google's own site move guide in short. It also says to expect temporary changes in rankings while Google recrawls, and that small and medium sites should move all their URLs at once. Our Site Move Playbook covers moves in full detail. This chapter is the short version, with the traps that are special to AI-built sites.
Step 1: list every URL
An AI-built site can have more addresses than you think. Gather them from every source, then remove duplicates.
- The sitemap, if there is one.
- Search Console: the Pages report and the Performance report, which show URLs Google knows about and that get clicks.
- A crawl of the live site. On an older Lovable app, a crawler that is not verified may get the single-page app, so it may find few links. Use the other sources too.
- Analytics: landing pages with visits in the last year.
- Backlinks: pages other sites link to. Our post on keeping backlinks in a migration shows how.
- The tool's preview domain, if it was ever public or shared.
Watch for hash routes such as /#/pricing. Google's JavaScript guide says it may not resolve fragments reliably, and a server never sees the part after #, so you cannot redirect those addresses on the server. If they were shared, a small script on the new home page can send them on.
Step 2: map old to new
Put the list in a sheet with two columns: old path and new path. Send each old URL straight to its closest new page. Google's site move guide says to avoid chains, because each extra hop adds delay.
| Old path | New path | Note |
|---|---|---|
| /pricing | /pricing | Same path. No redirect needed. |
| /blog/post/12 | /blog/planning-treats-for-offsites | New readable slug |
| /about-us | /about | Renamed |
| /old-promo | / | No match. Home only if nothing closer fits. |
Keep paths the same wherever you can. Each path you keep is one less risk. Our free redirect map tool turns your list into a Webflow CSV, a vercel.json file or a _redirects file. Our redirect checker tests them after launch.
Decision rule Point every old URL at the page a visitor would want. Sending everything to the home page throws away what those pages earned.
Step 3: set the redirects
How you add them depends on the new platform.
- Webflow. Webflow's redirects help page says 301 redirects need a paid site plan or a paid workspace plan. It recommends no more than 1,000 rules as good practice, and wildcard rules to keep the count down. Redirects for localized paths need their own rules.
- Webflow CSV import. Its import page warns that a new import overwrites all existing redirects. Export first, add your rows, then import, and publish for the rules to take effect.
- Astro. Set redirects in your host's config, such as vercel.json or a _redirects file, so they are real server redirects.
Test the status code, not the setting. The answer should be 301 or 308, and it should land on the final page in one hop.
Step 4: launch day
| # | Step | Proof it worked |
|---|---|---|
| 1 | Final copy and content on the new site | Latest pages and posts present |
| 2 | Remove noindex and staging passwords from the new site | Source of key pages shows no noindex |
| 3 | Point the domain at the new host | Domain loads the new site on phone data and wifi |
| 4 | Redirects live | Ten old URLs from the sheet each return one 301 to the right page |
| 5 | robots.txt and sitemap live | Both load on the real domain |
| 6 | Search Console verification kept | Property still verified |
| 7 | Submit the new sitemap | Search Console reads it |
| 8 | Forms and tracking | A test lead arrives; a test event shows in analytics |
| 9 | Rerun the chapter 2 test | Hero sentence in view source on three page types |
Google's guide says to verify both the old and new sites in Search Console, including every variant (www, non-www, http, https), and to keep your verification method in place on the new site. If you used an HTML file or meta tag to verify, carry it over. Lovable's docs also say to verify a new custom domain in Search Console again after you change it.
Changing domain too?
Many AI-built sites run on a tool subdomain first, then move to a real domain. If the move also changes the domain, there is one more step. Google's site move guide says the Change of Address tool in Search Console is for moves from one domain or subdomain to another. It is not needed for http to https, www to non-www, or path changes on the same domain.
- Redirect every old domain URL to its match on the new domain, not to the new home page.
- Use the Change of Address tool once the redirects are live.
- Update links you control: social profiles, email signatures, directory listings and ads.
The first weeks after launch
Expect some movement. Google's guide says rankings may change for a while as it recrawls and reindexes. Watch for real problems, not normal noise.
- Day 1 to 3. Check the Pages report for new 404s. Add a redirect for each one that had value.
- Week 1. Inspect your top ten pages with URL Inspection. Each should show your new URL as the Google-selected canonical.
- Week 2 to 4. Compare clicks and impressions per page with the weeks before launch. Look for single pages that dropped, not the total.
- Ongoing. Search Console may warn about redirects in the old sitemap. Google's guide says you can ignore that. Keep redirects for as long as you can, generally at least a year.
Then check what AI assistants can read. Our free AEO checker looks at a page the way an answer tool would. Our post on Search Console quick wins shows what to fix next.


