Start from sections and components
Design the home and one high-priority conversion page before expanding the site. Reuse navigation, buttons and layout sections. For a recurring content type, define CMS fields and test long entries, narrow screens and missing images.
Create responsive structure before adding motion
List the pages and conversion steps you need. Build reusable navigation, buttons and type styles. Use breakpoints and sizing that allow content to wrap. Review the longest heading, a crowded navigation label and a small phone. Add motion where it explains a change or draws attention to an action and test the same experience with reduced motion enabled.
- Build the layoutUse responsive components and meaningful reading order
- Connect CMS contentTest real items and their metadata
- Publish the pilotCheck reduced motion, forms and search directives
Set up pages for launch
Give important pages descriptive titles and summaries. Confirm the domain and preferred hostname, then check responsive image sizes, forms and keyboard navigation. Review whether embeds or animations delay the main content.
Model CMS pages and their search settings
Use collections for repeating pages like case studies or articles. Add fields for titles, summaries and accessible imagery. Connect each CMS template to its relevant page metadata and confirm that individual public URLs make sense. Set the domain, review redirects for any replaced URLs and inspect the sitemap generated after publishing. Pay particular attention to pages cloned from a template.
Validate a live copy
Publish, test enquiries, and inspect the live page rather than relying on the editor preview. Check mobile loading and whether key pages are discoverable through links. Keep a list of settings that must be recreated if the site is ever moved to another platform.
Publish a small proof before expanding the design
Test one contact flow and one CMS item first. Check that fonts load, form requests arrive and key links work on touch. Audit a motion-heavy page on a real phone, focusing on the time until the main content becomes useful. Review focus and keyboard navigation. Then share the published URL with a test visitor and ask them to perform the main task without guidance.
A Framer site for a design studio
A studio publishes its homepage, two project pages and a contact form. It keeps the hero animation decorative and shares project details in normal text. When a project slug changes, the old URL redirects to the updated case study. The studio tests booking completion and inspects the final live page.
If the business already has an indexed site, document the routes and metadata before you publish. Use redirects for changed URLs that have a useful equivalent and check the new sitemap against the release inventory. Treat the public site as the source of truth for search settings and accessibility. Some motion, focus or rendering problems appear only when real content and production fonts arrive, so repeat a few sample checks after custom-domain publication.
| Component | Goal | Check |
|---|---|---|
| CMS project | Readable page with its own metadata | Inspect multiple live project URLs |
| Motion | Adds context and remains optional | Reduced motion and phone test |
| Lead form | Visitor receives a usable response | Check inbox and confirmation after submission |
Common questions
Can a Framer site support SEO?
Yes, standard search fundamentals still apply. Check the published page’s content, metadata, index directives, sitemap and performance.
How should I choose between custom motion and a simpler layout?
Keep an animation if it helps understand an interaction or a product. Test the mobile experience and measure load and response before making it part of every template.
Can an editor update content without altering the layout?
Use collection fields and reusable components for repeatable content. Train the editor on the publishing flow and test a real update with longer text and a differently cropped image.
What to check next
- Reusable componentsUpdate navigation once and check affected pages
- FormsVerify live submission delivery
- PortabilityRecord content, URL and domain ownership




