# Similar-topic warning before new support thread

> Use the composer’s similar-topic warning so users see likely answers before they create another near-duplicate support thread.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/similar-topic-warning-before-new-support-thread/
- Source: [meta.discourse.org](https://meta.discourse.org/t/composer-popup-messages-guide/317734)
- GrowthDex source hub: [Discourse Meta: Composer Popup Messages Guide](/sources/discourse-meta-composer-popup-messages-guide-meta-discourse-org/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: free
- Channels: Support, SEO, Community
- Stages: duplicate prevention, forum seo, support deflection, composer ux


## Why this can grow

Duplicate support topics do not only waste moderator time. They also split search equity and force future readers to pick between several half-overlapping answers. Discourse surfaces similar topics while someone is composing a new thread, with settings for title length and how much existing topic volume is needed before suggestions appear. That small interruption can save a forum from steady answer fragmentation. It is one of the cheapest ways to protect both support bandwidth and the public answer archive.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where similar-topic warning before new support thread can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and SEO channel.
3. Use the evidence from meta.discourse.org to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Discourse documents a composer message that warns users when a new topic looks similar to existing topics and shows possible matches before posting.

## Adjacent tactics in the same lane

- [Solved topics prioritized in forum search](/growth-ideas/solved-topics-prioritized-in-forum-search/) - 3 shared channels, 2 shared stages
- [Discourse solved schema and search priority](/growth-ideas/discourse-solved-schema-and-search-priority/) - 3 shared channels
- [GitHub contributing tab before first PR](/growth-ideas/github-contributing-tab-before-first-pr/) - 2 shared channels, 1 shared stage
- [Custom welcome message with Discobot handoff](/growth-ideas/custom-welcome-message-with-discobot-handoff/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The forum should keep the answer after the chat scrolls away](/blog/the-forum-should-keep-the-answer-after-the-chat-scrolls-away/) - community-led growth, support deflection, forum seo

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.