Blog

Blog read time is stuck at "3 minute Read" for all of them. More accurate read time would nice.

Blogs are so complicated to create, and specially to make them look good. We are in the AI Era. creating a blog should be very dynamic and easy. All elements should be responsive to mobile and desktop

Problem Summary: In the Blog Home and Blog Post page editors, the Navigation Menu Builder does not support linking to Website Pages—only Funnel Steps or external URLs—causing critical navigation issues. Where the Problem Occurs: Blog Home Page Editor Blog Post Page Editor What Happens Now: When editing a top navigation menu (even a universal section), the “Go To” option only allows selecting: - Funnel Steps - External URLs - Popups There is no option to link to Website Pages. As a result, if you use a universal navigation menu in blog pages, all links pointing to Website Pages break. What Should Happen Instead: Menu Builder should support Website Pages in addition to Funnel Steps and external URLs—especially on blog pages, which naturally belong within websites, not funnels. Ideally, both Funnel Steps and Website Pages should be selectable. Real-World Use Case: Agencies and businesses often use universal menus across their site and blog. If those menus link to Website Pages, they completely break inside the Blog Home or Post pages, confusing visitors and breaking user flow. Current Workaround: The only workaround is duplicating the universal menu for blog pages and manually setting full URLs for each menu item. This is time-consuming and difficult to maintain—especially for agencies managing multiple sites. Suggested Fix or Enhancement: Allow the Menu Builder in Blog Home and Blog Post editors to access and link to Website Pages, just like in the Website Page editor. Ideally, support Funnel Steps and Website Pages to give full flexibility.

Texts like "3 min read", "more..." and "back to blog" should be editable or add a feature to change language.

I see we can add schema to the blog site - but what about blog posts? This is VITAL with Google's Ask engine philosophy

Instead of having the blogs show up with a very plain and basic Image > Title > Content layout, it would be nice to be able to custom design a layout that blogs will use. This way, we can add other sections, forms, ads, promotions, etc.

Currently all the blog post URLS are www.website.com/post/post-name . There is currently no way to change the word "post". We can change the website and the post name but becuase we can't change the middle word, we lose all SEO from previous URLs that we were using on previous platforms.

I’m requesting GoHighLevel add support for structured data (JSON-LD) at the individual blog post level. Currently, we can only inject tracking code at the global blog level, and any <script> tags added inside blog content (via Custom Code blocks) are either stripped or blocked from rendering. This prevents Google from detecting BlogPosting schema, which is essential for: Rich results (author name, publish date, preview image, etc.) Boosting SEO and click-through rates Meeting Google’s best practices for modern content Competitive advantage in real estate and other content-heavy niches What would solve this: A Head Tracking Code field per blog post Support for schema variables (like Liquid) for dynamic rendering Or, allowance for script tags in post content when labeled as safe Blog SEO is a major part of my lead-gen strategy. This feature would massively help professionals across industries.

Hey HighLevel Team, First off, I’ve got to say that I love how powerful the platform has become overall. But I’m honestly surprised that the blogging experience still feels extremely limited, especially compared to the rest of the system. Right now, the blog pages don’t allow any customization for headers, footers, side columns, or global sections, which makes the blog feel disconnected from the rest of the website. For a platform as advanced as HighLevel, this limitation makes the blog experience feel outdated, even less flexible than Blogger.com back in 2004. The current setup forces every blog post to look isolated, breaking brand consistency and user experience. For businesses trying to use their blog to build authority, this is a major drawback. Here’s what would make a huge difference: Allow the use of global header and footer sections within blog posts and blog lists. Allow the use of custom fields and Custom Values inside blog posts for dynamic, personalized content. Provide layout options or blog templates that match the site theme (so design stays consistent). Enable custom sections (hero, author box, related posts, etc.) so blogs feel part of the brand. Optional: Add SEO and Open Graph customization fields directly inside the blog editor. Adding even some of these features would make the blog experience 10x better and truly aligned with the professional standard of the rest of HighLevel. Thanks for taking this into consideration. It’s a small (big :) ) improvement that would make a huge difference for agencies building branded, content-driven websites on HighLevel. Best, Daniel Vargas @DanielVargasMKT