Website

HighLevel currently injects every Google Font family and weight ever chosen in the account into every page, forcing browsers to download large, unused files and hurting Core Web Vitals. Please add a per-page font audit so only the families and weights actually referenced in the final CSS are loaded (or let us toggle fonts on/off per page). This will slash render-blocking requests and make green Lighthouse scores achievable without custom hacks.

Please fix testimonials Scroll bars it should be hidden, we also need Auto Carousel with Vertical Masonry with blur bg support just like framer with Scroll animation preset controls

Need the GHL team to have a look at this !! ;) Hi guys ! I looked on different websites created with ghl and ALL OF THEM have this loading time between a font (which we don't want) and the font we choose (in the site builder). I don't see this on any other CMS (wordpress, webflow, wix,...). The websites created by them are all smooth and do not have any fonts to load. (or don't take time to load so we don't see it) The problem ? 1) The font takes 2/3/4 seconds to load every time we open a new page of the website. 2) Sometimes (it depends on the browser and the place from which the website is opened... Google, safari, google maps, firefox,...), and most of the time on mobile view (which is most important), the font loads perfectly on the first page but when we open another page it does not load at all and we therefore end up with a site which has a completely different font. We need to refresh the page for the font to load (which website visitors don't do). (see video) IN SUMMARY, the font takes a few seconds to download or simply does not download. which ruins the user experience on the beautiful website we are able to create on ghl ;) EDIT: I think I found where the problem comes from. This is a FONTAWESOME link called "fa-brands-400.woff2" and "fa-solid-900.woff2". (see screenshot) I don't know if they are necessary for websites. but why doesn't the ghl team just remove this font (link) on all the website? It will be much smoother to have only 1 font loading than to have a first font and then the second one loading...

I always get the "Error creating page" message anytime I hit the save or publish buttons. It's annoying since you have to recreate all the changes you last saved and GHL doesn't save it. The autosave feature also does this and makes this message appear every 5-10 seconds for me. Not sure if this is a user error on my end or something more technical.

For websites, you can create a header with menu buttons that takes the visitor to a specified section on the current page. This is particularly helpful for single page websites. The problem is that if you have a sticky header, when you click the button and are taken to the section, the section will be hidden behind the sticky header. It creates for a bad/ugly user experience. Please fix this bug. If you have a sticky header, and use menu buttons to go to sections, the section you're brought to should be below the sticky header so the top of the section is visible and not cut off.

Im receiving a ton of spam or irrelevant traffic. Is there a way to block regions or countries? If not there needs to be one. I converted my website over from wp to GHL because of the automation ease. But the amount of spam i receive has me wanting to go back ASAP.

YouTube and TikTok handle URLs have @ in them and GHL isn't allowing it, with this error: Invalid Url! Please enter the url in right format

HighLevel’s Reviews widget outputs AggregateRating structured data on website pages, but the markup is missing required fields, causing Google’s Rich Results Test to flag a critical issue: “Either ratingCount or reviewCount should be specified.” Where the problem occurs Websites (Website Builder) → Pages using the Reviews widget (Structured data / Rich Snippets output in the page source) What happens now When a page includes the Reviews widget, HighLevel injects Review/AggregateRating schema in the page code. Google’s Rich Results Test flags the AggregateRating as invalid/critical because neither ratingCount nor reviewCount is included, even though ratingValue is present (ex: 5.00). Result: pages get structured data warnings that can reduce eligibility or trust for review rich results, and it creates confusion for agencies trying to deliver “SEO-clean” sites. What should happen instead HighLevel should output valid AggregateRating structured data by including at least one of the required properties: ratingCount or reviewCount …and ensure the output aligns with Schema.org + Google’s structured data expectations. Real-world use case We build client sites in HighLevel and often add the Reviews widget to service pages/homepages for social proof. When we run QA using Google Rich Results Test or Search Console, we see a critical structured data issue on pages that otherwise pass. This creates: extra client support + explanations (“why is Google saying this is broken?”) potential reduced SEO performance/eligibility for review enhancements additional dev time to troubleshoot something generated by the platform Current workaround (if any) Avoid using the Reviews widget on SEO-critical pages, or Use a custom-coded schema injection (manual JSON-LD) and attempt to suppress/ignore the widget’s output (not always clean/easy), or Accept the error and ship anyway (not ideal for agencies and SEO deliverables) Suggested fix or enhancement Option A (Best): Update the Reviews widget schema generator to always include: reviewCount (total number of reviews displayed/available) and/or ratingCount (total rating count) …and ensure the values are accurate. Option B: If accurate counts are not available in some cases, provide a setting/toggle: “Enable Review Schema” (on/off) so users can disable invalid schema rather than being forced into a critical error. Option C: Output the schema as JSON-LD in a single, clean block (if not already), ensuring required properties are present for AggregateRating.

I'm not sure if this is a bug or just overlooked. When the button alignment is clicked, it aligns both the button itself and the text inside the button. If you click left justify, then both the button and the text inside the button justifies left. We need separate alignment options.