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.
Company 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 and metric
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`.
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.
Founder checklist
- Read Discourse Meta: Discourse Solved and identify what is directly supported.
- Choose one channel context: Community, Support, SEO.
- Define the test around The plugin exposes settings for `solved add schema markup`, `prioritize solved topics in search`, and `show filter by solved status`..
- 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.