Growth idea action plan
Solved topics prioritized in forum search
Mark resolved community threads as solved and let the forum push those answers higher in search instead of leaving every old thread to compete equally.
Why this can grow a startup
Community support starts compounding when the answer is easy to spot and easy to trust. Discourse's solved workflow does more than add a checkbox. It can add QAPage schema markup and prioritize solved topics in search results. That changes the shape of the archive. A buyer or user who lands on the forum is more likely to hit a finished answer instead of a half-debugged thread. It also makes the public forum feel less chaotic, which matters when the same surface is quietly doing support, brand trust, and long-tail SEO at once.
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
- Define one narrow startup segment where solved topics prioritized in forum search can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Community and SEO channel.
- Use the evidence from meta.discourse.org to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.
Source-backed example
Discourse's official Solved plugin lets teams mark accepted answers, add QAPage schema markup, and prioritize solved topics in search results.
Source: Discourse Meta: Discourse Solved (Accepted Answer Plugin) (meta.discourse.org)
GrowthDex source hub: Discourse Meta: Discourse Solved (Accepted Answer Plugin)
Last checked: 2026-05-29
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Similar-topic warning before new support thread 3 shared channels · 2 shared stages
- Slack shortcut into the feedback Autopilot queue 2 shared channels · 1 shared stage
- Status embed on help center and app shell 2 shared channels · 1 shared stage
- Doc category index for community knowledge base 2 shared channels · 1 shared stage
Related GrowthDex essays
- The forum should keep the answer after the chat scrolls away community-led growth, support deflection, forum seo
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory