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.
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-reported evidence
Source: Discourse Meta: Discourse Solved
The plugin exposes settings for `solved add schema markup`, `prioritize solved topics in search`, and `show filter by solved status`.
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, Support, SEO is relevant to answer retrieval, search quality, support-led growth and you can run a bounded test with a free 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 Support, using evidence from Discourse Meta: Discourse Solved 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.