Are the Firefox and Edge add-on stores open to crawlers?
Neither blocks AI crawlers, but they differ a lot. On 2026-11-12 we tested both robots.txt files and sitemaps with curl:
| Check | Firefox (addons.mozilla.org) | Edge (microsoftedge.microsoft.com) |
|---|---|---|
| robots.txt | 200, 13,735 bytes; the * group says Allow: / and blocks only download paths, plus search and collection pages under each language directory; no AI crawler is named and there is no Sitemap line | 200, but it returns HTML (51,288 bytes, no rules at all), not a robots.txt; no Sitemap line |
| sitemap.xml | 200, an index with 8,227 child sitemaps; 2,000 URLs per page with lastmod and multilingual hreflang; URL form /addon/<slug>/ | 200, 4,390 URLs, of which 4,336 are /addons/detail/<ID>; this is only what the sitemap lists, and the store's total is unverified |
| Detail page URL | A slug with the name, for example /addon/ublock-origin/ | Only a 32-character ID; the name is not in the URL |
One detail worth noting: Edge's robots.txt returns HTML. Naver's official guide says this can be read as no robots.txt, meaning everything allowed; we did not verify how other crawlers treat it.
What does a crawler read from an Edge add-on detail page?
Almost only the title. We took three detail pages from Edge's sitemap (2026-11-12, curl, no scripts executed):
| Check | Test result |
|---|---|
| HTTP status and size | All three returned 200, about 51 KB |
| <title> | "Extension name - Microsoft Edge Add-ons"; one of the three had just "Microsoft Edge Add-ons", with no name |
| meta description | All three pages had the same generic store sentence: Make Microsoft Edge your own with extensions..., not the extension's own summary |
| canonical, structured data, og tags | None |
| Body text | About 1,100-1,200 visible characters once scripts are removed, all of it Microsoft's site header and footer; the extension name appears only once, in the <title>; description, rating and version are not in the HTML |
So a crawler that does not run JavaScript can read only the extension name on the Edge store. Whether crawlers run scripts is covered in Do AI crawlers render JavaScript?. Conclusion: put the key description on your own website and do not expect the store page to carry descriptive information; for the same test on the Chrome Web Store see How do I get my Chrome extension recommended by AI?.
What about Firefox add-on detail pages?
We could not get the raw HTML. On 2026-11-12 we requested the ublock-origin, darkreader and privacy-badger17 pages with curl, trying the Mozilla/5.0, Chrome 130 and curl User-Agents, and every time we got the same 3,038-byte page titled "Client Challenge", which asks the browser to run a script. That is the result from our network exit; whether real search crawlers face the same challenge is unverified.
Opening the ublock-origin page from a different exit with a reading tool (converted and summarized, not raw HTML) showed the name, summary, user count, rating, permissions, version, update date, category and tags. So the page is complete for browsers; whether it is server-rendered is unverified.
Firefox's advantage is public data: addons.mozilla.org/api/v5/addons/addon/<slug>/ returns JSON without signing in (137,940 bytes for ublock-origin).
| API field | Meaning (measured value for ublock-origin) |
|---|---|
| name, summary, description | Dictionaries keyed by language (name has ar, bg, de, en-US, es-ES and more); the en-US description is 2,216 characters |
| tags, categories | tags are ad blocker, anti malware, anti tracker, content blocker, privacy, security; categories is privacy-security |
| default_locale | en-US |
| homepage, support_url | The website and support address the developer entered, which can differ by language |
| average_daily_users, weekly_downloads, ratings | 11,480,087 users; rating 4.8 from 22,293 reviews |
| promoted | recommended (firefox, android): Mozilla's recommendation badge |
| is_noindexed | false: this field says whether the listing is marked as not to be indexed by search engines; you can check its value for your own add-on in the API |
What do the two vendors officially require for listings?
| Item | Firefox (Mozilla Extension Workshop) | Edge (Microsoft Learn) |
|---|---|---|
| Name | Must be unique and descriptive; a unique name also gives a unique AMO slug | Use the extension name; "Extension name" comes from the manifest in the package |
| Short description | Summary limited to 250 characters, as short as possible while stating the key features and benefits | Comes from the manifest description field; re-upload the package to change it |
| Full description | No length limit; open strongly, and HTML formatting and bullet lists are available | Minimum 250 and maximum 10,000 characters, describing all functionality |
| Keywords | Entered as tags and used naturally in the summary and description; "forcing keywords in won’t help" | Search terms are optional, up to 21 words, and not shown to users |
| Categories | Pick the right category (Categorize well) | Required |
| Screenshot | No practical limit; 1280x800 or a 1.6:1 ratio recommended; put the explanation in text rather than in the image | Up to 6, at 640x480 or 1280x800 |
| Languages | Almost all listing text can be localized | Fill in each language separately |
The Firefox page has no date; we read it on 2026-11-12. Edge's Learn page says it was last updated 2026-08-12. Neither says how these fields affect AI search, so we have no evidence about which fields AI cites; unverified.
{
"manifest_version": 3,
"name": "Example Notes Search",
"description": "Search your notes by title and content from the toolbar.",
"version": "1.0.0"
}
The sample above is illustrative: the manifest description is also Edge's short description, so make the first sentence say what it does and for whom.
How do I make an add-on easier to find, step by step?
1. Write one page on your site that is fuller than the store page
The store page format is set by someone else, and Edge's page HTML does not even contain the description. Write one page on your own site covering features, supported browsers, install steps, changelog and privacy notes, and link it to your Firefox and Edge store pages. For how to write it see Do title and meta description matter for AI search?.
2. Make the name unique on Firefox
The docs say a unique name gives a unique slug, and the slug is part of the URL.
3. Make the first sentence of the summary a one-line definition
"What it does, for whom, replacing what"; Firefox limits it to 250 characters and Edge's description needs at least 250, so write two versions.
4. Fill in Edge's search terms and category separately
Search terms take up to 21 words and are how users find you in the store; the category is required.
5. Add SoftwareApplication data on your site
Describe the same add-on, with the browser name as the operating environment; for how to write it see Should a SaaS add SoftwareApplication structured data?.
6. Test again after a few weeks with the same questions
Ask ChatGPT and Perplexity "is there a Firefox or Edge extension that does X", three times per question, and note whether you are mentioned and which URLs are cited. For the AI entry points Edge users have, see How do I get my product recommended by Microsoft Copilot?.
Comparable stores: How do I get my Chrome extension recommended by AI?, How do VS Code extensions get recommended by AI?, How do Raycast extensions get found by AI search?.
FAQ
Will AI read Edge add-on store pages?
Test on 2026-11-12: a detail page's HTML contains only the extension name (in the title); the meta description is the generic store sentence, and the description and rating are rendered by script. A crawler that does not run scripts cannot read them. Whether AI cites them is unverified.
Are Firefox add-on pages server-rendered?
Unverified. Our curl got only a "Client Challenge" page with three different User-Agents; opening it with a reading tool showed the full page.
Why is Edge's robots.txt HTML?
We measured microsoftedge.microsoft.com/robots.txt returning 200 and an HTML shell with no rules. We did not verify the reason.
How long can the Firefox summary and Edge description be?
The Firefox summary is limited to 250 characters; the Edge description must be at least 250 and at most 10,000 characters, and the short description comes from the manifest description field.
How should I fill in keywords?
Firefox turns keywords into tags and wants them used naturally in the summary and description, saying forcing them in does not help; Edge's search terms take up to 21 words and are not shown to users.
Should I put my website link on the store listing?
Yes. Firefox's API has homepage and support_url fields; Edge's properties page has an optional Website. Your website is where you can write the full introduction.
How do I check whether my Firefox add-on is marked as not indexable?
Open addons.mozilla.org/api/v5/addons/addon/<your slug>/ and look at the is_noindexed field. We saw only false, on ublock-origin.
How is this different from the Chrome Web Store?
Chrome's detail page has the title and summary in the HTML, see the other guide; Edge's has only the title; for Firefox we did not get raw HTML.
Sources
- Mozilla · addons.mozilla.org/robots.txt and sitemap.xml (Read 2026-11-12)
- Mozilla · AMO API v5: example add-on (checked for fields) (Read 2026-11-12)
- Mozilla · Create an appealing listing (Read in full 2026-11-12, page has no date)
- Microsoft Edge · microsoftedge.microsoft.com/robots.txt, sitemap.xml and three detail pages (Read 2026-11-12)
- Microsoft Learn · Publish an extension in the Microsoft Edge Add-ons website (Read in full 2026-11-12, page says last updated 2026-08-12)
- kagentx evaluations: the data on the case study pages; each example gives its date.