If you haven't used HubSpot's SEO tool or Google PageSpeed Insights you're missing out on some critical recommendations to make your website faster and more accessible in search engines. Most of the recommendations are technical so they will need to be done by a skilled developer but there are some content recommendations that can be done by someone familiar with the HubSpot page editor.
I had a mentor a few years ago who said something that really stuck with me. He said, "all money flows through forms". This was so simple and so obvious that I didn't understand the implications at first. Instead of looking at forms as static elements on par with other page elements, this statement implies that forms are THE most important element. Of course, the content goes hand in hand with forms - if you don't have the content people want they won't be using your forms - but the ideal user flow culminates in some sort of form submission. Below, I outline three design concepts to elevate your form design and improve form submission rates.
When we approach projects that require custom modules (hint: most projects do), we consider the end users AND the content editors. We not only have to build a module that correctly displays the content to the end user, we also have to consider how our module displays to content editors in the page editor.
As dedicated HubSpot developers, one of our main goals is to produce the best possible content editing experience, not just for us as we're building out the site, but for whoever comes along in the future to edit content.
When you're finally done with development and the launch date is just around the corner, it's always a good idea to do a final review before going live.
Invest some time in the review but don't overthink it - a few hours should be sufficient.
The obvious review process will split responsibilities between the frontend and the backend and depending on the scope of the project, it might be a good idea to expand on these categories to ensure a thorough review.
Take yourself back to high school. Your parents are out of town so of course you're going to invite some friends over. Maybe you'll have some pizza and watch Adam Sandler movies (the ones from the 90s when he actually cared about being funny).
When I first started out, I created the same HubSpot module over and over again because I didn't structure it in a way that would make it easily portable between portals. Lesson learned.
Ah, yes, the age-old dilemma of plain text field vs. rich text field. A question almost as important as "paper or plastic" but without the environmental implications.If you've ever built out templates or created custom modules in HubSpot you've undoubtedly come across this issue.
Ultimately, this decision relies heavily on the end user's desired involvement. If they're more "hands off", the best solution might be a plain text field. If the end user wants more control and flexibility, a rich text field is the obvious choice. This is where it pays off to do a little planning before development.
Consider the end user's preference when choosing text fields.
Of course, there are obvious downsides to using rich text fields. Inline styling is not considered "best practice" and generally avoided outside development.
Also, if the end user isn't familiar with a rich text editor they may need training and the chances of them disrupting the design layout greatly increase.
