Ext Ops Panel
Open dashboard
Permissions and history

Is SearchDuo safe to install?

SearchDuo asks for 2 browser permissions and 187 site patterns. We do not audit code and we do not judge intent; what we can show is what the listing declares and whether that has changed while we have been watching.

SearchDuo

Chrome extension by yeheboo · Productivity · Tools

Open in the Chrome Web Store
What the developer says, and 2 screenshots

Loading from the Chrome Web Store. Open the listing if it does not appear.

At a glance

Facts, not a score: an ad blocker needs every page and a theme needs nothing, so one number would be wrong about both. Each fact links to its detail.

Site access
Access to specific sites only
Data collection
2 kinds of data declared
Audience
47 users · 5.0/5

What data it declares

The developer declares that it collects these kinds of data:

The developer also certifies that your data is not sold to third parties outside approved uses, not used for purposes unrelated to the extension's core function, and not used to decide creditworthiness or lending.

The listing links to a privacy policy.

This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.

What Chrome asks you to allow

When you add it, Chrome asks you to allow it to:

Derived from the manifest by Chrome's documented rules; the dialog's exact wording depends on your Chrome version and language. Chrome asks again if an update requests more.

What it can reach

Specific sites only: 187 match patterns.

Routine for an extension

Pages it runs its code on

It runs its own code on specific pages only: the first 50 site patterns we keep.

Show the remaining 47
  • *://*.google.com.af/search* google.com.af and all its subdomains
  • *://*.google.com.ag/search* google.com.ag and all its subdomains
  • *://*.google.al/search* google.al and all its subdomains
  • *://*.google.am/search* google.am and all its subdomains
  • *://*.google.co.ao/search* google.co.ao and all its subdomains
  • *://*.google.com.ar/search* google.com.ar and all its subdomains
  • *://*.google.as/search* google.as and all its subdomains
  • *://*.google.at/search* google.at and all its subdomains
  • *://*.google.com.au/search* google.com.au and all its subdomains
  • *://*.google.az/search* google.az and all its subdomains
  • *://*.google.ba/search* google.ba and all its subdomains
  • *://*.google.com.bd/search* google.com.bd and all its subdomains
  • *://*.google.be/search* google.be and all its subdomains
  • *://*.google.bf/search* google.bf and all its subdomains
  • *://*.google.bg/search* google.bg and all its subdomains
  • *://*.google.com.bh/search* google.com.bh and all its subdomains
  • *://*.google.bi/search* google.bi and all its subdomains
  • *://*.google.bj/search* google.bj and all its subdomains
  • *://*.google.com.bn/search* google.com.bn and all its subdomains
  • *://*.google.com.bo/search* google.com.bo and all its subdomains
  • *://*.google.com.br/search* google.com.br and all its subdomains
  • *://*.google.bs/search* google.bs and all its subdomains
  • *://*.google.bt/search* google.bt and all its subdomains
  • *://*.google.co.bw/search* google.co.bw and all its subdomains
  • *://*.google.by/search* google.by and all its subdomains
  • *://*.google.com.bz/search* google.com.bz and all its subdomains
  • *://*.google.ca/search* google.ca and all its subdomains
  • *://*.google.cd/search* google.cd and all its subdomains
  • *://*.google.cf/search* google.cf and all its subdomains
  • *://*.google.cg/search* google.cg and all its subdomains
  • *://*.google.ch/search* google.ch and all its subdomains
  • *://*.google.ci/search* google.ci and all its subdomains
  • *://*.google.co.ck/search* google.co.ck and all its subdomains
  • *://*.google.cl/search* google.cl and all its subdomains
  • *://*.google.cm/search* google.cm and all its subdomains
  • *://*.google.cn/search* google.cn and all its subdomains
  • *://*.google.com.co/search* google.com.co and all its subdomains
  • *://*.google.co.cr/search* google.co.cr and all its subdomains
  • *://*.google.com.cu/search* google.com.cu and all its subdomains
  • *://*.google.cv/search* google.cv and all its subdomains
  • *://*.google.com.cy/search* google.com.cy and all its subdomains
  • *://*.google.cz/search* google.cz and all its subdomains
  • *://*.google.de/search* google.de and all its subdomains
  • *://*.google.dj/search* google.dj and all its subdomains
  • *://*.google.dk/search* google.dk and all its subdomains
  • *://*.google.dm/search* google.dm and all its subdomains
  • *://*.google.com.do/search* google.com.do and all its subdomains

We keep the first 50 patterns of a list; the manifest may declare more.

A content script is code the extension injects into pages matching these patterns. On those pages it can read and change what you see, whether or not a host permission is listed above.

How usual this is for its category

In Productivity · Tools, 20% of extensions ask for access to every site. This one: Access to specific sites only.

The typical extension there declares 3 browser permissions; this one declares 2 browser permissions.

Counted over the live extensions of the same category after our latest full pass of the store. A share is context, not a verdict: what is normal depends on what the extension is for.

Who uses it and how it is kept up

47 users

Users
+6 since 01.09
37-47 · 27 readings
  1. 2026-09-0141
  2. 2026-09-0244
  3. 2026-09-0443
  4. 2026-09-0644
  5. 2026-09-0943
  6. 2026-09-1042
  7. 2026-09-1339
  8. 2026-09-1540
  9. 2026-09-2046
  10. 2026-09-2247
  11. 2026-09-2542
  12. 2026-09-2643
  13. 2026-10-0441
  14. 2026-10-0837
  15. 2026-10-0938
  16. 2026-10-1037
  17. 2026-10-1139
  18. 2026-10-1639
  19. 2026-10-1840
  20. 2026-10-1939
  21. 2026-10-2142
  22. 2026-10-2241
  23. 2026-10-2343
  24. 2026-10-2441
  25. 2026-10-2543
  26. 2026-10-2745
  27. 2026-11-0147

What the store shows

Has it asked for more over time?

This is the question a permission list on its own cannot answer. An extension that shipped narrow and widened later is a different proposition from one that always asked for the same thing.

The permissions this extension requests have not changed since we started watching it.

Who publishes it

yeheboo, who publishes 8 listings we track. This listing has been in the store since 2025-03-18 and was last updated on 2025-03-18.

Similar extensions that ask for less

Listings close to this one in what they say they do, which declare less reach. Less reach is not a verdict on either: compare what each needs for the job.

  1. SearchLayout - 搜索结果布局 No site access · 1 permission 4 users
  2. Google 100 Results: Now you can have this again in google search settings! No site access · 1 permission 10k users ★ 3.0
  3. Searchhub No site access · 2 permissions 17 users

How to check or remove it in Chrome

  1. Type chrome://extensions in the address bar and find the extension in the list.
  2. Open its details. The site access setting shows where it can run; set it to run only on click and it reaches a page only after you press its icon.
  3. To uninstall it, choose Remove on the same page.

Questions people ask

What can SearchDuo access?
Specific sites only: 187 match patterns. It declares 2 browser permissions.
What data does SearchDuo collect?
The developer declares that it collects these kinds of data: Personally identifiable information, User activity. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has SearchDuo asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does SearchDuo publish a privacy policy?
Yes, the store listing links to a privacy policy.

We read the public store listing up to 2 times a day and keep what it declared. We do not install the extension, do not audit its code, do not judge its intent and publish no contact details for its developer. Last read on 2026-11-01.

Back to SearchDuo · Alternatives to SearchDuo

Where the data comes from: how the catalog is built