Does the Raycast Store let AI crawlers in? Is the page server-rendered?
Yes, and the body is server-rendered. Tested on 2026-11-11: raycast.com's robots.txt blocks only four account and upgrade paths and names no AI crawler, so GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended and Bingbot all fall under the * group and are allowed. On an extension detail page (we fetched thomas/color-picker) the title, description, author, install count, command names and the full README can be read without running scripts.
| Check | Test result (2026-11-11) |
|---|---|
| robots.txt | * group Allow: /, only /upgrade, /settings/sessions, /handles/new and /users/confirmation blocked; no AI crawler named |
| Detail page HTTP status and size | 200; Color Picker about 185 KB, the GitHub extension about 346 KB |
| <title> | “Raycast Store: extension name”, from the title in package.json |
| meta description | Identical to the description in package.json (Color Picker: Pick and organize colors, everywhere on your Mac) |
| Is the body in the HTML? | Yes: author, install count, full README and command names are in the HTML; there is no structured data (JSON-LD) |
| sitemap.xml | 98 URLs, only the home page, store home, feature pages, blog and so on; neither of the two extension detail pages we checked is in it; other sitemaps not verified |
Conclusion: on Raycast, what crawlers can read is what you write in package.json and the README. Extension detail pages are not in the sitemap we read, so crawlers have to find them through the store list pages and links, which means links to your store page from elsewhere (your GitHub README, your website) help. For whether crawlers run scripts see Do AI crawlers render JavaScript?.
How do package.json fields become the store page?
An extension's package.json is public, in the github.com/raycast/extensions repository (we read color-picker's package.json and compared it with its store page). The field descriptions come from the Raycast developer docs (developers.raycast.com, viewed 2026-11-11).
| package.json field | Docs | What the store page shows (Color Picker) |
|---|---|---|
| title | The title shown in the Store and in Preferences; describe the extension well so users can find it | Page <title> and heading: Color Picker |
| description | The full description shown in the Store | The meta description and the sentence under the heading, identical |
| commands[].title, description | The name and description of each command | Command names are in the HTML, such as Pick Color; the list shows the command count (9 Commands) |
| README.md | The description file in the extension directory | The body of the Overview tab: features, API, options, all in the HTML |
| author | Your Store username | The “thomas” in the page address /thomas/color-picker |
| platforms | Supported systems: macOS or Windows | The list shows a “macOS only” label |
| keywords | Users who search for these words in the Store can find the extension | Used by in-store search; we did not verify whether it appears in the page source |
| categories | The category the extension belongs to | How the category is shown on the page: not verified |
{
"$schema": "https://www.raycast.com/schemas/extension.json",
"name": "example-ext",
"title": "Example Ext",
"description": "One sentence: what it does and for whom",
"icon": "icon.png",
"author": "your-handle",
"platforms": ["macOS"],
"categories": ["Productivity"],
"license": "MIT",
"commands": [
{
"name": "search-notes",
"title": "Search Notes",
"description": "Search your notes by title and content",
"mode": "view"
}
]
}
The above is an example of how to write it (names are placeholders). Note that description is both the meta description and the page subtitle: say “what it does, for whom” in one sentence, not a slogan. The release notes are on the Version History tab, whose content we did not verify.
How do the discovery channels of Raycast, Alfred and the Chrome Web Store differ?
For a developer writing an extension for a productivity tool, the pages on the three channels behave differently toward AI crawlers. On 2026-11-11 we tested one page on each.
| Channel | robots.txt | Page title and meta description | Structured data | Is the body in the HTML? |
|---|---|---|---|---|
| Raycast Store (raycast.com) | Only account and upgrade paths blocked | title “Raycast Store: name”; the description is your description | None | Yes, the full README |
| Alfred Gallery (alfred.app/workflows/) | alfred.app returns 404 and www.alfredapp.com returns an empty file; neither has rules | title “Alfred Gallery • Workflows • name”; the description is “name: one sentence” | None | Yes: version, author, usage |
| Chrome Web Store (chromewebstore.google.com) | Blocks sub-pages such as reviews, privacy and support, and addresses with tracking parameters | title “name - Chrome Web Store”; the description is the one-sentence summary | None | Yes, including the rating and rating count |
The detail pages on all three channels have a body that does not depend on scripts, and none has structured data, so the difference is not “can it be read” but “whose words are read”: on Raycast and Alfred it is the description and README you wrote, and on the Chrome Web Store it is the summary you entered. For how to write for Chrome extensions see How do I get my Chrome extension recommended by AI?; for the matching advice on VS Code extensions see How do VS Code extensions get recommended by AI?.
How do you make a Raycast extension easier to find, step by step?
1. Write the description as a one-sentence definition
“What it does, for whom, what it replaces”; it is both the subtitle on the store page and the meta description.
2. Make each command's title and description specific
Command names appear in the store page HTML, and users and crawlers use them to judge what the extension can do; start with a verb: Search Notes, not Main.
3. Let the first paragraph of the README answer “what is it, how do I use it”
The README is the body of the store page's Overview; put features, options and screenshot captions here. For how to write it see How should a GitHub README be written so AI quotes it?.
4. Link to the store page from your own GitHub README and website
The sitemap we read has no extension detail pages; links from elsewhere help crawlers find it. For how to add SoftwareApplication data to your website see Should a SaaS add SoftwareApplication structured data?.
5. First make sure your website does not block search crawlers
Use AI crawler check to look at robots.txt.
6. Test again after a few weeks with the same questions
Ask ChatGPT and Perplexity “what Raycast extensions do X”, three times per question, and note whether you are mentioned and which URLs are cited.
JetBrains Marketplace plugin pages are script-rendered; the test and the official listing rules are in How do AI search tools find JetBrains plugins? The Marketplace plugin page, tested.
FAQ
Will ChatGPT cite a Raycast Store page?
We found no official statement and no evidence of actual citations (not verified). What we can confirm: on 2026-11-11 raycast.com's robots.txt places no restriction on AI crawlers, and the extension detail page's body is written straight into the HTML.
Where does the store page's meta description come from?
Tested on 2026-11-11: Color Picker's meta description is identical to the description in package.json, so write the description as the snippet for search results.
Does the README matter for a Raycast extension?
Yes. The store page's Overview tab renders the README body (on the Color Picker page we fetched, Key Features and the API notes can be read), and it is the longest stretch of your own writing a crawler can read.
Why isn't my extension page in the sitemap?
The raycast.com/sitemap.xml we read has 98 URLs and no extension detail pages; other sitemaps are not verified. This is not a problem with your extension, but it means links from elsewhere (README, website, articles) are more useful for crawlers finding your page.
Should a Raycast extension also support Windows?
platforms in package.json can be macOS or Windows, depending on the APIs your extension uses. The store list has labels such as “macOS only”; state the supported systems accurately so users and AI have a clear basis when answering “does it work on Windows”.
Can an Alfred workflow and a Raycast extension share one description?
Yes. The detail pages on both channels render the one-sentence description and the usage you wrote; use the same sentence at different lengths and keep the wording for names and features consistent.
Should I build a website for the extension?
We suggest at least one page: say what the extension does, which systems it supports, how to install it, and the changelog, and link to the store page. Someone else sets the store page format; the website is where you can write it all.
Sources
- Raycast · raycast.com/robots.txt and sitemap.xml (Read 2026-11-11)
- Raycast · Example extension page: Color Picker (checked for what the HTML contains) (Read 2026-11-11)
- GitHub · raycast/extensions: color-picker package.json (read via raw.githubusercontent.com) (Read 2026-11-11)
- Raycast · Manifest (checked 2026-11-11)
- Raycast · Publish an Extension (checked 2026-11-11)
- Alfred · Example Alfred Gallery workflow page; alfred.app/robots.txt returned 404 (Read 2026-11-11)
- Chrome Web Store · chromewebstore.google.com/robots.txt and an example extension page (Read 2026-11-11)
- kagentx evaluations: the data on the case study pages; each example gives its date.