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

- Canonical HTML: https://growth.iangoh.com/growth-ideas/jetbrains-plugin-name-states-the-ide-job/
- Source: [plugins.jetbrains.com](https://plugins.jetbrains.com/docs/marketplace/jetbrains-marketplace-approval-guidelines.html)
- GrowthDex source hub: [JetBrains Marketplace Docs: Approval Guidelines](/sources/jetbrains-marketplace-docs-approval-guidelines-plugins-jetbrains-com/)
- Last checked: 2026-06-06T10:04:00Z
- Rarity: uncommon
- Budget: free
- Channels: Marketplaces, Brand, SEO
- Stages: jetbrains marketplace, naming, search intent, developer tools


## Why this can grow

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.

## 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 jetbrains plugin name states the ide job can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Brand channel.
3. Use the evidence from plugins.jetbrains.com 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

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.

## Adjacent tactics in the same lane

- [Firefox Add-ons name earns the slug](/growth-ideas/firefox-add-ons-name-earns-the-slug/) - 3 shared channels, 1 shared stage
- [VS Code extension category picks the right shelf](/growth-ideas/vs-code-extension-category-picks-the-right-shelf/) - 3 shared channels, 1 shared stage
- [JetBrains plugin first 40 characters carry the preview card](/growth-ideas/jetbrains-plugin-first-40-characters-carry-the-preview-card/) - 2 shared channels, 2 shared stages
- [JetBrains plugin tags fit the real search](/growth-ideas/jetbrains-plugin-tags-fit-the-real-search/) - 2 shared channels, 2 shared stages

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The JetBrains plugin page should finish the IDE trust check](/blog/the-jetbrains-plugin-page-should-finish-the-ide-trust-check/) - marketplaces, SEO, brand trust

## Advisory

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