Growth idea action plan
Discourse solved schema and search priority
Turn solved support threads into a cleaner answer surface by marking accepted solutions, adding solved filters, and letting solved topics rank better in on-site search.
Why this can grow a startup
A busy forum can hold the answer and still hide it in plain sight. Discourse Solved changes that by making the best reply explicit, exposing solved and unsolved filters, and adding settings for QAPage schema plus search prioritization. That matters because support content becomes far more useful when readers can tell whether a thread actually ended well. It also gives operators a better archive. Instead of treating every thread like equal evidence, the forum starts separating resolved answers from unresolved noise.
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 discourse solved schema and search priority can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Community and Support 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 Solved plugin includes settings for solved-status filters, auto-closing solved topics, QAPage schema markup, and prioritizing solved topics in search results.
Source: Discourse Meta: Discourse Solved (meta.discourse.org)
GrowthDex source hub: Discourse Meta: Discourse Solved
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
- Discourse solved tags on mixed discussion categories 2 shared channels · 1 shared stage
- Help-center search terms in title, description, and body 2 shared channels · 1 shared stage
- High-traffic help articles linking to low-traffic answers 2 shared channels · 1 shared stage
Related GrowthDex essays
- The support forum should stop acting like a chat room community-led growth, support-led growth, documentation
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