Atlassian app name brand first and product second
Name the Marketplace app with your brand first and the Atlassian product second, so the listing reads like a third-party product instead of an in-house Atlassian feature.
Why this can grow a startup
A lot of Marketplace traffic starts with a buyer comparing a short list under time pressure. The name has to do two jobs at once: say what the product is and avoid implying Atlassian made it. Atlassian's own naming rules push partners away from host-product-first naming because that creates attribution confusion. A clearer brand-first name makes the listing easier to trust, easier to remember, and less likely to stall in review.
Company example
Atlassian's brand guidelines allow names like 'Bug Fixer for Jira' and reject names like 'Jira Bug Fixer' because Atlassian app names should not appear at the beginning.
Source and metric
Source: Atlassian Docs: Brand guidelines for Marketplace Partners
Marketplace app names must be 60 characters or less, and host-product-first examples like 'Jira Bug Fixer' are listed as not allowed.
When to use it
Use this when Marketplace, Brand, SEO is relevant to naming, brand trust, review readiness 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 Atlassian Docs: Brand guidelines for Marketplace Partners and identify what is directly supported.
- Choose one channel context: Marketplace, Brand, SEO.
- Define the test around Marketplace app names must be 60 characters or less, and host-product-first examples like 'Jira Bug Fixer' are listed as not allowed..
- 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.