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're looking to display two versions of the same CMS content (with and without agent info) without duplicating collections, and you're concerned about Webflow's CMS item limits. Here's how to approach both.

1. Use a Single Collection with Conditional Visibility

• No, you don't need two collections. You can use one Collection (e.g., "Properties") and modify the template page to conditionally display agent info.
• Create a toggle field (e.g., a Switch field called “Is MLS-safe”) in your “Properties” collection.
• In the “Property” CMS template page:
• Add a section with agent info.
• Use Conditional Visibility to show agent content only when Is MLS-safe is false (off).
• You now have one page that automatically adapts its content based on the CMS entry.

2. Serve Two Versions Using URL Parameters or Refined Page Design

• Optionally, you can create two user-facing versions without duplicating content:
• Version A (Default): Shows agent info.
• Version B (MLS-safe): Add a query string (?mls=true) or structure your CMS page design so both variants are embedded on one page but toggled using script or visibility rules.
• Webflow does not support dynamic routing based on query parameters, but you can:
• Use JavaScript to detect ?mls=true in the URL and hide agent-related elements on the front end (don’t rely on this for compliance-sensitive use).

3. Handling CMS Item Limits Efficiently

Webflow CMS item limits can become tight for real estate:

• CMS Plans:
• CMS Hosting: 2,000 items
• Business Hosting: 10,000 items
• Enterprise: Custom limits
• Tips to stay within limits:
• Use multi-reference fields to relate multiple agents to many properties without duplicating agent bios.
• Compress media and host large files off Webflow (e.g., on Cloudinary or Vimeo for videos).
• Archive stale listings: Unpublish or delete old property records.
• Use a third-party CMS integration like Airtable + Whalesync or PowerImporter if you hit limits often.
• Consider Webflow Logic (beta) or Integromat/Make to automate updates and handle high-volume syncs with external MLS feeds.

Webflow is not ideal for large MLS-scale projects without customization or third-party tools.

Summary

You can manage both property page variants using a single CMS collection with conditional visibility. Separate collections are unnecessary. To cope with item limits, optimize CMS structure, archive listings, and use external tools to keep data volumes low.