How to migrate your website to Framer with MCP

Learn how to move your content, SEO metadata, redirects, and pages to Framer with MCP, then audit the site before launch.

Framer MCP connects an external AI tool to your Framer project so its agent can help rebuild pages and move CMS content. For a full-site migration, move your content and SEO metadata first, then set up redirects and a design system. After that, migrate your pages one by one and audit accessibility and SEO before launch.


1. Inventory your existing site

Create a spreadsheet of every page and its current URL, including CMS, localized, campaign, and utility pages. Mark each one to keep, rebuild, merge, redirect, or remove. Record the destination URL, owner, and review status. Export your sitemap and existing redirects as starting points, then check analytics and backlinks for important URLs that may be missing.

  • List CMS collections, fields, item counts, slugs, categories, references, and localized content.

  • Save original images, videos, files, fonts, and brand assets you have permission to use.

  • Document forms, analytics, consent tools, search, embeds, custom code, integrations, and any functionality that needs a separate solution.

  • Record page titles, descriptions, social images, canonical URLs, and indexing settings before making changes.

2. Prepare your project and connect MCP

Create a Framer project and connect a supported AI tool, such as Claude, Codex, or Cursor, using the Framer MCP setup guide. Sign in and approve the connection. If your source platform offers MCP access, you can also connect it with read-only permissions so the agent can inspect available content and fields.

In the full-site guide, copy the full-site and single-page migration skills into your AI tool. Save them if your tool supports skills, or keep the instructions in the same chat. Ask the agent to confirm it can read them.

Give the agent your source site URL, Framer project link, the pages and languages in scope, and any assets or design rules. Ask it to work on a branch if your plan supports it, check that your content fits your plan limits, and report what it completed, couldn’t verify, or needs a person to finish.

Before the agent builds anything, ask it to crawl your site and report the page count, the collections, and a migration plan. Each page it migrates uses tokens, so agree on the scope first.

The migration prompt in the full-site guide runs steps 3 to 7 in one go, in its own order. For more control, give the agent one step at a time instead. Either way, use the steps below to check its work.

Learn how to use Framer MCP

Connect your AI tool to Framer MCP

Open the full-site migration guide for the skills and prompts

3. Move and verify CMS content

Give your agent the collection names, fields, relationships, and source URLs. Ask it to create the collections and move content through the available tools, preserving slugs and full article bodies. Import referenced collections first where needed. CSV or another supported import workflow can fill gaps the agent cannot access. Map rich text, images, dates, references, localized content, and SEO fields before building detail pages.

A CMS prompt can look like this:

Migrate the CMS from [source URL] to Framer. Collections, in this order: [Authors, Categories, Posts]. Include every field, image, and the full article content as clean HTML. Keep slugs and URL paths exactly as they are. Add SEO Title, Meta Description, and OG Image fields to each collection. When you’re done, audit against the live site and list anything missing or incomplete.

Compare item counts and spot-check entries in every collection against the source. Check full article bodies, formatting, images, links, relationships, slugs, and localized content. List missing or unsupported content and transfer it separately. Connect collection lists and detail pages to the imported fields rather than typing content into the canvas.

4. Move your SEO metadata

Ask the agent to crawl your sitemap and collect the title, meta description, and social image of every page. Keep them exactly as they are on launch day to protect your search rankings. If you want to rewrite them, do it after the new site has settled.

For CMS pages, add SEO Title, Meta Description, and OG Image fields to each collection, ask the agent to fill them from the source, and bind them in the detail page settings. For static pages, keep the list and add each title and description in the page settings when you build the page. Transfer canonical settings and indexing rules the same way.

5. Set up redirects

Keep existing paths where practical. For each changed or removed URL, map the old path to the closest relevant destination and set a permanent redirect in Site Settings. Avoid redirect chains and test the final destination. If the domain itself changes, arrange the old domain redirect with its hosting provider.

Export the redirects your current platform already has and import them too, so older links keep working. If your CMS URLs change pattern, for example from /2024/05/post-name to /blog/post-name, ask the agent to add the redirects to your project, or to build a CSV of old and new paths that you can bulk import. Then ask it to compare every URL in your sitemap with the Framer project and list the ones that still need a page or a redirect.

Learn how to bulk import redirects

6. Set up your design system

With content and metadata in place, set up colors, fonts, text styles, spacing, and reusable components. Once the design system exists, Framer’s in-app agent and your external agent can both build pages from it quickly, and your pages stay consistent.

From this step on, you can work in Framer’s in-app agent. Add the single-page migration skill to your project’s skills so it follows the same instructions as your external agent. Give it your styles as a Markdown file extracted by your external agent, or let the skill pull them from your homepage and a few key pages. Turn repeated elements, such as buttons, cards, and legal disclaimers, into components.

7. Migrate your pages one by one

Run the single-page migration skill on your homepage first, in Framer’s in-app agent or your external tool. It creates the page template, navigation, and footer that your other pages reuse. Then migrate your static pages in small groups, and add each page’s title and description from your step 4 list as you go. Your CMS content is already in place, so for CMS detail pages you only use the skill to match the design and bind the fields.

Review one page at a time with the polish prompt from the full-site guide. Start with the homepage, one page per layout, and a CMS detail page, and ask the agent to apply shared fixes across the site. Compare each page with the source at desktop, tablet, and phone sizes, check that it reuses your components, and open menus, tabs, carousels, and overlays to check their hidden states.

Reconnect forms, analytics, consent, and third-party services. Test custom code and integrations in the environment and domain where they will run. Some features may need a different implementation or an external service, so sort those out before you set a launch date.

8. Build in accessibility and score your site

Framer has the settings you need to make your site accessible. Add alt text in each image’s settings, set heading levels on your text, add ARIA labels to icon-only buttons and links, and keep focus states visible. Then ask your agent to audit your staging site against WCAG 2.2 AA, fix what it can, and re-check every page and CMS template for:

  • Alt text on all images and logos

  • One H1 per page and a correct heading order

  • Color contrast between text and backgrounds

  • Labels on icon-only links and buttons, such as social icons, arrows, and close buttons

  • Keyboard access, including tab order, focus states, and closing modals with Esc

  • Form labels and error messages

Next, ask the agent for a technical SEO audit against your current site. Have it check that titles and descriptions are unique and match the original, every page has an OG image, canonical tags are correct, no internal links are broken or still point to your old platform, the sitemap includes every page, and only intended pages use noindex.

Ask Claude or your agent to score each page for accessibility and SEO, list the issues by page, and fix them. Re-score until nothing is left. Then run your key pages through the AEO scanner to see how AI search reads them, and fix what it flags. Automated scores miss things, so also tab through your key pages with only a keyboard, try a screen reader on one page, and review the flagged pages yourself.

Read the guide to web accessibility in Framer

Improve accessibility with ARIA labels

Read the guide to SEO features and tools

Test your pages with the Framer AEO scanner

9. Test before launch

  • Compare important pages and representative CMS items with the original. Check copy, images, links, responsive layouts, and interactive states.

  • Test forms, confirmations, integrations, consent, analytics, downloads, and custom code.

  • Recheck any accessibility issues from step 8 on the published staging site.

  • Test old URLs and redirect destinations, the 404 page, metadata, canonicals, sitemap, and indexing settings.

  • Have a site owner review the result and keep a list of unresolved issues and their owners.

10. Publish and monitor

When the site is ready, connect your domain and follow Framer’s domain setup instructions. Coordinate the DNS change with whoever manages your domain, and keep your existing site and backups available during the transition. Verify the live domain, key pages, forms, integrations, and redirects after publishing.

Submit or check the sitemap in your search tools, monitor indexing, traffic, errors, and form submissions, and fix issues as they appear. Search engines may take time to reflect a migration.

Can I migrate gradually?

Yes. If you need to move sections in stages, Framer can serve selected pages while the remaining pages stay on your existing site using a rewrite setup. Review the requirements and test the setup before changing your domain.

Read the page-by-page migration guide

Tips for working with an agent

Give the agent the source URL, screenshots, and the exact pages or collections for each batch. Ask it to reuse your styles and components, keep existing copy and URLs, and list anything it couldn’t access or reproduce. Start a new chat when the context gets long. In Framer’s in-app agent, you can also select a section to focus it.

After each batch, compare the result with the original yourself. Open hidden carousel slides and menus, confirm that CMS content is bound to fields, and click through images and links. Treat the agent’s completion report as the start of your review.

Follow the full-site migration workflow with an AI agent

FAQ

Do I need access to my current website’s backend?

Not necessarily. An agent can inspect public pages, but backend access helps you export CMS content, assets, and redirects. The agent may not be able to see drafts, private content, or every CMS field. Review its report and provide any missing exports or assets.

Will the agent move everything automatically?

The agent can help rebuild pages and move content using the tools it can access. Some interactions, integrations, assets, and account connections may need manual work. Compare the result with your existing site and test it before launch.

Do I need redirects for every page?

No. If a page keeps the same URL on the same domain, it does not need a redirect. For a changed or removed URL, redirect the old path to the closest relevant page and test the destination after publishing. If you change domains, arrange redirects for the old domain with its hosting provider.

Will I lose my search rankings?

You keep the most ranking signals when you keep your URLs, titles, and meta descriptions the same and redirect every URL that changes. Move your metadata before you rebuild pages, test redirects before launch, and watch indexing and traffic in your search tools for a few weeks after you switch domains.

Updated

Your next idea starts here

GPT 6.1 Sol

Create personal portfolio

Build startup site

Launch landing page

Start company blog

Framer UI showing Pages, Layers and Assets panels titles