You will need a server (or service) in the middle. Remember that Hexo just generate static site and there is no "action" beyond HTML transfer from the server where you host your site. That being said, one alternative you can try is to design a deployment plugin for hexo that actually send a message through a push service API. That would be simple to accomplish and your readers only have to subscribe to that push service (ie. Google Cloud Message, NMA, etc). Other option: AWS SNS can be used to implement a push service and/or/mixed email/sms messaging. You will have to setup a queue, push to it on hexo deploy, and design a interface that can subscribe your readers to a list of recipients. I never used it as push service but I do use it to notify me after a success/failure hexo generate on travis-ci. This is paid option and I know there are other suppliers already prepared as push service, you just need use their API. IFTTT integration: Use your RSS feed on a IFTTT applet to trigger a push notification through one of the available services (like notify my droid, etc). Other idea: Telegram Channel and a ChatBot (switch Telegram for: skype, facebook messenger, slack or other way a "chatBot" can push messages to). I use this to be notified by my homeTheather system when a new episode of my favorite TV Show is available. To accomplish this I wrote a microservice that receive a HTTP request and send it as message to me (or family group chat in my case) through a Telegram ChatBot. Telegram offers a thing called Channel, it is like a whatzapp group chat but only Channel owner can write message while all other members can just receive that message. (very similar to a Push notification). The microservice I wrote is way too simple written (badly) in NodeJS, runs for free on Hook.io but could be run on AWS Lambda or Google Cloud Function, App Engine, Heroku or any other, few modifications needed. Based on the microservice idea above and a mix of push service or IFTTT I think it should be pretty simple to have a deploy plugin for hexo where the deploy action is a simple API call or a HTTP request to specified URL and PUSH messages would be sent way. The worst part, IMHO, would be to elect a push service free for the subscribers (your reader) and with no need to install apps (many would no use if they have to install a new app just because of you).