Framer site launch checklist

Short answer: before publishing a Framer site for a client, check every breakpoint (desktop, tablet, phone) for overflow and overlapping layers, click every link including CMS detail pages, confirm page titles, descriptions and social images in each page’s SEO settings, submit every form and confirm delivery, connect and test the custom domain on www and non-www, and remove unused or draft pages before publishing.

General items apply to any builder; see the 36-item website launch checklist. This page lists the checks that come up most often on Framer builds. Always confirm settings against Framer’s current documentation, as the editor changes often.

Layout and breakpoints

• No horizontal scrolling at phone width; check absolutely-positioned layers and wide stacks. Proofday checks this
• Every breakpoint reviewed in the preview, not just desktop.
• Text does not overflow fixed-height frames when copy changes.
• Hover-only interactions have a tap-friendly equivalent on touch screens.
• Scroll and appear effects don’t hide content if they fail to trigger.

Links and CMS

• Navigation, footer and button links all open working pages. Proofday checks this
• CMS collection detail pages render for every item, including ones with empty optional fields.
• External links still resolve. Proofday checks this
• Old URLs from a previous site redirect to new pages (set up redirects in site settings).

SEO and sharing

• Each page has its own title and meta description. Proofday checks this
• One H1 per page; text styles mapped to the right heading tags. Proofday checks this
• Images have alt text where they carry meaning. Proofday checks this
• Social preview image set for the site and key pages.
• Search indexing enabled for the production domain; draft or test pages excluded.

Media and performance

• Every image and video loads. Proofday checks this
• No console errors from embeds or custom code. Proofday checks this
• Large background videos and images compressed.
• Pages load in about 3 seconds on a normal connection. Proofday checks this

Forms, domain and handoff

• Every form submits and the notification reaches the right inbox.
• Custom domain connected; www and non-www both work and one redirects to the other.
• Cookie banner/consent configured if the client needs one.
• Client has the right editor access and knows how to edit CMS items.

FAQ

How do I test a Framer site before launch?

Preview every breakpoint for overflow and overlapping layers, click every link including CMS pages, check each page’s SEO settings, submit every form, and test the custom domain. An automated check can cover links, mobile overflow, missing assets, console errors and SEO basics on public pages.

Can Proofday check a Framer site?

Yes, if the pages are public. Proofday loads up to 10 public pages of any builder’s site in Chromium at desktop and mobile sizes. Forms, logins and payments are marked not tested.

Should I test Framer sites on a real phone?

Yes. Preview breakpoints are a good start, but tap targets, scroll effects and video autoplay should be checked on at least one real phone.

Updated 2026-10-16 by Steven Jackson, who runs Proofday. Related: 36-item website launch checklist · Webflow QA before launch · Framer launch checklist · Client handoff QA · Proofday vs free tools