Ext Ops Panel
Open dashboard
Permissions and history

Is Bulk URL Remover for Google Search Console (GSC) safe to install?

Bulk URL Remover for Google Search Console (GSC) asks for 1 browser permission and 3 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.

Bulk URL Remover for Google Search Console (GSC)

Chrome extension by yep.az · Productivity · Workflow

Open in the Chrome Web Store
What the developer says, and 4 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
Declares it collects none
Audience
37 users · 5.0/5

What data it declares

The developer declares that it does not collect or use your 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: 3 match patterns.

Routine for an extension

Pages it runs its code on

It runs its own code on specific pages only: 1 site pattern.

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 · Workflow, 19% 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 1 browser permission.

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

37 users

Users
+15 since 01.09
21-37 · 37 readings
2026-11-17: released 2.0.0
  1. 2026-09-0122
  2. 2026-09-0224
  3. 2026-09-0421
  4. 2026-09-0522
  5. 2026-09-0621
  6. 2026-09-0825
  7. 2026-09-0923
  8. 2026-09-1324
  9. 2026-09-1526
  10. 2026-09-1622
  11. 2026-09-2028
  12. 2026-09-2127
  13. 2026-09-2630
  14. 2026-10-0427
  15. 2026-10-0828
  16. 2026-10-0929
  17. 2026-10-1030
  18. 2026-10-1331
  19. 2026-10-1630
  20. 2026-10-1929
  21. 2026-10-2030
  22. 2026-10-2227
  23. 2026-10-2526
  24. 2026-10-2827
  25. 2026-10-2930
  26. 2026-10-3029
  27. 2026-11-0128
  28. 2026-11-0427
  29. 2026-11-0628
  30. 2026-11-0729
  31. 2026-11-0831
  32. 2026-11-1032
  33. 2026-11-1133
  34. 2026-11-1432
  35. 2026-11-1534
  36. 2026-11-1735released 2.0.0
  37. 2026-11-2037

What the store shows

The listing says it offers in-app purchases.

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.

  1. Asked for fewer permissions (4, was 6) (changed: site access, pages it runs its code on, browser permissions)

Versions we have seen

  1. Version 2.0.0 · Asked for fewer permissions (4, was 6) (changed: site access, pages it runs its code on, browser permissions)

Who publishes it

yep.az, who publishes 10 listings we track. This listing has been in the store since 2025-12-13 and was last updated on 2026-11-17.

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. Google Search Console URL Removal Automation Runs its code on every site · No permissions declared 15 users ★ 5.0

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 Bulk URL Remover for Google Search Console (GSC) access?
Specific sites only: 3 match patterns. It declares 1 browser permission.
What data does Bulk URL Remover for Google Search Console (GSC) collect?
The developer declares that it does not collect or use your data. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Bulk URL Remover for Google Search Console (GSC) asked for more permissions over time?
Its permissions changed once while we watched, on 2026-11-17.
Does Bulk URL Remover for Google Search Console (GSC) 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-20.

Back to Bulk URL Remover for Google Search Console (GSC) · Alternatives to Bulk URL Remover for Google Search Console (GSC)

Where the data comes from: how the catalog is built