Unexpected Browser Notifications: Find the Source Before Clicking

Updated 13/10/2026 · Reviewed content

An unexpected alert can look like a message from a familiar service while coming from a website you allowed earlier. Start by identifying the sender and the kind of alert. Then change the relevant permission without following the message's call to action.

This i8 Live guide covers website notifications in Chrome on a computer and Android. It is not an i8 account notice or a diagnosis of your device. The examples and review worksheet below are our own; the browser-setting facts come from Google's documentation checked on 14 October 2026.

Identify what appeared before changing a setting

Google documents website notifications separately from pop-ups and redirects. Its pop-up help notes that messages can continue after pop-ups are disabled when a site has notification permission. Changing one control therefore does not necessarily address the other.

Use the visible context to decide where to look. A message painted inside a webpage needs a different investigation from an alert shown by the browser or operating system. If you cannot tell which it is, record what you can see rather than guessing.

These rows are a starting checklist, not a test that proves an alert's origin. Keep the browser name, site address if shown, and approximate time together. Do not use the message's logo alone to decide who sent it.

Review website notifications on a computer

Google's documented desktop route is Chrome Settings, then Privacy and security, Site Settings and Notifications. The page lets you choose a default behaviour and maintain site-specific allowed or blocked entries.

1. Open Chrome's menu yourself and choose Settings.
2. Open Privacy and security, Site Settings and Notifications.
3. Compare the site entries with the address recorded from the alert.
4. Use the site's available controls to block notifications you no longer want.
5. Return to the settings page and confirm the entry reflects your decision.

Use the address as the matching key. A friendly display name in an alert is less useful than the actual site entry when deciding which permission to change. If there is no matching entry, keep the sender unresolved and check whether another browser or app produced the alert.

The setting you choose controls notification permission. It does not decide whether every statement on that website is true, or whether the site has a relationship with a brand named in a message.

Review notifications on Android

Google's Android instructions place the general control under Chrome's menu, Settings, Site settings and Notifications. For a specific site, its documented route uses Page info beside the address bar, then Permissions. Some devices also offer Unsubscribe directly on a notification; Google describes that availability as device-dependent.

1. Open Chrome directly rather than tapping the alert's message.
2. Open Settings, Site settings and Notifications to review the notification control.
3. Check the relevant site entry and its current permission before changing it.
4. If you use Page info, first confirm that the address is the site you intend to manage.
5. Recheck the permission after saving the change.

Do not assume every Android phone presents identical labels. If an option is absent, follow the current Chrome help for your device instead of installing a tool recommended by the same unexpected message.

Work through an invented alert

Imagine a reader receives an alert headed “Match update” after browsing several sports pages. The notification identifies Chrome and a site the reader no longer recognises. Its message asks the reader to open a link urgently.

The reader records the visible sender, opens Chrome settings independently and finds the same site in the notification permissions list. They block that site's notifications, then verify the saved setting. They do not need to open the alert's destination to perform that review.

Now change one detail: the alert identifies a messaging app rather than Chrome. Looking only through Chrome's allowed sites would miss the relevant control. The useful first step remains identifying the sender, not repeating the same browser steps until something changes.

These are fictional situations. They illustrate how a small evidence record can guide the next action without turning an alert into proof of an account problem.

Keep a short record of the change

Our worksheet is intended to make the action reproducible. It is not a browser diagnostic report. When sharing a screenshot for help, crop out private messages, account identifiers and one-time codes; keep enough context to show the browser and relevant setting.

If alerts continue, check whether their sender is the same. A new sender or a different type of message needs a new investigation. Blocking one site's notification permission is not a complete review of the device or of every app installed on it.

Questions about website notifications

Is blocking pop-ups the same as blocking notifications?

No. Google documents separate controls. Identify which type of message you are seeing before selecting the setting to change.

Does an alert prove that my account has a problem?

The alert alone does not establish that. If you need to check an account, use a destination you independently know and verify the information there instead of treating the notification's wording as evidence.

Must I reopen an unwanted site to review it?

Start with Chrome's notification settings. If you use a site-specific Page info route, verify the address first; do not use the unexpected alert as your navigation shortcut.

What if the setting is unavailable?

Check the documentation for your current browser and device. Record the missing option and stop guessing. Avoid changing unrelated permissions simply because the notification control is hard to find.

Continue reading

Our account-access article covers destination checks and credentials. The Android installation guide covers downloaded files and installed-app permissions. Those are separate tasks from reviewing a website's permission to send notifications.