Cookie consent for Pro: Your blog can ask before it tracks
Consent management is live for Pro publications with a custom domain. Turn it on and your blog asks before loading analytics and marketing scripts. It works on blogs Hashnode renders. If you run headless with your own frontend, the banner doesn't apply there.
The reason is GDPR. Privacy laws in the EU, the UK, and elsewhere require consent before trackers load. Until now, your blog loaded them anyway.
Everything happens on your publication's Integrations page, and setup takes a minute. Open it, tick the box, add your privacy policy URL, and save.
That's the entire setup. New visitors now get a banner before any optional script loads, and until they answer it, nothing runs:
Readers who want more control than accept or reject can customize. The choice splits into analytics and marketing, so someone can say yes to readership stats and no to ad tools. Essential storage isn't listed at all, the site doesn't work without it.
Choices live in the reader's browser, scoped to your publication. Change your privacy policy or the setting itself and returning visitors see the banner again. If someone withdraws consent later, the trackers shut off and their cookies get cleaned up on the next page load.