Guide · JetBrains plugins

How do AI search tools find JetBrains plugins? The Marketplace plugin page, tested

Updated 2026-11-12 · kagentx

Short answer

Tested on 2026-11-12: JetBrains Marketplace's robots.txt names no AI crawlers, and sitemap_index.xml contains a plugin sitemap with 24,943 URLs; but with scripts stripped, the plugin detail page's HTML has only a title, with no meta description, canonical or structured data, only og tags, and the description is rendered by script. So the first 40 characters of the description that the vendor requires (a short English overview) matter most, and they are also the opening read in og:description; write the rest of the introduction on your official site and in the README. Whether AI cites Marketplace pages, we have no evidence, so it is unverified.

Is JetBrains Marketplace open to crawlers?

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

CheckTest result
robots.txt200, 194 bytes: the * group blocks only /plugin/download, /plugins/list, /pluginManager and */ajax*; one Host line; one Sitemap line pointing to sitemap_index.xml
sitemap.xml404 (returns JSON: No static resource sitemap.xml), so the sitemap is not at this common path
sitemap_index.xml200, 502 bytes, 4 sub-sitemaps: plugins, IntelliJ Platform docs, TeamCity docs, Marketplace docs
plugin/sitemap.xml200, 2,795,011 bytes, 24,943 URLs, of which 24,939 are /plugin/<ID>-<name>; 23,139 have lastmod (the earliest is 2005-06-18)

A detail page URL is “ID + name”, and the name part comes from the plugin name, so the plugin name is also part of the URL.

What is in the HTML of a plugin detail page?

Almost only a title and og tags. We fetched the Key Promoter X page, plugins.jetbrains.com/plugin/9792-key-promoter-x (2026-11-12, curl, no scripts executed):

CheckTest result
HTTP status and size200, 84,790 bytes
title“Key Promoter X - IntelliJ IDEs Plugin | Marketplace”
meta description, canonical, JSON-LDNone
og tagsHas og:title, og:type, og:url, og:image (the plugin icon) and og:description (the start of the plugin description, truncated with ... at about 160 characters)
Visible text (scripts removed)78 characters, only the title; the description, version and rating are not in the visible body and are rendered by script
Changing the User-AgentWe fetched once each with GPTBot, ClaudeBot and PerplexityBot as the User-Agent string; all returned 200 with sizes of 84,771–84,789 bytes and the same page (this only compares responses and is not a visit by a real crawler)

So a crawler that doesn't run scripts gets only the title and the short piece of description in og:description on this page; for whether crawlers run scripts, see Do AI crawlers render JavaScript?. What real search crawlers can read is unverified. For writing titles and descriptions, see Do title and meta description matter for AI search?.

Marketplace also has a JSON API that needs no login: plugins.jetbrains.com/api/plugins/9792 (3,693 bytes), with fields such as name, description, preview, downloads, vendor, urls, tags, screens and icon; /api/plugins/9792/updates is 43,644 bytes. We have not confirmed in the official docs that this is a publicly promised interface, so we only say it can be fetched without login in our test.

What does JetBrains officially specify for plugin names and descriptions?

The “Best practices for listing” in the JetBrains Marketplace docs (page marked last updated 2026-07-23; original text read on 2026-11-12):

ItemOfficial statement
NameRecommended 1–4 words and at most 20 characters; hard limit of 60 characters; don't use the word “Plugin”, emoji or symbols; don't put JetBrains or a specific product name in the name
DescriptionThe first 40 characters must be a short overview in English; mainly English, spelled correctly, no marketing adjectives; images recommended at 600–800 pixels wide; you can keep SEO keywords in mind when writing the description but don't stuff them; the description is used on the Marketplace preview card
ScreenshotRecommended minimum of 1200 × 760 pixels; don't mix different aspect ratios; theme plugins should show their visual style; videos recommended under 5 minutes
IconsSimple and recognizable; preferably without text; don't just repeat the plugin name as text; you can also go without an icon
TagsChoose at least one when uploading; it affects searchability; don't choose categories the plugin doesn't belong to
Change notesWritten in the change-notes tag of plugin.xml; the latest shows in What’s new on the plugin page and in the IDE's plugin manager; if there is too much, you can make a Custom page
<idea-plugin>
  <id>com.example.csvtools</id>
  <name>Csv Tools</name>
  <description><![CDATA[
    Edit, validate and convert CSV files inside the IDE.
    <ul>
      <li>Highlights broken rows as you type</li>
      <li>Converts a selection to JSON</li>
    </ul>
  ]]></description>
  <change-notes><![CDATA[
    Fixes quoted fields that span two lines.
  ]]></change-notes>
</idea-plugin>

The above is a plugin.xml writing example: the first line of the description is a one-sentence English overview, which falls within the first 40 characters the vendor requires; this passage is also the opening that gets read in og:description. The vendor doesn't say how these fields affect AI citation, so we have no evidence and it is unverified.

How do you make a JetBrains plugin easier to find, step by step?

  1. 1. Write the first 40 characters of the description as a one-sentence definition

    “What it does, and in which IDE”, in English; this passage is both the overview the vendor requires, the opening of the preview card, and the part of og:description that crawlers can read.

  2. 2. Keep the name short and specific

    1–4 words; don't add Plugin and don't write JetBrains; the name goes into the detail page URL.

  3. 3. Choose the right tags

    At least one, and only those the plugin really belongs to. The vendor states that tags affect searchability.

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

    For crawlers that don't run scripts, the Marketplace page has only a title and og tags. On your official site, write out the features, supported IDE versions, install steps and changelog, and link to the Marketplace page. For how to write it, see Will AI search cite my GitHub README?.

  5. 5. Add SoftwareApplication data on your site

    For describing the same plugin, name the IDE in the runtime environment; for how to write it, see 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 an IntelliJ plugin for X”, asking each question 3 times, and note whether you are mentioned and which URLs are cited.

Comparable store guides: How do VS Code extensions get recommended by AI?, How do I get my Chrome extension recommended by AI?, How do Raycast extensions get found by AI search?.

FAQ

Can a crawler that doesn't run scripts read the description on a JetBrains Marketplace plugin page?

No. On 2026-11-12 we fetched the Key Promoter X plugin page with curl (84,790 bytes); with scripts stripped, only 78 visible characters remain (just the title); the description, version and rating are rendered by script. The HTML contains only og:description, which holds the start of the description. Whether real search crawlers run scripts is unverified.

What is the meta description of a plugin page?

There isn't one. The page has no meta name=description, no canonical and no JSON-LD, only og tags such as og:title and og:description; og:description is the start of the plugin description, truncated at about 160 characters.

Does JetBrains Marketplace have a sitemap?

Yes, but not at /sitemap.xml (that returns 404). The Sitemap line in robots.txt points to sitemap_index.xml, which has 4 sub-sitemaps; the plugin one has 24,943 URLs, 23,139 of which have lastmod.

Does robots.txt block AI crawlers?

It names none. In our 2026-11-12 test, robots.txt is 194 bytes: under User-agent: * it blocks only /plugin/download, /plugins/list, /pluginManager and */ajax*.

What are the requirements for plugin names?

The vendor recommends 1–4 words and at most 20 characters (hard limit 60), no “Plugin” in the name, no emoji or symbols, and no JetBrains or specific product names in the name.

What matters most at the start of the description?

The vendor states that the first 40 characters of the description must be a short overview in English; the description should be mainly English and avoid marketing adjectives; it also says you can keep SEO keywords in mind when writing the description but shouldn't stuff them, and that this text is used on the Marketplace preview card.

What are tags for?

The vendor states that you must choose at least one tag when uploading, that tags affect searchability, and that you shouldn't choose categories the plugin doesn't belong to.

How can AI find the plugin outside JetBrains Marketplace?

Write a full introduction page on your official site (features, supported IDEs, install steps, changelog), and link the GitHub README and the official site to each other. For crawlers that don't run scripts, the Marketplace page has only a title and og tags, so don't put key information only on the Marketplace.

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.