AI Website Cloning
Migrate any website to Next.js with AI
Give Claude Code or Codex the live URL. It inventories the site, rebuilds the homepage in this starter, and stops for your review before it moves the remaining pages.
Choose your current platformStart with the migration prompt
I want to migrate my website ([YOUR WEBSITE URL]) to Next.js using this starter: https://github.com/Synscribe/launch-template.
Clone the starter into a new folder and open it. Read README.md and AGENTS.md, then run /site-clone with my source URL. Follow the skill and stop at the first review checkpoint.Clone from any platform
Choose the website you are moving from.
Start with the migration prompt on any public site. Open the platform-specific migration when your CMS, forms, localization, or export rules need extra attention.
From URL to Next.js
Move the site in three reviewable stages.
The first checkpoint is a working homepage. Nothing else needs to move until the visual direction and shared structure are right.
- 01
Inspect
Map the website you already have.
The agent records the public routes, visible widgets, assets, navigation, and responsive states before changing anything.
OutputSite inventory
- 02
Clone
Rebuild the homepage in Next.js.
The first route establishes the design system, shared components, and mobile behavior the remaining pages will use.
OutputHomepage preview
- 03
Review
Approve the foundation, then expand.
Compare the preview with the current site. Once it is right, move the remaining routes, integrations, and redirects.
OutputApproved direction
A complete website migration
Move more than the design.
A convincing homepage is the beginning. The remaining work keeps the content findable, the forms useful, and old links pointed at the right destination.
See these details in the Webflow migrationmigration-checklist.md
6 / 6 mapped- 01
Pages and responsive layouts
- 02
Copy, CMS content, and assets
- 03
Forms and integrations
- 04
Motion and interactive behavior
- 05
URLs, metadata, and redirects
- 06
Navigation and discovery files
Before you clone the site
Useful migration answers.
Start from what the agent can inspect, then add platform access and exports when the hidden parts of the site need to move.
01Can AI clone any public website?+
An AI coding agent can inspect and reproduce the pages, content, assets, and visible behavior it can reach. Protected content, private data, and third-party services need explicit access or a replacement plan.
02Do I need the original source code?+
No. A public website is enough to begin a visual and content inventory. Source files, exports, analytics, and platform access make it easier to account for hidden routes, CMS content, redirects, and integrations.
03Will migrating to Next.js preserve SEO?+
The workflow protects the parts you can control: valuable URLs, page copy, metadata, internal links, redirects, canonicals, structured data, and crawl settings. Rankings can still fluctuate while search engines process a site move.
04When should I use a platform-specific migration page?+
Use one when your current platform controls CMS templates, forms, localization, ecommerce, accounts, or animation behavior. The shared prompt gets the visual migration started; the platform page helps account for those dependencies.
Homepage first. Human reviewed.