Model your content before designing
Identify the pages that repeat, such as projects, services and locations. Put reusable fields into CMS collections. Create sample entries with long titles and missing optional fields so the template is tested against realistic content.
Separate static pages from repeated content
Start by mapping page types. A homepage and contact page can be static. Use CMS collections for repeatable items such as services, resources and case studies. Before styling the template, decide which fields editors need. A case study may need a client description, problem, approach, verified outcome and image. Keep relationships consistent so visitors can explore relevant services from each item.
- Model the contentSeparate reusable collection fields from static material
- Style the templateTry sparse items and long text on mobile
- Publish and checkVerify forms, old URLs and the sitemap
Build responsive pages and publish to staging
Create reusable components and check breakpoints from the smallest practical viewport upward. Use semantic headings and accessible form labels. Set titles and descriptions for static and collection pages, and manage which URLs should appear in the sitemap.
Set publishing and SEO controls before importing content
Design breakpoints around actual content lengths. Use descriptive labels for shared navigation and forms. Define dynamic title and description rules for collection pages and test the output on several items, including one with sparse fields. Set the public domain and check that published production pages have the intended canonical host. Use Webflow’s sitemap capability and inspect it on the live URL.
Check the live domain
Confirm the primary domain, redirects, mobile navigation and form delivery. Inspect a collection page in Search Console after launch. If moving from another CMS, use a URL inventory and compare old and new paths before changing DNS.
Make the first publish reversible
Keep a list of existing paths and their new destinations. Add redirects for genuinely moved content, then test chains and missing patterns. Inspect the production site’s form delivery and form-error path. Audit keyboard access, focus and visual layout on phones. Document which roles can publish changes so a draft, template adjustment or redirect can be released deliberately.
Model collections before drawing every page
Identify which content repeats, such as services, case studies, or articles. Define collection fields and relationships before designing their templates. A clear content model reduces duplicated layouts and makes later publishing easier for the person who will maintain the website.
Build responsive rules deliberately
Check desktop, tablet, and phone layouts using realistic content. Use flexible sizing rather than fixing every element to a desktop width. Review long titles, menus, and forms, since those often expose layout problems that a short placeholder heading conceals.
Treat interactions as optional enhancement
Keep important text, links, and actions usable before an animation runs. Provide reduced-motion behaviour and avoid interactions that depend entirely on hover. A visitor on a touch device should still understand the same offer and reach the same next step.
Check publishing and search settings
Confirm the preferred domain, redirects, sitemap, page titles, and indexing settings in the published environment. Review collection template metadata with several real records. A correct static page does not prove that every CMS item receives a useful title and description.
Hand over an editable system
Document class conventions, reusable components, and collection fields. Give editors a safe path for routine updates and test that workflow with them. Clear publishing ownership helps prevent a small copy edit from becoming an accidental structural change.
A case-study collection example
An agency migrates twelve case studies. It models industries and services as fields and publishes three trial case studies on staging. One has a long title and another has no client photo. Testing both catches truncation and empty media before the full import. After launch the team samples indexed and live URLs in Search Console.
When designing for editors, set clear requirements at the collection level. Write guidance on image dimensions, short descriptions and valid external links. Add a default image or safe layout for missing fields. Test publishing after removing or unpublishing an item to learn how links and templates respond. That small rehearsal prevents a project that looks finished to a designer from needing developer support every time an editor adds a case study.
| Area | Choose | Test |
|---|---|---|
| Static or CMS | Repeated fields belong in a collection | Publish two items with different content lengths |
| Redirects | One equivalent destination per retired path | Test the old and final addresses |
| Findability | Production canonicals and sitemap | Inspect a live collection item |
Common questions
Is a collection item indexable?
It can be when published to a public, crawlable URL that returns usable content and allows indexing. Inspect the page’s rendered directives.
How do I avoid duplicate staging results?
Keep staging restricted or excluded from indexing using your project’s relevant controls. Confirm that production uses its own public hostname and intended index settings.
How do I handle forms during a Webflow rebuild?
List every destination and success message first. Test a valid message and an invalid one on the public domain, then verify the enquiry reaches the intended inbox or CRM.
What to check next
- CMSTest entries with missing optional fields
- Responsive layoutCheck navigation and forms below desktop widths
- MigrationMap valuable old paths to relevant replacements




