Website

I would love to see some effects in the website and funnel builder. Does not have to be anything serious but simple effects. See image for an example. This will make it easier to add some cool effects to the website without heavy coding.

Because HL is missing 301/302 redirects, migrating websites into HL is impossible in some cases because we can't forward old URLs to new URLs. (For example, if the previous site had the .html or .htm extension on all URLs, HL drops this and, thus, the old URL path needs to be forwarded to the version without .html). For optimal indexing, websites also absolutely must have a sitemap. Further, what website doesn't have the ability to add blog posts? The website module is still very limited at this point. HIGHLVL-I-1757

It would be ideal if we could drag and drop website pages created in the website section to re-order them. Sometimes pages are created out of order, and it would be ideal to re-order as needed.

I would like to suggest adding a native language switcher option for websites and funnels inside GoHighLevel.

Currently, columns within section in a website/funnel always stack vertically when viewed on a mobile phone. This is a severe limitation on our ability to design mobile-first websites and funnels. For example, there is currently no way to create a section containing a grid of objects, that show as a grid on mobile phones using the High Level website/funnel builder. It can be done in desktop view, but in mobile they always stack vertically.

Currently unable to add them for domains managed by AI Studio

There were schema changes that need to be updated within HL: Physician has been split into two subtypes: IndividualPhysician and PhysiciansOffice IndividualPhysician is under MedicalOrganization PhysiciansOffice is under MedicalBusiness --------------------------------------- See Info Below Changes to Physician Type in Schema.org v24 Therefore, Schema.org made a few changes to the Physician type in v24 to provide users with greater clarity in their categorization. Redefined the Physician type The Physician type is now defined as ‘an individual physician or a physician’s office considered as a MedicalOrganization’. Removed Physician as a subtype of LocalBusiness The Physician type is now exclusively a subtype of MedicalOrganization. Added usNPI property to the Physician type The Physician type now also includes the usNPI (National Provider Identifier) property, a unique 10-digit identification number issued to healthcare providers in the United States by the Centers for Medicare and Medicaid Services. Introduced two new Physician subtypes: IndividualPhysician and PhysiciansOffice Schema.org added IndividualPhysician and PhysiciansOffice as subtypes of Physician to disambiguate between these two interpretations of the Physician type. Note: Schema.org version 26.0 later went on to restore PhysiciansOffice as a subtype of MedicalBusiness, after accidentally omitting it from the v24 update. You can read more about it in this GitHub ticket. Added occupationalCategory property to the Physician type The occupationalCategory property is used to describe a job, preferably using a term from a taxonomy such as BLS O*NET-SOC, ISCO-08 or similar. This means you can specify whether a Physician (or its subtypes) has a specific occupational category like obstetrics or pediatrics. Added new practicesAt property to the IndividualPhysician subtype We will expand on this more in the section below. But before that, let’s learn more about the two new Physician subtypes and how to use them. Using the IndividualPhysician Subtype The IndividualPhysician subtype should be used to describe an entity that is an individual medical practitioner. The IndividualPhysician subtype still has properties available for things like: address hospitalAffiliation availableService However, it also has the new ‘practicesAt’ property, which is unavailable to either Physician or PhysiciansOffice. The practicesAt property should be used to indicate the MedicalOrganization (i.e. hospital, clinic, pharmacies, etc.) where this individual physician practices. If you have the MedicalOrganization entity defined on a different page of your site, you can connect both entities using this property. Using the PhysiciansOffice Subtype The PhysiciansOffice subtype should be used to describe an entity that is a doctor’s office or clinic. It has the exact same properties as the Physician type, so you can still associate the PhysiciansOffice with a location using the address and hospitalAffiliation properties.

We need a status or incident page to show when GHL is having platform wide outages or issues of specific features. For example a page like github has -- https://www.githubstatus.com/ When the pages aren't loading or the CRM is loading really slow we're always guessing if the platform is broken or if we broke something in our own templates/custom agency javascript.

📢 Introduction Video Sales Letters (VSLs) are one of the most powerful tools for capturing and converting leads, but their success depends on how they are presented and how well they retain the audience's attention. To boost engagement and conversion rates, I propose developing an Advanced VSL Player directly within Go High Level. This new player would include intelligent features designed to enhance retention, optimize engagement, and increase conversion rates—eliminating the need for external tools. 🔥 Key Features of the Proposed VSL Player ✅ 🎯 Dynamic Progress Bar Moves faster at the beginning to create the illusion of a shorter video. Gradually slows down to encourage viewers to watch until the end. ✅ 🔊 Auto-Play on Mute The video autoplays without sound, following modern browser policies. A click-to-enable sound prompt appears to engage users. When clicked, the video restarts from the beginning, ensuring full attention. ✅ 🖼️ Custom Thumbnails Display attention-grabbing preview images before playback. Easily set up directly in the GHL page editor. ✅ 📌 Timed CTA Buttons Call-to-action buttons appear at strategic moments in the video. Automatically synced with key timestamps, directing users to checkout pages or the next step in the funnel. ✅ ⏳ Resume Playback Feature If users leave the page, the player remembers their exact position and resumes from there when they return. ✅ 📊 Built-in A/B Testing Allows testing of two different VSL versions to find the best-performing one. Detailed analytics on completion rates and CTA clicks. ✅ 💡 Reinforcement Messages (Mini Hooks) Small pop-up messages within the video highlight key benefits or address objections. Fully customizable in the GHL page editor. ✅ 📈 Advanced Analytics Detailed reports on watch time, CTA clicks, and completion rates. Seamless integration with GHL’s dashboard for centralized data tracking. 🎯 Key Benefits ✔️ Higher Retention → Users perceive the video as shorter, keeping them engaged longer. ✔️ Increased Conversions → Timed CTAs and reinforcement messages drive action. ✔️ Better User Experience → A sleek, optimized design builds trust and engagement. ✔️ Native Integration → Fully managed within Go High Level, removing reliance on third-party tools. 🚀 Implementation in Go High Level 💻 VSL Block in Page Builder → Add a pre-configured, customizable video component. 📊 Native Analytics Integration → View engagement metrics within the GHL dashboard. 🛠️ Custom Script Compatibility → For configuring dynamic progress bars, CTA pop-ups, and other interactive elements. 📌 Conclusion An Advanced VSL Player in Go High Level would significantly improve retention, engagement, and conversion rates, making GHL the top platform for video-based funnels. 📢 What do you think, GHL team? I’m happy to collaborate on the design and initial testing! 🚀 🔗 Demo of a VSL player in action: https://vturb.com/en 🎯 If you’d love to see this feature in GHL, support this proposal with your vote and let’s make it happen! 💡�

HighLevel needs a better way to support third-party cookie compliance platforms that require their scripts to load synchronously and directly in the HTML. Right now, because HL websites render scripts through JS injection in the header, some compliance tools do not function correctly. This creates a serious problem for anyone trying to meet privacy and consent requirements. The issue: When a visitor opts out of tracking cookies, those cookies may still load anyway because the compliance script is not being executed early enough to block them. Our cookie compliance widget provider explained it like this: “The scripts are required to load synchronously, directly embedded in the HTML (without async, defer, or JS injection). The JS injection from NextJS makes the scripts load parallel with other scripts. In order to block scripts, it needs to load in synchronously before other scripts.” So even if a business is trying to be compliant, the current rendering method can prevent the compliance script from doing its job. Why this matters: This is not just a technical inconvenience. It creates a real compliance and legal liability risk for agencies and businesses using HighLevel websites. Request / suggested solution: Please give us a way to place certain scripts so they are: embedded directly in the HTML loaded synchronously executed before other tracking or marketing scripts Even a dedicated option for compliance-critical scripts would help. Why third-party tools are still needed: The native HL cookie consent feature is not currently a viable replacement for many of us, at least until it can: -automatically scan and identify cookies/scripts in use -automatically generate a cookie policy -keep that policy updated as cookies are added, removed, or changed Until then, many users need to rely on specialized third-party compliance platforms, and HighLevel should support them properly. Bottom line: If cookie blocking depends on synchronous pre-load behavior, HL should provide a supported method for these scripts to load correctly. This is essential for privacy compliance and risk reduction.