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.
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-reported evidence
Source: Discourse Meta: Discourse Solved (Accepted Answer Plugin)
The Solved plugin includes settings to add QAPage schema markup and prioritize solved topics in search results.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 29, 2026
When to use it
Use this when Community, SEO, Support is relevant to community-led growth, support deflection, forum seo and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Community and SEO, using evidence from Discourse Meta: Discourse Solved (Accepted Answer Plugin) as context—not as a promised result.
- Record a baseline for: Qualified search visitors who complete the intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.