This guide focuses specifically on Chrome for Android — stopping notification spam that arrives through Chrome’s website-notification feature, as distinct from notifications sent by separately installed apps.
Menu names and exact taps shift between Chrome versions, Android versions, device manufacturers, and languages, so treat the paths below as current starting points to search from if your screen looks slightly different — see Browser Notification Scams and How Permission Abuse Works for the underlying mechanism this guide assumes you already understand.
Is this a website notification or an app notification?
The first useful check is identifying the Android app that delivered the alert, because Chrome website notifications and separately installed app notifications use different controls. Where Android provides it, long-press the notification or open its notification settings to see the responsible app. If Android identifies Chrome, inspect the website origin shown in the notification or review Chrome’s allowed sites. If Android identifies another app, use that app’s notification and permission settings. A missing web address alone is not enough to conclude which source sent it, because layouts vary.
Path 1: block one specific website
According to Google’s current Chrome Help documentation, this is done as follows: open Chrome on your Android device, go to the site whose notifications you want to stop, tap the icon to the left of the address bar (labeled “Page info” or similar), and tap Permissions. If a menu opens showing notification settings for that site, select the option to turn notifications off. If no menu opens, the site’s permissions remain at their original, unset state, meaning it has not yet been separately granted notification access through this path.
Path 2: review all website notification permissions
To review notification settings across sites rather than opening one site first, open Chrome, tap the three-dot menu, tap Settings, then Site settings, then Notifications. The current screen can show the broad notification control and site-specific entries available in that Chrome profile. Select the relevant origin to inspect or change its setting. Labels and grouping can vary with Chrome releases.
Path 3: stop future notification requests, where your Chrome version supports it
From the same Site settings → Notifications screen, a toggle near the top controls whether sites can prompt you to allow notifications at all going forward. Turning this off stops the request itself from appearing for new sites, rather than requiring you to decline each one individually as it comes up. This does not retroactively remove permissions already granted to sites before you changed the setting — those still need to be revoked individually through Path 1 or Path 2.
Path 4: disable Chrome notifications at the Android system level, as a broad fallback
Android’s per-app notification controls can suppress Chrome notifications broadly. Android documents that settings vary by phone; a common route is Settings → Notifications → App notifications → Chrome, followed by the available notification control. This is broader than Paths 1 through 3. The Android app-level switch controls whether Chrome’s notifications are shown by the system; it is not the same setting as a website origin’s permission stored inside Chrome. Revoking the specific origin remains the more targeted action when one site is responsible.
How Chrome handles sites it identifies as abusive
According to Google’s Chrome Help documentation, Chrome can automatically detect notification behavior it identifies as deceptive or spam-like and block that site’s notifications, requiring the site to request permission again before it can resume sending them. When this happens, you may see a notification-style warning from Chrome itself flagging the behavior, with an option to report it as spam. This automatic detection is a helpful backstop, but it depends on Chrome having already identified a specific pattern as abusive — it is not a guarantee that every unwanted or low-quality notification source gets caught this way, which is part of why the manual paths described above remain useful even when this automatic handling exists.
A quick comparison of the four paths
| Path | Scope | When it fits |
|---|---|---|
| Path 1: block one site | One specific website | You know which site is sending unwanted notifications |
| Path 2: review all permissions | Every site currently permitted | You want to audit everything at once, or are not sure which site is responsible |
| Path 3: stop future prompts | Sites you have not yet decided about | You want to stop being asked entirely, going forward |
| Path 4: system-level toggle | All of Chrome’s notifications | You want a broad, temporary fallback rather than a targeted fix |
Path 5: diagnosing notifications that continue
If unwanted notifications continue after you believe you have revoked the relevant permission, consider these possibilities before assuming the block failed:
If the alerts use an urgent security warning or a “verify you are human” story, see Browser Notification Scams and How Permission Abuse Works for how deceptive website notifications work and Fake CAPTCHA Scams: Warning Signs and Safe Responses for the separate pattern that asks people to run commands.
- A different browser or profile — if you use more than one browser or Chrome profile, the permission may still be active in a profile or browser you did not check.
- An installed app, not a website — revisit the “website versus app” check above; Chrome’s settings have no effect on a separately installed app’s notifications.
- A different but similarly named site — read the displayed origin carefully rather than assuming which site it is from memory, since a similarly named or spelled domain is a different permission entirely. See How to Tell Whether a Link Is Safe Before You Click for the general habit of reading an address carefully rather than at a glance.
- An alert already displayed — revoking permission prevents later delivery from that origin but does not necessarily dismiss an alert already present in Android’s notification shade; dismiss it separately.
Notification history and its limits
Some Android devices offer notification history, which can show recently dismissed alerts and help identify a source you missed. Google notes that some devices do not provide the feature and that settings can vary. If it is available, treat the recorded app and time as diagnostic clues; the history entry does not by itself prove that the message was legitimate or that its linked destination was safe.
What clearing history and site data does and does not do
Clearing your Chrome browsing history does not revoke notification permissions — history and permissions are tracked separately. Clearing site data or resetting all permissions has a broader effect than just notifications, potentially affecting saved logins, site preferences, and other stored data for that site — this is not a step to take casually just to solve a notification problem when Path 1 or Path 2 addresses it more precisely.
Recovery: page merely opened
If the page merely opened and you did not download or open a file, install an app, grant a permission, or submit information, close it. That page view alone does not establish device compromise and does not require a factory reset.
Recovery: credentials entered
Change that password immediately on the real site, reached independently, and anywhere else the same password was used.
Recovery: verification code shared
Contact the relevant account provider through its official app or independently reached site, change the password where appropriate, review recent activity and active sessions, and remove any unfamiliar linked device or recovery method. A verification code can authorize a specific sign-in or recovery action, so changing a password alone may not end an already authorized session.
Recovery: payment information entered
Contact your card issuer or bank through the number on the card or its official app. Explain what was submitted and follow its advice on monitoring, blocking, or replacing the card. Dispute a transaction only if an unauthorized charge appears or the issuer directs you to do so.
Recovery: money sent
Contact your bank or payment provider immediately; whether the transfer can be stopped or reversed depends on the specific method and how quickly you act.
Recovery: file downloaded
An unopened file can simply be deleted. If it was opened, treat it as the next scenario.
Recovery: app or APK installed
Uninstall it through Android’s app-management settings, review permissions it received, and run Play Protect or another updated security scan. Uninstalling and scanning are useful steps but do not guarantee that every change made while the app ran has been reversed.
Recovery: accessibility, device-management, or other sensitive permission granted
Revoke the specific permission through the relevant Android settings and uninstall the unfamiliar app that requested it. Review device-admin apps, accessibility services, VPNs, and installed apps for other entries you do not recognize. Run an updated security scan and seek qualified help if a management control cannot be removed or you cannot determine what access the app used.
Managing installed-app notifications, for comparison
For a notification confirmed to come from an installed app rather than a website, Android’s own per-app notification settings apply instead of anything in Chrome: open the device’s Settings app, go to Notifications → App notifications, find the specific app, and adjust its notification settings there. This is a completely separate control from anything covered above for Chrome’s own website-notification permissions.
What this guide does not claim
None of the steps above remove installed software, reverse a payment already sent, or secure a password already exposed — each of those requires its own specific recovery step from the sections above, not just blocking a notification. A security scan reduces risk but does not guarantee full recovery on its own. Reinstalling Chrome or performing a factory reset is not something this scenario automatically requires; it becomes more relevant only if a device continues behaving unexpectedly after the more targeted steps above.
Frequently asked questions
Will blocking one site’s notifications affect other sites?
No — Path 1 is specific to the one site you select. Other sites’ permissions are unaffected.
Does turning off Chrome notifications at the Android system level delete the underlying permission?
No — it suppresses Chrome’s notifications broadly while the system-level toggle is off, but the site-level permission itself remains recorded inside Chrome, which matters if you later turn Chrome’s notifications back on system-wide.
Is desktop Chrome or Firefox managed the same way?
The permission concept is similar, but desktop browsers use different interfaces. Follow that browser’s current official notification guide rather than copying the Android paths above; this article’s detailed steps are specific to Chrome on Android.
