{"id":2347,"date":"2020-02-28T18:52:53","date_gmt":"2020-02-28T18:52:53","guid":{"rendered":"https:\/\/www.aseohosting.com\/blog\/?p=2347"},"modified":"2025-05-06T16:11:59","modified_gmt":"2025-05-06T16:11:59","slug":"why-you-should-avoid-website-notification-prompts","status":"publish","type":"post","link":"https:\/\/www.aseohosting.com\/blog\/2020\/02\/why-you-should-avoid-website-notification-prompts\/","title":{"rendered":"Why You Should Avoid Website Notification Prompts"},"content":{"rendered":"\n

In January, Google announced that version 80 of Chrome, which launched in early February, would start blocking website push notifications<\/a>. For users who consistently block these notifications, blocking will be enabled by default. Blocking will also be enabled on websites with low opt-in rates.<\/p>\n\n\n\n

We estimate that most <\/em>websites have low opt-in rates.  The problem is that too many brands are terribly pushy <\/em>with their notification prompts. They start pestering the user the moment they open the site.<\/p>\n\n\n\n\n\n\n\n

You\u2019ve likely experienced this yourself <\/h2>\n\n\n\n

You\u2019re searching for something online and click on a promising article on the search engine results page. Before you can even start reading the content, a box pops up over your address bar, pulling your focus.\u00a0<\/p>\n\n\n\n

 \u201cWEBSITE WOULD LIKE TO SEND NOTIFICATIONS.\u201d <\/p>\n\n\n\n

If you\u2019re anything like most people, your first instinct is to click the block button, annoyed at the interruption. You aren\u2019t likelier to engage with the brand. Instead, the whole thing probably leaves a bad taste in your mouth. <\/p>\n\n\n\n

Even Google\u2019s own best practices warn against invasive notification prompts.<\/p>\n\n\n\n

\u201cThe worst thing you can do is to show the permission dialog to users as soon as they land on your site,\u201d writes Google WebFundamentals contributor Matt Gaunt<\/a>.\u00a0 \u201cThey have zero context on why they are being asked for permission, they may not even know what your website is for, what it does or what it offers. <\/p>\n\n\n\n

Blocking permissions at this point out of frustration is not uncommon, this pop-up is getting in the way of what they are trying to do.\u201d\u00a0Instead of trying to force push notifications down your audiences\u2019 collective throats immediately, focus on taking a more passive approach. <\/p>\n\n\n\n

Consider why <\/em>someone might be interested in receiving notifications and provide your audience with gentle prompts at key points through their conversion journey. For instance, let\u2019s say you publish a weekly thought leadership column.\u00a0<\/p>\n\n\n\n

At the end of each article <\/h2>\n\n\n\n

You might include a small text box providing readers with the opportunity to be notified whenever a new piece is live. The people who are interested in receiving push notifications will sign up, and you\u2019ll know which of your users are most engaged. And the people who aren\u2019t interested?\u00a0<\/p>\n\n\n\n

They weren\u2019t going to sign up in the first place.<\/p>\n\n\n\n

You also need to understand that not every business has something to gain from web-based push notifications, and not every website should use them. If you run an eCommerce site, an online publication, or a user-driven community, they may be worth considering. Otherwise, your development efforts are best focused elsewhere. <\/p>\n\n\n\n

Push notification prompts as they most commonly appear are no better than the popup ads of old. They\u2019re frustrating, intrusive, and provide very little value. If your website must <\/em>use push notifications, focus on making them contextually relevant.<\/p>\n\n\n\n

Otherwise, you\u2019re just wasting your time. 
<\/p>\n","protected":false},"excerpt":{"rendered":"

In January, Google announced that version 80 of Chrome, which launched in early February, would start blocking website push notifications. For users who consistently block these notifications, blocking will be enabled by default. Blocking will also be enabled on websites with low opt-in rates. We estimate that most websites have low opt-in rates.  The problem […]<\/p>\n","protected":false},"author":2,"featured_media":4527,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":[],"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[1],"tags":[],"class_list":["post-2347","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.aseohosting.com\/blog\/wp-json\/wp\/v2\/posts\/2347","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.aseohosting.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.aseohosting.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.aseohosting.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.aseohosting.com\/blog\/wp-json\/wp\/v2\/comments?post=2347"}],"version-history":[{"count":2,"href":"https:\/\/www.aseohosting.com\/blog\/wp-json\/wp\/v2\/posts\/2347\/revisions"}],"predecessor-version":[{"id":4528,"href":"https:\/\/www.aseohosting.com\/blog\/wp-json\/wp\/v2\/posts\/2347\/revisions\/4528"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.aseohosting.com\/blog\/wp-json\/wp\/v2\/media\/4527"}],"wp:attachment":[{"href":"https:\/\/www.aseohosting.com\/blog\/wp-json\/wp\/v2\/media?parent=2347"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.aseohosting.com\/blog\/wp-json\/wp\/v2\/categories?post=2347"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.aseohosting.com\/blog\/wp-json\/wp\/v2\/tags?post=2347"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}