Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3157 Ideas

    YoeriNew Participant

    Map an Article to Multiple Collections (Avoid Content Duplication)Submitted

    Currently, Intercom Articles can only live in one Collection (and one sub-section) at a time. However, many support topics are cross-functional. For example, an article about the report for ‘Functionality A’ is relevant to both the ‘Functionality A’ collection and the ‘Reports’ collection. The current workaround is to manually duplicate the article. This creates several critical issues:Maintenance Nightmare: If a screenshot or a feature changes, we have to remember to update every single copy of that article. This is prone to human error and leads to outdated information.Split Analytics: The fragmentation of data across multiple URLs prevents us from seeing the total impact or performance of a piece of content.SEO Penalties: Search engines flag "duplicate content." Having three identical pages on one Help Center hurts our organic search ranking.Broken User Experience: A user might encounter two versions of the same article (with slightly different titles), causing confusion about which one is the "official" guide. The Solution: Multi-Collection MappingWe need the ability to create an article once and "map" it to multiple Collections or Sections. How it should work:Within the Article Settings, instead of a single dropdown for "Collection," there should be a multi-select option or an "Add to another collection" button.The article should have one primary URL (Canonical) to protect SEO, but be visible and navigable through all assigned collections.Analytics should be aggregated for the article, regardless of which collection the user navigated through. Why this is important"Single Source of Truth": This is the gold standard for content management. It ensures that customers always get the most accurate, up-to-date information without the risk of us missing a duplicate during an update.Scalability: As our Help Centers grow from 50 to 500+ articles, manual duplication becomes impossible to manage. This feature would save our Content Team hours of repetitive work every month.Improved Discoverability: Customers have different mental models. Some look for a feature under "Pricing," others under "Account Settings." Allowing an article to exist in both places meets the customer where they are. The ImpactBy implementing this, Intercom would move from being a "basic" knowledge base to a sophisticated Content Management System (CMS). It prevents content rot, ensures SEO health, and significantly reduces the operational overhead for Support Operations teams. We want to spend our time writing great content, not copy-pasting it. Is this on the roadmap? We’d love to see Intercom support a more flexible content architecture!