How can I create a CMS or collection page in Webflow without having to create a whole new collection? Specifically, I want to create a "property page" for real estate listings where one version includes agent information and the other version is MLS-safe without agent information. Is it necessary to have two identical collections for this? Also, are the item limits on hosting plans too restrictive and how can I efficiently build websites within these quotas in Webflow?

You want to create a CMS Collection detail page with two variations (one with agent info, one without) without duplicating the CMS Collection. Plus, you're concerned about CMS item limits and how to work efficiently within them.

​

1. Use Conditional Visibility for Dual-Purpose Collection Pages

​

• You do not need two CMS Collections for versions with and without agent info.
• Use one "Property" CMS Collection, and leverage conditional visibility inside the Collection Template Page.
• Add a switch field (e.g., "Hide Agent Info From MLS") in your Property Collection.
• Use Webflow’s conditional visibility settings on the agent-related elements:
• Show agent info only when "Hide Agent Info From MLS" is not checked.
• Conversely, hide those sections when it's checked.

​

2. Build a Duplicate CMS Template Design as a Separate Static Page (Optional)

​

• If you want two separate URLs (e.g., /property/my-house and /mls/my-house), Webflow CMS doesn’t support multiple template pages per Collection natively.
• Workaround using static pages with dynamic Embed content:
• Create a static page (e.g., /mls/[slug]), and use custom code embeds or CMS-bound elements filtered to show the correct property.
• This is limited and harder to manage, so it's better to leverage conditional visibility inside your main template.

​

3. Efficient Use of CMS Items with Hosting Plan Limits

​

• CMS item limits differ per plan: 500 (CMS), 2,000 (CMS+), and 10,000 (Business).
• To reduce count:
• Centralize reusable content like agents, amenities, testimonials in separate CMS lists and reference them rather than duplicate content.
• Avoid creating multiple collections with identical structure (e.g., separate "MLS properties" and "Regular properties").
• Use switch fields, categories, or tags to differentiate content within one collection.
• Disable versions/drafts in your publishing workflow if not needed—they can consume item count.

​

4. Consider Webflow Logic or Jetboost for Dynamic Filtering (Advanced Control)

​

• Use Webflow Logic (for Enterprise or growing sites) to set redirects or dynamic experiences based on field states.
• Or, use tools like Jetboost to add dynamic filters/views without duplicating content or Collections.

​

Summary

​

You can use one CMS Collection with conditional visibility to manage “agent info” vs. “MLS-safe” displays. Avoid duplicating Collections, since that wastes CMS item space. Rely on fields, toggles, and dynamic visibility controls to work efficiently within Webflow’s item limits.