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.
Company example
Discourse's official Solved plugin lets teams mark accepted answers, add QAPage schema markup, and prioritize solved topics in search results.
Source and metric
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.
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.
Founder checklist
- Read Discourse Meta: Discourse Solved (Accepted Answer Plugin) and identify what is directly supported.
- Choose one channel context: Community, SEO, Support.
- Define the test around The Solved plugin includes settings to add QAPage schema markup and prioritize solved topics in search results..
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.