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

- Canonical HTML: https://growth.iangoh.com/growth-ideas/discourse-solved-schema-and-search-priority/
- Source: [meta.discourse.org](https://meta.discourse.org/t/discourse-solved/30155?tl=en)
- GrowthDex source hub: [Discourse Meta: Discourse Solved](/sources/discourse-meta-discourse-solved-meta-discourse-org/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: free
- Channels: Community, Support, SEO
- Stages: answer retrieval, search quality, support-led growth, crawlable answers


## Why this can grow

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.

## 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 discourse solved schema and search priority can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Community and Support 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 Solved plugin includes settings for solved-status filters, auto-closing solved topics, QAPage schema markup, and prioritizing 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
- [Discourse solved tags on mixed discussion categories](/growth-ideas/discourse-solved-tags-on-mixed-discussion-categories/) - 2 shared channels, 1 shared stage
- [Help-center search terms in title, description, and body](/growth-ideas/help-center-search-terms-in-title-description-and-body/) - 2 shared channels, 1 shared stage
- [High-traffic help articles linking to low-traffic answers](/growth-ideas/high-traffic-help-articles-linking-to-low-traffic-answers/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The support forum should stop acting like a chat room](/blog/the-support-forum-should-stop-acting-like-a-chat-room/) - community-led growth, support-led growth, documentation

## Advisory

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