JetBrains plugin tags fit the real search
Choose the tags that match the plugin's true use case because JetBrains exposes tags as search filters and the wrong category makes discovery noisier, not wider.
Why this can grow a startup
Marketplace search quality usually breaks through over-classification. Teams try to admit every feature, but buyers are still looking for one clear category. JetBrains' tag system rewards the narrower move because tags are visible on the page and double as search filters. When the tags fit the job the plugin actually does, the listing is easier to find and easier to trust once found.
Source-backed example
JetBrains requires at least one plugin tag during upload, shows tags above the plugin name on the page, and says tags are used as search filters across the marketplace.
Source-reported evidence
Source: JetBrains Marketplace Docs: Best practices for listing your plugin · Browse JetBrains Marketplace Docs: Best practices for listing your plugin tactics
JetBrains requires at least one tag on upload and uses tags directly as search filters on Marketplace.
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.
When to use it
Use this when Marketplaces, SEO, Distribution is relevant to jetbrains marketplace, taxonomy, search 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 Marketplaces and SEO, using evidence from JetBrains Marketplace Docs: Best practices for listing your plugin 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.
SOURCE HUB
More tactics from JetBrains Marketplace Docs: Best practices for listing your plugin
Explore related GrowthDex examples and evidence connected to JetBrains Marketplace Docs: Best practices for listing your plugin.
Open JetBrains Marketplace Docs: Best practices for listing your plugin source hub