Great minds think alike

You should be able to list multiple authors on a blog! ...read more

Multi languages features like Landing pages & website have. I think it's essential to have a blog in multiple languages. ...read more

As all of you might know the current blog post is just a simple rich-text which is fine for general posting. But many of our customers want a flexible solution. Like multi-column grids with different content-types like images, text, accordions/toogles ...    The only way to achive this right now is a custom module with all possible content types and pre-defined layouts and a repeater function.    It would be awesome if the blog post would get the drag&drop functionality so that every customer/user could design each blog post to his needs.  ...read more

Hello product team,   For HubSpot admins, one of the biggest challenges is keeping a portal organized, cleaned up and prevent overall chaos. Especially in Enterprise portals with sometimes hundreds of users, it's almost impossible to get users to follow a naming convention for email names, landing page names, workflow names. Quickly this becomes a cat and mouse game where HubSpot have to constantly chase and remind users to name their assets correctly.   Why is this currently a bad user experience for users?   Naming conventions are usually documented outside of HubSpot, in a wiki, stored as a Google Doc or something similar along the same lines. Forcing them to interrupt what they're currently doing, look up a naming convention and then come back means that they're losing time. They also have to leave HubSpot momentarily. Even then, they might misunderstand the naming convention and type in an incorrect name.   Why is this currently a bad user experience for admins?   Incorrect naming means that list or workflow filters for Recent conversion might not work. It can also mean that reports become a mess, if these reports are pulling in asset names.   If admins have to look into this on a permanent basis, in portals where there are new assets every day, this takes time away from developing the HubSpot portal and generating more value for all users.   Here's what a solution could look like   To solve this, it would be great if there were tools to enforce a naming convention. Ideally, admins would specify what constitutes a correctly named asset and similar to the forms editor, arrange fields to their liking.   Here's a quick mockup of what this could look like when creating a new page.     The user could select from dropdowns which team they belong to, the language of the assets, the asset type, include a title and date. The system would then generate a title from this that cannot be further edited.   Admins should be able to specify the options for each dropdown, separators, order and field validation (e.g. max length for a title).   (In case this is eventually introduced, please consider to make this a feature that is at least included in all Professional and Enterprise subscriptions.)   I would love to see this for all assets in HubSpot: emails, workflows, lists, campaigns, imports, properties, files etc.   Thanks in advance for reviewing! ...read more

My idea is to grant users the ability to set-up "structured data" on blog posts to help with SEO.   Structured data is a system of pairing a name with a value that helps search engines categorize and index your content. Microdata is one form of structured data that works with HTML5. Schema.org is a project that provides a particular set of agreed-upon definitions for microdata tags.   Structured data seems to matter more often now with search engines and help boost SEO.  ...read more

Currently, whatever the page or blog post title is, the title tag <title> is the same. This is extremely limiting. A great strategy I use to increase CTR is to use different words and even brackets. However, I don't want these in my post title. Instead, I would like to be able to have a longer, more explanatory title on the site.    When a person arrives on a blog post, it is important to have the title to explain what they are getting. However, you can't always do that in 600 pixels Arial font 16px, which is what Google use for title in the listing. A succesful strategy that I have been using for a few years now is using bracket and other simples to increase CTR and having the title longer. Having a longer title also helps you to incorporate a secondary keyword phrase, which is another successful SEO strategy I use.  With the use of Yoast plugin, WordPress sites have had this ability for almost ever, but HubSpot's CRM pigeon holes you into only having a title that fits in Google's search titles.  ...read more

Our company has one blog that covers a wide variety of topics and targets multiple audiences. Would love for our readers to be able to subscribe by topic, not just post frequency, to ensure they're only getting emails when content is posted that is directly relevant to them. ...read more

I would recommend having a built-in search and replace function. So you can search through all your blog posts and replace a certain word or phrase. For example, we renamed our company and now I have to go through all our blog posts, find every instance of our old name and replace it with our new name. A search and replace function would probably save me the 5+ hours I need to spend on this.   I've used WordPress plugins that have this feature and it can be quite helpful and save a lot of time.   Thank you for your consideration. ...read more

Currently you can only edit the blog listing head and the blog posts head shared for all posts. It would be nice to be able to go into a post and edit that individual posts head information.    1 example use would be to edit the social meta tags if you would like to preset an image that doesn't match the featured image or social descriptions that don't match the meta description.   There are numerous other specific situations where editing an individual posts head information would be necessary. The functionality could mimic that already used for website pages since you can edit each website page individually. ...read more