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.
Company 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 and metric
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.
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.
Founder checklist
- Read JetBrains Marketplace Docs: Best practices for listing your plugin and identify what is directly supported.
- Choose one channel context: Marketplaces, SEO, Distribution.
- Define the test around JetBrains requires at least one tag on upload and uses tags directly as search filters on Marketplace..
- 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.