Back to Troubleshooting

Move a Framer site without downtime.

Custom domain issues are usually caused by an incorrect DNS record, conflicting old records, propagation, or a domain that has not been verified. Change one record at a time and keep a copy of the working setup.

Troubleshooting · 8 min read · Updated 2026-06-06

Use a controlled sequence

Here is the process broken into clear steps. Take them one at a time and check each off before moving on.

  1. Confirm the exact domain and preferred www or apex version.
  2. Copy the records currently set at the DNS provider.
  3. Add only the records Framer requests and remove conflicts carefully.
  4. Wait for DNS propagation while checking from more than one resolver.
  5. Verify the domain in Framer, then test HTTP to HTTPS and both hostnames.
  6. Set one canonical version and redirect the other.

Alongside that sequence, there are a few things to avoid while the change is live.

  • Do not edit nameservers unless you intend to move DNS management.
  • Do not leave old hosting records competing with the new target.
  • Do not publish a domain migration without checking forms, assets and redirects.
SSL is normally issued after DNS points correctly. Repeatedly reissuing certificates will not fix a DNS conflict.

Rollout checklist for a migration

A few moving parts are involved here. The points below cover each of them, so you can see the full scope before deciding where to start.

  • Working DNS configuration recorded before any changes.
  • Downtime window agreed if the domain currently serves live traffic.
  • Redirects planned from the old canonical host to the new one.
  • Forms, third-party scripts and analytics retested after cutover.
  • Email routing (MX records) confirmed unaffected by the change.

Warning signs of an unresolved DNS conflict

This comes down to a handful of concrete details. Work through the list below and flag the ones you have not covered yet.

  • SSL certificate stuck in a pending state for longer than expected.
  • The domain resolves correctly from one location but not another.
  • Old hosting still serves the site after DNS changes were made.

Questions

It varies from minutes to around forty-eight hours depending on record type and previous TTL settings. Check resolution from more than one network or DNS resolver before assuming a change has failed.

This is almost always caused by DNS not yet pointing correctly to Framer, a conflicting record, or CAA records restricting certificate issuance. Fix the DNS first rather than repeatedly retrying certificate issuance.

Adding the specific records Framer requests at your existing DNS provider is usually enough and lower risk. Only move nameservers if you intend to manage all DNS for that domain in a new place.

Outgrowing Framer?

We rebuild Framer sites as fast, custom-coded ones and protect your rankings through the move.

See the service

Related guides

Framer CMS, forms, domains and publishing troubleshooting

Framer problems with CMS pages, forms, email, domains and publishing often cross a boundary between canvas settings and a third-party service. Test the published response and the handoff, not only the design.

Framer XML sitemaps and Search Console

An XML sitemap lists canonical URLs that you want crawled. Search Console helps you inspect what Google discovered, but submitting a sitemap does not force indexing.

Framer SEO checklist for launch

Use this practical Framer SEO checklist before publishing. It covers titles, descriptions, canonicals, Open Graph, image alt text, sitemaps, robots.txt, performance and Search Console.