クリエイティブな才能を開花させよう

We do a lot of site migrations from WordPress and other CMS' to HubSpot, and as we know WordPress always has the trailing slash and other CMS's have it, and in order to not hurt any SEO we need the ability to keep this. When you do a blog import HubSpot removes the trailing slash then we manually have to do go through and add the slash and when they have over 100 blogs it is very time consuming.   It would be great if there was just a global control to have this turn on if we need. ...その他を表示

We have several blogs with posts in multiple languages. We would love to import all the posts and associate them together with an ID so they can automatically be added to a multi-language group. This includes the importing of tags and authors in the correct multi-language groups. We have 5 blogs and 3500 posts between them all. Manually associating posts to a multi-language group is impossible and now we are forced to build an API-based application to create the posts.  ...その他を表示

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! ...その他を表示

Right now, deleted blog posts land in an internal “trash,” but it’s only accessible via the (legacy) Blog Posts V2 API or through HubSpot Support. That’s error-prone, slow, and an unnecessary hurdle for many teams.   Proposal: Add a native recycle-bin experience directly in the HubSpot backend for blog posts—modeled after WordPress (aligns with the most widely used CMS—familiar UX and lower learning curve for most teams): Soft delete instead of permanent delete: “Move to Trash” sends the post to a separate area; it’s no longer live. One-click restore: “Restore” brings the post back with all metadata (title, content, tags, authors, SEO fields, URL slug, featured image, comments) to its previous state (published/draft when possible; otherwise draft). Permanent delete: “Delete permanently” removes the post irreversibly. Retention window: Auto-purge after X days (e.g., 30), ideally account-configurable. List & search: Dedicated Trash view with filters (author, blog, date, status), search, and bulk actions (restore/delete multiple). Permissions & audit: Only authorized users can restore/delete; all actions logged in audit history. API parity (optional): Modern endpoints/webhooks for restore/delete events to support automation. Benefits: Prevents data loss and accidental deletions. Reduces support tickets and reliance on a legacy API. Meets user expectations. If you’d find this helpful, please upvote. Happy to add real-world use cases or acceptance criteria from practice. ...その他を表示

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.  ...その他を表示

You should be able to list multiple authors on a blog! ...その他を表示

When inserting an anchor link within the rich text field in web/landing pages, or the blog's editor, please provide some extra parameters in its Advanced dialog:   Classes - A text field that lets you type in multiple classes. E.g. Typing class1 class2 would output as: class="class1 class2" ID - A text field that lets you type a unique ID. E.g. Typing id1 would output as: id="id1" Title - A text field that lets you type in tooltip text. E.g. Typing External link would output as: title="External link"   ...その他を表示

I would love the ability to bulk add, edit, or remove tags from blogs. Especially helpful during blog redesigns or restructuring your blog to be more search-friendly. Currently, you have to individually go into every post to edit a tag.  ...その他を表示

Could you please add the option to add a job title to a blog author. Or better yet, make this an object that we can create custom properties for.   https://knowledge.hubspot.com/blog/create-and-manage-your-blog-authors ...その他を表示