# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/solved-topics-prioritized-in-forum-search/
- Source: [meta.discourse.org](https://meta.discourse.org/t/discourse-solved-accepted-answer-plugin/30155/)
- GrowthDex source hub: [Discourse Meta: Discourse Solved (Accepted Answer Plugin)](/sources/discourse-meta-discourse-solved-accepted-answer-plugin-meta-discourse-or/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: low
- Channels: Community, SEO, Support
- Stages: community-led growth, support deflection, forum seo, answer quality


## Why this can grow

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.

## 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

1. Define one narrow startup segment where solved topics prioritized in forum search can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Community and SEO channel.
3. Use the evidence from meta.discourse.org to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Discourse's official Solved plugin lets teams mark accepted answers, add QAPage schema markup, and prioritize solved topics in search results.

## Adjacent tactics in the same lane

- [Similar-topic warning before new support thread](/growth-ideas/similar-topic-warning-before-new-support-thread/) - 3 shared channels, 2 shared stages
- [Slack shortcut into the feedback Autopilot queue](/growth-ideas/slack-shortcut-into-feedback-autopilot-queue/) - 2 shared channels, 1 shared stage
- [Status embed on help center and app shell](/growth-ideas/status-embed-on-help-center-and-app-shell/) - 2 shared channels, 1 shared stage
- [Doc category index for community knowledge base](/growth-ideas/doc-category-index-for-community-knowledge-base/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The forum should keep the answer after the chat scrolls away](/blog/the-forum-should-keep-the-answer-after-the-chat-scrolls-away/) - community-led growth, support deflection, forum seo

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.