How to Connect WordPress as a Framer Custom Domain

WordPress and Framer serve different audiences and solve different problems. WordPress is a full-stack CMS — it handles content management, user management, e-commerce, and can serve the front end. Framer is primarily a design and prototyping tool that has evolved into a no-code site builder with impressive visual fidelity and animation capabilities.

The scenario where someone asks about connecting WordPress as a Framer custom domain usually falls into one of three situations: they’ve built their site in Framer and want to use a domain currently pointing to a WordPress installation; they want Framer for the front-end design while keeping WordPress for blog content and SEO; or they’re considering a full migration from WordPress to Framer and want to understand the domain transition process.

All three are legitimate and achievable, but each requires a different approach. Understanding exactly what “connecting WordPress as a Framer custom domain” means determines which path you need to take.

To be precise: Framer doesn’t “use a WordPress domain” — it uses a domain, period. If your domain currently points to a WordPress server, you redirect it to Framer by changing DNS records. WordPress is not involved in the domain itself; it’s just a web application running on a server that your domain happens to be pointing to right now.

Framer supports custom domains on any paid plan (Mini, Basic, or above). You add your domain in the Framer project settings under “Custom Domain”, then Framer gives you DNS records to configure: typically an A record pointing to Framer’s IP address, or a CNAME for a subdomain. You make those changes at your domain registrar or DNS provider (Cloudflare, Namecheap, GoDaddy, etc.).

Once DNS propagates (usually 1-48 hours), your domain serves your Framer site. Your WordPress installation is still there on your hosting server — it just isn’t receiving traffic from that domain anymore. You can keep it as a staging environment or decommission it.

The process depends on where your domain is registered and where your WordPress site is hosted. Here’s the general sequence:

1. Identify your DNS provider — this is your domain registrar (Namecheap, GoDaddy, Google Domains) or a DNS management service (Cloudflare). Log in to their dashboard.
2. Get Framer’s DNS values — in Framer, go to your project’s Publish settings, click “Custom Domain”, enter your domain, and Framer will display the required DNS records.
3. Update your DNS records — in your DNS provider, update or replace the A record for your root domain (@ or yourdomain.com) to point to Framer’s IP, and add a CNAME for www if needed.
4. Wait for propagation — DNS changes can take up to 48 hours globally, though most propagate within a few hours.
5. Verify in Framer — once propagated, Framer will automatically provision an SSL certificate and your site will go live on the custom domain.

Before making DNS changes, make sure your WordPress content is either backed up and accessible at a different URL, or that you’ve exported everything you need. Moving DNS is a one-way switch in terms of where your visitors land.

A more sophisticated approach is to keep WordPress running as a headless CMS while using Framer (or another front-end framework) for the user-facing site. In this architecture, WordPress manages content through its REST API or WPGraphQL, and the front end fetches and renders that content.

Framer doesn’t natively support data fetching from WordPress’s REST API in the way that Next.js or Astro would. However, you can use Framer’s CMS integration to pull content from external sources if you build a connector, or use Framer’s API capabilities to fetch data on page load. For most teams, a proper headless WordPress setup is better served by a dedicated front-end framework like Next.js than by Framer, which is optimized for visual design rather than data-driven page rendering.

If you’re drawn to Framer for its design capabilities but need WordPress’s content management, the practical middle ground is to run Framer for marketing pages (home, features, pricing, about) while keeping WordPress for the blog and documentation — each on a different subdomain (framer.yourdomain.com for the app site, blog.yourdomain.com for WordPress).

If your domain is registered through WordPress.com (not just hosted there), the transfer process has an extra step. WordPress.com acts as a domain registrar for domains purchased through their platform, and you’ll need to transfer the domain to an independent registrar before you can freely manage DNS records for Framer.

To transfer: go to WordPress.com → My Sites → Upgrades → Domains → your domain → “Transfer Domain to Another Registrar”. WordPress.com will give you an authorization (EPP) code. Take that code to your chosen registrar (Namecheap is a common choice), initiate the transfer, and confirm the email WordPress.com sends. The transfer takes up to 7 days. Once complete, you own the domain at the new registrar and can point it to Framer’s DNS records.

Moving from WordPress to Framer has significant SEO implications that many designers overlook. WordPress has a mature SEO ecosystem — Yoast, Rank Math, XML sitemaps, structured data, and years of accumulated link equity. Framer is improving its SEO tooling but remains less capable than WordPress for content-heavy, SEO-driven sites.

The most critical concern is 301 redirects. If your URL structure changes during the migration (e.g., WordPress used /blog/post-title/ and Framer uses /blog/post-title), you’ll lose the link equity those URLs have accumulated unless you configure proper redirects. Framer’s redirect management is available in project settings but is more limited than WordPress’s options.

Before migrating, audit your highest-traffic pages using Google Search Console, document all URLs and their ranking positions, and build a redirect mapping document. Post-migration, monitor rankings closely for 30-60 days. If you rely on blog content for organic traffic, I’d strongly recommend keeping WordPress for the blog and using Framer only for pages where the visual design is the primary differentiator.