JetBrains plugin name states the IDE job
Use a short, original plugin name that tells the IDE user what work gets done instead of burning the title on generic words or pricing noise.
Why this can grow a startup
JetBrains buyers scan fast. A loose title pushes the real product story further down the page and makes the plugin feel harder to place. JetBrains' listing and approval rules are useful because they force the opposite discipline: keep the name short, clear, original, and free of filler like Plugin, IntelliJ, or plan language. That means the title starts qualifying the reader before the description has to do cleanup work.
Company example
JetBrains recommends a short plugin name of one to four words that reflects the core purpose, while its approval rules cap names at 30 characters and reject names that include Plugin, IntelliJ, pricing text, or search-gaming punctuation.
Source and metric
Source: JetBrains Marketplace Docs: Approval Guidelines
JetBrains recommends 1 to 4 words, strongly prefers names under 20 characters, and approval rules cap names at 30 characters.
When to use it
Use this when Marketplaces, Brand, SEO is relevant to jetbrains marketplace, naming, search intent 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: Approval Guidelines and identify what is directly supported.
- Choose one channel context: Marketplaces, Brand, SEO.
- Define the test around JetBrains recommends 1 to 4 words, strongly prefers names under 20 characters, and approval rules cap names at 30 characters..
- 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.