Guide · Atlassian apps

How do AI search tools find Atlassian Marketplace apps? App pages tested, plus the vendor's requirements

Updated 2026-11-13 · kagentx

Short answer

Tested on 2026-11-13: Atlassian Marketplace's robots.txt names no AI crawlers, and the sitemap lists 8,872 app pages; an app page's body can be read without running scripts, and it has a meta description, a canonical, and Product plus SoftwareApplication structured data. The naming rules say “App X for Jira” passes and “Jira App X” is rejected. So the store page itself is already quite complete; what an indie developer should add is an introduction page on their own site, kept consistent with the listing. We have no evidence that AI cites these pages: not verified.

Is Atlassian Marketplace open to crawlers?

Yes, and it names no AI crawlers. On 2026-11-13 we tested the robots.txt and sitemap of marketplace.atlassian.com with curl (User-Agent Mozilla/5.0):

CheckTest result
robots.txt200, 303 bytes: the * group blocks only /login, /server/, /rest/, /download/, /admin/, /manage/, /files/, /users/; MauiBot is blocked site-wide; atlassian-bot is allowed only /apps/; one Sitemap line pointing to sitemap.xml
sitemap.xml200, 312 bytes, an index: sitemap-discovery.xml and sitemap-listings.xml
sitemap-discovery.xml200, 4,561 bytes, 29 URLs: home, search page, 1 bundle, 10 categories, 7 collections, 9 product pages; no lastmod
sitemap-listings.xml200, about 2.5 MB, 12,028 URLs: 8,872 /apps/<numeric ID>/<name>, 3,156 /vendors/<numeric ID>/<name>; 8,872 have a lastmod

robots.txt names no AI crawlers, so the * group's rules apply to them: app pages and vendor pages are not blocked. What each crawler does is in AI crawler user agents: a side-by-side table, how to write the rules is in How do you write robots.txt for AI crawlers?. We found no official explanation of what atlassian-bot is: not verified.

What does the app detail page's HTML contain?

More complete than most stores: the body and the structured data are both in the HTML. We fetched two app pages (2026-11-13, curl, no script execution, only these two tested): /apps/1210933/draw-io-diagrams-uml-bpmn-aws-erd-flowcharts and /apps/6820/scriptrunner-for-jira.

CheckTest result
HTTP status and size200, about 454 KB and 348 KB
title“App name | Atlassian Marketplace”
meta descriptionYes, one sentence from the app's Key highlights
canonical, h1canonical points to its own full URL; <h1> is the app name
og tagsHas og:type, og:description, og:image, og:title, og:url, og:site_name
hreflang, meta robotsNone
JSON-LDTwo blocks: WebSite (with SearchAction); Product plus SoftwareApplication (name, image, description, dateCreated, applicationCategory, applicationSuite, offers, screenshot, aggregateRating, creator)
Visible text (scripts and styles removed)About 4,411 and 3,671 characters: vendor, compatible products and versions, rating and review count, install count, trust badges, Key highlights and Overview text, edition notes

So a crawler can read the summary, rating and structured data without running scripts; whether crawlers run scripts is in Do AI crawlers render JavaScript?. How to write structured data is in Should a SaaS add SoftwareApplication structured data?; titles and descriptions are in Do title and meta description matter for AI search?. We have no evidence that AI answers cite these pages: not verified.

What does Atlassian require for names and descriptions?

Atlassian developer documentation (read in full on 2026-11-13; the pages carry different update dates, noted in the table):

ItemOfficial statement
Naming (approval guidelines, marked updated 2026-05-15)Trademark infringement is grounds for automatic rejection, including names and visual assets; “Jira App X” is rejected, “App X for Jira” passes
Naming (creating a listing, marked updated 2026-04-09)The app name should describe what the app does or match your brand; do not start with an Atlassian product name; the logo must not contain or modify Atlassian brand elements
Listing content (approval guidelines)Describe what the app really does; reference documentation on setup and use; do not advertise other apps, products or services; a cloud app with the same core functionality as a published server app should share its listing
Text length and images (“Building your presence”, marked updated 2020-06-05; an old page, specs may have changed)App name up to 60 characters, avoid “Atlassian”, “plugin”, “beta”, “add-on”, “app”; tagline up to 130 characters; Summary (Legacy) 250; More details 1000; logo 144 × 144 px; banner 1120 × 548 px; exactly 3 Highlights (title 50, summary 220, screenshot 1840 × 900 px); release summary up to 80 characters
Privacy and security (Forge listing, marked updated 2026-08-26)Provide accurate information in the Privacy and Security tab; have End User Terms; explain why each API scope is needed and list the remote hosts and data the app sends; the aim is a review result within a week, actual time varies
SEO (marked updated 2017-06-05, older still)Use the phrase buyers search for in the title, tagline, URL and image alt text; link to the listing from elsewhere; keep the information complete; update regularly; the page says nothing about the meta description

The vendor does not say how these fields affect AI citation, and we have no evidence: not verified. Whether the 2017 and 2020 pages' specs still apply is also not verified.

How do you make an Atlassian app easier to find, step by step?

  1. 1. Short, specific app name that follows the naming rules

    Use an order like “App X for Jira”, do not start with an Atlassian product name, avoid “Atlassian”, “plugin”, “add-on”; the app name goes into the app page's title, <h1> and URL.

  2. 2. Write the tagline and Key highlights as sentences that can be quoted directly

    The meta description is taken from the app's summary, so make the first sentence say what it does and where in Jira or Confluence it is used.

  3. 3. Pick the right category and put the phrase buyers search for into the listing

    The vendor's SEO page suggests using this phrase in the title, tagline, URL and image alt text.

  4. 4. Write a full introduction page on the official site

    Which products and versions it works with, permissions and where data goes, install steps, changelog, with a link to the Marketplace page; keep it consistent with the Marketplace listing. How to write integration pages is in How do you write an "X and Y integration" page so AI will cite it?.

  5. 5. Add SoftwareApplication data on your site

    The Marketplace page already has Product and SoftwareApplication; add it on your site too, with the same name and category as on Marketplace; how to write it is in Should a SaaS add SoftwareApplication structured data?.

  6. 6. Test again after a few weeks with the same questions

    Ask ChatGPT and Perplexity “is there a Jira app that does X”, 3 times per question, and note whether you are mentioned and which URLs are cited.

Compare with similar stores: How do Slack apps and Discord bots get recommended by AI?, How do Shopify apps get recommended by AI?, How do WordPress plugins get recommended by AI?, How do AI search tools find Google Workspace add-ons? The Marketplace app page, tested.

FAQ

Can the body of an Atlassian Marketplace app page be read without running scripts?

Yes. On 2026-11-13 we fetched two app pages with curl (about 454 KB and 348 KB); with scripts and styles removed, the visible text is about 4,411 and 3,671 characters, including the vendor, compatible products, rating, install count, and Key highlights and Overview text; the <h1> is the app name. We tested only these two pages.

Do app pages have structured data?

Yes. Each of the two pages has two JSON-LD blocks: one WebSite and one Product plus SoftwareApplication, with fields such as name, description, applicationCategory, screenshot, aggregateRating and creator.

Does robots.txt block AI crawlers?

No. On 2026-11-13 the robots.txt was 303 bytes: the * group blocks only /login, /server/, /rest/, /download/, /admin/, /manage/, /files/, /users/; MauiBot is blocked site-wide; atlassian-bot is allowed only /apps/.

Does Atlassian Marketplace have a sitemap?

Yes. sitemap.xml is an index pointing to sitemap-discovery.xml (29 URLs: home, categories, collections, product pages) and sitemap-listings.xml (12,028 URLs: 8,872 app pages and 3,156 vendor pages); app pages carry a lastmod.

What are the requirements for the app name and tagline?

The vendor's old page “Building your presence on Marketplace” (marked updated 2020-06-05, specs may have changed) says: app name up to 60 characters, do not start with an Atlassian app name, avoid “Atlassian”, “plugin”, “beta”, “add-on”, “app”; tagline up to 130 characters. The 2026 approval guidelines say “Jira App X” is rejected and “App X for Jira” passes.

What does the vendor recommend for SEO?

The vendor's SEO best practices page (marked updated 2017-06-05, an old page) says: find the phrase buyers search for and use it in the title, tagline, URL and image alt text; link to the listing from elsewhere; keep the information complete; update regularly. The page says nothing about the meta description.

Besides the store page, what other page does an indie developer need?

One full introduction page on your own site: what it does, which Atlassian products and versions it works with, permissions and where data goes, install steps, changelog, privacy policy, End User Terms. The approval guidelines require the listing to reference setup and usage documentation, and Forge apps must also explain each API scope; keeping these on your own site is the safest.

Sources

kagentx

Can crawlers read your pages?
Let the evaluation tell you

The evaluation checks whether crawlers can get in and whether the text is served directly, then asks ChatGPT, Perplexity and Claude (with web search on) your buyers' questions and sees whether you are mentioned. The Basic plan is $1, and results usually take 2–3 minutes.