Website

When building pages with the AI Website Builder in GoHighLevel, each section is automatically assigned a random ID such as: #section-V53-VJtx-P These IDs are used when linking navigation items (About, Services, Contact) to sections on the same page. This is not just a cosmetic issue. When building websites for clients, random anchors like this appear in URLs and navigation links, which looks unprofessional and undermines the quality of client-facing websites. The issue is that these section IDs cannot be edited, which removes an important level of control when building landing pages or one-page websites. For agencies, clean and readable anchors are important for maintainability and professionalism. Instead of random IDs, developers should be able to define simple section IDs like: about services contact This would automatically create clean anchors such as #about or #services for navigation. Allowing editable section IDs in the AI Website Builder would significantly improve the ability to build professional one-page websites and landing pages.

I am reporting what appears to be a HighLevel infrastructure/Page Builder failure affecting a white-label location. Both independent users are affected, multiple browsers and Incognito reproduce it, including brand-new pages, and the console shows LeadConnector 403 responses and Firebase permission failures. Location ID: Nd3Llqdv1jsAo8DGEfd4 Failure: Page Builder blank screen Affected users: at least 2 Affected browsers: Chrome, Chrome Incognito, Opera Affected pages: existing AND newly created pages Console: FirebaseError: Missing or insufficient permissions plus repeated 403 Forbidden from backend.leadconnectorhq.com and services.leadconnectorhq.com

Quick description (copy-paste): HighLevel’s built-in reCAPTCHA is served with a site key registered to a generic HighLevel domain, not to the custom domain the page is actually on. Browsers log “ERROR: domain mismatch for site-key”; Lighthouse and security scanners flag it. Functionality still works, but the warning clutters audits and undermines trust. Why it matters Clean console → easier debugging and higher perceived quality. Stops false-positive warnings in SEO / security tools. Allows strict Content-Security-Policy setups (no wildcard domains). Requested fix Domain-aware provisioning – when a custom domain is connected, automatically register that domain to the default reCAPTCHA key. Custom key option – add fields in Site Settings → Security to paste our own reCAPTCHA v2/v3 keys (or hCaptcha key) per workspace. Toggle off – let power users disable the built-in reCAPTCHA and embed their own script if they prefer. One update removes the console noise, keeps security teams happy, and gives agencies full control over CAPTCHA branding.

I have noticed when connecting google drive to the media library, the search is only user lever - it doesnt allow to check shared drives, so if the required folder isn't under the solo person, it's impossible to navgigate to that perdsons shared folded (which oif course is where the needed files work).

there's a bug in the website builder: when I enable the cookie banner, save and publish, it actually doesn't save it.

Currently, when a visitor accesses a non-existent URL, GoHighLevel performs: 301 Redirect → /error-404 /error-404 returns 200 OK This causes SEO tools such as Screaming Frog, Ahrefs and Semrush to report Soft 404 pages because the server never returns a real HTTP 404 status. The expected behavior should be: Non-existent URL → HTTP 404 Display the user's custom 404 page No redirect required This is the standard behavior expected by search engines and improves SEO, crawl efficiency, and error reporting in Google Search Console. Benefits: Eliminates Soft 404 warnings. Better compliance with Google's SEO recommendations. More accurate crawling and indexing. Consistent behavior with other CMS platforms (WordPress, Webflow, Shopify, etc.). Use case: A custom-designed 404 page should be displayed while the server responds with HTTP 404 Not Found, not 301 → 200 OK. Suggested implementation: Allow custom 404 pages to return the correct HTTP status code (404) instead of redirecting to a normal page that returns 200. This could be a simple toggle in Website Settings or the default behavior for all custom 404 pages.

When i turn off website permission, the client still sees the "sites" menu on the left and the webchat is accessible above and editable. Both should be not shown when this is turned off.

Please make the websites and funnels responsive to maintain the integrity of each word in the text. Go to just about any other website or funnel on the market and change the size of the window and the text will adjust by word so the text stays coherent. In GHL when you size the window displaying a website/funnel it drops the text down letter by letter, making the site look very amature and unprofessional.

Transferring a website from Manus to GHL I don't understand why we can't simply transfer HTML and CSS into GHL. There should be a simple process for this. I had to go to Manus to create the site because I was having so much trouble with GHL.

I keep experiencing several issues with the margins and padding of sections. Bug 1: Inconsistencies between the website builder and external preview. For example, see the difference in the spacing between the website builder (Picture 1) versus when I preview the website (Picture 2). Both on the same screen, same window size. I have checked the padding and margins of every single element inside these containers and they are all set to zero. This is not the first time this has happened either. Bug 2: Sometimes my rows randomly align to the left instead of center, and no matter what I do, I cannot get them to re-center. Again, all the padding and margins are set to zero. I end up having to add a new row and move all the contents into it and just pray it doesn't happen again. Bug 3: After adjusting the padding/margins of an element, when I go to click on another element, it changes the padding of that element too. I have to click out of the Settings column on the right before clicking on a different element every single time, it's incredibly frustrating.