Website

Requested Features Ideally, the tool would include: SEO Title & Meta Description: Ability to create and edit custom SEO titles and meta descriptions for every page. SEO Content Analysis: Real-time feedback on keyword usage, content optimization, readability, and on-page SEO best practices. Focus Keyphrase: Ability to assign primary focus keywords to individual pages and receive optimization recommendations. XML Sitemap Management: Automatic sitemap generation and updates when pages are created, edited, or removed. Canonical URLs: Ability to set custom canonical URLs to prevent duplicate content issues. Robots Meta Controls: Options to set pages as index/noindex and follow/nofollow. Open Graph & Social Metadata: Custom social sharing titles, descriptions, and images. Schema Markup: Built-in support for structured data, including LocalBusiness, Organization, Service, Article, and FAQ schema. Redirect Management: Ability to create and manage 301 redirects when URLs change. SEO Recommendations: Suggestions for improving page content, image alt text, internal linking, and other important ranking factors. Why This Would Be Valuable Many agencies use GoHighLevel as their primary website-building and marketing platform. However, the lack of a comprehensive SEO management solution makes it more difficult to compete with platforms that offer dedicated SEO tools. Integrating Yoast SEO or developing a similar native solution would: Improve the overall SEO capabilities of GoHighLevel websites. Reduce the need for third-party tools and manual workarounds. Help agencies deliver more complete SEO services to their clients. Make GoHighLevel a stronger alternative to WordPress for businesses prioritizing organic search visibility. Provide a more centralized website management experience for agencies and their clients. Ultimately, having Yoast-like SEO functionality built directly into GoHighLevel would be a significant improvement for agencies managing multiple client websites and focused on organic search growth.

Creating a password protected page, enabling only certain people to view the information HIGHLVL-I-3588

I would like to use trigger links as hyperlinks in the body of my sites and funnels.

when you open Layers it goes over the page so you can't see the page behind it. open it so the page is next to it rather than on top of it. as it appears over the page you can't see what layer you are selecting. Ask AI appears on the side. make it like that.

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

I created a personalized Santa letters and depending on the product choose I need to collect certain information.

A previous request titled “Chat widget accessibility” was marked Completed, and the alt text on the avatar image was indeed added — thank you. However, two accessibility issues remain in the widget that weren’t covered by that fix. Widget content sits outside landmark regions. The avatar image and the prompt text (“Hi there, have a question? Text us here.”) are not contained within any defined landmark region. Screen reader users who navigate by landmarks cannot reach the widget at all. Wrapping the widget in a region with an appropriate role and accessible name would resolve this. SVG elements inside the widget are missing accessible names. Two SVGs in the widget’s shadow DOM have no <title> child element and no aria-label, so assistive technology announces them as unlabelled graphics. The other 33 SVGs on our own site are all correctly labelled — these two are the only failures, and they’re inside the widget. Because the widget renders in a closed shadow DOM, neither issue can be fixed from the site side. We confirmed this with HighLevel support today, who advised submitting it here. We run two client sites using the widget and both fail the same two checks in every accessibility audit. This affects every HighLevel client using the chat widget, not just us.

Choice to Storage and processing of data exclusively in the EU

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.

if this issue happened again, can ghl send the emel or any notification so that we can calm the clients down. it happen quite few times this month and clients were mad.