As many of you may know, WordPress is my go-to website builder. Clients often ask me to integrate or embed features I am not familiar with. Today, a client sent me a link from Beehiiv and asked me to add it as a Subscribe button in the main navigation of her WordPress website.
At first glance, that sounds simple enough.
But when I clicked the link, it asked me to log in or create a Beehiiv account. That told me right away that this was not the public subscription link. It was an internal Beehiiv Website Builder link.
That matters because visitors to client website.com should not need a Beehiiv account to subscribe to a newsletter.
After logging into the client’s Beehiiv account, I saw that clients-newsletter.beehiiv.com already had subscription forms on the public Beehiiv page. Those forms work there, but they are part of the Beehiiv-hosted website. They are not the same as an embeddable subscribe form for the WordPress site.
So the solution was to clarify the options to the client:
- The Subscribe button in the WordPress navigation can link directly to the public Beehiiv newsletter page.
- Or, if the client wants the subscription form to appear directly on clientwebsite.com, she needs to create an external subscription form in Beehiiv and send me the embed code.
This is one of the things I enjoy about website work. I do not need to be an expert in every platform my clients use, but I do need to understand how to ask the right questions, test the link, and make sure the visitor experience is clear.
A small detail like using the wrong link can create unnecessary friction for the audience.
The goal is always simple: make it easy for people to take the next step.
Leave a Reply