# Why the built-in addons search in about:addons gives different results comparing to AMO?

**URL:** <https://discourse.mozilla.org/t/why-the-built-in-addons-search-in-about-addons-gives-different-results-comparing-to-amo/9207>\
**Category:** addons.mozilla.org\
**Created:** [June 12, 2016, 8:21am UTC](https://discourse.mozilla.org/t/why-the-built-in-addons-search-in-about-addons-gives-different-results-comparing-to-amo/9207 "2016-06-12T08:21:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![erosman](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/erosman/32/15447_2.png) [@erosman](https://discourse.mozilla.org/u/erosman)\
**Post date:** [June 12, 2016, 8:21am UTC](https://discourse.mozilla.org/t/why-the-built-in-addons-search-in-about-addons-gives-different-results-comparing-to-amo/9207/1 "2016-06-12T08:21:11Z")

</div>

I noticed it when searching for a Fully Reviewed addon that I created recently. When searching on AMO, with a single keyword (refresh), it comes as as the 4th listed (both in the pop-up suggestions and the search result page) but when searching via the built-in addons search in _about:addons_, it doesn’t come up at all!!?

Are there some filtering involved (e.g. marketing, etc) or does _about:addons_ use a different server (which makes no sense) or does it use different criteria (which makes no sense either)?

---

<div class="post-metadata">

**Author:** ![eviljeff](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/eviljeff/32/30628_2.png) [@eviljeff](https://discourse.mozilla.org/u/eviljeff)\
**Post date:** [June 13, 2016, 11:39am UTC](https://discourse.mozilla.org/t/why-the-built-in-addons-search-in-about-addons-gives-different-results-comparing-to-amo/9207/2 "2016-06-13T11:39:37Z")

</div>

Assuming its ‘Refresh Blocker’ (Fully reviewed addon was a little vague) it’s 2nd place in about:addons and AMO for me. The only filtering should be platform/version filtering - i.e. about:addons is supposed to _only_ show compatible add-ons with that version of Firefox, whereas AMO will show some incompatible versions too but greyed-out.

---

<div class="post-metadata">

**Author:** ![erosman](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/erosman/32/15447_2.png) [@erosman](https://discourse.mozilla.org/u/erosman)\
**Post date:** [June 13, 2016, 12:39pm UTC](https://discourse.mozilla.org/t/why-the-built-in-addons-search-in-about-addons-gives-different-results-comparing-to-amo/9207/3 "2016-06-13T12:39:01Z")

</div>

@eviljeff … Thank you Andrew.  
yes… I was referring to Refresh Blocker… however, I was only using “ **refresh** ” as the search word.

When I search from Firefox Addon (FF47.0 Win7) I get:

[![](http://s31.postimg.org/406ty8d97/Refresh_about_addons.jpg) ](http://s31.postimg.org/406ty8d97/Refresh_about_addons.jpg)

The same search from AMO web site with “ **refresh** ” as the search word shows **Refresh Blocker** as its 4th item.

---

<div class="post-metadata">

**Author:** ![eviljeff](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/eviljeff/32/30628_2.png) [@eviljeff](https://discourse.mozilla.org/u/eviljeff)\
**Post date:** [June 14, 2016, 10:59am UTC](https://discourse.mozilla.org/t/why-the-built-in-addons-search-in-about-addons-gives-different-results-comparing-to-amo/9207/4 "2016-06-14T10:59:59Z")

</div>

![](https://us1.discourse-cdn.com/flex001/uploads/mozilla/original/2X/d/dda7b1f2b00189699b228b3e509825c68d574d30.png) 3rd for me this is on Fx49. And 2nd (oddly) on AMO. Maybe you have it installed already so it’s filtering it out?

---

<div class="post-metadata">

**Author:** ![erosman](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/erosman/32/15447_2.png) [@erosman](https://discourse.mozilla.org/u/erosman)\
**Post date:** [June 14, 2016, 11:34am UTC](https://discourse.mozilla.org/t/why-the-built-in-addons-search-in-about-addons-gives-different-results-comparing-to-amo/9207/5 "2016-06-14T11:34:06Z")

</div>

> [@eviljeff](#):
>
> Maybe you have it installed already so it’s filtering it out?

That could very well be it 🙂

PS. You seem to have more results than me 😛