Follow up on the latest improvements and updates.

RSS

October 12, 2026

new

Funnels and Websites

SEO

Schema management at Website/Funnel level

We’re launching a Schema markup dashboard at the website and funnel level, under the new SEO & AEO tab. User no longer need to open each page in the builder to check or fix its schema. From one screen, user can:
See overall schema health
. The Schema coverage card rates your site as Needs work, Getting there, Good, or Excellent, with counts for Up to date, Might be outdated, and No schema.
Check every page at a glance
. Each page shows its schema types, its status (Up to date / Might be outdated / No schema / Unpublished / Unsaved), and when it was last updated.
Generate schema with AI, one page or many
. Select pages and click Generate schema. Progress shows live, and results appear for your review before anything goes live.
Add or edit schema manually
. Click + Add schema for pages with none, or click any schema tag to open the editor.
Review, then publish
. Generated or edited schema stays Unsaved until you click Save and publish. You can also Discard it.
Find what needs fixing
. Search by page name or path, and filter by schema status.
Spot stale schema
. Pages edited and republished 2 or more times since their schema was created are flagged Might be outdated.
Why this matters?
Accurate, current schema makes your pages eligible for Google rich results and helps AI answer engines understand and cite your business. Until now, keeping schema current meant going through the builder one page at a time, so most sites fell out of date. This dashboard turns that into a quick check you can act on in bulk.
Impact on existing users
No data loss and no action required.
Every website and funnel now has an SEO & AEO tab. Any existing schema appears there automatically.
Pages without schema are flagged No schema, so user can fix them in bulk.
Schema editing in the page builder still works exactly as before. Both places stay in sync.
Running Generate schema on a page that already has schema replaces it entirely. Review before Save and publish click.
How to use
Go to Sites → Websites/Funnels → select one → SEO & AEO.
Check the Schema coverage card, and filter by No schema or Might be outdated.
Select pages and click Generate schema, or use + Add schema / click a tag to edit manually.
Review the results, then click Save and publish.
Sample screens
Screen 1: SEO & AEO - Schema home screen 1
Screen 2: SEO & AEO - Schema home screen 2
Screen 3: SEO & AEO - Select page For Schema generation
Screen 4: SEO & AEO - Schema generation progress
Screen 5: SEO & AEO - Schema generated using AI
Screen 6: SEO & AEO - Schema edit

October 12, 2026

improved

Funnels and Websites

Meta Pixel: Improved InitiateCheckout Accuracy & Enhanced AddPaymentInfo Data

InitiateCheckout now fires when a buyer

reaches checkout page

, not when they submit payment. AddPaymentInfo now also sends full order and customer details to Meta. Together, these changes give you an accurate picture of checkout drop-off and give Meta better signals to optimise your campaigns.

This applies to funnels, websites and stores that have the Meta Pixel set up with the InitiateCheckout event enabled.

🆕

What's New

Smarter InitiateCheckout timing
: The event now fires at the moment the buyer starts checking out:

When the page loads on store checkout pages.
When the page loads on any page where you added InitiateCheckout at the page level.
On the buyer's first click, tap or keystroke in an order form everywhere else. This covers one-step, two-step and popup order forms, plus the new order form.

Page-level control:
Adding InitiateCheckout at the page level makes it fire as soon as that page loads. Adding it at the funnel, website or webinar level makes it fire on the buyer's first interaction with the order form.
Protection against duplicates and false triggers
: InitiateCheckout fires at most once per page visit, even when a page has several order forms or more than one trigger is configured. Browser autofill, password managers and fields that are focused automatically on load don't trigger it.
Abandoned-cart recovery support:
When a buyer comes back through an abandoned-cart link, the event waits for their saved cart to load, so it includes the cart value and products.
Express wallet coverage:
Buyers who go straight to Apple Pay etc without touching the form are still counted. For them, InitiateCheckout fires when payment starts.
Richer AddPaymentInfo data
: AddPaymentInfo now includes order value, currency, product IDs, and hashed customer details (email, phone, name, external ID) when they're available.

💡

Why It Matters

See real checkout drop-off:
InitiateCheckout and AddPaymentInfo used to count the same buyers, so the step between "started checkout" and "entered payment" showed nothing. You can now see how many buyers reach checkout but leave before paying.
Better ad optimisation
: Meta can now optimise and build audiences around buyers who show checkout intent, including those who don't complete the purchase.
Higher Event Match Quality
: Full order and customer details on AddPaymentInfo help Meta match more events to real people, which improves attribution and targeting.
Consistent, trustworthy data:
Every event now reports the same currency for an order, and invalid or blank values are never sent to Meta.

✨

What Stays the Same

Setup:
Your Meta Pixel settings work exactly as before. No reconfiguration is needed.
Other events: PageView, ViewContent and Purchase fire at the same moments as before.
Consent:
Events still respect your cookie-consent settings. If a visitor hasn't accepted advertising cookies, nothing is sent.
Conversions API:
When the Conversions API is enabled, browser and server events are still sent together and deduplicated in Meta Events Manager.
Free orders:
If an order requires no payment details at all, AddPaymentInfo is not sent, same as before. New: orders fully covered by a gift card now send it (with a value of 0).
Pixels without InitiateCheckout:
If InitiateCheckout isn't enabled on your pixel, nothing changes.

✨

What to Expect

InitiateCheckout counts will go up.
This is expected: the event now includes buyers who reach checkout and leave without paying. The gap between InitiateCheckout and AddPaymentInfo/Purchase now shows real checkout drop-off. Keep this in mind when you compare reports, automated rules or cost-per-InitiateCheckout before and after this release.
Page-level settings may take up to 24 hours to take effect on already-published pages
. To apply them immediately, edit and save the page.
No change to consent or Conversions API behavior.
Events still respect your cookie-consent settings. When the Conversions API is enabled, browser and server events are still sent together and deduplicated in Events Manager.
No action required
. The update applies automatically.

October 12, 2026

new

Phone System

📢 Voice Pricing Updates - Effective October 13, 2026

Overview
The previously announced Voice pricing updates scheduled to take effect on October 13, 2026 will no longer be implemented.
Underlying providers have confirmed the cancellation of these changes. As a result, the affected Voice rates will remain unchanged.
You can view the original announcement here: Voice Pricing Updates - Effective October 13, 2026
No action is required for now.
We’re sharing this update to ensure you have the latest pricing information and avoid any confusion ahead of the previously communicated effective date.

October 12, 2026

new

Introducing New Templates

We are thrilled to announce our new web templates, designed to elevate your marketing efforts. Whether building a website, creating a sales funnel, or sending email campaigns, our versatile and user-friendly templates have you covered. Fully customizable and professional, they streamline your workflow, saving you time and letting you focus on engaging your audience and driving results.
List of New Templates
------------------------------------------------------
🚀 21New Website Templates Published
  🚀
------------------------------------------------------
Legal - 1
------------------------------------------------------
🚀 1 New Funnel Templates Published
  🚀
------------------------------------------------------
Automotive - 1
------------------------------------------------------
🚀 1 New Email Templates Published
  🚀
------------------------------------------------------
Restaurant & Bar - 1
-----------------------------------------------------
🚀 1 New Survey Templates Published
  🚀
-----------------------------------------------------
Business, Coaching & Consulting - 1
-----------------------------------------------------
🚀 8 New Social Templates Published
  🚀
-----------------------------------------------------
Marketing Agency - 2
Creative - 2
Business Coaching and Consulting - 2
Financial. -2
-----------------------------------------------------
🚀 2 New Facebook Ad Templates Published
  🚀
-----------------------------------------------------
Creative - Interior Designer
Real Estate - Realtor
-----------------------------------------------------
🚀 5 New Google Ad Templates Published
  🚀
-----------------------------------------------------
Other - Medical Research
Medical - Dental Clinic
Marketing Agency - Digital Marketing Services
Legal - Mediation Services
Insurance - Life Insurance
-----------------------------------------------------
🚀 6 New LinkedIn Ad Templates Published
  🚀
-----------------------------------------------------
Real Estate - Real Estate Appraiser
Real Estate - Escrow Officer
Marketing Agency - AI Marketing Implementation Specialist
Marketing Agency - Conversion Rate Optimization
Business Coaching & Consulting - Diversity, Equality & Inclusion Consultant
Creative - Interior Architecture Firm
------------------------------------------------------
📣 1 New Snapshot
 📣
------------------------------------------------------
Finance - Bookkeeper

October 10, 2026

new

Contacts

Introducing snapshot and public API support for new custom field types

Overview
We're excited to announce that snapshot and public API support
 is now available for all our recently launched custom field types (URL, Date & Time, Rich text, Users field, Image support in Radio and Checkbox fields - https://highlevel.canny.io/changelog/introducing-new-custom-fields)
With these enhancements, you can now seamlessly replicate custom field configurations across sub-accounts using snapshots and manage custom field data programmatically through public APIs.
Whether you're setting up multiple sub-accounts, building integrations, or automating processes, these additions make it easier to manage, reuse, and scale your custom fields across HighLevel.
What's new?
1. Snapshot support for new custom field types
 - You can now include the newly introduced custom field types in your snapshots, eliminating the need to manually recreate field configurations across sub-accounts.
Why it matters:
 Save time, maintain consistency, and simplify sub-account setup by reusing custom field configurations through snapshots.
2. Public API support for new custom field types
 - We've also extended our public APIs to support all the newly introduced custom field types, allowing developers to work with these fields programmatically.
https://marketplace.gohighlevel.com/docs/ghl/locations/create-custom-field/
Why it matters: 
Build more flexible integrations, synchronize custom field data with external applications, and automate processes without relying solely on manual updates.
Availability
: Both snapshot and public API support are now live in production and available to all accounts. If you've already enabled the new custom field types through Labs,
 you can start taking advantage of these enhancements without any additional activation.
With snapshot and public API support now available, we're making custom fields more powerful, reusable, and easier to integrate into your everyday business processes.

October 9, 2026

new

Studió AI

AI Studio Cloud: A Built-In Backend for Your Apps

☁️ Your AI Studio apps can now have a real backend

You've built a great app in AI Studio, and now it needs to remember things. It needs to know who's signed in and store the photos people upload. Until now, that meant wiring up a backend yourself.

Not anymore.

Open

More → Cloud

and turn it on from

Overview

. In about a minute, HighLevel creates a private backend just for that project, with a

database

user accounts

, and

file storage

. There's nothing extra to connect.

You can keep building while it sets up.
If setup stops, your app is untouched, and
Try again
picks up where it left off.
AI Studio checks with you before it builds anything against Cloud.

🌟

Once Cloud is running, here's what you get:

🗃️ Database: your app's memory

See every table, roughly how many rows it holds, and whether row-level security is on.
Open a table to add rows, double-click a cell to edit it, or select rows to delete them.
Need a new table or policy? Just ask AI Studio in chat and it handles the schema.
Slow or costly database?
Optimize
sends a health check to chat. It uses credits, like any message.
Daily Backups
snapshot your schema and rows (not storage files or app code).
Restore
replaces the live database with a snapshot. The app pauses its database access for a few minutes while that happens. If the schema no longer matches your code, ask chat to patch it.

👥 Users: the people using your app

Watch signups on a chart and search people by email.
Create new user
adds someone already confirmed, with no email sent.
Send invitation
emails them a link to set a password.
Open a person to see how they sign in, or
Delete user
. Deleting can't be undone.
Signup, invite, and reset emails go out through your account's email, and the links open your app.

Auth settings

lets you shape sign-in:

Email confirmation is required by default.
Auto-confirm email
is for testing only.
Close registration any time with
Allow new sign-ups
. Existing users stay signed in.
Reject passwords found in public breaches, and set your own password rules.
Set your
Site URL
and
Redirect URLs
. A mismatch here is the usual reason a login fails. Preview URLs are handled for you, and you can add your own, including mobile links like
myapp://callback
.

⚠️

Heads up for v1:

sign-in supports email and password only. We'll expand to more sign-in methods in future releases.

📁 Storage: where files live

Buckets
hold uploads. Public buckets open for anyone with the link. Private ones are for signed-in users.
Names use lowercase letters, numbers, and hyphens (3 to 63 characters) and can't be changed later.
Upload, organize into folders, download, delete, rename, and
Copy URL
. Renaming a file changes its URL.
Set an
Upload size limit
and review who can read and write through RLS policies.

📈 Advanced settings: grow at your pace

Database size
starts at
Tiny (free)
. Move up to Mini, Small, Medium, Large, or X-Large, or back down, once an hour. Each size shows its hourly price. A change takes a few minutes and briefly restarts the app.
Database storage
can grow, never shrink, up to 4 times a day. You pay hourly for the space you set aside, even when paused.
File storage
grows and shrinks with your files, and you pay for what's actually stored.
Pause
stops access to your data while keeping it safe.
Resume
wakes it.
If your wallet can't cover Cloud, it pauses itself. Nothing is deleted, and
Wake up
returns once billing is fixed. You can still move down to Tiny.
Remove Cloud
permanently deletes that project's database, users, and files. Export tables as CSV and download files first. Other projects aren't affected.

🛡️ A friendly watchdog

If the security advisor spots a problem, a card appears on

Overview

View issues

lists them, and

Try to fix

asks AI Studio to repair them.

Fix
critical
issues before you publish.
Warnings
are worth a look but aren't urgent.

✅ Good to know

Cloud works with apps built on
TanStack Start
. For an existing React project, go to
Project Settings → Migrate to SSR
first. That creates an upgraded copy and leaves your original live. Migrating doesn't turn Cloud on.
Your published site stays as is until you publish again.
Sharing or remixing doesn't copy your Cloud data. The copy can still send requests to the original project's Cloud, following its access rules.

October 8, 2026

new

Studió AI

AI Studio: Sell Products and Accept Payments

You can now take payments in apps built with AI Studio. Connect the products in your catalog, ask the agent to “add payments”, and your app gets a secure, hosted checkout.

Payments in AI Studio uses HighLevel’s native payments. Your products, orders, payment providers and subscriptions are the ones already set up in your HighLevel account. There’s nothing extra to set up.

What’s new

Payments in a few clicks

More → Payments
is a new settings tab. Turn Payments on, switch between test and live mode, and choose which catalog products your app can sell.
Choose how each product is priced: one fixed price, a selected set of variations (sizes, tiers, plans), or the product’s full catalog.
Only the products and prices you allow can be shown or charged. Your settings decide what buyers can buy.

The agent adds the checkout for you

Ask the agent to add payments. It shows a card asking you to approve the connection, then builds a storefront and checkout into your app.
The payment code is managed by the platform, so neither you nor the agent can break it by accident. Edits to it are restored on the next turn.

A hosted checkout

Card details are entered and processed in the platform’s hosted checkout, never in your app’s code.
PayPal express checkout is supported.
Coupon codes can be entered at checkout, and a fully discounted order goes through without asking for a card.
Subscriptions work in checkout and upsells, including carts with more than one subscription product.
Your colours: the checkout picks up your site’s colour scheme instead of a fixed default.
Bot protection runs on every purchase.

One-click post-purchase upsells

After a successful purchase you can show buyers an offer page. They can accept it with one click, without entering card details again.
One-click works with saved cards from Stripe (3D Secure supported), Square, Authorize.net, NMI, Adyen and Mercado Pago. Other payment methods use the regular payment form.
An upsell can only be charged after the original order is paid, and only once per order, even with several tabs open.

Product pages

Generated storefronts show product listings and detail pages from your catalog, with thumbnails and formatted descriptions.

Availability

Payments currently works only with apps built on TanStack Start. Other project types won’t see the option yet.
To use Payments in an existing React project, migrate it. Go to
Project Settings → Migrate to SSR
. This makes an upgraded copy of your project and leaves the original unchanged and live. You can also test the new copy before you publish it.

October 8, 2026

new

Improved Rejection Guidance for A2P Campaigns

We’ve rewritten the guidance in the “View required fixes” modal so it matches how you registered your campaign.

What’s new:

Guidance for your setup: the most common rejection reasons now have separate guidance for campaigns set up through the Chat Widget (Quick Setup) and through Manual Setup, since the fix is in a different place for each.
Only steps you can act on: if you registered through the Chat Widget, the guidance focuses on what you control, like your website, other forms on your site and your policy links. It no longer asks you to change the consent wording or form fields the widget creates for you.
Clearer next steps: each reason explains in plain language what happened, then lists the specific actions to take.
Exact wording where carriers require it: for reasons like privacy policy verification, the steps include the required statement.
Notice when resubmitting won’t help: for reasons like a business type mismatch, we’ll tell you what needs to change first.

Examples of the updated Chat Widget guidance:

Previously:

The modal showed the carrier’s generic guidance, written for every registration method. Chat Widget users were often asked to fix fields or consent wording they never wrote.

Why it matters:

Guidance that matches your setup helps you fix the right thing the first time and resubmit with confidence, without waiting on support.

October 8, 2026

new

Studió AI

AI Studio - Analytics & Submissions for your sites

Every published AI Studio site now measures itself. See page views, opt-ins and opt-in rate right inside your project, compare all your sites in Sites Analytics, and follow every lead from first visit to CRM contact. No setup or tracking code needed.
📈 Analytics inside your project
Your project → More → Analytics → Overview
See page views, unique visitors, opt-ins and opt-in rate, with trends and the change from the previous period. Dig into top pages, time on page, traffic sources, devices, browsers, and countries, regions and cities.
📝 Every form submission in one place
Your project → More → Analytics → Form Submissions
Every lead your site's forms collected, with a link to the contact. Filter by form and date, or create a workflow right from there.
🗂️ All your sites in Sites Analytics
Sites → Analytics → AI Studio
See every AI Studio site next to your Funnels and Websites, or pick one project to focus on it.
🧭 Know where every lead came from
Contacts → Contact details → Activity
Contacts created from your site keep their visit history: the pages they viewed, where they came from, and the form they submitted.
🔗 Reconnect forms to see each visitor's full path
Opt-ins from forms you connected before today keep counting. To link a submission to the pages that visitor viewed first, ask AI Studio to reconnect form tracking, then publish again.

October 8, 2026

new

Social Planner

Social Planner: Community Posting via Public API

Community posting just became more powerful for developers and integration partners.

You can now schedule and publish Community posts through the Social Planner Public API, including choosing which Community member the post should be published as.

This makes it easier for marketplace apps and custom integrations to bring Community publishing into their own workflows.

What's new

List Community Members

Integration partners can now retrieve eligible Community members who can publish posts.

Search members by name
Paginate through member lists
Only active, permitted members are returned
Private Communities return only members of that specific group

Validate Member Eligibility

Before scheduling a post, integrations can verify whether a selected member is still active and authorized to publish in the Community.

Publish as a Specific Member

When creating a Community post through the API, integrations can specify which eligible member the post should be published as.

Publish-Time Verification

Social Planner performs a final eligibility check before publishing. If the selected member has left the Community or lost permission, the post won't be published under the wrong identity.

Instead, the post fails with a clear and actionable error.

How it works

Connect a Community group in Marketing → Social Planner → Settings → Social Accounts
Use Get Accounts to retrieve the Community account ID
Use Get Community Members to retrieve eligible members
Select the member you want to publish as
Create the post using the Community post API
Optionally validate the member before scheduling
Social Planner verifies the member again before publishing

Why it matters

Enable Community publishing through marketplace apps and custom integrations
Automate Community announcements from external workflows
Ensure posts are always published by an eligible member
Catch invalid member selections before publishing
Get clear error messages instead of silent publishing failures
Bring Community posting closer to API parity with other social channels

Notes

Community account connection and management remain available in the HighLevel UI.
The Public API supports member listing, member validation, scheduling, and publishing.
Draft posts don't require a postAsUser selection.
Member eligibility is checked when posts are scheduled or published.
The selected member must remain active and permitted in the Community at publish time.
API access requires the appropriate Social Planner scopes.

Marketplace API link - https://marketplace.gohighlevel.com/docs/ghl/social-planner/get-community-users/

→